WinVNC crashes when client connects

[pauldurham]

I am testing TigerVNC (latest 64-bit version) between two Windows 10 Enterprise 64-bit installations in a domain. The product installs successfully on both machines but I cannot successfully remote from either one to the other.

I found that the installer does NOT create any Windows Firewall rules. I manually added an inbound rule for the server executable for all profiles, IP's, protocols & ports. (By the way, why does it not create a Windows Firewall rule automatically?)

The viewer requests the password, which it accepts, but then displays nothing and closes. No blank screen or anything else. I have the options set at their defaults, and have defined a password. I have tried between other PC's but get the exact same result.

Interestingly, I have the same issue with UltraVNC. However, TightVNC works perfectly with a default install, and it automatically creates the correct Windows Firewall rule.

Any ideas as to why TigerVNC is not working? I'd really like to be using this version.

Lastly, surely good Windows documentation would not be difficult to create for TigerVNC. Why isn't there any?

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[bphinz]

There was a linker error in the binary created for the 1.10.1 release. Please try the latest nightly build, which you can find from our homepage, and see if that works for you.

-brian

On Wed, Jan 15, 2020 at 4:28 AM Paul ***@***.***> wrote: I am testing TigerVNC (latest 64-bit version) between two Windows 10 Enterprise 64-bit installations in a domain. The product installs successfully on both machines but I cannot successfully remote from either one to the other. I found that the installer does NOT create any Windows Firewall rules. I manually added an inbound rule for the server executable for all profiles, IP's, protocols & ports. The viewer requests the password, which it accepts, but then displays nothing and closes. No blank screen or anything else. I have the options set at their defaults, and have defined a password. I have tried between other PC's but get the exact same result. Interestingly, I have the same issue with UltraVNC. However, TightVNC works perfectly with a default install, and it automatically creates the correct WIndows Firewall rule. Any ideas as to why TigerVNC is not working? I'd really like to be using this version. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#943?email_source=notifications&email_token=AB45M3LWUF25ZGIUS6GIQS3Q53JL5A5CNFSM4KHAKZT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IGJK2OQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB45M3ICCH45SMTXT4R43O3Q53JL5ANCNFSM4KHAKZTQ> .

-- Sent from Gmail Mobile

[pauldurham]

I have uninstalled all VNC products & deleted related Windows Firewall rules from both PC's.
I installed TigerVNC 1.10.80 x64 on both PC's. Again no WIndows Firewall rules were created automatically. I manually created a rule for the server allowing all IP's, ports & protocols. Shouldn't the installer do this?
I run the server with default settings & set a basic password.

• When I connect from the viewer to the server the viewer prompts for the password and then displays "read: Connection reset by peer (10054)." This is more information than 1.10.1 provides, but it still fails.

• Each time I attempt a connection from the viewer & it fails it creates an additional TigerVNC icon on the Taskbar.

• I have the Viewer encryption set to use only "TLS with anonymous certificates" and "None" authentication deselected. However, the Viewer still states "This connection is not secure".

[bphinz]

I don’t know if the installer creates firewall rules, I’d have to look at the code, but I wouldn’t be surprised if it didn’t - the Windows server is really unmaintained. Create or make the directory C:\Temp and then try starting the server from a cmd prompt with a “-Log *:file:100” and that should create a debug log that might help diagnose the problem

On Wed, Jan 15, 2020 at 6:43 AM Paul ***@***.***> wrote: I have uninstalled all VNC products & deleted related Windows Firewall rules from both PC's. I installed TigerVNC 1.10.80 x64 on both PC's. Again no WIndows Firewall rules were created automatically. I manually created a rule for the server allowing all IP's, ports & protocols. Shouldn't the installer do this? I run the server with default settings & set a basic password. When I connect from the viewer to the server the viewer prompts for the password and then displays "read: Connection reset by peer (10054)." This is more information than 1.10.1 provides, but it still fails. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#943?email_source=notifications&email_token=AB45M3PC7Z2SXDSD6BL5H5TQ53ZHBA5CNFSM4KHAKZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJABAJA#issuecomment-574623780>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB45M3KX763E4IQM24BFMCTQ53ZHBANCNFSM4KHAKZTQ> .

-- Sent from Gmail Mobile

[pauldurham]

I will attempt your above suggestion.

Two other things I have noticed:

