Full Screen Mode: Problems

[Hartmut M. Bromkamp]

Hi there,

I've already posted this message in another thread, but I think the problem is worth starting it here again in a thread of its own:

I have problems with the Linux TightVNC viewer against Windows 2000 servers. I have two Win2000 machines, called A (running Windows 2000 Professional) and B (running Windows 2000 Server) for now:

1) Connecting to A succeeds, even when the "login" screensaver is running. I don't even need to use F8 -> Send CTRL-ALT-DEL, I can press this combination right away and get my login window.

2) Once a connect to A or B is established, pressing F8 and using the menu item "fullscreen" will crash the viewer immediately. Launching vncviewer with -fullscreen succeeds, but switching back to normal mode using the menu item "fullscreen" will again crash the viewer.

3) Connecting to B always fails, when the login screensaver is running: 

bromkamp "at" machine # vncviewer B
VNC server supports protocol version 3.3 (viewer 3.3)
Password: 
VNC authentication succeeded
Desktop name "B"
Connected to VNC server, using protocol version 3.3
VNC server default format:
  16 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using shared memory PutImage
vncviewer: read: Connection reset by peer
ShmCleanup called
bromkamp "at" machine # 

When I try this more than once, I also get:

bromkamp "at" machine # vncviewer B
VNC server supports protocol version 3.3 (viewer 3.3)
Password: 
VNC authentication succeeded
vncviewer: VNC server closed connection
bromkamp "at" machine # 

Connects will be established immediately and without problems when the screensaver is not protecting the console.




I have reinstalled both servers and clients to be sure that all parts stick together correctly but to no avail.

Any hints?

Okay, at this point I got an answer recommending to patch the Windows systems as far as needed to get them in a real up-to-date state. I'm still in the process of patching :(((

BUT: I'm ready with server A (the Windows 2000 Professional machine): it has all important (!) Windows updated applied, and it has got driver updates for its ATI graphics card!

This happens on my Linux console, when I start the vncviewer, get connected, press F8 and then "Full Screen":

------------------------------------------------------------------------------
bromkamp "at" machine # vncviewer A
VNC server supports protocol version 3.3 (viewer 3.3)
Password: 
VNC authentication succeeded
Desktop name "A"
Connected to VNC server, using protocol version 3.3
VNC server default format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using shared memory PutImage
------------------------------------------------------------------------------

At this stage, the lcoal console of A is blocked (because I checked the appropriate checkbox), and only when I press CTRL-C on my Linux box to stop the process, A can be controlled locally again.

My resumee thus far: The problem is NOT on the server side as was suggested, it seems to be more likely on the client side.

Stay tuned <s>, I'm still in the process of updating the Windows 2000 Server machine, I'll keep you informed. Although I don't expect that the incriminated behaviour will be affected in any way by my updates...

Bye, Hartmut