#180 Error: Connection has been gracefully closed

[Steve Williams]

Been using tight VNC for many years it is a great product. Have installed it on many computers without issue until today. Got a new laptop and installed the version 2.8.27 to match my desktop. I use the Tight VNC Viewer on my Desktop computer to connect to a few computers in my office. I can connect to all of them fine except for the new laptop. The hostname for the laptop is Sales-LT2 I use the Port 2500 for the Main Server port on the laptop Tight VNC Service Configuration dialog. On my desktop I open the TightVNC Viewer and use "SALES-LT2::2500" to connect and I get a notification dialog that reads "Connection has been gracefully closed" I cthen click the ok button and the dialog closes and thats all I get. I looked at the firewall settings on the laptop and it shows that the TightVNC application is allowed through Domain, Public & Private. What are my next steps? The laptop is using Windows Professional version 1909 with all updates current as of 5/6/2020 OS Build 18363.815

My local network is on a local domain using an OPNSense router/firewall device. But since I'm trying to connect a local computer to a local computer that device should not interfer. It hasn't with any other computers that I connect to.

I have attached two logs from C:\Programdata\TightVNC Directory

What is my next step in solving this issue? Any help with this would be greatly appreciated.

[Steve Williams]

I should also note that I used the laptop Ip address as well in the TightVNC Viewer like "10.14.1.60::2500" and that produced the same result.

[Steve Williams]

Ok So another thing that I forgot to mention is that TightVNC Service Configuration dialog on the Access Control tab, there is Rules box. I have two rules set up in this box the 1st rule was Deny 0.0.0.0 to 255.255.255.255 and then I added an Allow rule 10.14.0.0 to 10.14.7.255 for our local domain. What I did not realize when I added these two rules is that it makes a difference of the order that thay are added. I added the Deny rule 1st the the Allow rule. This was backwards, 1st you have to add the Allow rule, then the Deny rule. Otherwise it blocks everything. This is why I could not connect. This is a good lesson in following documented procedure to the letter and why it is important. I wasted two days on this to discover it was an error that I made myself. Hope this helps others that may come across this same thing.

[Anton]

Hi!
first uninstall, clean HKLM\software\TightVNC\Server
reinstall and try to make connection from the same computer (enable Allow loopback in configuration), set loglevel 9 and send the log to support@tightvnc.com

[Steve Williams]

@anton19286 If you read my previous message, you will see that I have it working now. I had my allow and deny rules out of order and that is what was causing the issue. Since I moved the allow rule to the top of the list everyting works fine now.