Limited/no connectivity error

September 26, 2010 at 08:37:31
Specs: Windows XP Service Pack 3, Intel Celeron 2.66ghz. 512mb of ram
I have a limited/no connectivity error balloon popping up. I am running windows xp Service pack 3 on a Dell dimension 1100 (Hey its crap, but its my piece of crap). Yesterday, I started windows in safe mode, and changed a user account password, and made another account an admin. I rebooted and logged into the newly minted admin account, and got the no connectivity error in the system tray. I have not updated anything, so is this just a coincidence that it happened after i changed the accounts? I haven't updated any drivers, and the only thing I accessed during safe mode was change user account. I can still browse the internet somewhat, but i have to reload every page a couple of times before the page displays. Any help would be appreciated.

See More: Limited/no connectivity error

September 26, 2010 at 08:49:51

click on the + sign next to "network adapters".
what does it show??


Report •

September 26, 2010 at 08:52:35
It says: intel(R) PRO/100 VE Network Connection

Report •

September 26, 2010 at 20:26:40
Whenever I get that error, I run down to the basement, unplug the router, and plug it back in. That usually gives me a month or two of error-free surfing.

They don't build routers like they used to. :-(

Socket 939 | Dual-core Opteron 185 @ 3.2GHz | 4GB | 1.0TB | Win7 x64
GeForce GTX 460 1GB | X-Fi Ti Pro | A8N32-SLI Deluxe | Antec P182

Report •

Related Solutions

September 26, 2010 at 22:38:18
I would say it's a coincidence, as you've already stated, changing a user account should not affect the network.

As jackbomb pointed out, many SOHO routers are cheap pieces of BS that need to be rebooted alot. Especially if it's an all in one, Switch/Router/Wireless combination thing - I always seem to have problems with them. My guess is, crappy software causing memory leaks, builds up over time, eventually the router runs low on network buffer space & starts running like crap until you reboot it to 'free' the space.

In a real mission critical router, this would be a big deal, but for home/residential customers...they don't care, and making you reboot your router is a cheaper fix (for them) than writing proper software.

That being said - upgrade your router firmware, it may be out of date. And try rebooting it - does that fix the problem?

Report •

Ask Question