DHCP on single Windows 2000 Server

[TechyLike]

Heres a good one!

here is our setup:-

1 x Windows 2000 DHCP Server member of a AD Domain, 500+ DHCP Clients members of various NT domains. We have recently moved the DHCP from NT to 2000 by exporting the scopes using MS's tool DHCPEXIM.
After a couple of teething problems we are all up and running on the new DHCP and new DNS (AD 2K) servers.

1 x DHCP Scope 1000 addresses available 550 or so in use. Single simple range of addresses with no other DHCP on the network. No superscoping or anything like that.

We have one single W2000 client that cannot obtain an IP address - Event 1006 and 1011 logged on the client, the DHCP request was refused "Access is denied". The local user on the Client is Local Administrator and IPCONFIG /RENEW logs the same errors. Trying this machine in our test lab (seperate network completely) the machine picks up an address no problems. If you install a PC Card in the laptop (the other is on board) that also works on the live DHCP server.

Looking at the DHCP server's logs, it hasnt logged any problems with DHCP whatsoever. Looking at the Audit logs (C:\winnt\system32\dhcp\log file) however tells us that is has issued NACKs to this MAC address about 1000 times on that day!

I cannot find anything on the web that helps. Checked MS Technet, Google Groups, Google.com, EventID.net.... none of the problems described anywhere on the web seems to be the same symptoms.

Has anyone out there got any ideas? We cannot change the system board on the laptop and the user is not keen on running with an extra card and cable all the time.

Any suggestions will be greatly appreciated.

Thanks.

Colin Scott
Milkinfirst.com

 

[erans]

hi,
It looks like a network adapter problem.
try to change the network adapter on the pc.
Eran
erans@convergys.co.il

 

[isguyatlanta]

try these:
reinstall the nic driver.
manually set the IP address to a number in the pool that is not being used, then set it back to dhcp.
set a reserved address to the mac of the onboard nic.
see if you can change the MAC on the onboard nic.

look at MS article Q284145

 

[TechyLike]

Apon trying your list of things above, we noticed that the address was actually Reserved to another (unauthorised) client. We're sure that the address was not there before. Hmm I sense a "too many cooks" problem!!

Thanks for you help!

Colin.