Page 1 of 1

Authentication Failed viscosity 1.3.7

Posted: Thu Jul 19, 2012 10:56 pm
by jackmullen47
every time I try to connect I am prompted for username/password and it says authentication failed

it started doing this with both my computers, and both my vpns

openvpn client lets me connect to it fine

strange - this just happened this morning - any idea whats up?

I cant run viscosity beta , as it crashes before it can even start up

cheers

Re: Authentication Failed viscosity 1.3.7

Posted: Thu Jul 19, 2012 11:11 pm
by jackmullen47
update - i downgraded to 1.3.5 and that didn't work

next I clicked Keep original certificate/key names on import and boom it works again

Re: Authentication Failed viscosity 1.3.7

Posted: Thu Jul 19, 2012 11:22 pm
by jackmullen47
jackmullen47 wrote:
update - i downgraded to 1.3.5 and that didn't work

next I clicked Keep original certificate/key names on import and boom it works again
tried that with my other computer/vpn and that solution didn't seem to work for it

strange

Re: Authentication Failed viscosity 1.3.7

Posted: Sat Jul 21, 2012 2:04 am
by James
Hi jackmullen47,

Viscosity will display an Authentication Failed message whenever the OpenVPN server sends an AUTH_FAILED message. Most of the time this means your username/password is incorrect (which is what Viscosity assumes), however it can also mean a script on the OpenVPN server's end has rejected your connection attempt. This could mean your certificate was rejected, your account has expired, etc. etc. You would need to check out the OpenVPN server's log to find out the real reason it is sending an AUTH_FAILED message.

Cheers,
James

Re: Authentication Failed viscosity 1.3.7

Posted: Tue Dec 25, 2012 6:09 am
by rsalomon
Hello all!

I wanted to add in general, in case this info helps anyone, that VPNs tend to have an issue when a domain user's password expires before they have had a chance to log in remotely. There is no mechanism for the VPN software to note that the reason auth failed is due to an expired password, and no mechanism for updating the password from the outside.

It doesn't sound like it applies to this exact situation, but it is an issue I've been burned with a couple times, as it requires someone on the inside to change the password