Wireless doesn't work anymore: "Limited or no connectivity"

  • Thread starter Thread starter void.no.spam.com@gmail.com
  • Start date Start date
V

void.no.spam.com@gmail.com

I have a Windows XP SP2 laptop, which connected to my network
wirelessly. It worked fine, until I uninstalled a bunch of apps that
I didn't need anymore, and then it stopped working. Whenever it tries
to connect to my wireless network now, it connects, but then it can't
get an IP address for some reason. It just says "Limited or no
connectivity."

The only thing I uninstalled that was related to wireless was
something called a "Venturi Client". I didn't think that was related
to wifi, I thought it was for a wireless modem that I used at a
previous job. Anyways, I'm using the built-in Windows Zero Wireless
utility, so nothing I uninstalled should have affected that.

Any ideas why it suddenly can't get an IP address?
 
"void.no.spam.com@gmail.com" <void.no.spam.com@gmail.com> wrote:

>I have a Windows XP SP2 laptop, which connected to my network
>wirelessly. It worked fine, until I uninstalled a bunch of apps that
>I didn't need anymore, and then it stopped working. Whenever it tries
>to connect to my wireless network now, it connects, but then it can't
>get an IP address for some reason. It just says "Limited or no
>connectivity."
>
>The only thing I uninstalled that was related to wireless was
>something called a "Venturi Client". I didn't think that was related
>to wifi, I thought it was for a wireless modem that I used at a
>previous job.


It's definitely wireless-related: it's a wifi accelerator program.

http://www.venturiwireless.com/tech_support/VenturiWireless.html

It's definitely possible that it tied in with your wireless setup, and
didn't put things back together properly when you uninstalled it.

>Anyways, I'm using the built-in Windows Zero Wireless
>utility, so nothing I uninstalled should have affected that.
>
>Any ideas why it suddenly can't get an IP address?
 
void.no.spam.com@gmail.com wrote:
> I have a Windows XP SP2 laptop, which connected to my network
> wirelessly. It worked fine, until I uninstalled a bunch of apps that
> I didn't need anymore, and then it stopped working. Whenever it tries
> to connect to my wireless network now, it connects, but then it can't
> get an IP address for some reason. It just says "Limited or no
> connectivity."
>
> The only thing I uninstalled that was related to wireless was
> something called a "Venturi Client". I didn't think that was related
> to wifi, I thought it was for a wireless modem that I used at a
> previous job. Anyways, I'm using the built-in Windows Zero Wireless
> utility, so nothing I uninstalled should have affected that.
>
> Any ideas why it suddenly can't get an IP address?


