|
|
Question : DHCP problems.
|
|
We've been having intermittent issues with WinXP clients and slow DHCP.
The pattern with regard to which clients are affected seems pretty random. Things can be fine for a couple of days, then a handful of clients will be hit by slow DHCP again- displaying a "Limited or no connectivity" icon for up to 30 seconds.
The disruption to network connectivity at logon affects GPO processing (e.g. logon scripts applied by GPO fail to run), and affected users are required to log off, then back on again to get their network drives etc.
Setting a static IP on affected clients also resolves all problems.
We have: - a 192.168.0.* network. - W2K3 server. DHCP runs on a D.C. - Win XP SP2 clients. - Cisco Catalyst 3500 Switches
The errors in XP client Event logs include: --------------------------------------------------
1) Source: Userenv Event ID: 1054 Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.
2) Source: userinit Event ID: 1000 Description:
Could not execute the following script Logon.vbs. The system cannot find the file specified.
3) Source: DHCP Event ID: 1007 Type: Warning
Description: Your computer has automatically configured the IP address for the Network card with network address XXXXXXXXXXXX. The IP address being used is 169.254.57.55
4) Source: DNSApi EventID: 11191 Type: Warning
Description: The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings:
Adapter Name : {XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} Host Name : XXXX Adapter-specific Domain Suffix : company.local DNS server list : 192.168.0.X, 192.168.0.Y Sent update to server : > IP Address : 192.1.1.1
The system could not remove these PTR RRs because because of a system problem. For specific error code, see the record data displayed below.
5) Source DHCP EventID: 1002 Type: Error
Description:
The IP Address lease 192.168.1.12 for the network card with network address XXXXXXXXXX has been denied by the DHCP server 192.168.0.X (the DHCP server sent a DHCPNACK message).
-------------------------------------------
With 3) above it's weird- the client will display a 192.168.0.* address when I run ipconfig on it- not an APIPA address as indicated.
4) and 5) are also strange given our network is a 192.168.0.*
Any ideas? I'm concerned about possible rogue servers or ICS on the network (some of our users get a bit "creative" occasionally)- but a second opinion / confirmation would be great.
I've already tried the following without any luck: - Applying the "Always wait for the network at computer startup.." GPO setting - Disabling Spanning Tree protocol on the Switches: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q168455
Thanks, Farfo.
|
Answer : DHCP problems.
|
|
By chance do you have a firewall, router, or access point anywhere on the network that is trying to hand out DHCP addresses? Obviously the 192.168.1.x IP range is used very frequently by many types of devices. Perhaps there is another device on the network somewhere beating your server to the punch? Just a thought.
|
|
|
|
|