Limited or No Connectivity

[Shaun]

Anyone else getting this? I see google groups pulls up a
huge amount of info regarding this but no real solution.
I have a onboard Intel Pro 100VM and then bought a PCI
Dlink and i still do not get any IP address form the cable
modem. It is NOT hardware related, it is SP2 related
100%. I've even tried to roll back to SP1 and even pre
SP1 and still nothing. SP2 does something to the
machine. Is there a solid fix yet or what?

 

[Steve Winograd [MVP]]

Anyone else getting this? I see google groups pulls up a
huge amount of info regarding this but no real solution.
I have a onboard Intel Pro 100VM and then bought a PCI
Dlink and i still do not get any IP address form the cable
modem. It is NOT hardware related, it is SP2 related
100%. I've even tried to roll back to SP1 and even pre
SP1 and still nothing. SP2 does something to the
machine. Is there a solid fix yet or what?

The "limited or no connectivity" message is the result of a problem,
not the cause of the problem.

It means that the network connection is configured to obtain an IP
address automatically and can't communicate with a DHCP server to get
the address assigned.

With some cable modem services, you must turn the cable modem off and
back on when changing the NIC that it connects to.

Try un-installing the NIC in Device Manager and letting XP re-install
it.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Colin C]

I too got the same problem after SP2, everything OK up till then, PC gets IP
info from Win2003 SBS server and routes out via SMC ADSL router.after SP2,
no IP address obtainable, disabled firewall, re-loaded network card drives,
put in fixed IP settings all to no avail, de-installed SP2 and all works
perfectly.

The Microsoft MVP people all want to point at the routers or anything non
Microsoft but the problem is in SP2 nowhere else, I just wish I had the
answer.

Colin

 

[Try This]

There was one person that came up with this fix:

Subject: Possible solution for DHCP (ip address) and SP2
From: "deejay" <[email protected]> Sent: 8/30/2004
10:13:44 PM

1)
on a cmd window type
netsh int ip reset [log_file_name]

as explained here
http://support.microsoft.com/default.aspx?scid=kb;en-
us;299357

and /or

2) The registry key that must be added is as follows
(without the
brackets):

[HKLM\System\CurrentControlSet\Services\IPSec\AssumeUDPEnca
psulationContextOnSendRule
= REG_DWORD].
The value data should be set to equal 2.
You can reset the behavior to Default SP2 by changing the
Value to "0". A
value of "1" will only enable a Client
with a public (i.e.non-NAT'd) address to connect to a
NAT'd server.
The value of "2" enables both public and NAT'd clients to
connect to
a NAT'd server. The value of "2" is equal to the pre-SP2
behavior.
The key can be entered into the registry by a system's
user.

I had the problem of not getting ip address from my cable
modem (direct,
without any router) upon installing sp2.
changing of any network properties settings like "QoS
packet scheduler" or
any others would crash my internet client log -in software
(BSOD) , on
uninstalling that client software i would get ip address
and all, but no
internet connection (since the client software was not
installed)

previosly i was using sp1 without any problems for the
last 2 yrs or so (
not a single crash / BSOD of any kind)

tried the above two in sequence without rebooting so do
not know which one
helped, an hour back, now i can get ip address and can log
to the net.
(Still keeping fingers crossed)

 

[Shaun]

I have tried to uninstall the NIC and let Windows pick it
up. Still no go. Everyone has said that it works fine
with SP1 and as soon as SP2 comes around it's broken.
Sure the Limited or No Connectivity might be the cause of
a problem but nobody really knows what this problem is but
the one common thing is people with DSL or Cable modems
cannot get an IP address. I'll try the Regedit and the
other suggestions and see if that helps.

Thanks
Shaun

-----Original Message-----

 

[Colin C]

Well here is the oddest thing, Last time I got SP2 via Windows update and it
failed as described, I downloaded the full SP2 (270MB) and applied it and
guess what, eveything worked network wise.

Perhaps this will help someone

Colin

There was one person that came up with this fix:

Subject: Possible solution for DHCP (ip address) and SP2
From: "deejay" <[email protected]> Sent: 8/30/2004
10:13:44 PM

1)
on a cmd window type
netsh int ip reset [log_file_name]

as explained here
http://support.microsoft.com/default.aspx?scid=kb;en-
us;299357

and /or

2) The registry key that must be added is as follows
(without the
brackets):

