-
April 30th, 2007, 02:51 PM
#1
Registered User
Error connecting to VPN
I have a user that is having problems with our VPN. When they try to connect, this is the error message they receive:
TCP/IP CP reported error 2. The system cannot find the file specified.
I have looked at numerous MSKB articles involving looking through the registry and have tried these, but nothing seems to work. i still get this error message.
Has anyone come across this error while trying to connect to a VPN?
I think the problem is either an ID10T or PEBCAK error
-
May 1st, 2007, 02:34 AM
#2
Registered User
2x info below. hope it helps!
__________________________________________________ ______________
This error may be intermittent, and is usually caused by a problem in the registry. If your system's Control Panel-> System -> Hardware -> Device Manager lists a network adapter that is not present in the system, this error can occur. You may not be able to remove the phantom adapter with normal tools in which case editing the registry is required.
You might be able to solve the problem by checking/changing the order of 'Adapters and Bindings' in Control Panel->Network Connections -> Advanced Menu item -> Advanced Settings: put (Remote Access Connections) at the top of the Connections list.
If this does not help, you will need to edit the registry. The phantom network adapter and all references to it need to be deleted. See the following Microsoft Knowledge Base Articles for more information:
MS KB 169116
MB KB 165846
If deleting the phantom adapter does not help (or you cannot find a phantom adapter), you may need to remove and reinstall remote access service (RAS), other installed network adapters, and all installed network protocols.
info found here:
http://www.modemsite.com/56k/duns-tcpip2.asp
__________________________________________________ _________
After some hardware (network adapter) changes connecting with VPN from Windows (WinXP) to a server suddenly raised this error.
No help was found in the web that was solving it.
So I installed a new XP and compared the registry data of working and non working versions.(I'm not really familar with networking at all)
I found one single change that solved the problem for me:
(I'm not sure if this is working in other cases too)
In
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\D hcp\Parameters
there are one or more REG_BINARY values witha long (GUID?) name in brackets { }
Copy one of the bracket names (not sure wich) into clipboard.
e.g. {A2F5650E-D377-4A0A-9C90-784ED1EA5A92}
Make a new Key under
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\N etBT\Parameters\Interfaces\
With that name and 'Tcpip_' in front of it:
e.g. "Tcpip_{A2F5650E-D377-4A0A-9C90-784ED1EA5A92}"
Perhaps a MULTI_SZ (Multi-String_Value) with the name
"NameServerList" is needed under that new key too.
Please don't ask me why this works or why that problem occurs but it works for me. Perhaps there are easier ways.
info found here: http://www.tek-tips.com/viewthread.c...1199801&page=1
__________________________________________________ ______________
Mr Miyagi, by any other name... (is this sig short enough?)
Similar Threads
-
By wuter in forum Networking
Replies: 0
Last Post: April 12th, 2007, 01:04 AM
-
By amp10000 in forum Windows NT/2000
Replies: 0
Last Post: April 13th, 2004, 11:10 AM
-
By snooper2 in forum Networking
Replies: 4
Last Post: August 23rd, 2002, 06:29 PM
-
By deh1217 in forum Networking
Replies: 1
Last Post: November 1st, 2001, 03:37 PM
-
By Hell_Fire in forum Windows NT/2000
Replies: 0
Last Post: July 6th, 2001, 06:51 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks