Re: Clients can't find the domain controller

JH wrote: 
Hi,

I have a W2K domin with 13 DC's at different locations, at one location the W2K clients can't find the local DC. In the application log there are lots of Error messages:

Source:Userenv
Eventid:1000
Description: Windows cannot obtain the domain controller name for your computer network. Return value (59).

There was 2 DC's at that location earlier, but I had to demote one of them and take it away. Where do the clients store data about which DC it should ping contact. I have some feeling that the clients may try to find the demoted DC and not the one up and running...

In the file C.\Winnt\debug\Usermode\userenv.log there are some entries ping failures:

USERENV(bc.c8) 11:13:17:634 EnterCriticalPolicySection: User critical section has been claimed. Handle = 0x63c
USERENV(bc.c8) 11:13:17:634 ProcessGPOs: Machine role is 2.
USERENV(bc.c8) 11:13:17:644 PingComputer: PingBufferSize set as 2048
USERENV(bc.c8) 11:13:17:644 PingComputer: First send has a reply buffer failure of 11002
USERENV(bc.c8) 11:13:23:082 PingComputer: First send 0x358519f failed with 11010
USERENV(bc.c8) 11:13:23:082 PingComputer: First send has a reply buffer failure of 11002
USERENV(bc.c8) 11:13:23:082 PingComputer: No data available
USERENV(bc.c8) 11:13:23:482 PingComputer: PingBufferSize set as 2048
USERENV(bc.c8) 11:13:28:589 PingComputer: First send 0x472519f failed with 11010
USERENV(bc.c8) 11:13:28:589 PingComputer: First send has a reply buffer failure of 11002
USERENV(bc.c8) 11:13:33:597 PingComputer: First send 0x472519f failed with 11010
USERENV(bc.c8) 11:13:33:597 PingComputer: No data available
USERENV(bc.c8) 11:13:33:597 ProcessGPOs: DSGetDCName failed with 59.

It's almost certainly DNS. Clients do not store information about the DCs. When you said in another post that nslookup works fine, what were you looking up? The client must be able to find the SRV records in DNS.

Cheers,

Cliff

--

Barzoomian the Martian - http://barzoomian.blogspot.com
.

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: WINS and DNS issue
    ... Do they have their DNS name configured in the SYSTEM CONTROL ... It may be unnecessary to have the server on "both nets" directly. ... things you need to do (AD Domain, DNS clients servers etc.) ... ANd not if the clients register themselves. ...
    (microsoft.public.win2000.dns)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: WINS and DNS issue
    ... > do have various DNS issues and our event viewer is full on DNS errors ... > and XP clients) ... This number of registrations is no big deal for a WINS server. ... Dynamic for the zone supporting AD ...
    (microsoft.public.win2000.dns)
  • Re: Clients connecting to server
    ... DNS: 192.168.1.64 ... > I also do not know how to set up DHCP on the SBS and have the Clients ... > I get an internet connection on the server, ...
    (microsoft.public.windows.server.sbs)