Help with file transfers, and crashes.

skilover · Post by **skilover** » 2005-08-15 18:33

My VNC server is running on XP Home SP2. Viewer is on XP Pro. I'm using version 1.0 on both machines and am having three problems.

1) When the viewer is on the same LAN as the server file xfer works. I just can't see some directories like "C:\program files" for some reason.

2) When the viewer is at a remote location (same laptop, different location) and I'm connecting to the home network via OpenVPN, file transfer doesn't work at all. I get "File Transfer permission denied: disabled or unknown user or version incompatibility". Nothing has changed except for OpenVPN connectin verses physical connection to same router.

3) No matter where the viewer is connecting from, when I try to view what a restricted user is doing on the server, the user gets logged off and the viewer crashes. No error message. It just closes.

I appreciate any help you can offer.

redge · Post by **redge** » 2005-08-15 19:04

[topic=3753][/topic]

http://www.uvnc.com
update your winvnc AND vncviewer to 1.0.1

skilover · Post by **skilover** » 2005-08-15 19:19

Thanks.

Just updated viewer. When I get home I'll do the server.

Will this take care of the "restricted user" problem too, or just the file transfer problems?

redge · Post by **redge** » 2005-08-15 19:29

Will this take care of the "restricted user" problem too

No, and not possible.
license limitation of Windows XP of 1 remote user.
[topic=3050][/topic]

skilover · Post by **skilover** » 2005-08-15 20:20

Posted this once but it didn't show up so I'll try again.

The problem I'm referring do with "restricted user" is not a WinXP restriction on the # of remote user. By restricted user I mean someone who is not an adminstrator of the box. XP Home refers to these as "restricted users". If one of them is currently working on the server, and I try to view them, the viewer crashes immediately upon connecting, and the user on the server gets logged out.

skilover · Post by **skilover** » 2005-08-16 13:31

I'm reading that FAQ but can't make heads or tails out of it. Could someone kindly explain it to me?

And what exactly does all this mean. I have no context for what's being referred to as FUS, session0, session1, user2, etc.

You are always able to connect, but this is done by reverting to session0.
FUS use session1 for user 2.

When you connect, session1 is switch to session0 (logon screen). If you select user2, this activate back session1, vnc disconnect.

Thanks.

redge · Post by **redge** » 2005-08-16 15:58

I'm reading that FAQ but can't make heads or tails out of it. Could someone kindly explain it to me?

And what exactly does all this mean. I have no context for what's being referred to as FUS, session0, session1, user2, etc.

mean only 1 user remote session) can be used per time on host ! 2nd user account can be log on locally but can't be used remotely !

is not valid, nothing to do for your present situation.

I tested user limited account without any problem
Please sure you really use winvnc AND vncviewer 1.0.1 dated aug 6 2005
if not fixed
possible problem about the profile on host containing the restricted user account !
or
I miss something ?

skilover · Post by **skilover** » 2005-08-16 16:48

By "only 1 user remote session) can be used per time on host " are you referring to a vncviewer session or a user locally on the server? Host is a generic term and I'm not sure if you are referring to the host running the viewer, or the host running the server.

My setup is an XP Home PC running vncserver (as a service). There are multiple users logged on simultaneously but only one at a time ever has control of the desktop. I am running vncviewer remotely and want to view what they are doing, or possibly take control to help them do something.

Also, I upgraded both viewer and server to 1.01 last night and still have the same problem with file transfers. When connected over the VPN and trying to do a file transfer I get "File Transfer permission denied: disabled or unknown user or version incompatibility". Haven't tried it while both machines are on the same physical LAN yet.

If nobody is logged on to the server, and I connect with the client, I see the main logon screen. If I choose any except for one user, the session disconnects.

redge · Post by **redge** » 2005-08-17 02:32

the answer is "host running the server"

and you need the activate User impersonation (for Service only)
mean, no user logged
if already activate, disable it,
[ ] User Impersonation (for service only)
as soon you authenticated, [X] User Impersonation would be self activated again and lock File Transfer as service level !
some inconsistancy about FTUserImpersonation between User and Service

[topic=2892][/topic]
[topic=3281][/topic]

skilover wrote:If I choose any except for one user, the session disconnects.

One user? mean is administrator level or user limited acces disconnected

skilover · Post by **skilover** » 2005-08-17 12:38

I am still a bit confused. There is only one user logged on remotely - it's ME. There is only one user logged on locally on the server and it turns out that I was wrong about it being a "restricted" user. The user is actually an administrator. I am not understanding why I can't do what I want and why I can't view what that user is doing. Do I have to have all users logged out on the server and only the one who's desktop is currently active be logged in?

Step by step example of what happens.

Code: Select all

On server: User A is already logged in.
On Viewer: I log in with vncviewer and can view what user A is doing.
On Server: Desktop is switched (but [color=red]not [/color]logged out) to user B
On Viewer: I get disconnected.
On Viewer: I reconnect while user B is still in his desktop
On Server: As soon as I reconnect user B gets unexpectedly logged out
On Viewer: I see the logon screen 
On Server: User B reenters password and presses enter.
On Viewer: As soon as user B presses enter, viewer gets disconnected.

Post by **Rudi De Vos** » 2005-08-17 13:37

This is the behaviour running as service.

+A service can only view session0
+On the <XP OS's, the viewers desktop==session0
+XP "Fast user switching"
User A run on session0
User B run on session1

AS VNC can not view session1 (black screen) we switch to session0 and lock the screen. Implementing it this way, you always can logon, independed the current desktop user.

If you want to connect to session1, you need to run winvnc as application.
There is no restriction to sessions in application mode, an application can always view his own session.

skilover · Post by **skilover** » 2005-08-17 13:47

Now I think I'm getting it. My previous exposure to VNC (the original AT&T/UK version) allowed me to run VNC as a service on NT or Win2K and see anyone's session. I guess that changed in XP.

So in order to do what I want, I need to run multiple copies of VNC server as an application. One in each user's startup folder perhaps. Is that correct?

And if I continue to run it as a service insead, should I be able to log in to anyone's desktop from the viewer as long as I'm the only one doing anything on the server?

redge · Post by **redge** » 2005-08-17 14:37

as application, you lost the ability to use Ctrl+Alt+Del

as service system

if you want to use XP like windows nt and windows 2000, you need to inform yours persons when finish to LOG OFF instead of Fast User Switch and next person LOG IN as single user like your experience with NT and w2k

And if I continue to run it as a service insead, should I be able to log in to anyone's desktop from the viewer as long as I'm the only one doing anything on the server?

yes

skilover · Post by **skilover** » 2005-08-17 15:14

Ding!

I just dawned on me what you meant by "FUS" in an earler post - fast user switching. That was an acronym that was confusing me before.

I think perhaps I will just turn off FUS altogether and that should solve my problem.