Hide Forgot
Description of problem: NM failed to connect to vpnc - and was just giving all the time only message about failed connection. After configure /etc/vpnc/default.conf to be able to use 'vpnc' command line - it's been pretty simple to log in - as the command line provided simple query to insert next token. == S5.3 type-is-xauth check [2011-02-23 18:42:12] S5.4 xauth type check [2011-02-23 18:42:12] Wait for token to change, then enter the new tokencode: === Version-Release number of selected component (if applicable): NetworkManager-gnome-0.8.2-8.git20101117.fc15.x86_64 NetworkManager-glib-0.8.2-8.git20101117.fc15.x86_64 NetworkManager-vpnc-0.8.1-1.fc14.x86_64 NetworkManager-debuginfo-0.8.2-8.git20101117.fc15.x86_64 NetworkManager-0.8.2-8.git20101117.fc15.x86_64 How reproducible: One probably needs to get out of sync with i.e. RSA SecureID. Any futher login seems to fail without giving any hint how to fix problem. Command line tool doesn't have such problem. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I've run into the same issue, but only saw the "Wait for token to change" text when running vpnc with --debug=3 (didn't try 1 or 2 here, but didn't see it before using this option).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This is getting worked on finally, thanks for the output Nils; now I don't have to go reproduce it with the new tokens somehow :) *** This bug has been marked as a duplicate of bug 655882 ***