which port is best for customers behind firewalls?

[Guest]

Hi folks,
I'm new to SC but very very impressed of the possibilities, this tools gives into my hands. Thanks for this great piece of software!

I tried it with several "private" customers, who have a direct connection to the internet over a personal firewall. Everything OK here. Now the problem: I tried to connect to a friend of mine at university, say let him download and execute the server app, while I was listening with the viewer. And - nothing! No connection nada, nope.

So my first thought: must be the firewall at the university not allowing for port 5500 to be remotely accessed. Can it be something like that?

My secound thought: port 80 must have access to the net. So why not listening on port 80? But the viewer told me "Error creating listening daemon: error binding socket..." or something.

Isn't it possible to establish a connection on port 80? That should work on every system accessing the internet through a browser, or am I completely wrong?

How would You guys solve a situation like this? Or should I use port 21? Seems to work. And most firewalls and routers will access ftp-connections, won't they?

Thanks for any answers on my silly questions

[Guest]

But the viewer told me "Error creating listening daemon: error binding socket..." or something.

Probably some other prog on your PC is using port 80. Try running [pre]netstat -a -o[/pre] to identify disturbing process ID.

[tim71]

try 443

it's not as obvious as 21 or 80

P.S. I use 443 to connect to AOL server, when using AIM at work.

[ipsec]

How would You guys solve a situation like this? Or should I use port 21? Seems to work. And most firewalls and routers will access ftp-connections, won't they?

Most firewalls allow certain access out and not in, or if they allow it in they only allow internal connections over port 21 (for FTP) to a specific box, which redirects ALL attempts unless internally requested. E.g. you ftp to www.myhost.com and thats how you get in The firewall then allows www.myhost.com back to you... so technically if you can ftp out you should be able to have your customers use that port from the network in question.

And as far as all of them... well... only if its configured like I said.

and its not silly, its a good one to probe us that are using it / have used it our $0.02.

My opinion is to use the SSL port 443, that way it looks like the customer is connecting to a secured server ect and the flags dont jump up too much for reporting for traffic since SSL is pretty noisey.