Fix for File transfer failure after 1.0.1 Server upgrade

[edward]

After upgrading a couple of our UltraVNC servers to v1.0.1 we found that File Transfer failed with a message something like "Connect failed, the remote server has file transfer disabled". On investigation we found that, on the contrary, file transfer was enabled on the server.

However, after some searching around I found reference to a "User Impersonation option" which "limits remote file system access to identified Windows users only". In other words, with this option enabled, you have to be using one of the new MS Logon modes with a windows username recognized in the VNC server or its associated domain.

Since we don't use the MS Logon options we would not expect this to be a problem, but it appears that in v1.0.1 the the "User Impersonation option" is on by default unless disabled by adding a new registry entry.

I have encapsulated the solution into a .reg file which we now use on any UltraVNC server that refuses to participate in File Transfer, so far with impressively consistent results.

We placed the following text into a suitably named reg file, e.g. "FixUltraVNC101FileTransferFailure.reg", saved the file, double clicked on the file to set the necessary registry entries, restarted, then tried the File Transfer again.

Comments, corrections, and admonishments welcomed. The REGEDIT4 format has been used to ensure compatibility with most of the Windows OSs. N.B. The two blank lines at the end are important.

==================== Begin ====================
REGEDIT4

[HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\Default]
"FileTransferEnabled"=dword:00000001
"FTUserImpersonation"=dword:00000000


==================== End =======================

[RenStar]

Someone should add this to the readme or FAQ. I wasted hours before I found this post.

[Rudi De Vos]

FTUserImpersonation use the current logged user, NOT the mslogon user.

FTUserImpersonation=1
FT only works when somebody is logged.
FT permission are local user
FT can copy/delete files with the permission of the desktop user
FT can acces shared folders

FTUserImpersonation=0
FT does not require a logon
FT is being done as "local system"
FT has full access, you can copy/delete files as you where administrator
FT has no access to network shares and special "current user folders"

Just know what you are doing before setting FTUserImpersonation=0

[Frmg]

Ok but Why when the UserImpersonation=0 and user is logged dont is possible to access the network shares and special "current user folders" ???

[apohl]

I´ve applied the reg-patch on a machine, which was upgraded to 1.0.1.

Unfortantly File transfer is continuing to be disallowed.

[kgarland80]

You will need to restart the service for the change to take effect

[bevtech]

made FAQ a solution 2 for File Transfer not working..