DHCP Client in XP get 0.0.0.0 when DHCP enabled but works when "hard" DNS addresses used.

[Larry K. Reynolds]

I bought a Gigabyte 8KNXP which has an integrated IntelPro1000 NIC. OS is
XP under NTFS. FIREWALL IS OFF! Connected to a workgroup (home) with 4
computers all fed to a cable internet connection through a Linksys
Router/Switch. The gateway is 192.168.1.1 (very common) and the Linksys
acts as the DHCP Server. Under the TCP/IP properties, everything is set up
to automatically get the lease for the DNS address to be assigned by the
DHCP server. It fails and the event viewer indicates "the IP lease 0.0.0.0
for the network card ... has been denied by the DHCP server 192.168.1.1 (the
DHCP server sent a DHCPNACK message). So, I hard coded the addresses for
both the LAN and the WAN under the TCP/IP properties and they all worked.
Of course, the problem is that I do not have "hard" DNS addresses from the
service provider and must get back to the DHCP protocol. Although logic
tells me it is not the hardware, what else could it be? It is not Winsock
in the registry (tried that too by putting a known good reference in the
registry since such might have become corrupted!). Any thoughts would be
appreciated.
Regards - Larry K. Reynolds - Riverside, CA

 

[Tristian]

I bought a Gigabyte 8KNXP which has an integrated IntelPro1000 NIC. OS is
XP under NTFS. FIREWALL IS OFF! Connected to a workgroup (home) with 4
computers all fed to a cable internet connection through a Linksys
Router/Switch. The gateway is 192.168.1.1 (very common) and the Linksys
acts as the DHCP Server. Under the TCP/IP properties, everything is set up
to automatically get the lease for the DNS address to be assigned by the
DHCP server. It fails and the event viewer indicates "the IP lease 0.0.0.0
for the network card ... has been denied by the DHCP server 192.168.1.1 (the
DHCP server sent a DHCPNACK message). So, I hard coded the addresses for
both the LAN and the WAN under the TCP/IP properties and they all worked.
Of course, the problem is that I do not have "hard" DNS addresses from the
service provider and must get back to the DHCP protocol. Although logic
tells me it is not the hardware, what else could it be? It is not Winsock
in the registry (tried that too by putting a known good reference in the
registry since such might have become corrupted!). Any thoughts would be
appreciated.
Regards - Larry K. Reynolds - Riverside, CA

I would suggest trying this remove the network adapter from device manager
and then shutdown. Power down the router and leave both the pc and router
off for 20 seconds then power up the router and let it fully come online and
then power up the pc and let it get into windows and install the network
adapter again with a bit of luck it should get a suitable address from the
router. If you're still having trouble I would also look into : finding
updated drivers for the network card, checking for newer firmware for the
router and verifying the network cable is not damaged.

hope this helps.
Tristian

 

[j]

-----Original Message-----
I bought a Gigabyte 8KNXP which has an integrated IntelPro1000 NIC. OS is
XP under NTFS. FIREWALL IS OFF! Connected to a workgroup (home) with 4
computers all fed to a cable internet connection through a Linksys
Router/Switch. The gateway is 192.168.1.1 (very common) and the Linksys
acts as the DHCP Server. Under the TCP/IP properties, everything is set up
to automatically get the lease for the DNS address to be assigned by the
DHCP server. It fails and the event viewer

indicates "the IP lease 0.0.0.0

for the network card ... has been denied by the DHCP server 192.168.1.1 (the
DHCP server sent a DHCPNACK message). So, I hard coded the addresses for
both the LAN and the WAN under the TCP/IP properties and they all worked.
Of course, the problem is that I do not have "hard" DNS addresses from the
service provider and must get back to the DHCP protocol. Although logic
tells me it is not the hardware, what else could it be? It is not Winsock
in the registry (tried that too by putting a known good reference in the
registry since such might have become corrupted!). Any thoughts would be
appreciated.
Regards - Larry K. Reynolds - Riverside, CA


.
Hey Larry...I have the same question posted. If you

figure it out please email me at (e-mail address removed)
Every day I have to reset this...and though it sound weird
this is what I do. Go to Local area 1>internet protocal

properties> Change to use the following ip> manually put

any combination for ip>doesnt matter> then close out of
both open windows> then go back and change to >obtain ip
automatically> and obtain dns> it will start up again.
Three hours with a tech to tell me I needed a new
card....not the problem.