L
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
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