Problems with Multiple TCP/IP Addresses

If you have multiple TCP/IP addresses on your machine, some of which have reverse DNS defined, and some which do not, you can tell ListManager to only uses the TCP/IP addresses which have reverse DNS defined.

To do this, you use the "tcpip" command line option.

For example, if you have three TCP/IP addresses, say:

207.90.101.4
207.90.101.5
207.90.101.6

And the last one, 207.90.101.6, does not have reverse DNS defined, then you want ListManager to only use the first two. To do this, you would run the following command:

lm tcpip 207.90.101.4 207.90.101.5 127.0.0.1

Each TCP/IP address is separated by a space. Note: We added the TCP/IP address "127.0.0.1" to the end. This is very important: the web interface talks to the ListManager server over the 127.0.0.1 TCP/IP address (note: 127.0.0.1 means "localhost", or this machine). If you do not list 127.0.0.1 as a TCP/IP address for ListManager to use, your web interface will no longer work (it will say "server unavailable").

You can reset ListManager to automatically use all TCP/IP addresses (the default) with the command line command:

lm tcpip

When using multiple TCP/IP addresses, it is important to remember that the TCP/IP address ListManager expects the Activation Code to be bound to is not necessarily one of the TCP/IP addresses ListManager is configured to listen to. To determine which of your machine's TCP/IP addresses ListManager expects the Activation Code to be bound to, use the "gettcpip" command line option:

lm gettcpip