Unable to Obtain DHCP lease: ipconfig /renew : Access is denied

Just a first  few verifications:

Are your services running properly? (Start/Control Panel/Administrative Tools/Services)
- DHCP client
- IPSEC Services

Try restarting them and see if there is anything different.

I might also want to ask you which model of router are u using? There are alot of chances that the router's DHCP server is the culprit...

Also try to disable all the Offloads from your network adapter and see if it helps...

http://img.photobucket.com/albums/v422/longsiu/IT/offloads.jpg

Both services started, I restarted them and have the same problem.

I am using windows 2003 server for the DHCP Server. All other computers are recieving DHCP info just fine. I have a netgear router that I use to segment part of the network and it's dhcp server works fine for the computers attached to it - I just hooked up the laptop to see if there was any difference and since there was no change I figure that the problem must reside on the laptop.

I checked under the advanced tab for the NIC and there are no offloads present.

I would check the DHCP Client service on the laptop to make sure it is started, then make sure there is a valid log on account specified (most likely the local account)

how about deleting the NIC and re-installing it from scratch?

have you also checked if your MAC address is listed on the win2003's DHCP server? if it is, try flushing it from the DHCP server and try again...

Hi,

May I also suggest if the problem persist to try this command: "netsh diag gui" and select "scan your system" then look if there is any red comment....
If so, maybe you will find out what the trouble is....

Also, before doing a renew, have you tried to release ?

Hope that can help.

Have you tried disabling XP firewall on your lan connection?

Jess

do you have any firewall software ?if, just disable it

M.Ayad

Thanks for all of the responces!

wvrlogin: DHCP Started using local system account - restarted service - same problem.

longsiu: I uninstalled the NIC, downloaded the newest drivers from intel and reinstalled but still have the same issue.
            I also checked for the MAC address on the DHCP Server and it was not listed.

Arl: I tried netsh diag gui and scanned the system but found no red comments, and yes I have done a release and renew.

Jessmca: the network firwall is disabled.

Good tips - Unfortunately the problem still remains.

Nothing in the Event Viewer? Also, not that it matters since you can change the IP, but is the account you are using a local and domain admin (domain admin if applicable)??

And what about other commands, such as ipconfig/flushdns or release?

^ what wvrlogin said:

try:

ipconfig /displaydns
ipconfig /flushdns
ipconfig /registerdns

Then check your Event Viewer in the following 15 minutes and see if anything's been reported...

Look in your dhcp settings on the server.  
Are there spare addresses left in the ip range and not all leased out?

Are you connecting to the same subnet as the dhcp server with no other dchp service running on any router for example?

on your DHCP server, also try to reserve an IP to that MAC address and see if it responds better...

And no other DHCP servers on the network?? Maybe a rogue WAP or router??

If nono of this is the case, then you probably have a damaged Winsock stack. Try the Windows repair button first.

can u also tell us which model of NIC you are using?

Hi,

Just by the way, this laptop is not configure as a bridge, or there are no other network devices that needs this NIC for working properly ?
No wireless that is making your laptop acting as a kind of access point ?

I hope I am not saying a big ..... ;)

Do you also happen to have another spare NIC available? If you do, try and using it and see if it works, this will help knowing whether it's a MAC/IP problem or the NIC itself...

Ok guys, yall are getting closer.

 In the event veiwer of the laptop I see the following:

The IP address lease 0.0.0.0 for the network card with network address 0000bdbdf14d has been denied by the dhcp server (The DHCP Server sent a DHCPNACK message.)

So.. there must be something wrong with the dhcp server. I stopped and restarted the DHCP Server Service and still get the same results.

 

When I try to reserve an IP for the laptop I get the following:

The Unique Identifier you have entered may not be correct. Do you want to use this Identifier anyway?

I say Yes and then I get:

The DHCP server received a message from a client that is not valid.
I hit oK and the reservation is not created.

NIC is Intel Pro/100 VE

No bridge - Just installed XP Pro / all windows updates and nic drivers. I then formated and reinstalled when I first saw the error.

There are spare addresses left for leasing - I am on the same subnet.

I will have to look to see if I have a NIC that will install on this laptop and I will post with results asap.

Thanks

At the command line run ipconfig/all

If the physical address is 0000bdbdf14d and you have no typo then your dhcp server cannot see the card.

Either your nic is on a different subnet or ports 137-139 are not open to your client machine from the dhcp server.

Or your dhcp service could be banjaxed on the client I suppose.  You would need to replace the dhcp dll files.

Jess

Ok, I tried a different network adaptor and it worked without a hitch.

Why would my DHCP Server be blocking this mac from receiving DHCP info?

Jessmca: the mac is actually:  000bdbd7f14d

It would'nt block any mac address, if you copied / pasted the error as I did from your post, you had 4 0's at the start and 13 chars.
Must have been conflict with previous card and only problem was on the client not the server.

Still, glad its sorted

Since other network adaptors work on the same client machine, the problem is probably not the client PC but more likely the NIC, and since that NIC works when you give it an IP address manually, that would probably mean that there is a conflict on the DHCP server side concerning the MAC/IP assignment. Try installing Ethereal on  you server and capture the traffic for a while then try to look for 000bdbd7f14d and see if there is anything abnormal going on...

Uninstall the Intel Proset software - not the nic driver, but the two are bundled from a factory install and I have seen major problems with the Proset software and service pack 2
GL

Ok guys.

mtpcbypc - I uninstalled the proset software but had no change.

Longsiu: I think that you are right about the problem being on the DHCP server. I installed Ethereal and captured traffic but I am not really sure what to look for. I do see the DHCP NAK being sent to the laptop but I don't understand why.

A DHCP NAK is a negative acknowledgement message...

• Cause:  The scope in use is full and can no longer lease addresses to requesting clients.
 
• Solution:  If the DHCP server does not have IP addresses available to provide to its clients, it returns DHCP negative acknowledgment messages (DHCPNAKs) to them. When this occurs, consider the following possible solutions:
 
1.
 Expand the address range by increasing the End IP address for the current scope.
 
2.
 Create a new additional scope and a superscope, then add the current scope and the new scope to the superscope.
 
3.
 Create a new scope or extend the range. Optimally, you could renumber your current IP network. Deactivate the old scope as needed, and then configure and activate the new one.
 
4.
 Reduce the lease duration. This can help to expedite the reclaiming of lapsed scope addresses.

Other DHCP-related procedures and techniques might also help to accelerate or ease the transition from an existing scope being retired to a new scope created to take its place at the server. These include deleting client leases from the scope being retired, excluding addresses from that scope, and then deactivating it once the new scope has been activated. This ensures that the DHCP client obtains leasing from the new scope.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/2a535b4d-1771-485b-8bfa-459d35d563fb.mspx

Thanks to everyone for your good suggestions.

I finally got my problem solved. This is what I did. After reading longsiu's suggestion on checking the DHCP server logs - I found that when the server was declining an ip for the specified mac address - there was also an ip associated with it. The same IP was already being used on the network and was reserved. I removed the reservation and then like magic - the laptop picked up an ip - and not the reserved one either. I don't know why this happened but it is working now.

All points to longsiu!

Thanks for hanging in there with me.