Hello,

I am running Turbo VNC server, version 2.0.1, with options  -dontdisconnect 
and -nevershared.   My client accesses the server through a VPN tunnel with 
dynamically assigned IP address.

In the first VPN session the client address was 10.202.110.51.  The VPN 
connection failed due to some network glitch while I was using VNC and 
broke the client-server connection.

I established a new VPN session, but the second time the host was assigned 
a different IP address which was 10.202.110.53.   Attempts to reconnect to 
the VNC server with the new IP address produce this error.

05/02/2018 18:05:27 Got connection from client 10.202.110.53
05/02/2018 18:05:27   (other clients 10.202.110.51)
05/02/2018 18:05:27 Using protocol version 3.8
05/02/2018 18:05:27 Enabling TightVNC protocol extensions
05/02/2018 18:05:29 Full-control authentication enabled for 10.202.110.53
05/02/2018 18:05:29 -dontdisconnect: Not shared & existing client
05/02/2018 18:05:29   refusing new client 10.202.110.53
05/02/2018 18:05:29 Client 10.202.110.53 gone
05/02/2018 18:05:29 Statistics:
05/02/2018 18:05:29   framebuffer updates 0, rectangles 0, bytes 0

Evidently the server fails to recognize that the connection to 
10.202.110.51 is no longer valid.   How can I reconnect to the existing 
session?  Is there a way to tell the server that 10.202.110.51 is gone, so 
that the VNC session can be continued?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/turbovnc-users/4e425955-42c4-4d7e-884d-bea1b39a4b56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to