RealVNC Logo
VNC 3.3.5 Known Bugs and Features
The following are known bugs and features in version 3.3.5.

Date ID Platform / Program Description Workaround Status
10 Oct 2002 6 Windows server The connection settings options do not take effect until a new connection is made. Remake the connection. Under consideration
18 Oct 2002 11 Windows server Inability to cause a remote reboot. If "Logoff Workstation" is selected "When Last Client Disconnects" in the server properties, and the server is sent a reboot request with Ctrl-Alt-Del etc, the VNC connection closes, the VNC server stops, but the machine does not reboot. Disable "Logoff Workstation" before rebooting remotely. Under investigation
11 Nov 2002 16 Windows 95/98/ME server Shift with mouse click, or arrow keys etc does not work None Fixed in 3.3.6
12 Nov 2002 17 Windows server The HTTP server part of winvnc has a timeout on the download to avoid any one client from holding the server too long. This timeout was set to be 15 milliseconds rather than 15 seconds. None Fixed in 3.3.6
14 Nov 2002 18 Win95/98/ME installation If 3.3.4 or 3.3.5 is installed over 3.3.4 or 3.3.5 whilst it is running as a service, and the machine is then rebooted, some of the the installed filenames are shortened. It does, however, appear to nevertheless work in most circumstances. Stop the 3.3.4 service before installing 3.3.5. Fixed in 3.3.6
14 Nov 2002 19 Windows server If there is a VNC connection active, then some VB ActiveX components may fail to initialise correctly. Find the Use_Deferral registry key in the VNCHooks Advanced Settings for the VB application affected and set it to 0. Under consideration
14 Nov 2002 20 Windows server Some systems running VNC servers (with a connection active...) could find that their roaming profiles were not saved back to the profile server when they logged out because their registry hive was being used by the VNC server. If possible, close the connection to the VNC server before logging off. Fixed in 3.3.6
19 Nov 2002 21 Windows server and x2vnc viewer The clipboard doesn't work from the windows server to an x2vnc client. None Fixed in 3.3.6
22 Nov 2002 22 Windows server A viewer may appear to freeze. This can happen particularly when multiple clients are connected simultaneously, when one or more of the viewers appears to freeze but the others do not. Believed to be a bug in the Win32 HREGION API. Request screen refresh (Windows viewer, pulldown menu) or reconnect (Windows and X viewer) Fixed in 3.3.6
22 Nov 2002 23 Windows 98 server When the server is run as an application under 98 the tray icon is not displayed if there is no logged on user. None Fixed in 3.3.6
22 Nov 2002 24 Windows 98 server The advanced VNC hook settings can only be specified in the current users registry entry, not the local machine registry defaults. None Fixed in 3.3.6
26 Nov 2002 25 Windows viewer The port number of the listening viewer cannot be changed. None Fixed in 3.3.6
26 Nov 2002 26 Windows server On initial connection, the server sends a spurious black screen on connection. None Under consideration

If you encounter a bug with with VNC 3.3.5 which is not listed above, please see here.