indigo6
asked on
Windows 7 VPN Client Does Not Connect, Error 2250
Hello,
I have a linksys RV042 that I am using as a PPTP VPN server. There is a machine that cannot connect to the VPN with error 2250. The connection fails at the Verifying Username and Password phase, but I know the username and password is correct. I have also tried the connection on multiple networks, and the same thing happens. I have also tried using the same connection on a different computer, and everything works well. Also, when trying to open the property sheet for the VPN connection, or when trying to change the password in the connect dialog box, it is extremely slow.
Thank you!
I have a linksys RV042 that I am using as a PPTP VPN server. There is a machine that cannot connect to the VPN with error 2250. The connection fails at the Verifying Username and Password phase, but I know the username and password is correct. I have also tried the connection on multiple networks, and the same thing happens. I have also tried using the same connection on a different computer, and everything works well. Also, when trying to open the property sheet for the VPN connection, or when trying to change the password in the connect dialog box, it is extremely slow.
Thank you!
To confirm, the VPN works for other clients but not from one particular machine?
A time out waiting for authentication can be due to blocked GRE. If other clients can connect then the problem is not at the server end, but could be at the client end. This can be due to the client's ISP or router, but you say you have tried other networks, so that would likely indicate security software on the connecting PC. Some that often cause problems are Norton/Semantic, Trend Micro, and OneCare, though problems have been reported with many others. Can you disable or uninstall any security software? I would also recommend testing with a wired connection, rather than wireless, until working.
A time out waiting for authentication can be due to blocked GRE. If other clients can connect then the problem is not at the server end, but could be at the client end. This can be due to the client's ISP or router, but you say you have tried other networks, so that would likely indicate security software on the connecting PC. Some that often cause problems are Norton/Semantic, Trend Micro, and OneCare, though problems have been reported with many others. Can you disable or uninstall any security software? I would also recommend testing with a wired connection, rather than wireless, until working.
>> I also get error 829 in the application log
What is the source for this 829 error?
What is the source for this 829 error?
....and is it 829? I have never heard of that error with VPN's. Usually it is; 800, 721, 691, or less common; 649, 720, 733, 734, 806, 807, 812. However you are not connecting to a Windows PPTP server so the errors may be different.
ASKER
I suppose the errors could be different, but it is windows' built in VPN client causing the issue.
It can be due to a negotiation issue, try in the VPN client properties, under the security tab, changing the type from automatic to PPTP.
Have you tried disabling the security software as mentioned?
Have you tried disabling the security software as mentioned?
@indigo6: What is the source for this 829 error?
Post some details from the event log if possible.
Post some details from the event log if possible.
Any feedback indigo6? Difficult for us to assist further until you respond to the suggestions and questions we have put forward.
Thanks.
Thanks.
I have the same exact issue as indigo6. A laptop, which is a Windows 7, would toss this error 2250 after an excruciatingly slow process of trying to connect to a PPTP VPN server (WatchGuard). No other laptops or computers are having any issues connecting to the same VPN server. Everything regarding the process of connecting or even pulling up properties is met with a very sluggish performance. I ran a PRO version of Malwarebytes scan and it found only one infection, but while it was scanning the Microsoft Security Essentials discovered a bunch of viruses and cleaned them up. I suspect that this whole thing is due to some nasty virus cocktail that has inserted itself into the TCP/IP or the windows authentication protocol stack. It always fails after trying to verify the user name and password, which should get verified after "All devices connected" message is displayed. I tried switching from WiFi to the standard Ethernet cable connection, but to no avail. I also tried running the "netsh int ip reset resetlog.txt" at the admin command prompt, rebooted the machine and it still errors out. I restarted the client's AT&T DSL modem and it still did the same thing. I'm at the end of my wits on this one, except that I haven't tried the ComboFix yet. I can supply more logs later on this evening if anyone cares to respond to this message by then. Any suggestions?
Thank you!
Thank you!
Hi Croatlan.
Experts-Exchange protocol dictates that you must open your own question, if for no other reason that it will shine a fresh light on it. However I would suggest including a link to this question so people can view the similarities and see if there is a pattern or common element.
--Rob
Experts-Exchange protocol dictates that you must open your own question, if for no other reason that it will shine a fresh light on it. However I would suggest including a link to this question so people can view the similarities and see if there is a pattern or common element.
--Rob
ASKER
Hi All,
Sorry, I have been away from this problem for a while, since it's a remote employee. The internet at the remote office went down as well so I have been unable to remote in and get the logs. I will post back as soon as I have more info.
I was thinking though, is there a way to "reset" the network stack in Windows 7 short of reinstalling the OS? sfc doesn't seem to do it.
Thanks!
Sorry, I have been away from this problem for a while, since it's a remote employee. The internet at the remote office went down as well so I have been unable to remote in and get the logs. I will post back as soon as I have more info.
I was thinking though, is there a way to "reset" the network stack in Windows 7 short of reinstalling the OS? sfc doesn't seem to do it.
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Duly noted, Mr. RobWill. Thanks!
ASKER
Thanks RobWill,
Will that reset the VPN components as well?
Will that reset the VPN components as well?
Good question, I have never checked, but by definition of what it does, it should. It will wipe any wireless settings too.
indigo6, if you're referring to the command "netsh int ip reset resetlog.txt" I can tell you that in my case it made no difference.
ASKER
Ok, it looks like the built in client still has issues. At this point, I'm thinking of doing an SSL VPN instead.
The RV042 doesn't support an SSL VPN, but t's not a bad idea, however it sounds like an underlying TCP/IP stack issue which may affect more than just PPTP.
Have you tried the Linksys IPSec QuickVPN client for that machine? Having said that the QuickVPN can be problematic.
Have you tried the Linksys IPSec QuickVPN client for that machine? Having said that the QuickVPN can be problematic.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Good to know. There have been many VPN conflicts with Norton/Symantec, One Care, Trend Micro, and others so it is possible. However, I have 4 VPN clients and Security Essentials on this workstation, and no problem.
I wonder if it may have to do with sequence. If Essentials is installed first a rule may be automatically added when the VPN is created, but in the reverse sequence that may not be the case.
I wonder if it may have to do with sequence. If Essentials is installed first a rule may be automatically added when the VPN is created, but in the reverse sequence that may not be the case.
this has been driving me nuts for weeks.
I added C:\Windows\tracing to the Microsoft Security Essentials exceptions list and it worked immediately.
Thanks indigo6
I added C:\Windows\tracing to the Microsoft Security Essentials exceptions list and it worked immediately.
Thanks indigo6
ASKER
It seems as though there are multiple things that can cause this. So I'm marking multiple solutions as such.
ASKER