Clients can't find the domain controller

[JH]

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.

Anyone have an idee what I shold do to get this working..
JH

 

[gingerdazza]

I thoguht they get the DC info from DNS. Check and ensure that the
demoted server is no longer listed as a DC in DNS

 

[gingerdazza]

.....believe it may be listed as a name server/NS record in DNS

 

[JH]

The DC is also the local DNS server (NS record) and the old DC is removed.
Everything looks fine when i run nslookup.
DHPC DNS server options is pointing to local DC as primary and another
DC/DNS as secondary

 

[Ken B]

Have you configured Sites & Services correctly, listing the various sites,
and assigning DC's to them?

Ken

 

[Enkidu]

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

 

[Jorge_de_Almeida_Pinto]

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.WinntdebugUsermodeuserenv.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.

Anyone have an idee what I shold do to get this working..
JH

have you seen:
http://www.eventid.net/display.asp?eventid=1000&eventno=1441&source=Userenv&phase=1

 

[ss161]

have you seen:
http://www.eventid.net/display.asp?eventid=1000&eventno=1441&source=Userenv&phase=1

Run gpresult from the client.
Check whether the Site value contains the correct AD site.

If it does, then go to the DNS (ADIZ) and check the Forward Lookup
Zones/<domain>/_sites/<sitename>/<tcp>. Check whether the old records
are removed and that the current DC record exist.