Salvatore,

Please see VNC 4.0 Known Bug #2 at
http://www.realvnc.com/v4/known-bugs.html, which relates to use of the
Logoff on Disconnect option and a bug in its implementation in the current
release.  This bug is fixed in the Enterprise release and will be fixed in
the next GPL release too.

The fact that your VMs sit there with a blank screen indicates that they are
incapable of shutting down cleanly, which suggests other problems with those
guest operating system installations, by the way!

Cheers,

Wez @ RealVNC Ltd.
 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] 
> Sent: 13 October 2004 14:31
> To: James Weatherall
> Cc: [EMAIL PROTECTED]
> Subject: RE: Problem with RealVNC 4.0 on Guests of VMWare ESX
> 
> 
> OK, here's a clarification: Unlike the other versions of 
> VMWare, with VMWare ESX the Virtual Machines runs as services 
> that are not reachable or visible on the physical system 
> through the physical console. So the only way to see the 
> console of the Virtual Machines is to open a VNC Session or 
> the VMWare own Remote Console. 
> 
> We see this behaviour only when we open a VNC Session. But to 
> make this happen, I have to open a VNC Session for a first 
> time. Then, after ~2 hours, the console becomes blue. 
> 
> I set up VNC 4 with the standard setup except that I set up 
> to logoff when the last VNC Session ends. I'm unsure if I set 
> to remove wallpaper, background pattern and the effects. But 
> even when this settings are the cause, its a bug anyway. Isn't it? 
> 
> I will set up the promised VM and install VNC 4. Then 
> Activate the logging as described before. Please give me a 
> little bit time for this. 
> 
> I will let you know what I find in the Log and the events.
> 
> Thanks for your help 
> 
> Cheers
> 
> Salvatore Cagliari
> E-Mail: [EMAIL PROTECTED]
> Bechtle IT-Systemhaus Basel
> Switzerland 
> 
> 
> 
> 
>       "James Weatherall" <[EMAIL PROTECTED]> 
> 
> 13.10.2004 15:13 
>         
>         To:        Salvatore Cagliari/X/PH/[EMAIL PROTECTED] 
>         cc:        <[EMAIL PROTECTED]> 
>         Subject:        RE: Problem with RealVNC 4.0 on 
> Guests of VMWare ESX 
> 
>          Category:         
> 
> 
> 
> 
> Salvatore,
> 
> Are you saying that just running VNC Server 4 on the servers 
> in question causes the Ctrl-Alt-Del window to dissappear 
> after a couple of hours?  Or does there have to be a VNC 
> connection active for that behaviour to be seen?
> 
> What are the settings that you have configured the server with?
> 
> If you are running VNC Server 4 then there will definitely be 
> events logged in the Applications Event Log, every time a 
> connection is opened or closed - are you sure you don't see 
> any events in there?
> 
> You can enable further logging by adding the "Log" registry 
> entry as a REG_SZ under HKLM/Software/RealVNC/WinVNC4 and 
> setting it to "*:file:100".
> This will create a verbose log file in "C:\temp\WinVNC4.log" 
> on the host machine.
> 
> Cheers,
> 
> Wez @ RealVNC Ltd.
> 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]
> > Sent: 13 October 2004 14:07
> > To: James Weatherall
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: Problem with RealVNC 4.0 on Guests of VMWare ESX
> > 
> > 
> > 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

Reply via email to