RE: ManagedListener: Unable to Bind Listening Socket (10048)

2005-03-17 Thread James Weatherall
23:44 To: James Weatherall; vnc-list@realvnc.com Subject: Re: ManagedListener: Unable to Bind Listening Socket (10048) James, I have VNC Server 3.37 disabled and VNC Server 4.1.1 starting automatically under Services. When I manually run VNC 3.37, there are more limited options under

Re: ManagedListener: Unable to Bind Listening Socket (10048)

2005-03-16 Thread Yann Renard
Jeffrey P. Straus wrote: I am running Windows XP Home Edition. I just installed VNC Server Free Edition 4.1.1. I was not prompted to uninstall version 3.37 and it is still on my system. I have disabled winvnc.exe (version 3.37) and enabled Winvnc4.exe in my Startup

RE: ManagedListener: Unable to Bind Listening Socket (10048)

2005-03-16 Thread James Weatherall
Jeffrey, Your VNC 3.3.7 server is still running, using port 5900. You need to stop it, or uninstall it, and then restart your VNC 4 server. From then on, VNC 4 should work as expected. Alternatively, you can simply set the two to use different ports, if you wanted for example to try VNC 4

Re: ManagedListener: Unable to Bind Listening Socket (10048)

2005-03-16 Thread Jeffrey P. Straus
James, I have VNC Server 3.37 disabled and VNC Server 4.1.1 starting automatically under Services. When I manually run VNC 3.37, there are more limited options under Properties than in VNC 4; there is no Connections tab or ability to set a port. I was reticent to uninstall VNC 3.37 until I was