Windows Forum

Ask something
Discussion Locked

Cannot get IP address on dhcp

0 helpful
15 replies

by sphynx 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,
i experienced today in windows 2000 that it wasn't able to get ip address for our dhcp. Our dhcp server is working very fine because i test it on other pc and it works great.
Every time i power up the computer it always get the ip address starting at 169.x.x.x .

Can anyone help me how to solve this?

Thanks,

15 replies

by sphynx

Yes the dhcp is started and the status is "automatic" so every time you boot up it automatically start.

by ricardomenendez

Try this:

open a command prompt and try typing:

>ipconfig /all
that should show your current IP address.

then type:
>ipconfig /release

that will erase your IP settings

last type:
>ipconfig /renew

that tells the DHCP server to send the client a new address and restart the Network Interface.

That should work.

But of course first check DHCP is enabled on that computer in the IP settings :)

by sphynx

This is the first thing i do but once you release and renew it gives the default ip of windows which is 169.x.x.x

by shortbus

Is this a new network installation or have all of these components been in place?

If it's new, and your network is subneted, check and see if your router is able to forward BOOTP messages. If it's able to forward BOOTP, then it's able to forwardDHCP as well.

If it's a previously installed network, try setting a static IP address and other information. Then try and ping other computers on its subnet, across the subnet, etc, to see if you have any connectivity. If you can't ping them, then DHCP is probably working fine.

Check your physical cabling. Make sure you didn't plug it into an active "uplink" port ;-)

Hope some of this helps,

Bus

by sphynx

It used to work before on dhcp and now what i do it put static ip address but this guy is travelling and need to have dhcp on his laptop. Cables are working and was able to work once put the static ip address. This is really weird stuff. DHCP pool is 100 ips and the used is only 20 ip.

by virus2k

When A DHCP server is configured U have to give a static IP address and in your case u have configured ur dhcp to obtain ip address automatically ....thats y it on boot first contacts to any available dhcp and if no one is there to assign the ip to it then dhcp assigns itself the ip 169.254.x.x.....so try to configure it with static ip.

by mark_lt

I have seen this happen on a bad Switch. If you did a manual IP, then straight back to DHCP and renew it, then you will get the IP. Concentrate on the network segment that the PC is connected to, my guess is that is where the problem will be

by benwagg

Just restarting the PC may not cause it to request an address from the DHCP server. Your Win2k system does not request a DHCP-assigned IP address because it "thinks" it does not need one, since it already has the address it assigned itself. You can force it to release the current "automatic" address and get a DHCP address by opening a Command Prompt and typing:
IPCONFIG /RELEASE
IPCONFIG /RENEW
Occasionally I have still had Win2k still balk at requesting a DHCP address, and corrected it as follows:
1. Open Properties for adapter on Win2k system, and assign a static IP address within your subnet.
2. Verify that you can connect to (ping) other systems on network, including the DHCP server.
3. Reboot system while it has static IP. (I sometimes do this even though Win2k can change IP addr w/o reboot)
4. Re-verify connectivity by pinging/browsing.
5. Open Properties for adapter on Win2k system, and change to DHCP (remove static IP).
6. Open a Command Prompt ("DOS prompt") and verify DHCP-IP assigment with IPCONFIG /ALL.

This discussion is closed to new replies.