Version 4.0| Version 4.0 |
User's Guide |
4. Configuring NetProxy Services
4.6. SOCKS Service
The SOCKS service allows your network users to use any client software that supports the SOCKS protocol. The SOCKS protocol provides transparent proxy services to clients, and is all encompassing in the services it can provide.
NetProxy supports versions 4, 4a and 5 of the SOCKS protocol.
The configuration
dialog for the SOCKS server is shown below. For specific help on each of the
settings, click the Windows 'context help' icon at the top of the dialog box in
NetProxy, then select the item you wish to learn more about
Local Port
Specifies the TCP port number that the SOCKS service should run on.
Port 1080 is the standard port for SOCKS.
Bind To Interface
Allows you to select a specific IP interface that NetProxy should bind
the service to. Any connection attempts not received on this IP address will be
blocked by the operating system before they even reach NetProxy's firewall.
For example, if the IP address assigned to your local network card is selected,
any connections arriving via your external IP interface (the one belonging to
your dialup or ADSL connection) will be rejected by Windows.
The version 4 SOCKS protocol requires you to have full Internet
domain name service (DNS) available to your network. NetProxy has a DNS
forwarding option under the SOCKS tab that acts as a gateway between your
network and a remote DNS server on the Internet. Client software that
fully supports SOCKS versions 4a or 5 does not require DNS.
NetProxy does not support the SOCKS BIND command. This is
intentional, as the use of the socks BIND command provides a potential security
loophole that could be exploited to gain access to machines on your
network.
Both Netscape Navigator and Microsoft Internet Explorer can be
configured to use the SOCKS protocol for a variety of services, including FTP
and Gopher.
SOCKS5 is a registered trademark of NEC Systems Laboratory Inc.