Re: Understanding NAT, Firewalls, TCP/IP
- From: Thomas Weidenfeller <nobody@xxxxxxxxxxxxxxxx>
- Date: Thu, 12 Jan 2006 10:35:05 +0100
Roedy Green wrote:
The client would initiate connections and there is no client to client communication. Just traditional client to server.
Then NAT shouldn't be a problem for setting up the TCP connection.
I want wondering if there are firewalls that might by default block outgoing tcp/ip connections to anything other than port 80 or FTP ports.
Many, maybe not by default, but configured that way. And particular the software ones take the process into account which tries to set up the connection. If it is not your browser or some other trusted program, they complain. That's their job.
You can argue if software firewalls make sense at all, but the fact is, many people now have them. And particularly the people who couldn't handle their computer in the past and couldn't keep it clean, are now the ones who can't handle their firewall(s) ...
/Thomas -- The comp.lang.java.gui FAQ: ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq http://www.uni-giessen.de/faq/archiv/computer-lang.java.gui.faq/ .
- References:
- Understanding NAT, Firewalls, TCP/IP
- From: Roedy Green
- Re: Understanding NAT, Firewalls, TCP/IP
- From: Mark H
- Re: Understanding NAT, Firewalls, TCP/IP
- From: Roedy Green
- Re: Understanding NAT, Firewalls, TCP/IP
- From: Thomas Weidenfeller
- Re: Understanding NAT, Firewalls, TCP/IP
- From: Roedy Green
- Understanding NAT, Firewalls, TCP/IP
- Prev by Date: Re: Smart XCopy
- Next by Date: Applet looking for class file improperly
- Previous by thread: Re: Understanding NAT, Firewalls, TCP/IP
- Next by thread: Re: Understanding NAT, Firewalls, TCP/IP
- Index(es):
Relevant Pages
|