Software should struggle mightily to work and if it fails it should say why. In my case, it immediately closes without any indication as to what went wrong. I have something of the same issue as others here - client simply won't connect. Its lack of 'workingness' is astonishing to me.
I installed TigerVNC across a few machines under Windows 10 (3 machines, 2 of them virgin) and Windows 7 (1 machine). I have used variants of VNC for years and have never had much trouble. TcpSocket: Connecting to localhost port 5700ĬConn: Connected to host localhost port 5700ĬConnection: Server supports RFB protocol version 3.8ĬConnection: Using RFB protocol version 3.8ĬConnection: processing security types messageĬConnection: Server offers security type VeNCrypt(19)ĬConnection: Server offers security type None(1)ĬConnection: Choosing security type None(1)ĬConnection: processing security result message MsgWindow: created window "VNCTray" (00000000000505D0)ĭecodeManager: Creating 4 decoder thread(s) VNCSConnST: closing ::7173: Unable to connect session to Console: Access SConnection: Client requests security type None(1) SConnection: processing security type message SConnection: Client needs protocol version 3.8 SocketManager: accepting incoming connection ManagedListener: set server to 00000000016FF698
Server (please complete the following information):
If I try to connect with tightvnc the same happens but I get the message "Connection has been gracefully closed"Ĭlient (please complete the following information):.After I click connect, the viewer just closes.I try to connect to the VNC server using tigerVNC viewer.Connection gets closed right after being made on windows 10 1909