Things You Need to Know to get your SOCKS server up and running

If you already have a TCP/IP network running, you can skip over the domain-related information here. If not, this just suggests the basic information you need, and if there are additional issues you should consult online how-to documentation.

To make things easier, you should choose a "domain name" for the private network that will be communicating through the SOCKS server. This can be anything you want, but shouldn't be a domain that is already defined in the "real" Internet, such as For example, I chose "" but more interesting names are certainly possible. This is the name you want for your network, not the domain name of the Internet service provider you are connecting to. Since it's private, this name won't be recognized or accessible from the Internet.

Examples:,,,, boring.etc

Each machine in the private network requires a unique number identifying it specifically. A network address must be used to assign these numbers in an orderly fashion. These are normal IP addresses, but they won't be visible to the "real" Internet (since it's a private network). The "" address is reserved for private networks, so that you can safely choose numbers that aren't actually in use out there.

For a small private network, this means that the machines should be numbered as:,, .. ,
or in a similar orderly fashion. For example, I chose to number the machines in my private network,,,
so my "domain address" is -- i.e. I keep the "10.10.10." part always the same, and change only the last number.

Just use a netmask of "" unless you know specifically that need something different. Make sure that all the computers on the private network have IP numbers that are different only in the last number (i.e. 100,110,120 and 130, in my case).

For each machine number, choose a specific name associated to that number only. Using names to refer to computers is easier than remembering the unique numbers.

For example, for my network, I have          hobb          slug          deimos          max
These are combined with the domain name to give each machine a full name, such as "" for on my network.

The unique IP number assigned to the machine on the private network that will be running the SOCKS server and domain name server. In my case, this is

The name associated to the SOCKS server address. In my case, this is "hobb" ( is

The Internet IP number of the machine on your Internet service provider, that runs a real domain nameserver (DNS.) This is the machine that your private name server will talk to get "real" Internet names. In my case, I use "", one of the name servers operated by IBM Advantis, my Internet service provider.

The Internet name associated with the DNS IP, if any. For example, my DNS server is called "". Many providers don't allocate names to their nameservers. If this is the case, simply use the DNS IP number as its name (i.e. dns ip number:, dns ip name:

The configuration for TCP/IP and other networking functions are stored in an "etc" directory, on OS/2 and on other systems. To figure out where this directory is located, type

from a command prompt under OS/2. Usually, it's X:\MPTN\ETC or X:\TCPIP\ETC, but could be something else. This will be needed for both the client and the SOCKS server machines.
This page is maintained by Falcon Networking. We welcome your suggestions.

Copyright © 1996 - Falcon Networking