S
Scott Clowers
OK, I'm stumped on this one. Windows XP Pro. Started with SP1, installed SP2
to see if it would correct the problem. Logged in as administrator and have
checked to make sure administrator is member of administrators group. DHCP
client service is started. This computer was working and will still work
with a static IP Address. I changed it to DHCP and it would not obtain an IP
address. Rebooted it and still no IP Address. Go to command prompt and type
ipconfig. It has no IP Address (0.0.0.0). Type ipconfig /renew and after a
delay it responds with "An error occurred while renewing interface Local
Area Connection : Access is denied".
I have gone as far as running a sniffer on the network and here is what
happens:
1) This machine sends out a DHCP Discover
2) The DHCP Server (a SonicWall Pro230) sends a DHCP offer of IP Address
10.1.81.20
3) This machine sends a DHCP Request for 10.1.81.20
4) The DHCP server sends a DHCP NAK
5) The process repeats
I have moved the machine to a different jack to see if it was a connectivity
issue but it made no difference. Has anyone else seen this?
Scott Clowers
Network Administrator
Nexcheck
to see if it would correct the problem. Logged in as administrator and have
checked to make sure administrator is member of administrators group. DHCP
client service is started. This computer was working and will still work
with a static IP Address. I changed it to DHCP and it would not obtain an IP
address. Rebooted it and still no IP Address. Go to command prompt and type
ipconfig. It has no IP Address (0.0.0.0). Type ipconfig /renew and after a
delay it responds with "An error occurred while renewing interface Local
Area Connection : Access is denied".
I have gone as far as running a sniffer on the network and here is what
happens:
1) This machine sends out a DHCP Discover
2) The DHCP Server (a SonicWall Pro230) sends a DHCP offer of IP Address
10.1.81.20
3) This machine sends a DHCP Request for 10.1.81.20
4) The DHCP server sends a DHCP NAK
5) The process repeats
I have moved the machine to a different jack to see if it was a connectivity
issue but it made no difference. Has anyone else seen this?
Scott Clowers
Network Administrator
Nexcheck