om 192.168.20.44.
>
>H. Milton Johnson
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
>Zoltan Forray/AC/VCU
>Sent: Tuesday, April 13, 2004 12:01 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Server IP controls
>
>The conn
<[EMAIL PROTECTED]>
04/13/2004 04:23 PM
Please respond to
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To
[EMAIL PROTECTED]
cc
Subject
Re: Server IP controls
Zoltan,
Try this, from a command line "on the client":
ping 192.168.20.44
Does the ping wo
on Johnson
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Tuesday, April 13, 2004 12:01 PM
To: [EMAIL PROTECTED]
Subject: Re: Server IP controls
The connection isn't the problem. The client talks to the server (and
vice-versa) ju
esday, 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
ne
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
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 v
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
