From a newsgroup post: "In my case it seems that the default Access Control ("+") doesn't work on Win2003. If I manually add our subnet, connections are accepted."
To add subnet, start the VNC Server Configuration and use the "Add" button on the "Connections" tab.
- Description: "Threading: failed TrayIcon(8c3f90):unable to create WMNotifier window instance: Not enough storage is available to complete this operation. (14)" - I was receiving this error on a Win2K3 terminal server and I was unable to connect using VNC. The problem was caused by a (HP) printer driver running hundreds of port monitoring services. Preventing these from running solved the problem.
If you use another VNC viewer (for example UltraVNC) to connect to a RealVNC server 4.1.2 you will get two Event ID 1 from Source WinVNC4 events within the same second with the following descriptions:
SConnection: Client uses unofficial protocol version 3.4
SConnection: Assuming compatibility with version 3.3
The connection will be established successfully but to avoid the error events just use the RealVNC viewer.
- Description: "Connections: closed: <IP Address>::4353 (state(): The specified program is not a Windows or MS-DOS program. (1151))" - When I tried to connect to a server from Start -> Programs -> RealVNC -> VNC Viewer 4 -> Run VNC Viewer, the following message was displayed:
“read/select: Connection reset by peer (10054)
Do you wish to attempt to reconnect to <computer name>”?
Attempting to reconnect gave the same result. To resolve the problem install RealVNC 4.2.1 or later. See the link to “Read-Select Connection reset by peer”.