DHCP assigning IP issue

[Sargeras]

I'm playing WoW last night when suddenly I get disconnected. Ok, fine, I try to log back in and nada. Reboot, and I can't access the internet. It turns out that my DHCP server won't assign a net IP so I can get online.

When I disable and reenable my connection, I get this:


And when I try to load IE/Firefox, or do ipconfig /renew, I get this:


So Windows is assigning a local IP because it cannot assign one from DHCP. Whenever I do an ipconfig /renew, I get an error saying a DHCP server was not found.

/ipconfig release does nothing. It just shows my config info again.
I've tried swapping NIC cards (hence why it says #2).
I've tried swapping NIC cables.
I've used WinSockFix, for the possibility that WinSock was corrupted.
The only other thing I can think is that I have a virus or trojan that's acting as a proxy, and I have a symantec av running on the comp now.

My setup at this house is 2 computers, the one I'm on now and the one I'm trying to fix. Both are using XP, both can see each other on the network, and are connected through a Netgear hub (with auto-upload) that is also connected to a Verizon DSL modem.

Any help would be greatly appreciated!

[Aabidano]

Do you usually get a verizon IP or a local one?

Did you power cycle the DSL box?

[Sargeras]

Before the problem... Verizon IP, and Yes.

[Boogahz]

Think your problem is a bit different than mine since your can see both comps on the network. I was having a similar problem, and it turned out that my onboard LAN port went poof. I put a different NIC in and it started working again.

[Aabidano]

Try powering all your devices off and connnect one of the computers directly to the DSL box. Power up the PC and modem and check to see if you've got an IP, if not run "arp -a" from a command prompt. You should see at least one address listed, usually your next hop. If there's nothing there, or a MAC address and no associated IP your problem's most likely on the providers side.

If you do have an IP it's likely something with your hub\router.

[Kilmoll the Sexy]

It won't be his provider as he does have an IP on the other machine. With the Auto Private Addressing you will be able to hit other boxes on the network just fine but it is not getting the IP correctly from DHCP.

I would actually do the rebooting of the Netgear Router...and I am assuming it is a router and not a hub as a hub is not able to assign IP's the way a router would. Check your router info bu typing 192.168.0.1 into IE and make sure that DHCP is on and that nothing is through your firewall and hosing you.

As an alternative, while you are connected to the router in this way, set up static IP's for each machine and see if you connect that way.

[Winnow]

Turn off your computer(s). Unplug the modem and the router, plug in the modem, let it do it's bootup thing for 30 seconds or whatever. Then plug in the router and let it do it's thing. Then turn on your main computer.

I'd also try directly connecting your modem to your computer without the router to see if you can connect to the internet.

Beyond that, I suppose I'd reset the router to defaults and start the entire setup process over. Make sure you're not late on a bill or something and not temporarily cut off!

[Tenuvil]

If all else fails, switch the ports that your Ethernet cables are entering the router from. Since you have one PC that is fine and dandy, it's got to be somewhere from the router port that the malfunctioning PC is on to the PC itself.

[Aabidano]

It won't be his provider as he does have an IP on the other machine.

Unless it is a hub and his provider started limiting him to one IP. That's why I asked my previous question

Connecting directly to the DSL box limits variables.

If it is a router unless something has failed it's not going to change settings by itself and stop working. An auto-update could have done it and it may need reset as others have said.

[noel]

I've been somewhat annoyed with all of the responses to this thread. Anytime you have a device that's not being assigned an IP address, the following steps should be taken (Windows specific):

edit: You really don't even need to release and renew if you still have the lease you had when you lost connectivity. You're better off a) verifying that your cable/DSL bridge (modem) still has connectivity, and then connecting to your router/firewall (assuming your using one) and having it do a release/renew. If you can't ping your gateway, reboot your router/firewall and try again.

1. Ensure that the device has physical connectivity.
2. Perform an ipconfig/release
3. Perform an ipconfig/renew
4. Assuming failure, STATICALLY ASSIGN THE IP ADDRESS to a known free IP address, or the one you previously had and attempt to PING A) the gateway, B) the DHCP server.
5. If you cannot reach the gateway, troubleshoot the gateway. This could involve power cycling your router/firewall or your cable/DSL bridge (modem) (see below), or moving to an alternate port on your router/firewall/AP.
6. If you can reach the gateway, verify that the gateway is responding to ARP requests, by checking your ARP cache and verifying that you're learning the gateway's MAC to IP address information.
7. If you can reach the gateway but not the DHCP server, troubleshoot the server.
8. If you're directly connected to your ISP with no firewall/router (you're a fool) and you've reached this step, work with your ISP to resolve this issue. If you're behind a firewall/router/AP, proceed.
8. In many home environments, where you're using a router/firewall/AP or some combination thereof, the gateway and the DHCP server are one in the same. Power cycling this device and/or verifying it's configuration is the best option.

Finally, if your firewall/router is providing your home devices with IP information, but it is not receiving a DHCP lease from your ISP:
1. Have your firewall/router do whatever is the equivalent of a release/renew.
2. If that does not resolve the issue, power cycle your DSL/Cable bridge (modem), and then the router/firewall AP. The idea is to have the cable/DSL bridge totally rebooted prior to the firewall/router rebooting. Your cable/DSL must be in a connected state for your router/firewall to get an IP address from your ISP, and your router/firewall must have an IP address from your ISP for you to reach the Internet. When everything comes back up, connect into your firewall/router/AP. If it's assigned an IP address from your ISP, you're done, if not, call your ISP and resolve the issue with them.

Sorry, but some of the responses to this thread have been a bit on the drastic side for such a relatively simple issue.

Things you should not be doing as initial steps:

• Reboot your PC
• Swap NIC cards
• Connect directly to your DSL/Cable modem. Once you do this, you're computer is effectively unprotected. Yes this is a valid troubleshooting technique, but more of a last resort.

The most likely reasons for you to lose network connectivity to the Internet:

• Your DSL/Cable connection dropped
• Your DSL/Cable modem was somehow reset
• Your Router/Firewall/AP reset or somehow lost its configuration
• Your wireless signal was interrupted
• Your cable is shitty and caused a loss of connection cause you bumped it
• Your NIC failed (this really doesn't happen that often folks)

[Zaelath]

[*]Your NIC failed (this really doesn't happen that often folks)[/list]

Unless it has a chip with a little crab emblazoned thereon (realtek). Those fucking things fall over more often than drunken teenagers at an oil wrestling festival.

[Boogahz]

Yup, the NIC I had that failed was RealTek

[*~*stragi*~*]

This happened to me on two different computers sarge.

Turn your router on and off rapidly for about 5 seconds and I'll bet it fixes.