Blank Screen and User Fast Switching

garretto · Post by **garretto** » 2004-08-12 02:55

Ultra VNC works fine until a user logs on and leaves. Then the screen saver comes on and eventually, the moniter turn off. User fast switching is enabled and it goes to the login when the screen saver come on.

When I try to connect now, it connects but I only get a black screen. However, I can still transfer files. How do I fix this?

I have the server on a windows xp pro and the viewer on xp pro as well. Using ultravnc rc18.

Post by **Rudi De Vos** » 2004-08-12 09:35

Check TEST19-1 TEST19-2
"Semi fast user switching support"

Could you test it to provide some feedback ?

ink · Post by **ink** » 2004-08-26 17:28

I am experiencing this same problem; but where do I find TEST19-1 TEST19-2 "Semi fast user switching support"

Thanks,
Ink

Guest · Post by **Guest** » 2004-08-26 19:32

check out the ultravnc downloads page (the full one). There are experiemental rc19 versions out there for grab.

NightRyder · Post by **NightRyder** » 2004-08-26 20:52

its http://dl.ultravnc.net btw.

Ink · Post by **Ink** » 2004-08-30 21:04

Thanks you; I was thinking it was an option somewhere that I couldn't find.

Now what about these ms logon files in that directory, are those also intended to help with the problem I am having?

Thanks,
Ink.

Post by **Rudi De Vos** » 2004-08-30 21:15

mslogon is auth...nothing to do with FUS.

You should try 19_7 found on
http://sourceforge.net/project/showfile ... p_id=63887

To test, you need to install RC18.
Rename winvnc.exe (from RC18) to winvnc_RC18.exe
Rename winvnc19_7_xp.exe to winvnc.exe and copy this file
in the ultravnc directory.

After testing, you can remove winvnc.exe and rename the old
winvnc_RC18.exe back to winvnc.exe

If installed as service
#dosbox net stop winvnc (stop service)
....
rename_copy_files
....
#dosbox net start winvnc (start service)

Guest · Post by **Guest** » 2004-09-06 04:46

That does not appear to work. (i'm using the file with the xp- cause I run xp- correct me if i'm not supposed to do that)

It does work a little better, but if you try to switch users, you are out. And I couldn't connect a second time using the web browser.

Post by **Rudi De Vos** » 2004-09-06 07:53

"FUS" switching not tested with browser
Did you run vnc as service ? Only works running as service.

Viewer behaviour

On "FUS", viewer disconnect...you need to reconnect
the viewer to the new session.

Each session creates it's own vnc server, the session connected to the current desktop get's port 5900.

Session for user A ---> connected to viewer
Switch to session B
Vnc server for A disconnect all viewers
Vnc server for A change port to 5901
A new vncserver for B is started on port 5900
After switch, your viewer should be able to reconnect to session B
Switch back to A
VncServer B close
Viewer disconnect
VncServer A switch port back to port 5900
Your viewer should be able to reconnect on port 5900 to session A.

johnh123 · Post by **johnh123** » 2004-09-06 19:38

Ok, well maybe this is the problem. In my router, I only have ports 5800 and 5900 open. I think I saw somewhere here that is what I am supposed to do. What other ports should be open other than those two?

Post by **Rudi De Vos** » 2004-09-06 19:49

19_7 automap the active session to the selected vnc port
(default 5900)

Please try to test with the plain viewer first.
If plain does not work, java will certain not work.

Current, only 5900 is managed, auto switch between active
server.
But indeed, 5800 ??? for java , need to check what happen
5801 ?? not started because port is in use by other session.

Revers connection does not work.

johnh123 · Post by **johnh123** » 2004-09-06 21:26

Here is an example from the log of a failed attempt (black screen)- see anything?

Mon Sep 06 14:50:00 2004
vncHTTPConnect.cpp: HTTP client connected
vncHTTPConnect.cpp: started HTTP client thread
vncHTTPConnect.cpp: file / requested
vncHTTPConnect.cpp: HTTP headers skipped
vncHTTPConnect.cpp: sending main page
vncServer.cpp: GetScreenInfo called
vncDesktop.cpp: initialising desktop server
vncDesktop.cpp: KillScreenSaver...
vncDesktop.cpp: SCR-WBB: current display: w=1280 h=1024 bpp=32 vRfrsh=60.
VideoDriver.cpp: No 'Mirage Driver' found.
VideoDriver.cpp: No 'Mirage Driver' found.
vncDesktop.cpp: failed to activate video driver interface
vncDesktop.cpp: bitmap dimensions are 1280x1024
vncDesktop.cpp: created memory bitmap
vncDesktop.cpp: got bitmap format
vncDesktop.cpp: DBG:display context has 1 planes!
vncDesktop.cpp: DBG:memory context has 1 planes!
vncDesktop.cpp: attempting to create main and back buffers
vncDesktop.cpp: enabled fast DIBsection blits OK
vncDesktop.cpp: DBG:true-color desktop in SetPixShifts()
vncDesktop.cpp: no palette data for truecolour display
vncDesktop.cpp: killing desktop server
vncDesktop.cpp: quitting desktop server thread
vncService.cpp: SelectHDESK() to Default (28) from 28
vncService.cpp: SelectHDESK failed to close old desktop 28, error=170
vncHTTPConnect.cpp: sent page
VSocket.cpp: closing socket
vncHTTPConnect.cpp: quitting HTTP client thread

Post by **Rudi De Vos** » 2004-09-06 21:36

This is the logging of tightvnc .....

Will not help a lot for debugging ultravnc

UltraVNC

Blank Screen and User Fast Switching

Blank Screen and User Fast Switching

I have this same problem too

Thanks