Running explorer causes connection to drop

[Petroclus]

I am using uvnc 1.0.6.5 on a Windows XP system that is running my own 'shell' (i.e. bypassing the default windows shell/desktop etc).

This system (server) connects to a listening viewer with no problems and operates great.

However, if I then use the viewer to issue ctrl-alt-del to the server and run explorer.exe using 'New Task', after a few seconds the connection is dropped.

In this state, the server can reconnect to the viewer and will operate fine for a few seconds but then the connection will drop again, and this repeats.

Booting the server with the default windows shell (explorer.exe) loaded from boot-up works fine - the connection is never dropped. The problem seems to be related to running explorer.exe on-demand.

It seems as though when the windows shell (explorer.exe) is loaded 'after' unvc, then something is going wrong.

I hope that makes sense to someone.

Thanks for any help

[B]

Maybe a video driver thing? Does it happen even if you set the video to plain old VGA or SVGA?

Does it happen if you set up your custom shell with an option to launch Explorer.exe itself directly, rather than Ctrl-Alt-Deling and using the task manager?

You're doing something fairly unusual, as I'm sure you know. Windows does some interesting things when it's relaunching OS essentials....

[Petroclus]

Hi B

Yes, my setup is unusual - I'm using vnc to access some public kiosks that are locked down.

Re your suggestions:

I tried changing graphics to 800x600 with the same result.

I then tried configuring Windows to have no shell at all (to eliminate my software) - Windows just boots to a blank screen but still allows ctrl-alt-del/new task etc.

Then, directly on the server I can start a vnc connection - cad, new task, c:\program files\ultravnc\winvnc -connect {ipaddress}. The vnc session is fine and stays connected indefinately.

Then, (again on the server, instead of doing it remotely), if I do cad, new task, explorer.exe the vnc session is closed by something after a few seconds.

I looked at log file but it doesn't mean very much to me.

Thanks

[Petroclus]

Forgot to say I am building in the ability within my custom shell to launch explorer as per B's suggestion. Will let you know the result.

[B]

Hmm, I wonder what would happen if you ran cmd.exe instead of Explorer.exe. Or another program for that matter. Is it only Explorer that locks you up?

If cmd.exe works, you can try launching Explorer from the command line there...

[Petroclus]

Tried invoking explorer.exe from my custom shell but same result as using cad/new task.

[redge]

try to remove the schook.dll and vnchook.dll who use explorer.exe
reboot.

if not better...
try replace old 1.0.6.5 by new build 1.0.8.2 for test if this solved ?