Generally, personal firewalls allow outbound ports like that. They care more about unexpected applications trying to make outbound connections than where outbound connections are made to. However, many corporate firewalls block uncommon outbound ports. I can't get to port 8000 anywhere on the net from my desk at work, even though it's not that unusual. Something odd like 40443 won't have a chance at a lot of large companies.
Put some extra hardware in front of those boxes and redirect the connections from ports 80 and 443 if you can't use standard ports. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Eric J. Hansen > Sent: Thursday, June 30, 2005 3:39 PM > To: [email protected] > Subject: [BBLISA] outbound ports 8080/40443 firewall question > > We're looking at setting up a special website on alternate TCP ports > such as 8080 and 40443 (i.e., http://www.mysite.com:8080). This would > be > accessible by the Internet at large, and ideally as many end users as > possible. My question to the group has to do with corporate and/or > personal > firewalls -- namely, do you think these (or similar non-standard) > ports are > likely to be blocked so end users can't browse to these URL's? > > I looked through some docs about the Microsoft XP personal firewall as > well as ZoneAlarm, but couldn't find a definitive list of what > outbound > TCP ports would be allowed (not cause an alert/pop-up.) > > thanks > Eric > > _______________________________________________ > bblisa mailing list > [email protected] > http://www.bblisa.org/mailman/listinfo/bblisa
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
