#29 Connection gracefully closed in Windows Domain account when run TightVNC

[Woody Smith]

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 network for testing
SSHD_CONFIG, CONFIG, RSA key files are identical in all tests.

Trying to use TightVNC with OpenSSH in Windows computer with windows domain login.
TightVNC fails in domain login. TightVNC works in non-domain login.

Expected behavior
TightVNC to connect through OpenSSH tunnel from OpenSSH Client computer to OpenSSH Server computer

Additional Comments
If OpenSSH Server computer login into Windows as local account (ie: no domain)
OpenSSH tunnel opens, and TightVNC connects

If OpenSSH Server computer login into Windows as DOMAIN account
OpenSSH tunnel opens, and TightVNC fails.
Dialog Box at client with msg "Connection has been gracefully closed"
Error in OpenSSH debug
debug3: socketio_getsockopt - ERROR:10022
debug1: getsockopt TCP_NODELAY: Invalid argument

OpenSSH server and client debug files attached.

Question
Is this OpenSSH not handling Windows sockets in a standard way when logged in to a Windows Domain account
or
Is this an issue in TightVNC?