Woody Smith

Forgot to add this. TightVNC control of OpenSSH server computer WITHOUT SSH works. Fails with SSH tunnel.

Connection gracefully closed in Windows Domain account when run TightVNC

Describe the bug OpenSSH Server computer Windows 10, build 1903. 32 bit OpenSSH server ver 8 running in Applicaton mode with DEBUG option Only changes to SSHD_CONFIG - disable password. login using key - disable ADMIN AuthorizedKeys - change AddressFamily to inet OpenSSH Client computer Windows 10, build 1909, 32 bit OpenSSH version 8 Only item in config is - LogLevel DEBUG3 TightVNC Viewer for Windows, version 2.8.27 Windows server in Windows Domain Small Business Server 2011 All computer on same...

Ran some isolation tests. Same client computer. Same server computer. Port 22 for SSH. Port 5900 for TightVNC. Only difference is server computer logged into Windows SBS 2011 domain - SSH tunnel works, TightVNC fails. Server logged in as local account - SSH tunnel works, TightVNC works. Issue seems to be sockets. Attaching client and server logs for both domain test and local test. ssh_config and sshd_config identical for both domain test and local test. The TightVNC log files where empty both t...

Today captured SSH debug log after TightVNC tries to connect. I changed port to see if that would make a difference. excalibremanage\station02@STATION-02 C:\Users\station02.DOMAN-NAME-REMOVED>debug1: Connection to port 40200 forwarding to IP-ADDRESS-REMOVED port 40200 requested. debug2: fd 8 setting TCP_NODELAY debug2: fd 8 setting O_NONBLOCK debug3: fd 8 is O_NONBLOCK debug1: channel 2: new [direct-tcpip] debug3: send packet: type 90 debug3: receive packet: type 91 debug2: channel 2: open confirm...

Forgot to add. I am using port forwarding in the SSH command like this ssh -L 127.0.01:501xx:192.168..1.xxx:501xx name@192.168.1.xxx -P 65xx

Connection gracefully closed