| Event Id | 1 |
| Source | WinVNC4 |
| Description | SocketManager: unknown network event for listener |
| Event Information | This information from some newsgroups may help you: 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. ------------------------------------------------------------------------------------------------------------------ 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. ------------------------------------------------------------------------------------------------------------------ "Connections: closed: read/select: Connection reset by peer (10054) Do you wish to attempt to reconnect to 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”. |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.