[HKLM\System\CurrentControlSet\Services\IPSec\AssumeUDPEnca
psulationContextOnSendRule
= REG_DWORD].
The value data should be set to equal 2.
You can reset the behavior to Default SP2 by changing the
Value to "0". A
value of "1" will only enable a Client
with a public (i.e.non-NAT'd) address to connect to a
NAT'd server.
The value of "2" enables both public and NAT'd clients to
connect to
a NAT'd server. The value of "2" is equal to the pre-SP2
behavior.
The key can be entered into the registry by a system's
user.

I had the problem of not getting ip address from my cable
modem (direct,
without any router) upon installing sp2.
changing of any network properties settings like "QoS
packet scheduler" or
any others would crash my internet client log -in software
(BSOD) , on
uninstalling that client software i would get ip address
and all, but no
internet connection (since the client software was not
installed)

previosly i was using sp1 without any problems for the
last 2 yrs or so (
not a single crash / BSOD of any kind)

tried the above two in sequence without rebooting so do
not know which one
helped, an hour back, now i can get ip address and can log
to the net.
(Still keeping fingers crossed)

-----Original Message-----
I too got the same problem after SP2, everything OK up till then, PC gets IP
info from Win2003 SBS server and routes out via SMC ADSL router.after SP2,
no IP address obtainable, disabled firewall, re-loaded network card drives,
put in fixed IP settings all to no avail, de-installed SP2 and all works
perfectly.

The Microsoft MVP people all want to point at the routers or anything non
Microsoft but the problem is in SP2 nowhere else, I just wish I had the
answer.

Colin




.

 

[Jaykayd]

Hi
I have a SMC Barricade Wireless Router ; Sony Vaio laptop with inbuil
Wireless; XP-SP2 and a cable broadband modem. I have connection to th
internet etc with an ethernet connection, but cannot connect wirelessly
I get the 'limited or no connectivity' message. I have taken off al
firewalls, security etc to no avail.

Suggestions Appreciated

 

[murtaza]

I Have the same problem. I tried all of the thing but cannot solve th
problem.
tried winsocks xp, netsh command, firewall off, changing NICs, tr
different PCI slots, is there any way to solve this problem. Machin
cannot connect to the network. It's not take ip from dhcp. Tried t
give ip adress manual but it didn't worked.Give same ip adress an
subnet but didn't ping with other computers.
Trying for one week but couldn't ping with other computers.

Well here is the oddest thing, Last time I got SP2 via Windows updat
and it
failed as described, I downloaded the full SP2 (270MB) and applied i
and
guess what, eveything worked network wise.

Perhaps this will help someone

Colin

"Try This" (e-mail address removed) wrote in message
There was one person that came up with this fix:

Subject: Possible solution for DHCP (ip address) and SP2
From: "deejay" (e-mail address removed) Sent: 8/30/2004
10:13:44 PM

1)
on a cmd window type
netsh int ip reset [log_file_name]

as explained here
http://support.microsoft.com/default.aspx?scid=kb;en-
us;299357

and /or

2) The registry key that must be added is as follows
(without the
brackets):

[HKLM\System\CurrentControlSet\Services\IPSec\AssumeUDPEnca
psulationContextOnSendRule
= REG_DWORD].
The value data should be set to equal 2.
You can reset the behavior to Default SP2 by changing the
Value to "0". A
value of "1" will only enable a Client
with a public (i.e.non-NAT'd) address to connect to a
NAT'd server.
The value of "2" enables both public and NAT'd clients to
connect to
a NAT'd server. The value of "2" is equal to the pre-SP2
behavior.
The key can be entered into the registry by a system's
user.

I had the problem of not getting ip address from my cable
modem (direct,
without any router) upon installing sp2.
changing of any network properties settings like "QoS
packet scheduler" or
any others would crash my internet client log -in software
(BSOD) , on
uninstalling that client software i would get ip address
and all, but no
internet connection (since the client software was not
installed)

previosly i was using sp1 without any problems for the
last 2 yrs or so (
not a single crash / BSOD of any kind)

tried the above two in sequence without rebooting so do
not know which one
helped, an hour back, now i can get ip address and can log
to the net.
(Still keeping fingers crossed)

-
-----Original Message-----
I too got the same problem after SP2, everything OK up-
till then, PC gets IP-
info from Win2003 SBS server and routes out via SMC ADSL-
router.after SP2,-
no IP address obtainable, disabled firewall, re-loaded-
network card drives,-
put in fixed IP settings all to no avail, de-installed-
SP2 and all works-
perfectly.

The Microsoft MVP people all want to point at the routers-
or anything non-
Microsoft but the problem is in SP2 nowhere else, I just-
wish I had the-
answer.

Colin

"Shaun" (e-mail address removed) wrote in-
message-
Anyone else getting this? I see google groups pulls up--
a--
huge amount of info regarding this but no real solution.
I have a onboard Intel Pro 100VM and then bought a PCI
Dlink and i still do not get any IP address form the--
cable--
modem. It is NOT hardware related, it is SP2 related
100%. I've even tried to roll back to SP1 and even pre
SP1 and still nothing. SP2 does something to the
machine. Is there a solid fix yet or what?
-


.
-