Dear James
It behaves exactly as described in my post. When I run VNC 4.0 as Server
after a few hours (~2 hours) the Ctrl-Alt-Del Window disappear. This means
that that when I connect to one of the affected Virtual hosts the VNC
Windows remain blue (Default Windows Background Color). For the VMWare
Remote Console it's the same.
Sorry that I don't have more informations. VMWare does not find anything
in his logs or in the system logs. No Events in any Windows Logs on the
affected Guest VM's.
I like to repeat our offer to run tests on one dedicated VM Machine. If
you have a debug Version, I can install it on this test VM and send you
log files as you need it.
Best Regards
Salvatore Cagliari
E-Mail: [EMAIL PROTECTED]
Bechtle IT-Systemhaus Basel
Switzerland
"James Weatherall" <[EMAIL PROTECTED]>
13.10.2004 14:53
To: Salvatore Cagliari/X/PH/[EMAIL PROTECTED], <[EMAIL PROTECTED]>
cc:
Subject: RE: Problem with RealVNC 4.0 on Guests of VMWare ESX
Category:
Salvatore,
We have never had such a bug reported to us, I'm afraid.
Can you provide a description of the actual behaviour you are seeing?
Cheers,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: 13 October 2004 10:32
> To: [EMAIL PROTECTED]
> Subject: Problem with RealVNC 4.0 on Guests of VMWare ESX
>
> Dear all
>
> I hope that there is a VNC Developer out there that can help
> us in solve this problem:
>
> We have a Linux Box with VMWare ESX 1.2.1 installed on it. On
> VMWare we created three Windows 2000 Guests and installed
> RealVNC 4.0 on it.
>
> Now comes the problem: After a while (a few hours), after I
> connected on one of the VM's with the VNCViewer, the
> Ctrl-Alt-Del Windows is disappeared! We are no more able to
> log in to this machine through VNC nor through the VMWare
> Remote Console (They both connect to the same console).
> The only way is to connect with RDP/Remote Console. But even
> through this, or through a remote shutdown command, it was no
> more possible to cleanly reboot the server. We have to power
> down the VM to restart it.
>
> After communicating with VMWare about this problem we isolate
> RealVNC 4.0 as the cause of this problem. After installing
> TightVNC 1.2.9 or RealVNC
> 3.3.3 the systems behaves normally and we are able to connect
> to the VM's through VNCViewer (4.0) and VMWare Remote Console.
>
> I hope that someone can fix this problem, or at least publish
> an advisory about this. I think it would be better to solve
> it, isn't it?
>
> We could build a Test VM make tests on it with
> improved/patched VNC versions. Please contact me for this. Thanks.
>
> Best Regards
>
> Salvatore Cagliari
> E-Mail: [EMAIL PROTECTED]
> Bechtle IT-Systemhaus Basel
> Switzerland
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
