According to RFC 1918, the following are private, non-routed subnets:
10.0.0.0 -> 10.255.255.255
172.16.0.0 -> 172.31.255.255
192.168.0.0 -> 192.168.255.255
Being non-routed you cannot connect from 184.108.40.206 to 192.168.20.44
unless you have a connection to the same physical subnet as
192.168.20.44. We use a private, non-routed subnet for our clients, but
the clients are required a second NIC connected to the private,
H. Milton Johnson
Voice: (210) 677-6728
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Tuesday, April 13, 2004 8:22 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Server IP controls
Recently, we have been reconfiguring/locking down a lot of the TCPIP
ports in use by the TSM servers and clients, attempting to control/route
TSM traffic across a private subnet versus the more heavily used public
However, we have been having some TSM scheduler communications, due to
port blocking issues. I am trying to figure out if/how the TSM server
can be configured to control which of its 2-IP connections it uses to
communicate with the clients.
Here is my configuration:
TSM AIX 220.127.116.11 server. 2-IP connections, 18.104.22.168
(primary/public) and 192.168.20.44 (private).
The TSM client in question only has 1-IP connection, 22.214.171.124.
DSM.SYS (AIX) points to the server via DNS name that resolves to
My networking person says the traffic is flowing across the 6.201
connection, not the 20.44 private connection.
How, if possible, can I get the TSM server to use the private 20.44
connection to perform the backups ? Is there some server setting that
can control this ?
We are trying to get another connection to the client, using the private
subnet. Unfortunately, there aren't any available ports in the switch,
at this time. Yes, I know that when I get the other port in the client,
I can use the TCPNODEADDRESS options to control this.