- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
You may occasionally get an error message that reads "This connection has limited or no connectivity. You might not be able to access the Internet or some network resources." It indicates that your PC is having a problem trying to access your network device to connect to the Internet. Very often, a bug that typically affects Windows XP Service Pack 2 causes this error message. This bug causes a loss of your network connectivity in workstations that use Microsoft's L2TP-based VPN (virtual private networking) client to connect to the NAT-based networks. You can fix the "Limited or No Connectivity" problem in a few steps. (If your connection works but you still get the error message, go to Section 2 to learn how to disable it.)
Review the following symptoms and determine if you experience any of them after you install the Windows XP Service Pack 2:
You get the error message "Limited or No Connectivity" when you attempt to connect to your network.
You have a problem connecting to your local area network or to the Internet. You keep on receiving an error message: "Acquiring IP Address" message. If you experience these symptoms after installing Windows XP Service Pack 2, then this bug is causing the problem. In this case, go to Step 2; otherwise, skip to Section 3 Download the Microsoft patch (KB884020) from the Microsoft website. Run this update to install it. Create a registry fix by launching Notepad and typing: [HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\IPSec] "AssumeUDPEncapsulationContextOnSendRule\"=dword:00000002 Save the file as FixReg.reg to your desktop. Double-click the saved file to install it into your registry. Restart your computer and the error message will likely be gone. If you still see the error message, follow the steps in Section 2. b> If Your Connection Works But You Still Get the Error Message b> Navigate to the "Start" button and select the "Control Panel." Double-click on the "Network Connections" icon. Right-click the "Local Area Connection" icon and select "Properties" from the popup menu. Click on the "General" tab. Uncheck the option that is labeled "Notify me when this connection has limited or no connectivity." Click "OK." b> If the Patch Doesn't Fix the " Limited or No Connectivity" Problem b> Check your DSL router for any malfunctions. Re-configure or power cycle your router. Check your computer's network card configurations and network cabling to ensure that the problem does not lie here. Check your firewall to determine whether it is blocking you from connecting to the network or to the Internet. Disable the firewall and attempt connecting to the network or Internet while with the firewall is disabled. If the firewall is causing connection problems, then reset or uninstall and re-install the firewall. Reduce your connection speed to 10 Mbps and test this to determine if it fixes the problem. To do so, navigate to the "Start" menu and select the "Control Panel," "System" and "Device Manager." Review the properties of your network card. Click the "Advanced tab." Locate the "Link Speed and Duplex" section. Change the settings from "Auto Detect" to "10Mbps/Full Duplex." Hope this helps.
When you try to connect a drive that was previously connected to a Distributed File System (DFS) resource, you may receive the following error message:
System error 85 has occurred. The local device name is already in use.This error message persists for the particular drive letter in that particular Terminal Services session. The same drive letter for other Terminal Services sessions may work as expected. A different drive letter that is not typically used also works as expected. The only way to correct the issue is to restart the Terminal Services-based system. To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to obtain the latest Windows 2000 service pack (if you are using windows 2000)
This usually happens due to missing or corrupt SharedAccess reg key, which represents the Windows Firewall Service. Resolution
Download sharedaccess.reg (for Windows XP SP2 only) and save to Desktop. Then double-click the file to merge the contents to the registry. The Services entry will be created. Restart Windows (mandatory step, otherwise the following NETSH command will display an error message).
After restarting Windows, run the following from Command Prompt (cmd.exe)
NETSH FIREWALL RESET
Launch firewall applet from Control Panel, and then configure your Windows Firewall settings.
If nothing helps, as a last-resort solution (before reinstalling Windows XP Service Pack 2), give these two commands a try. Click Start, Run and type: