Watchguard VPN Issues: Same VPN credentials fail from different user account on same PC.

Hi guys,

I have an XP pro machine on a remote site that uses Watchguard Mobile VPN client to establish a connection back to our head office.

It all works perfectly on the existing user account (UserA) except now I have created a new user account (UserB) on the remote PC I cant use  any VPN credentials to establish a VPN connection from the new computer when in UserB's account.

However I can still establish a VPN connection using UserA's VPN credentials when logged into UserA's account, as well as UserB's VPN credentials from UserA's account on the remote PC.

So it would appear that there is some authentication issue withe the new UserB's account on the PC that is preventing the VPN connection from succeeding. It always hangs and fails at the same point. It appears to be when it gets the configuration from the VPN server, but here is a copy of the log.

2011-09-07T12:46:23.452 Launching WatchGuard Mobile VPN with SSL client. Version 11.2.0 (Build 252737)  Built:Dec 21 2009 13:20:49
2011-09-07T12:46:27.686 Requesting client configuration from VPNSERVER:443
2011-09-07T12:46:30.733 FAILED:inflate returned -3
2011-09-07T12:46:32.202 CreateProcess cmd="C:\Program Files\WatchGuard\WatchGuard Mobile VPN with SSL\openvpn.exe" --config client.ovpn --verb 3 --management 127.0.0.1 1337 --service wgsslvpnc_ExitEvent --management-query-passwords --management-hold
2011-09-07T12:46:34.811 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:46:38.421 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:46:42.358 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:46:46.515 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:46:50.452 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:46:54.171 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:46:57.780 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:01.499 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:05.108 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:08.608 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:12.108 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:15.608 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:19.108 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:22.608 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:26.327 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:30.265 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:34.311 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:38.358 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:42.077 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:45.921 Error: connect() failed. ret = -1 errno=10061
2011-09-07T12:47:45.921 Failed Launch

Any help would be greatly appreaciated.
defectaAsked:
Who is Participating?
 
defectaConnect With a Mentor Author Commented:
i have since fixed a different problem that means this new VPN connection is no longer needed so other than the sake of my education, I no longer "need" an answer as I have a workaround.
0
 
dpk_walCommented:
I think you are using extended authentication [Authenticating users with servers like AD/LDAP/RADIUS]; have you added userB to the same group as to which user A belongs; other that I cannot think of anything else that would cause such a behavior.

Please check and update.

Thank you.
0
 
dpk_walCommented:
Please ahead and close the question; was typing out the response so did not see that you have posted a comment.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
defectaAuthor Commented:
sure thing. but for the sake of practice I would like to ask for clarification.

We are authenticating against AD. Can you explain how in the the scenario you outlined, one account can make VPN connections successfully and the other cant, using the same VPN credentials? Im not following.
0
 
dpk_walCommented:
Case I:
Let's say you have created a group named Allow_VPN on AD which has userA added as member; but userB is not added as member; on WG when you configure xauth you specify the exact group/user name. I think this is what is happening.

Case II:
If the issue is when you are logging as userA on the local machine [which is not part of AD] you can connect but when you login as userB from same laptop and connect using same VPN credentials then this is something strange.
If there is a change in permissions, userA is power user and userB is not it could be something, but if no then am not sure.
Also, if both users A and B are part of AD then case I might be applicable.

I was only talking about case I and not about case II.

Thank you.
0
 
defectaAuthor Commented:
Ii have both UserA and UserB members of the AD group that allows VPN access through Watchguard.
Both users are local admin on the remote machine and both are users on the AD domain.

frustrating, oh will. good thing I dont need an answer anymore. Thanks anyway.
0
 
BrianCommented:
It sounds like the Watchguard Mobile VPN client was not working correctly on User Bs account. When it was installed it may have been installed for only one user, instead of under the administrator account. Just a thought.
0
 
defectaAuthor Commented:
as I mentioned, a different issue in a different user account was requireing me to establish a new VPN connection in a new account but the original issue was resolved leaving me longer requiring a solution to this issue.

Thanks for everyones insights however.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.