Workstation - DHCP Client _ ERROR "Access Denied" DNS 0.0.0.0

[Larry K. Reynolds]

I bought a Gigabyte 8KNXP which has an integrated IntelPro1000 NIC. OS is
XP under NTFS but I figure same issue in W2K. 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

 

[Ace Fekay [MVP]]

In

I bought a Gigabyte 8KNXP which has an integrated IntelPro1000 NIC.
OS is XP under NTFS but I figure same issue in W2K. 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

This is more of a networking question then a DNS question.

But let's see...
Did you setup the Linksys DHCP service correctly? There is an Enable button
and you also have to tell it how many clients you are allowing IPs. I think
you probably didn;'t set the allowed number of clients, unless you have MAC
filtering or something else blocking it. I'm going on the error message
you're getting, the DHCPNACK message. Otherwise, it would have given the
client the IP.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Larry K. Reynolds]

In doing my testing, I had turned off the onboard LAN and installed a
D-Link 530TX which also had the same problem so I was second thinking about
my position that the Motherboard had a problem. My DHCP Server (the Linksys
cable router/switch) works just fine and has been set up for over a year.
Even so, I checked to see the number and it was set for 5. It struck me
that perhaps it counted itself as 1 which means that as soon as it needed a
number above 192.168.1.104, it would be in trouble. The 192.168.1.104 had
been assigned to the onboard LAN so the next in order would be 105. To test
the theory, I increased the number to 10. I also turned off the onboard LAN
on the 8KNXP and connected the cable to it. No problem! The D-Link NIC
kisked right off and was assigned an address 192.168.1.105 by the DHCP
server (Linksys). So, I took out the D-Link NIC card, reenabled the LAN in
the BIOS. it failed again exactly as it had before. the DHCP server
rejects. One last test. I oput the D-Ling NIC card back in, connected the
cable (I now had 2 ethernet cards. The D-Link worked fine. I switched the
cable to the onboard LAN. It still did not work. So, I uninstalled the
onboard and reinstalled. Still did not work. That is where I am now.
Putting a NIC in a slot works, using the onboard LAN does not unless, of
course, I set up static addresses (which I can't do as a permanent solution
since the provider needs to be able to use dynamic addresses on the cable.
Any further thoughts? Your insigt was sincerely appreciated.
Regards - Larry K. Reynolds
"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

In doing my testing, I had turned off the onboard LAN and
installed a D-Link 530TX which also had the same problem so I was
second thinking about my position that the Motherboard had a problem.
My DHCP Server (the Linksys cable router/switch) works just fine and
has been set up for over a year. Even so, I checked to see the number
and it was set for 5. It struck me that perhaps it counted itself as
1 which means that as soon as it needed a number above 192.168.1.104,
it would be in trouble. The 192.168.1.104 had been assigned to the
onboard LAN so the next in order would be 105. To test the theory, I
increased the number to 10. I also turned off the onboard LAN on the
8KNXP and connected the cable to it. No problem! The D-Link NIC
kisked right off and was assigned an address 192.168.1.105 by the
DHCP server (Linksys). So, I took out the D-Link NIC card, reenabled
the LAN in the BIOS. it failed again exactly as it had before. the
DHCP server rejects. One last test. I oput the D-Ling NIC card back
in, connected the cable (I now had 2 ethernet cards. The D-Link
worked fine. I switched the cable to the onboard LAN. It still did
not work. So, I uninstalled the onboard and reinstalled. Still did
not work. That is where I am now. Putting a NIC in a slot works,
using the onboard LAN does not unless, of course, I set up static
addresses (which I can't do as a permanent solution since the
provider needs to be able to use dynamic addresses on the cable. Any
further thoughts? Your insigt was sincerely appreciated.
Regards - Larry K. Reynolds

Well, at least it sounds like you covered all the possibilities. Sounds like
the onboard is fried, assuming it's enabled in the BIOS (assume so since you
had it working at one point).

When you uninstalled the onboard, I assumed you did it thru Add/Remove
Hardware, then restarted and let the OS find the new hardware and reinstall
it from scratch.?

Weird that it works with a static IP and not thru DHCP. Have you looked at
the reg entries under TCPIP
under:HKLM\CCS\Service\TCPIP\Parameters\Interfaces
and checked the settings in there and compare it to the added on NIC?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory