Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

limited or no connectivity

Status
Not open for further replies.
Jan 24, 2005
38
US
After installing service pack 2 I get this "limited or no connectivity" message on my lan. I have found several possable fixes for this on the web, but of them work. I am Running Windows XP Home.
 
The only "valid" repair efforts are to update tcpip.sys with a Hotfix, and make a registry modification if L2TP VPN client protocals are involved:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec]
"AssumeUDPEncapsulationContextOnSendRule"=dword:00000002

See:
Everything else I have read involves using Group Policy or Network Connections to disable the message.

You should consider seriously the possibility that your physical plant - NIC, NIC drivers, cabling and/or router connection is marginal.
 
I have tried that and the registry would not except the string. I am useing a newer version of registry editor.
 
I am useing a newer version of registry editor."

And that would be what?

In any case, open a notepad session and copy/paste the below as fix_connect.reg :

*** start copy/paste below this line
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec]
"AssumeUDPEncapsulationContextOnSendRule"=dword:00000002

****** end copy/paste above this line (note the one blank line)

Double click fix_connect.reg and agree to the registry addition. Reboot and test.

 
Should make no difference as long as the total syntax is correct.

Try the copy/paste.

But the registry edit only affects L2TP VPN matters.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top