• Each time I attempt a connection from the viewer & it fails it creates an additional TigerVNC icon on the Taskbar.

• I have the Viewer encryption set to use only "TLS with anonymous certificates" and "None" authentication deselected. However, the Viewer still states "This connection is not secure".

It is a pity the Windows TigerVNC is being neglected. No everyone wants to use RDP, especially with all its vulnerabilities ;-)

[bphinz]

I have the Viewer encryption set to use only "TLS with anonymous

certificates" and "None" authentication deselected. However, the Viewer still states "This connection is not secure". Correct. AnonDH encryption is considered insecure because there isn't non-repudiation

It is a pity the Windows TigerVNC is being neglected. No everyone wants

to use RDP, especially with all its vulnerabilities ;-) Agreed, we've been keeping it in the hopes that someone would come along and support it but I'm not optimistic about that. Note that it's only the windows server that's unmaintained. The native viewer is cross-platform and actively developed/supported.

…

On Wed, Jan 15, 2020 at 7:59 AM Paul ***@***.***> wrote: I will attempt your above suggestion. Two other things I have noticed: - Each time I attempt a connection from the viewer & it fails it creates an additional TigerVNC icon on the Taskbar. - I have the Viewer encryption set to use only "TLS with anonymous certificates" and "None" authentication deselected. However, the Viewer still states "This connection is not secure". It is a pity the Windows TigerVNC is being neglected. No everyone wants to use RDP, especially with all its vulnerabilities ;-) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#943?email_source=notifications&email_token=AB45M3MJZHYRSZMBPAS5FIDQ54CDHA5CNFSM4KHAKZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJAHHMI#issuecomment-574649265>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB45M3JD2LT5KMM7JJKEDKDQ54CDHANCNFSM4KHAKZTQ> .

[pauldurham]

Result of the log file output: Note that the server appears to crash / shut down after attempting to connect from the Viewer & entering the password.

Wed Jan 15 15:21:11 2020
Config: set immutable Log
VNCServerST: creating single-threaded server IZAN5LSL2X
Registry: duplicated FFFFFFFF80000001 to FFFFFFFF80000001
Registry: createKey(FFFFFFFF80000001,Software\TigerVNC\WinVNC4) =
0000000000000240
MsgWindow: creating window "VNCTray"
Registry: RegCloseKey(FFFFFFFF80000001)
RegConfig: registry changed
Config: set Password(Binary) to dbd83cfd727a1458
Config: set SecurityTypes(String) to VeNCrypt,TLSVnc
Config: set QueryConnect(Bool) to 1(1)
Config: set QueryOnlyIfLoggedOn(Bool) to 0(0)
Config: set DisconnectAction(String) to None
Config: set RemoveWallpaper(Bool) to 0(0)
Config: set DisableEffects(Bool) to 0(0)
Config: set PortNumber(Int) to 5900
Config: set IdleTimeout(Int) to 0
Config: set LocalHost(Bool) to 0(0)
Config: set Hosts(String) to +,
Config: set AcceptKeyEvents(Bool) to 1(1)
Config: set RawKeyboard(Bool) to 0(0)
Config: set AcceptPointerEvents(Bool) to 1(1)
Config: set AcceptCutText(Bool) to 1(1)
Config: set SendCutText(Bool) to 1(1)
Config: set DisableLocalInputs(Bool) to 0(0)
Config: set DisconnectClients(Bool) to 1(1)
Config: set AlwaysShared(Bool) to 0(0)
Config: set NeverShared(Bool) to 0(0)
Config: set UpdateMethod(Int) to 0
Config: set PollConsoleWindows(Bool) to 1(1)
Config: set UseCaptureBlt(Bool) to 1(1)
RegConfig: unable to process UseHooks
Config: set Protocol3.3(Bool) to 0(0)
ManagedListener: set server to 0000000001A4F6C8
ManagedListener: set port to 5900
MsgWindow: null _this in 00000000000B0A4A, message 24
MsgWindow: null _this in 00000000000B0A4A, message 81
ManagedListener: set filter to +,
MsgWindow: null _this in 00000000000B0A4A, message 83
VNCServerWin32: Refreshing tray icon
VNCServerWin32: Entering message loop
MsgWindow: created window "VNCTray" (00000000000B0A4A)

