Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

UVNC 1.01: No Directory Transfer At All

Post Reply
bevtech
800
800
Posts: 2168
Joined: 2005-08-03 14:07
Location: Pennsylvania, United States

UVNC 1.01: No Directory Transfer At All

Post by bevtech »

Solution 1:

Make sure that zip32.dll and unzip32.dll in the same folder as the viewer. Download the files from http://cvs.sourceforge.net/viewcvs.py/u ... ipUnZip32/

Solution 2: After an upgrade to UVNC 1.0.1

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 =======================



Rudi
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
Last edited by bevtech on 2006-02-19 17:46, edited 1 time in total.
Post Reply