Windows XP Clients Refuses to Recognized DHCP server

[Ramsey]

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

[Stefan09]

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.

[Marlon]

On a client computer that is connected to an Ethernet switch, you may receive several logon-related error messages during Startup.

In the event log, you may receive the following error message:

No domain controller available

NOTE: The source of this error may be the NetLogon service and how the NetLogon service sets up its secure channel.

Also, if you log on to the console before Startup has completed, you may receive one of the following error messages:

No domain controller was available to validate your logon.

A domain controller for your domain could not be contacted. You have been logged on using cached account information. Changes to your profile since you last logged on may not be available.

You may receive this error message only when you make the initial attempt to log on to the computer. When you make subsequent attempts to log on to the computer, you may not receive this error message.

[Ramsey]

On a client computer that is connected to an Ethernet switch, you may receive several logon-related error messages during Startup.

In the event log, you may receive the following error message:



NOTE: The source of this error may be the NetLogon service and how the NetLogon service sets up its secure channel.

Also, if you log on to the console before Startup has completed, you may receive one of the following error messages:





You may receive this error message only when you make the initial attempt to log on to the computer. When you make subsequent attempts to log on to the computer, you may not receive this error message.

Yup i am Getting this kind of Error .pls Help

[Marlon]

To resolve this behavior, disable the Spanning Tree Algorithm feature of your Ethernet switch.

For information about how to disable the Spanning Tree Algorithm feature on a switch, contact the switch manufacturer.

and also you can workaround Here

Important :This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following Link

Backup registry


To work around this behavior, on the clients add the following parameter to the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

Value Name: ExpectedDialupDelay
Data Type: Reg_Dword
Data Value is in seconds (default = 0)
Data Range is between 0 and 600 seconds (10 minutes)

This workaround forces the NetLogon service to pause for the specified amount of time before the service attempts to establish its secure channel.

[Ramsey]

To resolve this behavior, disable the Spanning Tree Algorithm feature of your Ethernet switch.

For information about how to disable the Spanning Tree Algorithm feature on a switch, contact the switch manufacturer.

and also you can workaround Here

Important :This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following Link

Backup registry


To work around this behavior, on the clients add the following parameter to the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters



This workaround forces the NetLogon service to pause for the specified amount of time before the service attempts to establish its secure channel.

ok Thanks N good But what is the cause of this problem ? thanks in advance

[Marlon]

This behavior can occur because some Ethernet switches have a feature that checks the ports for a loop condition when the ports become active (the Learning mode for the Spanning Tree Algorithm feature). If a loop is found, all traffic is blocked from accessing the port. This process of checking for a loop condition takes approximately 10 to 15 seconds during which the Windows NT Workstation-based computer seems to be on the network, yet no traffic is being passed. The NetLogon service packets (along with any other traffic during that time) are lost.

If you have a hub at the end of the port, the hub has already brought the port up. Your connection is only unsuccessful when your computer is connected directly to the switch