VNC showing white screen from 770

[osxmg]

Hi,

I've got a real strange problem with ultravnc.

I've installed ultravnc on my server and can access it from my powerbook without any problems. From my Nokia 770 I get the password dialog and then the screen gets white.

It's really tricky because I tested 2 hosts (as Server) and with one everythings ok and the other shows the problem mentioned above (any parameter are the same!!)

Does anybody know about this problem?

Thanks in advance

Mark

[NokNok770]

I switched over from tightVNC to ultraVNC because ultraVNC had server side screen scaling, but I get the same white screen if I try to resize my desktop for the 770. If I don't use server side resize it works fine. I don't see any speed difference either. The only reason I switch was to resize the desktop...since that is not working I might switch back to tightVNC.

[thoughtfix]

The only time I had a problem like this is when I had TightVNC running as a "logged in" account on my XP box and the screen was locked (Window+L)

If I leave it logged in, it always works.

[osxmg]

The only time I had a problem like this is when I had TightVNC running as a "logged in" account on my XP box and the screen was locked (Window+L)

If I leave it logged in, it always works.


I've made some tests and it seems to have someting to do when starting the VNC Server in a RDP-Session (Terminalserver Session in Windows 2000).
If I start the VNC-Server locally on the Win2000 then I can login from Nokia770.
If I start the VNC Server within the RDP-Session I can login from my Powerbook but get a white screen from the Nokia 770.

[Hedgecore]

I know this solution will be frowned upon, but try RealVNC. Works without a hitch with the 770 in both host or server mode.

[Psyclic]

I've seen this behavior using RealVNC on my W2K box with the Prompt local user to accept connections switched on in the Authentication page of the server properties. With it switched off, I can connect even when windoze is logged off. :p

[chrwei]

unltravnc tries to use a special video driver hook into the video subsystem of win2k and newer. If you start it in a RDP session, the video hook doesn't have anything to hook to since it's all virtual and that's probably why its failing.