Thanks for the info, port 443 sounds perfect for me as I will probably use the same PC for web and FTP. I am guessing if I redirect port 443 to 1328 on my router/firwall I can use a single instance of Echosever
Regards, Rolf -----Original Message----- From: Scott Best [mailto:[EMAIL PROTECTED] Sent: 24 February 2006 16:36 To: Scott Mize Cc: Rolf Heelas; [email protected] Subject: Re: [Echovnc-users] Ports Scott: Heya. I understood that to be Rolf's question: which port should he run his echoServer on to maximize likelihood that it's *not* blocked by an outbound-filter on a firewall he doesn't control. What I do with the demo server is run it on the normal port (1328), but also run it on TCP 443, usually reserved for HTTPS traffic. The two instances don't "talk" to one another (so if you're logged into one and your partner is logged into the other, you can't establish a connection), but it's possible in a future version of the server. Besides 443, the other "popular" ports I've seen users try to work around with over the years are 21 (FTP), 53 (DNS), and 80 (HTTP). None of which, as you point out, are a 100% solution. cheers, Scott On Feb 24, 2006, at 8:14 AM, Scott Mize wrote: > Hey, > > Your echoServer should be in an environment that you control, which > would > mean that you can open whatever inbound port you need to. All user > connections are outbound, so if the user in question is in an > environment > that blocks outbound traffic based on port, you will be out of luck, > regardless of which port you assign to the echoServer. Unless you > get their > firewall admin to open that specific port for outbound traffic. > > > Scott Mize > Technology Specialists LLC > Phone: 503-504-7748 > Fax: 503-643-8279 > Email: [EMAIL PROTECTED] > Website: www.technology-specialists.net > > Not everything that can be counted counts, and not everything that > counts can > be counted. -- Albert Einstein > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Rolf Heelas > Sent: Friday, February 24, 2006 4:37 AM > To: [email protected] > Subject: [Echovnc-users] Ports > > Hi, > > Just curious what ports people are typically using for their > echoservers. > While echoserver is great for getting round NAT issues, more and more > companies are restrictive about what they let through their > firewall, port > 1328 I have found to be blocked. > > Just curious what other ports others maybe using to get past such > issues I > don't want to use 80 as I have a webserver running off the same box > > Regards, > > Rolf ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
