"Limited Connectivity" showing in XP until Router reboot

[Pulsar]

I have windows XP with all the latest updates. I'm using Zonealarm, Kaspersky Antivirus, and AVG Anti-Malware. I run my computer's 100 Mb ethernet through a Linksys 8 port BEFSR81. Then the router runs into a Voip adapter, then to my broadband modem.

I have been using this exact configuration for 6 months with no issues.

In the last 3 days, we have been having connetivity problems. We had a snow storm, and we lost ALL connectivity. (I am using long range wireless internet - parabolic antennae to a broadband tower 27 miles away). I cleaned the snow off my parabolic and the broadband modem and voip connector immediately reconnected. No issues. However, my computer reported "Limited or no connectivity" in the little balloon in the task bar. So I rebooted my linksys.

It works fine for a bit. But every time I have left the computer (I leave it running) to go do something else, I'll come back a couple of hours later and find that the balloon is back saying no or limited connectivity. A reboot of the router fixes this every time.

I went to a command prompt on my computer and tried a /release then a /renew, and the computer hung up at the /renew (until another router reboot).

Of course, I suspect the router.... but as this router wasn't cheap when I bought it, I'd like to know a way to diagnose the deal. Is it the ethernet card, the router, or the Wan port on the voip adapter, and how to I narrow it down to find what I need to replace?

My first guess would be to connect the computer directly to the Voip adapter and see if I get the problem again - that should narrow it down to the router which I already suspect. But what type of trouble shooting can I do with the router itself to diagnose it?

 

[sieistganzfett]

your computer->router->voip adapter->modem... right?

1. try connecting the ethernet cable from your pc to a different lan port on the router. -are you sure the router isnt experiencing a power loss or something?
2. try static ip on your pc which is connected to the router -it just loses ip when this no connectivity occurs and as a result it wont connect to the internet from what i understand from you.
3. i think you are familar with connecting the modem directly to your pc and configuring it properly to work since you configured the router to work right. try it by bypassing both the router and the voip adapter. so your computer ->modem. see if the connection lose still occurs.
4. your setup is such that computer gets IP from router. your pc does not get it or loses it, rebooting router gives it back out, so its very unlikely that its the wan port on the router or the voip adapter or modem. it sounds like the router, but it is possible it is the ethernet card, to figure this out try step 2 and 3 i mentioned.

 

[Pulsar]

Well, cutting out the voip adapter isn't really an option because... well... my family uses the phone on occasion. However, I will plug the computer into the voip and cut out the router so that I can narrow it down.

I HAVE been looking for an excuse to buy one of the inexpensive buffalo routers that can use the DD-WRT for QOS. Then I could put the voip behind the router as well and eliminate one "level" between the computer and the net...... but I can't justify it until I prove this router is on the down and out.

Oh - the router has the most updated firmware, as does the voip adapter. My drivers for the 'puter are also the newest. I just checked and they haven't made any changes to the voip configuration recently either.

 

[sieistganzfett]

ok, then just connect the pc to the voip adapter which connects to the modem. configure the pc so it works for internet (your voip should still work), if the problem still occurs it is the pc. but try the static ip idea 1st before you remove the router, since you will have to reconfig again anyways.

 

[Pulsar]

Well - that sorted it.

As it turns out, it wasn't the router and wasn't the voip adapter either.

Yesterday, I updated my computer. For whatever reason, when it tried to do internet explorer 7, it suddenly decided my computer wasn't legitimate (it was). I had to cancel the installation.

Well, turns out that it fubared the TCP/IP stack. I downloaded the winsock fix and ran it, rebooted it, and no problems since. Thanks Microsoft. Not only do you accuse me of being a pirate, but you screw my computer in the process....