Please try the 1.2.2 release candidate: http://www.turbovnc.org/DeveloperInfo/PreReleases
I think you're running into an issue that existed in 1.2.1 and prior but which I fixed in 1.2.2. The Windows viewer was making some of the unexposed (command-line-only) parameters persistent. Thus, if someone ran vncviewer.exe with the /nounixlogin argument, this would not only turn off Unix login authentication for the current connection, but it would turn it off for subsequent connections to the same VNC server session. The only way to turn it back on was to pass /user to vncviewer.exe. In this version of TurboVNC, only the parameters that are exposed in the GUI are made persistent between connections. The command-line parameters are one-time-use only. On 10/21/14, 4:39 PM, Paul McIntosh wrote: > Hi All, > > Anyone having trouble with Windows client pam-userpwd authentication? > > > On our cluster we have a manual method - ssh tunnel to a node and pam-userpwd > to login in. We also have an automated method using keys and otp through a > launcher app. > > I have been using the automated method for a while so I don't know when our > manual method broke but I'd like it unbroke for emergency/testing purposes :) > > It looks like the Windows client is not recognising the login protocol, a > Linux client works fine and asks for username/password, but the Windows > client only asks for password (username field is blocked out) > > > Here's the config: > > /etc/turbovncserver-auth.conf > pam-service-name = login > permitted-auth-methods = pam-userpwd, otp > > Here's the log messages (not it fails with KDE also) > > 22/10/2014 08:36:50 Got connection from client 172.19.1.251 > 22/10/2014 08:36:50 Using protocol version 3.8 > 22/10/2014 08:36:51 Enabling TightVNC protocol extensions > > ** (gnome-volume-control-applet:3454): WARNING **: Connection failed, > reconnecting... > > ** (gnome-settings-daemon:3434): WARNING **: Connection failed, > reconnecting... > 22/10/2014 08:36:55 rfbVncAuthProcessResponse: authentication failed from > 172.19.1.251 > 22/10/2014 08:36:55 Client 172.19.1.251 gone > 22/10/2014 08:36:55 Statistics: > 22/10/2014 08:36:55 framebuffer updates 0, rectangles 0, bytes 0 > > ** (gnome-settings-daemon:3434): WARNING **: Connection failed, > reconnecting... > > > Here's the full description of the manual method working: > https://www.massive.org.au/userguide/cluster-instructions/using-the-massive-desktop > > Snippet below: > > "To access the desktop first create a secure tunnel to m2106 > > Windows Putty Terminal: > 1) Right-click on Window border and select Change Settings... > 2) Select Connection-SSH-Tunnels > 3) Remove any existing tunnels to port 5901 > 4) Add a new tunnel to Source port 5901 Destination m2106:5901 > > Linux/Max Shell: > 1) Start a new login to MASSIVE using the following command > ssh -L 5901:m2106:5901 [email protected] > > Now connect using your local TurboVNC client to connect to localhost:1 > and use your MASSIVE login details." > > Cheers, > > Paul > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