Wed Jan 15 15:21:30 2020
SocketManager: accepting incoming connection
TcpSocket: ACCEPT 10.90.141.219
Connections: accepted: 10.90.141.219::65175
SConnection: reading protocol version
SConnection: Client needs protocol version 3.8
SConnection: processing security type message
SConnection: Client requests security type VeNCrypt(19)
SConnection: processing security message
SConnection: processing security message
SConnection: processing security message
SConnection: processing security message
SVeNCrypt: Client requests security type TLSVnc (258)
TLS: Process security message (session 0000000000000000)
TLS: Anonymous session has been set
TLS: Deferring completion of TLS handshake: Resource temporarily
unavailable, try again.
SConnection: processing security message
TLS: Process security message (session 0000000004B7BB90)
TLS: Deferring completion of TLS handshake: Resource temporarily
unavailable, try again.
SConnection: processing security message
TLS: Process security message (session 0000000004B7BB90)
TLS: TLS handshake completed with
(TLS1.2)-(ANON-ECDH)-(AES-256-CBC)-(SHA1)

Wed Jan 15 15:21:33 2020
SConnection: processing security message
VNCServerST: starting desktop
SDisplay: starting
SDisplay: Attaching to virtual desktop
SDisplay: deleting old pixel buffer & device
SDisplay: creating pixel buffer
DeviceContext: 32-bit BitFields: (ff0000, ff00, ff)
DIBSectionBuffer: recreateBuffer()
MsgWindow: creating window "rfb::win32::SDisplayCorePolling"
MsgWindow: null _this in 00000000000509DA, message 24
MsgWindow: null _this in 00000000000509DA, message 81
MsgWindow: null _this in 00000000000509DA, message 83
MsgWindow: created window "rfb::win32::SDisplayCorePolling"
(00000000000509DA)
SDisplayCorePolling: setScreenRect
SDisplay: Started Polling
MsgWindow: creating window "WMMonitor"
MsgWindow: null _this in 0000000000140814, message 24
MsgWindow: null _this in 0000000000140814, message 81
MsgWindow: null _this in 0000000000140814, message 83
MsgWindow: created window "WMMonitor" (0000000000140814)
MsgWindow: creating window "Clipboard"
MsgWindow: null _this in 00000000000609EA, message 24
MsgWindow: null _this in 00000000000609EA, message 81
MsgWindow: null _this in 00000000000609EA, message 83
MsgWindow: created window "Clipboard" (00000000000609EA)
Clipboard: local clipboard changed by 0000000000120B64
Clipboard: no clipboard notifier registered
Clipboard: registered clipboard handler
SDisplay: started
DeviceFrameBuffer: drawing cursor outline!

[bphinz]

I don't have access to a Win10 machine to try to replicate this right now. The fact that a connection is made and the TLS handshake begins suggests to me that it's not a firewall issue.

I looked at the InnoSetup script and the installer does not create firewall rules. I don't have much experience with Windows installers but a quick google search turns up lots of examples so I don't mind trying to add that.

[bphinz]

Take a look at #507 the OP shows a log from a client that doesn't support Anonymous DH ciphers and the debug log has those same "TLS: Deferring completion of TLS handshake: Resource temporarily
unavailable, try again." messages. Can you please try X509none with some self-signed certs and see if that works? Are you using our client?

[pauldurham]

Unfortunately I don't have the knowledge at the moment to create self-signed certs. I have been using the TigerVNC client.
One thing I did note when I was testing at home is that Windows 10 has an associated "Network profile" for every connection (Domain, Private, Public) and that if either one or both sides have their Network profile set to "Public" then communication between the server & client is blocked. This may have something to do with the blocked connections.
Unfortunately I don't have the time right now to continue testing but this information may be of some use.

[dbolton]

@pauldurham I finally got TigerVNC working between two Windows machines. I fully documented the process. See if the following instructions help you: https://github.com/TigerVNC/tigervnc/wiki/Setup-TigerVNC-server-(Windows)

[lbsfei]

i used the tigervnc64-1.10.80.exe ,but still cann't connection between two windows10. pls help.

@pauldurham I finally got TigerVNC working between two Windows machines. I fully documented the process. See if the following instructions help you: https://github.com/TigerVNC/tigervnc/wiki/Setup-TigerVNC-server-(Windows)

[dbolton]

@lbsfei In order to help, we need more information. Did you get any error messages? How far did you get on the Troubleshooting section? Are you using any other remote desktop or VNC software besides TigerVNC?