jnw "at" realvnc.com
Thu Mar 10 17:42:00 2005
Windows ME has an irritating habit of enabled Internet Connection Sharing
and thereby causing all manner of network issues.
In order to get a log of connection messages (and errors) under Windows Me,
you can add the registry key HKEY_LOCAL_MACHINE/Software/RealVNC/WinVNC4/Log
as a REG_SZ with the value "*:file:0,Connections:file:30" - this will log
connection information to the file C:\temp\winvnc4.log.
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: Dave Walton [mailto:dwalton "at" acm.org]
> Sent: 09 March 2005 19:34
> To: James Weatherall
> Cc: vnc-list "at" realvnc.com
> Subject: Re: Connection Problem
> James Weatherall wrote:
> > If VNC Server receives a connection and then closes it then
> you'll see a
> > message in the Windows Application Event Log under WinVNC4
> that starts
> > "Connections: closed" and indicates the reason for closing
> the connection.
> > If there are no such messages then VNC Server isn't seeing
> the connections
> > before they get rejected.
> Hmm.. The VNC server is running on WinME, which I don't
> believe has an
> event log. Is there something else I can have the user look for?
> > The only other causes we've seen of connection issues are
> to do with faulty
> > firewall software at either end. Some old versions of
> ZoneAlarm, for
> > example, used to completely prevent VNC Viewer 4 from
> connecting to servers!
> That was my first thought, but there is no firewall involved.