Page 1 of 2 12 LastLast
Results 1 to 15 of 19

Thread: Domain controller not found

  1. #1
    Jim Guest

    Domain controller not found

    From an XP pro system, all the latest updates installed, the system event
    log records a netlogon error:

    "No Domain Controller is available for domain SIENA due to the following:
    There are currently no logon servers available to service the logon request.
    .. "

    Yet, I can access the DC's shares and certainly ping it. But, it takes
    several minutes to get a functional desktop upon startup. Also, I can get
    sudden denial of access errors out of the blue and lose connection,
    apparently. Then I get "log in as" boxes popping up which do not accept
    even my domain admin login. Also, my system has taken to a 20 second delay
    to come back when it's "locked". It used to come up instantly. Finally,
    accessing files on the file server/DC is very sluggish. I have to wait a few
    seconds for explorer to refresh itself everytime I click on a file, change a
    name, click on a folder, etc. It's maddening.

    I have a fairly fresh install of SBS2003 and there are no apps installed on
    the server. It shows no errors in its event log. My local net stats are (the
    server has the 192.168.1.10 address):

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : ignatius
    Primary Dns Suffix . . . . . . . : Siena.local
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : Siena.local
    Siena

    Ethernet adapter PCI Card:

    Connection-specific DNS Suffix . : Siena
    Description . . . . . . . . . . . : Lite-On Communications
    Compatable PCI Fast Ethernet Adapter
    Physical Address. . . . . . . . . : 00-C0-F0-2D-BA-43
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 192.168.1.102
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.4
    DHCP Server . . . . . . . . . . . : 192.168.1.4
    DNS Servers . . . . . . . . . . . : 198.168.1.10
    192.168.1.4
    Lease Obtained. . . . . . . . . . : Friday, October 19, 2007 8:50:09
    AM
    Lease Expires . . . . . . . . . . : Monday, October 22, 2007 8:50:09
    AM

    Thanks for any help.
    Jim



  2. #2
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    Did you run dcdiag and netdiag on the DC? Also post an ipconfig /all from
    the DC/DNS server.

  3. #3
    Join Date
    Sep 2005
    Posts
    8

    Re: Domain controller not found

    dcdiag complains only of the fact that the time service is stopped and not
    advertising.
    As for netdiag, there are these two problems only:

  4. #4
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    What is the 192.168.0.1 for a machine? It is a different network address
    and can cause your problems.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.

    > 192.168.0.1
    >




  5. #5
    Jim Guest

    Re: Domain controller not found

    That is a DSL modem, on the other side of the gateway, which is supposed to
    forward to an external DNS if 192.168.1.10 is unable to fulfill the request.
    What is the ideal setting for the secondary DNS? What would this have to do
    with finding the DC?


    "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    news:ff16fb6662eaf8c9e0cb6d3afa70@msnews.microsoft.com...
    > Hello Jim,
    >
    > What is the 192.168.0.1 for a machine? It is a different network address
    > and can cause your problems.
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and
    > confers no rights.
    >
    >> 192.168.0.1
    >>

    >
    >





  6. #6
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    You have to configure a forwarder to your ISP's DNS server on the DNS server
    properties in the DNS management console. Here you find a tab called "Forwarders".
    If it is greyed out inside just remove the .zone in DNS, close the DNS console
    and reopen it. Then you can add the ISP's DNS server, not your router ip
    address. It should be an external internet ip address.
    So all internal request from the machines go to your inside DNS server, if
    that can't provide the information it will forward the request to the ISP's
    DNS server and get theire the answer.
    Remove the modem ip address and your internal errors should go away. But
    you also be aible to browse the internet.

  7. #7
    Join Date
    Sep 2005
    Posts
    8

    Re: Domain controller not found

    Well, the external DNS is already set up in the forwarders tab. I rechecked
    the IP's, and they are what the DSL modem is using.

    Another symptom: now my XP machine is taking 30 to 60 seconds just to open
    programs. But, when I'm off the net, they come right up, as does the
    desktop.

  8. #8
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    Is the first problem solved? Other wise lets go on with that. Did you remove
    the entry from DNS settings?

  9. #9
    Join Date
    Sep 2005
    Posts
    8
    Thanks for getting back to me!

    The modem IP was not in the forwarders list. Only two DNS's that belong to
    QWest.

    The 192.168.0.1 ip was in the network card TCP/IP properties as the
    secondary DNS. I changed that to 192.168.1.4 which is the gateway. Unless I
    should just leave it blank.

    Here are the startup errors now on the XP workstation, which takes, again,
    about 5 minutes to get a functional desktop:

    Windows cannot determine the user or computer name. (The specified domain
    either does not exist or could not be contacted. ). Group Policy processing
    aborted.

    Automatic certificate enrollment for local system failed to contact the
    active directory (0x8007054b). The specified domain either does not exist
    or could not be contacted.

    The PrintQueue Container could not be found because the DNS Domain name
    could not be retrieved. Error: 54b

    Okay, I have only the DC given out as a DNS. But, I am getting the same
    error messages on startup.

    But, with the DHCP server giving out only the DC as the DNS, my browser
    cannot resolve DNS requests. So either the DNS on the server is not
    forwarding or something.

  10. #10
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    Coming back to the ip settings. Your workstations and server works with ip's
    like 192.168.1.4 192.168.1.10 192.168.1.102

    The router (Default gateway) ip 192.168.0.1

    And you specify also 192.168.1.4 as a default gateway. Can you give some
    more info about the network setup please. You can not work with two default
    gateways in one network that have different ip ranges.

  11. #11
    Join Date
    Sep 2005
    Posts
    8

    Re: Domain controller not found

    1.4 is the only default gateway/router. It's WAN port is hooked up to the
    DSL modem and it gets it's external IP and DNS info from the modem. But all
    that should be transparent to the office network, and it has worked fine for
    quite some time. It just seems that the DNS and/or Active Directory services
    have been slowly degrading.

    Again, the forwarders on the DC's DNS properties are the external ones QWest
    uses for the DSL connection.

  12. #12
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    So the 192.168.0.1 is not longer used on any server or workstation?

  13. #13
    Join Date
    Sep 2005
    Posts
    8

    Re: Domain controller not found

    No, the gateway/router is the only device that "knows" that IP.

  14. #14
    Meinolf Weber Guest

    Re: Domain controller not found

    Hello Jim,

    Sorry for asking again about the 192.168.0.1 Did you use it anywhere in the
    network? You said the router is x.x.1.4 and now you say the gateway "knows"?
    the address. This address has nothing to do with your network.

  15. #15
    Jim Guest

    Re: Domain controller not found

    The WAN port on the gateway has an IP of 192.168.0.4. All internet traffic
    from the 192.168.1.x subnet goes through the gateway, which sends it to the
    DSL modem on the 192.168.0.x subnet. Technically, the gateway is really
    acting as a bridge, and the DSL modem is the "real" gateway.

    "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    news:ff16fb666488a8c9e4965ff5e860@msnews.microsoft.com...
    > Hello Jim,
    >
    > Sorry for asking again about the 192.168.0.1 Did you use it anywhere in
    > the network? You said the router is x.x.1.4 and now you say the gateway
    > "knows"? the address. This address has nothing to do with your network.
    >
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and
    > confers no rights.
    >
    >> No, the gateway/router is the only device that "knows" that IP.
    >>
    >> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    >> news:ff16fb666457d8c9e42b3e1ce408@msnews.microsoft.com...
    >>
    >>> Hello Jim,
    >>>
    >>> So the 192.168.0.1 is not longer used on any server or workstation?
    >>>
    >>> Best regards
    >>>
    >>> Meinolf Weber
    >>> Disclaimer: This posting is provided "AS IS" with no warranties, and
    >>> confers no rights.
    >>>> 1.4 is the only default gateway/router. It's WAN port is hooked up
    >>>> to the DSL modem and it gets it's external IP and DNS info from the
    >>>> modem. But all that should be transparent to the office network, and
    >>>> it has worked fine for quite some time. It just seems that the DNS
    >>>> and/or Active Directory services have been slowly degrading.
    >>>>
    >>>> Again, the forwarders on the DC's DNS properties are the external
    >>>> ones QWest uses for the DSL connection.
    >>>>
    >>>> Thanks again,
    >>>> Jim
    >>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    >>>> news:ff16fb66643908c9e3dcc1fc19e0@msnews.microsoft.com...
    >>>>> Hello Jim,
    >>>>>
    >>>>> Coming back to the ip settings. Your workstations and server works
    >>>>> with ip's like 192.168.1.4 192.168.1.10 192.168.1.102
    >>>>>
    >>>>> The router (Default gateway) ip 192.168.0.1
    >>>>>
    >>>>> And you specify also 192.168.1.4 as a default gateway. Can you give
    >>>>> some more info about the network setup please. You can not work
    >>>>> with two default gateways in one network that have different ip
    >>>>> ranges.
    >>>>>
    >>>>> Best regards
    >>>>>
    >>>>> Meinolf Weber
    >>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
    >>>>> and
    >>>>> confers no rights.
    >>>>>> Okay, I have only the DC given out as a DNS. But, I am getting the
    >>>>>> same error messages on startup.
    >>>>>>
    >>>>>> But, with the DHCP server giving out only the DC as the DNS, my
    >>>>>> browser cannot resolve DNS requests. So either the DNS on the
    >>>>>> server is not forwarding or something.
    >>>>>>
    >>>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    >>>>>> news:ff16fb66640c68c9e3a0c62b7c4f@msnews.microsoft.com...
    >>>>>>
    >>>>>>> Hello Jim,
    >>>>>>>
    >>>>>>> see inline
    >>>>>>>
    >>>>>>> Best regards
    >>>>>>>
    >>>>>>> Meinolf Weber
    >>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
    >>>>>>> and
    >>>>>>> confers no rights.
    >>>>>>>> Thanks for getting back to me!
    >>>>>>>>
    >>>>>>>> The modem IP was not in the forwarders list. Only two DNS's that
    >>>>>>>> belong to QWest.
    >>>>>>>>
    >>>>>>>> The 192.168.0.1 ip was in the network card TCP/IP properties as
    >>>>>>>> the secondary DNS. I changed that to 192.168.1.4 which is the
    >>>>>>>> gateway. Unless I should just leave it blank
    >>>>>>>>
    >>>>>>> The NIC should only point to your INTERNAL DNS server, that's
    >>>>>>> all.
    >>>>>>>
    >>>>>>>> Here are the startup errors now on the XP workstation, which
    >>>>>>>> takes, again, about 5 minutes to get a functional desktop:
    >>>>>>>>
    >>>>>>>> Windows cannot determine the user or computer name. (The
    >>>>>>>> specified domain either does not exist or could not be
    >>>>>>>> contacted. ). Group Policy processing aborted.
    >>>>>>>>
    >>>>>>>> Automatic certificate enrollment for local system failed to
    >>>>>>>> contact the active directory (0x8007054b). The specified domain
    >>>>>>>> either does not exist or could not be contacted.
    >>>>>>>>
    >>>>>>>> The PrintQueue Container could not be found because the DNS
    >>>>>>>> Domain name could not be retrieved. Error: 54b
    >>>>>>>>
    >>>>>>> This will depend on the ip address from the router, remove it
    >>>>>>> like i wrote before. DNS settings should only point to the
    >>>>>>> internal DNS. In the moment the computer tries to find the domain
    >>>>>>> also outside your network, what will not work.
    >>>>>>>
    >>>>>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    >>>>>>>> news:ff16fb6663f788c9e360c93c57f0@msnews.microsoft.com...
    >>>>>>>>
    >>>>>>>>> Hello Jim,
    >>>>>>>>>
    >>>>>>>>> Is the first problem solved? Other wise lets go on with that.
    >>>>>>>>> Did you remove the entry from DNS settings?
    >>>>>>>>>
    >>>>>>>>> Best regards
    >>>>>>>>>
    >>>>>>>>> Meinolf Weber
    >>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
    >>>>>>>>> warranties,
    >>>>>>>>> and
    >>>>>>>>> confers no rights.
    >>>>>>>>>> Well, the external DNS is already set up in the forwarders
    >>>>>>>>>> tab. I rechecked the IP's, and they are what the DSL modem is
    >>>>>>>>>> using.
    >>>>>>>>>>
    >>>>>>>>>> Another symptom: now my XP machine is taking 30 to 60 seconds
    >>>>>>>>>> just to open programs. But, when I'm off the net, they come
    >>>>>>>>>> right up, as does the desktop.
    >>>>>>>>>>
    >>>>>>>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    >>>>>>>>>> news:ff16fb6663be58c9e2eddcd97c4c@msnews.microsoft.com...
    >>>>>>>>>>
    >>>>>>>>>>> Hello Jim,
    >>>>>>>>>>>
    >>>>>>>>>>> You have to configure a forwarder to your ISP's DNS server on
    >>>>>>>>>>> the
    >>>>>>>>>>> DNS
    >>>>>>>>>>> server properties in the DNS management console. Here you
    >>>>>>>>>>> find
    >>>>>>>>>>> a
    >>>>>>>>>>> tab
    >>>>>>>>>>> called "Forwarders". If it is greyed out inside just remove
    >>>>>>>>>>> the
    >>>>>>>>>>> .zone
    >>>>>>>>>>> in
    >>>>>>>>>>> DNS, close the DNS console and reopen it. Then you can add
    >>>>>>>>>>> the
    >>>>>>>>>>> ISP's
    >>>>>>>>>>> DNS
    >>>>>>>>>>> server, not your router ip address. It should be an external
    >>>>>>>>>>> internet
    >>>>>>>>>>> ip
    >>>>>>>>>>> address.
    >>>>>>>>>>> So all internal request from the machines go to your inside
    >>>>>>>>>>> DNS
    >>>>>>>>>>> server, if
    >>>>>>>>>>> that can't provide the information it will forward the
    >>>>>>>>>>> request
    >>>>>>>>>>> to
    >>>>>>>>>>> the
    >>>>>>>>>>> ISP's DNS server and get theire the answer.
    >>>>>>>>>>> Remove the modem ip address and your internal errors should
    >>>>>>>>>>> go
    >>>>>>>>>>> away.
    >>>>>>>>>>> But
    >>>>>>>>>>> you also be aible to browse the internet.
    >>>>>>>>>>> Best regards
    >>>>>>>>>>> Meinolf Weber
    >>>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
    >>>>>>>>>>> warranties,
    >>>>>>>>>>> and
    >>>>>>>>>>> confers no rights.
    >>>>>>>>>>>> That is a DSL modem, on the other side of the gateway, which
    >>>>>>>>>>>> is supposed to forward to an external DNS if 192.168.1.10 is
    >>>>>>>>>>>> unable to fulfill the request. What is the ideal setting for
    >>>>>>>>>>>> the secondary DNS? What would this have to do with finding
    >>>>>>>>>>>> the DC?
    >>>>>>>>>>>>
    >>>>>>>>>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
    >>>>>>>>>>>> news:ff16fb6662eaf8c9e0cb6d3afa70@msnews.microsoft.com...
    >>>>>>>>>>>>
    >>>>>>>>>>>>> Hello Jim,
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> What is the 192.168.0.1 for a machine? It is a different
    >>>>>>>>>>>>> network
    >>>>>>>>>>>>> address
    >>>>>>>>>>>>> and can cause your problems.
    >>>>>>>>>>>>> Best regards
    >>>>>>>>>>>>> Meinolf Weber
    >>>>>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
    >>>>>>>>>>>>> warranties,
    >>>>>>>>>>>>> and
    >>>>>>>>>>>>> confers no rights.
    >>>>>>>>>>>>>> 192.168.0.1
    >>>>>>>>>>>>>>

    >
    >




Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 7
    Last Post: 28-12-2010, 09:35 PM
  2. Replies: 4
    Last Post: 15-05-2009, 11:18 AM
  3. Replies: 2
    Last Post: 08-12-2008, 06:33 PM
  4. Replies: 20
    Last Post: 12-07-2008, 08:53 AM
  5. How to promote additional domain controller to domain controller
    By SocialAbility in forum Window 2000 Help
    Replies: 2
    Last Post: 11-04-2007, 08:49 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,638,077,885.01716 seconds with 16 queries