Stuck on Acquiring Network Address. Then on Limited or no Connectivity.?

Question

Starting two days ago, for no reason, I lost use of my LAN line.
When I try to connect to the internet, I see a message saying "Acquiring Network Address" for a while, before it changes to "Limited or no connectivity."

I send packets out, but I do not receive any back. As a result, I have tried the following:
Enabling/Disabling
Reinstalling the driver
Updating the driver
Tried multiple network cables
Tried different machines (they work fine with my lan line)
I then did a clean reformat, which didn't change anything.
Reset IP address to default
Reset subnet mask to default
Reset TCP/IP to default
Repaired the connection
Changed the settings to auto. config.
Upgraded to SP3, didn't work.
Tried pinging default gateway 192.168.1.1 (4 packets sent, 4 received, 0% loss)

Since then, I now see "Status: Connected"
However, I still am not receiving packets.
I am baffled, I have never had any problems such as this.
Windows Device Managers says that my NIC is functioning normally.
Despite that, could this be a hardware failure?

Answer 1

are people answering questions here simply pulling answers out of thin air . or just guessing . look at what the man is telling you . and still no one sees the problem ???



I am willing to bet that the router is set to the same IP as the modem (192.168.1.1)



change the ip for the router to 192.168.2.1 and you should connect because the dhcp client will then know where to route

Answer 2

You question leads to other questions since I am having trouble with some inconsistencies in it.



You say you are not receiving packets, yet you say you ping and it sends 4 and receives 4. That in itself says you are receiving packets. So what is it that makes you think you are not receiving packets?



The fact that other machines can work says that there is something different about that one, but we don't really know. The message about limited connectivity usually means that you cannot get an IP address from your DHCP server, which is probably your router. It would be helpful to know what else is going on in the network, and how the machines that are working are configured. Is the acid test the ability to access the internet? But you cannot ping without having a valid IP address, so the fact that you have one is inconsistent with the message about limited connectivity. It could also be that your DHCP server is not handing out a proper default gateway address, which would limit your connectivity. Have you tried powering down your router / gateway? The other machines may work if they are getting renewed IP addresses and retaining their existing gateway and DNS information whereas the problem machine is trying to get a new IP address lease.



I threw a lot out there because of holes in the information. Need more input.

Answer 3

in case you're connecting by way of the Ethernet then the two the modem is performing as a bridge or that's a router and not a modem. whether that's a modem. The modem isn't properly negotiating DHCP with the ISP's router. Are there any DHCP settings for the modem? Do you have a static IP handle? whether that's a router. Your computing device isn't properly negotiating DHCP with the router. Are there any DHCP settings on the router interface? what's the modem called?

Answer 4

A very simple procedure, that often fixes a lot of network problems, is unplugging everything, and then plugging it all back in. The thing to remember when doing this, is to plug things in in the proper order. Always start with what is connected to the internet first. For example:

I have a gateway, a router, and a wireless router, and then my computer. If anything messes up I would unplug it all and plug in the gateway first, wait for it to fully boot up, then plug in the first router, wait for it to boot up, and so on. Works for me a lot. Give it a try.

Answer 5

I have had the same problem in the past, and so has my friend. Go touch your internet Router. Is it hot? if so then more then likely it is burnt out and not sending packets correctly. I found out mine was overheated and the circuits had melted, I just called my internet company up and told them, and they sent me a new router.

Answer 6

Sounds like you are pretty knowledgeable! Im impressed. Sounds like a hardware failure to me. You could try running winsock from the command prompt. Do this



type this into the cmd prompt window: netsh winsock reset



and then restart your computer

Answer 7

That really seems like the only option left. If you have the know-how and the spare parts, try a different NIC.