WinXP Pro not getting valid IP from DHCP server

[Marlon Brown]

For whatever reason some XP Pro machines are not getting valid IP addresses
upon logon and GPO's are failing.

I enabled policy "wait for network upon startup on logon" (I thought that
was supposed to make WinXP behaves as Win2000). However that didn't solve
the problem. I startup, logon and I see on eventvwr and experience that no
valid IP address is present.

What else can I do to fix this ?

 

[Michael Johnston [MSFT]]

Is the machine getting an IP address? If not, this is the place to start troubleshooting. What you may try is configuring a static IP
address on this machine. Just make sure it's an available IP address on your subnet. Once you've got the IP address, try
pinging the server by it's IP address. If you have basic connectivity then you can proceed to name resolution. The client should
be pointing to the DNS server that is hosting the zone for the AD domain only. Do not point at any other DNS servers.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Marlon Brown]

When I connect a Win2000 Prof instead on that same ethernet connection, the
whole thing works and I get the IP address immediately.
It really seems that is related to Fast Logon behavior on XP.

Is the machine getting an IP address? If not, this is the place to start

troubleshooting. What you may try is configuring a static IP

address on this machine. Just make sure it's an available IP address on

your subnet. Once you've got the IP address, try

pinging the server by it's IP address. If you have basic connectivity

then you can proceed to name resolution. The client should

be pointing to the DNS server that is hosting the zone for the AD domain

only. Do not point at any other DNS servers.

Thank you,
Mike Johnston
Microsoft Network Support

rights. Use of included script samples are subject to the

terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this

message are best directed to the newsgroup/thread from

 

[AT]

You say that you get a non valid IP address. If you get an APIPA that means
your DHCP server do not provide the address. Since it is working with other
computers your server seams to be working. Try with uninstall and reinstall
your TCP/IP protocoll on your client and see if that make any difference.

AT