Some XP clients refuse to see new DHCP server

[MetalFRO]

I have an environment where our main DC (Windows Server 2003 SP2)
died, and that was our DHCP server. In its absence, I set up DHCP
services on the PDC (also W2k3 SP2). Most XP workstations are seeing
the new DHCP services just fine & obtaining addresses, but a handful
of stubborn clients refuse to pick up an address. They are receiving
an event in the System log, ID 5719, source NETLOGON:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: Date
Time: Time
User: N/A
Computer: Server
Description:
No Domain Controller is available for domain <domain name> due to the
following: There are currently no logon servers available to service
the logon request. Make sure that the computer is connected to the
network and try again. If the problem persists, please contact your
domain administrator.

The DC that is now the DHCP server has been promoted successfully (via
Microsoft tech support) to PDC, and the dead server was replaced w/
like hardware & rebuilt to be a new BDC/DNS server. The environment
is different than it was originally, but not so drastically that
clients should be refusing to see/use the new DHCP server. If I set
the problem workstations to a static IP, they communicate fine. I
have attempted to do ipconfig/flushdns and ipconfig/release, then
ipconfig/renew, and that hasn't helped. I also attempted to run the
common "WinsockfixXP" tool that cleans up crapped up networking stacks
& starts fresh, but that hasn't alleviated the problem either.
EventID.net has a number of theories, but none seem to apply in my
situation. Also, KB article 938449 suggest an outdated driver (which
isn't the case) or a registry entry to fix, but that shouldn't be
necessary because they were working fine before the change. Any help
to get me in the right direction would be appreciated.

 

[Daniel Tulen]

I have an environment where our main DC (Windows Server 2003 SP2)
died, and that was our DHCP server. In its absence, I set up DHCP
services on the PDC (also W2k3 SP2). Most XP workstations are seeing
the new DHCP services just fine & obtaining addresses, but a handful
of stubborn clients refuse to pick up an address. They are receiving
an event in the System log, ID 5719, source NETLOGON:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: Date
Time: Time
User: N/A
Computer: Server
Description:
No Domain Controller is available for domain domain name due to the
following: There are currently no logon servers available to service
the logon request. Make sure that the computer is connected to the
network and try again. If the problem persists, please contact your
domain administrator.

The DC that is now the DHCP server has been promoted successfully (via
Microsoft tech support) to PDC, and the dead server was replaced w/
like hardware & rebuilt to be a new BDC/DNS server. The environment
is different than it was originally, but not so drastically that
clients should be refusing to see/use the new DHCP server. If I set
the problem workstations to a static IP, they communicate fine. I
have attempted to do ipconfig/flushdns and ipconfig/release, then
ipconfig/renew, and that hasn't helped. I also attempted to run the
common "WinsockfixXP" tool that cleans up crapped up networking stacks
& starts fresh, but that hasn't alleviated the problem either.
EventID.net has a number of theories, but none seem to apply in my
situation. Also, KB article 938449 suggest an outdated driver (which
isn't the case) or a registry entry to fix, but that shouldn't be
necessary because they were working fine before the change. Any help
to get me in the right direction would be appreciated.

The situation you're describing is a known one in the DHCP. The next
step for these non-functioning DHCP clients is to go the the MS network
169.x.
What you will have to do is the following:
On every affected client do a IPCONFIG /RELEASE
Then reboot the system. Now it will do a DHCP broadcast. Basically this
is the problem. The client keeps unicasting to the former DHCP server
address. This is a bug in the clients DHCP stack.

 

[John Wunderlich]

:

I have an environment where our main DC (Windows Server 2003 SP2)
died, and that was our DHCP server. In its absence, I set up DHCP
services on the PDC (also W2k3 SP2). Most XP workstations are
seeing the new DHCP services just fine & obtaining addresses, but
a handful of stubborn clients refuse to pick up an address. They
are receiving an event in the System log, ID 5719, source
NETLOGON:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: Date
Time: Time
User: N/A
Computer: Server
Description:
No Domain Controller is available for domain <domain name> due to
the following: There are currently no logon servers available to
service the logon request. Make sure that the computer is
connected to the network and try again. If the problem persists,
please contact your domain administrator.

The DC that is now the DHCP server has been promoted successfully
(via Microsoft tech support) to PDC, and the dead server was
replaced w/ like hardware & rebuilt to be a new BDC/DNS server.
The environment is different than it was originally, but not so
drastically that clients should be refusing to see/use the new
DHCP server. If I set the problem workstations to a static IP,
they communicate fine. I have attempted to do ipconfig/flushdns
and ipconfig/release, then ipconfig/renew, and that hasn't helped.
I also attempted to run the common "WinsockfixXP" tool that
cleans up crapped up networking stacks & starts fresh, but that
hasn't alleviated the problem either. EventID.net has a number of
theories, but none seem to apply in my situation. Also, KB
article 938449 suggest an outdated driver (which isn't the case)
or a registry entry to fix, but that shouldn't be necessary
because they were working fine before the change. Any help to get
me in the right direction would be appreciated.

See if this article is of any help:

"A client connected to an Ethernet switch may receive several logon-
related error messages during startup"
<http://support.microsoft.com/kb/202840>

HTH,
John

 

[MetalFRO]

:






See if this article is of any help:

"A client connected to an Ethernet switch may receive several logon-
related error messages during startup"
   <http://support.microsoft.com/kb/202840>

HTH,
  John

Gentlemen, thanks for the suggestions. I figured it out - when I
built the DHCP scope on the secondary DC before & set it up, I
miskeyed the subnet mask, so when I deleted & re-added the new scope
to fix that, I forgot to re-authorize the DHCP server. Once I did
that, problem solved. I had already tried the ipconfig/release &
reboot combo, as well as using the freeware "Winsockfix" tool out
there, but I saw that when I was having another look at it. Thanks!