At 04:00 PM 12/13/05 -0000, James Weatherall wrote: >It's extremely suspicious that port 5900 is in use on the computer in >question, particularly if it's not listed by netstat -an. Are you running >any firewalling software on the problem system?
Yes, ZoneAlarm, with VNC accepted as server and client (as on the machines that work fine). I've been to the ZoneAlarm site to double-check that my setup is supposed to work with VNC. I also have McAfee, Spybot Search & Destroy, and Ad-Aware, all of which report a clean system. I decided to try port 5900-5909 for the VNC server. 5900 and 5901 do not work, and 5902-5909 work. Doing that triggered an idea, though it may be way out in left field: This is my main computer and it (and only it) has the hard drives of all the other machines on the network mapped to it. Could it be that, since ports 5900 and 5901 are in use by other VNC clients and servers on those machines, that this computer's VNC somehow sees those ports as being in use (even though netstat doesn't see them)? If that's the case, even though I don't access VNC from outside my LAN and according to the documentation really don't need to do this, perhaps I should indeed set each machine on the LAN to a different port? Thanks, Dennis >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Bathory-Kitsz >> Sent: 13 December 2005 14:58 >> To: [email protected] >> Subject: RE: Disconnects with 4.1 >> >> At 02:42 PM 12/13/05 -0000, James Weatherall wrote: >> >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. >> >> Netstat shows nothing else running on port 5900, but changing >> VNC to 5904 >> works. >> >> Netstat shows ports 0, 80, 137-139, 1027-1028, 1033-1034, 1042-1043, >> 1045-1047, 1058-1059, 2656-2657, 2723, 2914-2915, 2949-2950, >> 2961-2962, >> 2964, 2979, 6666-6668 and now 5904 are in use. (Many route to >> port 2080 on >> the WinGate server.) >> >> Dennis >> >> >> > >> >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 _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
