First, upgrade to the 2.1 final release. 2.0.91 (2.1 beta2) has lots of bugs that were fixed. Always try the latest version before reporting that something doesn't work.
Secondly, provide more details about exactly what you are trying to do. What type of authentication are you attempting (VNC password? PAM? X.509?) Are any error messages displayed? Describe the failure in detail. On 11/14/16 11:03 AM, [email protected] wrote: > Hello, > > I'm having problems authenticating to my turbovnc server. > It used to work, then it stopped, for unknown reasons. > > This is what I tried so far: > - re-running vncpasswd > - verifying selinux is in permissive mode > - restarting the turbovnc server > > Can I run the server in some verbose logging mode? > > this is the command I use at the client > /opt/TurboVNC/bin/vncviewer 192.168.201.66::5902 > > the rpm I use at the server: > Name : turbovnc > Version : 2.0.91 > Release : 20160315 > Architecture: x86_64 > Install Date: Thu 04 Aug 2016 10:54:17 PM CEST > Group : User Interface/Desktops > Size : 6888873 > License : GPL > Signature : DSA/SHA1, Wed 16 Mar 2016 01:08:45 AM CET, Key ID > 6bbefa1972feb9ce > Source RPM : turbovnc-2.0.91-20160315.src.rpm > Build Date : Wed 16 Mar 2016 01:08:33 AM CET > Build Host : bullwinkle > Relocations : (not relocatable) > URL : http://www.TurboVNC.org > Summary : A highly-optimized version of VNC that can be used with > performance-critical applications > > The machine is Fedora 25, but turbovnc stopped working on Fedora 24. > > ------------------------------------------------------------------------------ _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
