Zoltan, 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 128.172.6.177 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, non-routed subnet. H. Milton Johnson Voice: (210) 677-6728 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, April 13, 2004 8:22 AM To: [EMAIL PROTECTED] 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 network. 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 5.2.1.3 server. 2-IP connections, 128.172.6.201 (primary/public) and 192.168.20.44 (private). The TSM client in question only has 1-IP connection, 128.172.6.177. The DSM.SYS (AIX) points to the server via DNS name that resolves to 192.168.20.44. 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.
