I have to say, it looks like you found the culprit, all right. Not sure why it would bother just two machines, but sometimes software will do strange things. :-)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dennis Bathory-Kitsz Sent: Wednesday, December 14, 2005 11:21 AM To: [email protected] Subject: RE: Disconnects with 4.1 At 10:26 AM 12/14/05 -0500, John Aldrich wrote: >Do you have any tunnelled connections from the machine in question? I was >troubled by why I couldn't connect to my machine at work after VPN-ing in. I >finally tracked it down to the fact that I had port 5900 in use by PuTTY on >an SSH tunnel to my linux box at home. At 02:45 PM 12/14/05 -0000, James Weatherall wrote: >There aren't five ports used by VNC, only two - one for RFB traffic and one >for HTTP. >As I said before, it's very suspicious that port 5900 is "in use" but >doesn't appear as "LISTENING" when you run "netstat -an". Gents, First, Wez, I meant my five separate machines are now set to five separate ports (5900-5904) for VNC. But John got me thinking, as I was still wondering about the other machines on the LAN. Running the WinGate management panel on the server/router machine, I saw that WinVNC4 was one of the networking apps being shown as active on this client computer ... as it should be. It was also showing UPS and Iconclnt (both my power line monitor), WMP54GV4 (the wireless access point), Vsmon and Zlclient (both ZoneAlarm), Eudora (as I'm writing this), and Firefox (as I'm searching for answers). Thinking that perhaps -- since every network activity (LAN or WAN) is monitored by WinGate -- it was hanging port 5900 by simply monitoring the process while it itself was using WinVNC on port 5900, I changed the WinGate machine's VNC port to an arbitrary 5907. And voila, 5900 then worked on this client machine. I changed the WinGate machine back from 5907 to 5900 and this client VNC stopped functioning on 5900. My network knowledge isn't good enough to explain why, but the presence of port 5900 on the server/router denied this client machine's VNC the ability the use port 5900 -- and did so on one other client machine. That would seem reasonable ... except that it didn't bother the *other* two on the LAN using port 5900. And John, there is no tunneling running in WinGate. Neither VPN nor the WinGate port mapping service is in use. (I use SSH, but over port 22, and not while I was trying to solve this problem.) Enough for now, I think, unless there's something I can report that would help someone else with this problem. Many thanks, Dennis >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Bathory-Kitsz >> Sent: 14 December 2005 14:07 >> To: [email protected] >> Subject: RE: Disconnects with 4.1 >> >> Well, Wez, I'm out of ideas, and so long as I keep each machine with a >> separate running port for VNC, I appear to be functioning. I >> did a search >> through the registry for "590" just to see if there was >> anything else with >> fixed info, and came up with some parts of CLSIDs, version numbers and >> product codes; the five assigned ports in VNC4; and the >> country codes for >> Guadalupe (590) and the French Antilles (5901). :) >> >> If anything turns up, I'll let you know. >> >> Dennis >> >> >> At 09:03 AM 12/14/05 -0000, James Weatherall wrote: >> >Dennis, >> > >> >Mapped drives are handle via SMB, which doesn't use port >> 5900 or 5901. >> > >> >Regards, >> > >> >Wez @ RealVNC Ltd. >> > >> > >> >> -----Original Message----- >> >> From: [EMAIL PROTECTED] >> >> [mailto:[EMAIL PROTECTED] On Behalf Of Dennis >> Bathory-Kitsz >> >> Sent: 13 December 2005 21:31 >> >> To: [email protected] >> >> Subject: RE: Disconnects with 4.1 >> >> >> >> At 02:56 PM 12/13/05 -0500, John Aldrich wrote: >> >> >Do you have another version of VNC running on the same PC or >> >> trying to run, >> >> >or something else trying to take port 5900? That's what it >> >> sounds like the >> >> >problem is. >> >> >> >> Good thought on the other VNC. I had had VNC 3.3 running >> >> before 4.1, but >> >> removed it. I just did a look through the registry, and there >> >> are no traces >> >> of the original VNC (or ORL). >> >> >> >> As for something else using port 5900, I can't find anything >> >> even close, >> >> except the thought I had regarding this machine having mapped >> >> the drives on >> >> all the other machines (including those with VNC servers on >> >> 5900 and 5901). >> >> >> >> For now, all seems well with separate ports assigned all >> around. Still >> >> makes me nervous, though. >> >> >> >> 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
