One of the main differences is that SOCKS
requires special client programs to access
services (Netscape and MSIE support it,
as well as other apps) while NAT usually
is "transparent" to the user. That is, the
user can use regular versions of apps
just like they were connected directly.
I don't know about the NAT RFC, but the
two product I'm familiar with ar Firewall-1
and PIX.
Ryan
---------- Previous Message ----------
To: firewalls
cc:
From: rjoshi @ wipinfo.soft.net (Rajesh Joshi) @ smtp
Date: 08/23/96 11:20:43 AM
Subject: SOCKS Vs NAT
Hi,
SOCKS is used to provide connectivity of the private hosts with the
valid internet hosts using a single valid IP address. NAT ( Network
Address Translator ) (defined by the RFC1631) is also used for the same
purpose.
Can somebody list the pros and cons of both the approaches? What are
the differences (applicationwise) between SOCKS and NAT?
Your help will be highly appreciated.
Best Regards
Rajesh Joshi
email address: rjoshi @
wipinfo .
soft .
net
|
|
