Limited or no connectivity message

[Guest]

Hi,

I have 3 PCs on my home network. The 2 desktops work fine and the notebook
did until the last few days. It is a Dell Inspiron 6000. I have a wired
network (Linksys BEFSR41 router/switch) and the PCs pick up a dynamic IP when
they start up.

A few days ago we started up the notebook and got the "limited or no
connectivity" message for the first time in almost two years. Since the
other PCs were working fine, I thought that jack might be suspect, brought
the notebook PC to a different jack and it picked up a dynamic IP from my
router. I unplugged, went back to the original jack and the IP stuck. This
stayed fine for a few days and I thought it was just a fluke. But today I
got the same message again. This time I couldn't get it to pick up an IP
from my router. I tried "repair", "ipconfig /release", and "ipconfig /renew"
with no luck.

After poking around a bit, I discovered it had picked up a completely
foreign IP address. I checked and found out that it was sensing a weak
wireless network. Is it possible that I'm picking up an IP from a neighbor's
wireless network that's preventing my own wired network from assigning an IP?

To sorta test that theory, I assigned a static IP in the normal range for my
router. I was able to connect to my home network and see files on the other
PCs. I would have accepted that solution but I still couldnt get to the
internet (or ping outside my own network). So I attempted to disable the
wireless function on the PC (don't know if that really worked) and blocked an
IP range on the (McAfee) firewall. I went back to DHCP and tried to restart,
but the bad IP is still coming up, and I'm still getting the "limited or no
connectivity" message.

I don't think it's the router, since the other PCs continue to function just
fine. Any thoughts on how to completely disable the wireless function?

Sorry for the long story, but does anyone have any suggestions how to get
the notebook PC to work only with my wired network?

Thanks.
Dan

 

[Lem]

Hi,

I have 3 PCs on my home network. The 2 desktops work fine and the notebook
did until the last few days. It is a Dell Inspiron 6000. I have a wired
network (Linksys BEFSR41 router/switch) and the PCs pick up a dynamic IP when
they start up.

A few days ago we started up the notebook and got the "limited or no
connectivity" message for the first time in almost two years. Since the
other PCs were working fine, I thought that jack might be suspect, brought
the notebook PC to a different jack and it picked up a dynamic IP from my
router. I unplugged, went back to the original jack and the IP stuck. This
stayed fine for a few days and I thought it was just a fluke. But today I
got the same message again. This time I couldn't get it to pick up an IP
from my router. I tried "repair", "ipconfig /release", and "ipconfig /renew"
with no luck.

After poking around a bit, I discovered it had picked up a completely
foreign IP address. I checked and found out that it was sensing a weak
wireless network. Is it possible that I'm picking up an IP from a neighbor's
wireless network that's preventing my own wired network from assigning an IP?

To sorta test that theory, I assigned a static IP in the normal range for my
router. I was able to connect to my home network and see files on the other
PCs. I would have accepted that solution but I still couldnt get to the
internet (or ping outside my own network). So I attempted to disable the
wireless function on the PC (don't know if that really worked) and blocked an
IP range on the (McAfee) firewall. I went back to DHCP and tried to restart,
but the bad IP is still coming up, and I'm still getting the "limited or no
connectivity" message.

I don't think it's the router, since the other PCs continue to function just
fine. Any thoughts on how to completely disable the wireless function?

Sorry for the long story, but does anyone have any suggestions how to get
the notebook PC to work only with my wired network?

Thanks.
Dan

Is the "completely foreign IP address" something like 194.254.x.x? If
so, that's not "picking up a weak wireless signal," it's Windows
assigning itself an IP address because it can't connect to the DHCP
server (Google APIPA). The business with the wireless network is a red
herring. And I'd be careful what you block with a firewall. You're
likely to forget what you did and it'll come back to bite you someday.

I think your first guess was close: it's either a bad jack or a bad
cable. I think a bad cable is more likely. Your NIC also could be
failing, but that's less likely. You might also check to see that all
power save options on the NIC are disabled, but that seems a remote
possibility if the connection lasted a day or so before cutting out.

When you set the static IP, you may not also have set a DNS server and a
default Gateway (both of which are automatically picked up from the DHCP
server when the NIC is set to obtain an IP address automatically). If
so, that's why you could connect to your own network, but not the
Internet (no gateway, no router to the Internet).

If you want to keep trying the static IP route, run ipconfig /all on one
of the other (working) computers (run it in a command prompt window) and
note the values for DNS server and Default Gateway, then set the same
values in the same dialog box where you set the static IP (and don't
forget the subnet mask, either). I don't think that this will be a long
term solution: if you're not getting a reliable connection to the DHCP
server, you won't get a reliable connection, period.

Note that

 

[RalfG]

The "limited or no connectivity" is typical for wireless connections, I
haven't seen it myself on any wired connections. One of your neighbours may
have installed a new unsecured wireless network recently.
When two network connections in the computer are active on the same subnet
they can contend for an IP address. Usually the first adapter enabled by
Windows would win and the second would fall back to automatic addressing.

If you disable the wireless adapter in Network Connections that should be
sufficient. Alternatively you can configure the adapter Interface metrics
(eg 10 for the wired, 20 -wireless) for each to give priority to the wired
connection. In that case also turn off autoconnect on the wireless adapter.

Example here: http://www.ezlan.net/network/metrics.jpg

 

[Guest]

Limited or No Connectivity Message IS available on a wired ethernet connection.

Go into RUN then CMD

Type IPCONFIG /RELEASE

And you will receive the message.

Type IPCONFIG /RENEW

And your NIC will ask your router for a new IP address. If you're using
DHCP, then it will be the same ip address.

IP addresses are normally valid for 7 days. Releasing it, discards it
completely and asks the router for a new ones to use for communications.

Hope this helps.

P.S Another good example of LIMITED OR NOT CONNECTIVITY is when I've made
some home-made ethernet network cables. I hadn't quite got it crimped right,
so it causes a problem. (i.e. it could sense that something was there, but
they were not all in the right order etc.)

I have subsequently learnt how to make them properly!

DAN WALTERS

 

[Guest]

Hi First things first, make sure that your wireless card it not on when using
the wired connection.

Secondly, has the network cable that you're using to connect to your network
switch changed? (Often problems with LIMTED connectivity... are due to wiring
problems, ie, not all 8 connections are wired in right order etc.) You can
normally get rid of this problem by purchasing a shop bought, tested cable.
(Or like me, just learn how to do it properly!)

If that's not the problem, try changin port on your switch.

If that still gives it the same problem.

Go into RUN.

then CMD, hit okay

In command prompt type in IPCONFIG /RELEASE

This removes any ip address assigned to your default active card. (This is
why it's essential to make sure that your wireless is disabled.)

Then in command prompt type in IPCONFIG /RENEW

This will renew the IP address given from your router.
Hopefully this will work. If this DOES work, then you may find that you need
to do this every 7 days.

If that does become a problem, then I can give you details on how to create
a script that does all of that everytime you log in. (Then you can forget
about it)

Hope it helps.

Let me know how you're getting on with this definately frustrating problem