File Transfer & Impersonation

Here you will find help for frequently asked questions as well as for your specific question.

File Transfer & Impersonation

Postby Mandrake » 2018-08-24 10:20

FT fails to pull FROM remote share but allows transfer TO share (ERROR: file is not accessible on remote machine")
I need to be able to both see in the FT window the remote shares on the remote target machine, and also FT TO and FROM them to my local drives on the machine logging in to the target PC with uVNC viewer, both server and viewer 1.2.2.2.
Some time ago Rudi de Vos gave an explanation found in "File Transfer trouble "http://www.uvnc.com/onlinehelp/4.html, but it is still a bit unclear to me.
Rudi's explanation divides the case into "User Logged" and "User NOT Logged", but what does User actually mean?
The remote PC is unattended, Windows 10 is started with a user logged in, winvnc is started as a service, it is Logged On in as "Local Service", and in VNC Admin the Enable and User impersonation are both checked.
FT allows me to see the remote shares on the remote machine and transfer files TO them but not FROM those shares.
But which is the "User" in the help statement? The one into which Windows is logged in, or the one that the winvnc is logged in? Or the one logged in to the calling machine?
I tried changing the uvnc_services Log On from Local Service to This Account end enter the same user that is logged into Windows on that machine, with the corresponding password, but it does not make a difference to FT.
If I uncheck Impersonation, then I can't see the remote shares in the FT window (but see them on the remote machine's File Manager and can manipulate them at will).
Can someone explain the User in "User Logged" and "User NOT Logged" and how to log or not log, and where to log?

Thanks
Mandrake
 
Posts: 1
Joined: 2018-08-24 09:45

Re: File Transfer & Impersonation

Postby Rudi De Vos » 2018-08-25 10:22

folder mapping is done by the OS at user level

Maps are done at user level, it's after you logon as user the map is established.
A service, run as system and is not able to create a map.

The server sharing the mapped folder, can also put permissions on it ( readonly, full..). This are the standard window permission
you see when you click properties of a folder/file

Uvnc
-impersonate user: uVnc act as Rudi, the desktop user.
*you have access to the mapped folders
*you have the same restrictions as user Rudi for the local file system ( you can't write to the windows folder)

-no imperonation: Uvnc act as system
*You can not access the mapped files
*You have full access to the local files system ( you can write in the windows folder)
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5739
Joined: 2004-04-23 10:21


Return to General help

Who is online

Users browsing this forum: Bing [Bot] and 4 guests

cron