Dennis, The problem you are seeing is caused by some other program running using the port that you have told VNC Server to use.
You just need to shut down the other program and restart VNC Server. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Bathory-Kitsz > Sent: 13 December 2005 13:36 > To: [email protected] > Subject: RE: Disconnects with 4.1 > > At 11:30 AM 12/13/05 -0000, James Weatherall wrote: > >Can you try running VNC Server with the "Log" parameter added, set to > >"*:file:100"? This will create a log file in > C:\temp\winvnc4.log, which > >will include messages indicating why the server was unable > to listen for > >connections. > > Here are the log results: > > Tue Dec 13 08:35:20 2005 > Config: set immutable Log > main: WinVNC service destroyed > main: WinVNC process quitting > (10048) > ManagedListener: unable to bind listening socket: (10048) > > Dennis > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
