Connection has been gracefully closed (Windows 10 only)

Brought to you by: anton19286, const_k, crazy-walrus

#1395 Connection has been gracefully closed (Windows 10 only)

Milestone: None

Status: open-accepted

Owner: Anton

Labels: None

Priority: 5

Updated: 2017-03-07

Created: 2016-10-26

Creator: Joe

Private: No

tvnserver.exe 2.8.5 is the problem. I tried using tnviewer of previous version 2.7.10.0 and 2.8.5 and both show the message "Connection has been gracefully closed" when connecting to a windows 10 host that is using tvnserver.exe version 2.8.5. If the host computer has not had a user log into it yet such as after a reboot or when the computer is first turned on, I will get this error message. If I log on to the computer via Remote Desktop or walk over to the computer and log in locally, and then use tightVNC, I no longer get that error and it works fine. It is only a problem when no one has longged into the machine before trying to use Tight VNC.

I went back to using tvnserver.exe version 2.7.10.0 and it is working fine with no errors. This must be a bug with the newer version. I have tried these scenarios with Windows 7 and Windows Vista, with both having the new verison of tvnserver.exe 2.8.5 and they have no problems. It is only on the Windows 10 PCs that are having this issue but only if they are using the latest version 2.8.5 tvnserver.exe.

Discussion

Anton - 2016-10-27

Sorry, can't reproduce the issue. I have 2.8.5 64bit server installed on Windows10 Pro and can connect to login screen remotely just after reboot. I'll try to investigate it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anton - 2016-10-27

status: open --> open-accepted

assigned_to: Anton

Group: -->
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Joe - 2016-10-27

I'm sorry I should have specified my version was 32 bit. Even though I am on a 64 bit.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Bob White - 2017-02-07

I can confirm that 32 bits versions on 64-bit Windows 10 Home fails as well. I even loaded 2.8.2 and it had the same problem as well. Specifically the problem happens when the all users are logged out. You can even have an existing VNC session and if you log off you get kicked off.

It seems to me that the failure occurs in WinDxgiOutput1. The program never advances past the dxgiOutput->queryInterface call.

Failure_32.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anton - 2017-02-08

please, try this version

tightvnc-2.8.7-gpl-setup-32bit.msi

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Bob White - 2017-02-10

I can confirm that version works. Worked when logging out, worked before any logins had occured.

Just curious what the solution was.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Anton - 2017-02-11
  
  Actually its just rollback to 2.7.10 version in output duplication (fast d3d screen capturing) part. The issue for two monitors on two different video cards on Windows8 still exists. Win10 and Win8 with displays connected to the same card works fast now.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ian Finlay - 2017-03-07

FYI: I have been experiencing "gracefully closed" on a couple of connections:
TightVNC Viewer v2.8.5 (23Sep2016 13:00:27) 64bit on Windows 10
TightVNC Server v2.7.10 (23Sep2016 13:00:27) 64bit on Window7 Embedded SP1

I just tried 2.7.10 64 bit on both Server + Viewer ...
I have just setup one additional Viewers that is on the local subnet to the TightVNC Server PC, now running 2.7.10 Viewer
My remote Viewer is using Cicso Anyconnect VPN tunnel and I can ping TightVNC Server PC
Reply from 10.36.35.231: bytes=32 time=360ms TTL=120 now running 2.7.10 Viewer

The local Viewer (w.r.t. TightVNC Server) still shows "closing gracefully",
The remote Viewer now shows: **"Failed to recv data from socket"

Last edit: Ian Finlay 2017-03-07

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.