Get to the list of preferred wireless networks and delete the entry for
yours (and all others that you don't recognize). Then try to connect
again and be sure that you enter the encryption password correctly.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
On Jun 9, 6:57 pm, Lem <lem...@hotmail.com> wrote:
> void.no.spam....@gmail.com wrote:
> > I have a Windows XP SP2 laptop, which connected to my network
> > wirelessly. It worked fine, until I uninstalled a bunch of apps that
> > I didn't need anymore, and then it stopped working. Whenever it tries
> > to connect to my wireless network now, it connects, but then it can't
> > get an IP address for some reason. It just says "Limited or no
> > connectivity."

>
> > The only thing I uninstalled that was related to wireless was
> > something called a "Venturi Client". I didn't think that was related
> > to wifi, I thought it was for a wireless modem that I used at a
> > previous job. Anyways, I'm using the built-in Windows Zero Wireless
> > utility, so nothing I uninstalled should have affected that.

>
> > Any ideas why it suddenly can't get an IP address?

>
> Get to the list of preferred wireless networks and delete the entry for
> yours (and all others that you don't recognize). Then try to connect
> again and be sure that you enter the encryption password correctly.


Yeah I deleted a bunch, and now have only 2 - my own, and a friend's
that I set to "on demand". Then I deleted my own, and re-created it,
and it still doesn't work.
 
void.no.spam.com@gmail.com wrote:
> On Jun 9, 6:57 pm, Lem <lem...@hotmail.com> wrote:
>> void.no.spam....@gmail.com wrote:
>>> I have a Windows XP SP2 laptop, which connected to my network
>>> wirelessly. It worked fine, until I uninstalled a bunch of apps that
>>> I didn't need anymore, and then it stopped working. Whenever it tries
>>> to connect to my wireless network now, it connects, but then it can't
>>> get an IP address for some reason. It just says "Limited or no
>>> connectivity."
>>> The only thing I uninstalled that was related to wireless was
>>> something called a "Venturi Client". I didn't think that was related
>>> to wifi, I thought it was for a wireless modem that I used at a
>>> previous job. Anyways, I'm using the built-in Windows Zero Wireless
>>> utility, so nothing I uninstalled should have affected that.
>>> Any ideas why it suddenly can't get an IP address?

>> Get to the list of preferred wireless networks and delete the entry for
>> yours (and all others that you don't recognize). Then try to connect
>> again and be sure that you enter the encryption password correctly.

>
> Yeah I deleted a bunch, and now have only 2 - my own, and a friend's
> that I set to "on demand". Then I deleted my own, and re-created it,
> and it still doesn't work.


This message occurs when your NIC is set to obtain an IP address
automatically but is not receiving an address from a DHCP server.

(You can check this by running ipconfig /all from a Command Prompt
window. You should see (about the 4th line down under your NIC's name)
"Dhcp Enabled: Yes" and the IP Address will be of the form 169.254.x.y)

In a wireless network, the usual cause is that the client (your
computer) has not properly authenticated to the access point (your
router) because of a security error. Eliminate this possibility by
(temporarily) removing *all* wireless security (encryption, MAC filters,
IP filters, etc.) using your router's configuration utility. While
you're in your router's configuration utility, double check that its
DHCP server is, in fact, on and set to allocate enough IP addresses to
accommodate your LAN. Go back and delete the entry for your network
from the list of preferred networks, because it will have a saved
password and thus won't connect to the now-unsecured wireless router.

If you still can't get a working connection, MVP Chuck has a page that
is a good starting point to continue your diagnosis:
http://networking.nitecruzr.net/2005/07/limited-or-no-connectivity.html

Given that you ran into this problem when you uninstalled things, I
would suspect an LSP/Winsock problem. See the link on Chuck's page
linked above for multiple suggestions on this, but for your first try,
I'd suggest:

netsh winsock reset catalog

from a Command Prompt window.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
On Jun 10, 1:43 pm, Lem <lem...@hotmail.com> wrote:
> Given that you ran into this problem when you uninstalled things, I
> would suspect an LSP/Winsock problem.  See the link on Chuck's page
> linked above for multiple suggestions on this, but for your first try,
> I'd suggest:
>
> netsh winsock reset catalog
>
> from a Command Prompt window.


When I try that, I get a popup that says "Network Command Shell has
encountered a problem and needs to close." What do you make of that?
 
void.no.spam.com@gmail.com wrote:
> On Jun 10, 1:43 pm, Lem <lem...@hotmail.com> wrote:
>> Given that you ran into this problem when you uninstalled things, I
>> would suspect an LSP/Winsock problem. See the link on Chuck's page
>> linked above for multiple suggestions on this, but for your first try,
>> I'd suggest:
>>
>> netsh winsock reset catalog
>>
>> from a Command Prompt window.

>
> When I try that, I get a popup that says "Network Command Shell has
> encountered a problem and needs to close." What do you make of that?


Assuming that you're logged on with administrator privileges, I don't
know what to make of that error message. Do you also get it if you just
try
"netsh /?" [without quotes]

Try the other methods suggested at PChuck's site.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
On Jun 11, 7:39 pm, Lem <lem...@hotmail.com> wrote:
> void.no.spam....@gmail.com wrote:
> > On Jun 10, 1:43 pm, Lem <lem...@hotmail.com> wrote:
> >> Given that you ran into this problem when you uninstalled things, I
> >> would suspect an LSP/Winsock problem.  See the link on Chuck's page
> >> linked above for multiple suggestions on this, but for your first try,
> >> I'd suggest:

>
> >> netsh winsock reset catalog

>
> >> from a Command Prompt window.

>
> > When I try that, I get a popup that says "Network Command Shell has
> > encountered a problem and needs to close."  What do you make of that?

>
> Assuming that you're logged on with administrator privileges, I don't
> know what to make of that error message.  Do you also get it if you just
> try
> "netsh /?" [without quotes]
>
> Try the other methods suggested at PChuck's site.


Thank you for pointing out PChuck's site, Lem. The LSPFix detected a
problem in the chain, and it fixed it. Now I can connect and access
the Internet.

But if I do "netsh /?" from a command line, I still get the "Network
Command Shell has encountered a problem and needs to close" error.
How serious is that? Do you think some of the other fixes listed on
the PChuck site might fix that problem?
 
Back
Top