ADSM-L

Re: Client acceptor port on multiple NICs on WIN

2006-05-12 10:28:56
Subject: Re: Client acceptor port on multiple NICs on WIN
From: "Large, M (Matthew)" <Matthew.Large AT RABOBANK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 12 May 2006 15:28:29 +0100
Hi Richard,

I had my suspicions about that.. 
Do you think the TCPCLIENTADDRESS option would be of any use? I guess
(without looking) this updates the TCP_ADDRESS column on the server to
suggest an IP to make next contact with, not to ensure the client only
listens on that IP address.

Regards,
Matthew

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: 12 May 2006 14:01
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Client acceptor port on multiple NICs on WIN

Matthew _

I'm not aware of any TSM client parameter to limit port listening to a
specific computer network interface. Usually, the access is limited by
convention, which is to say instructing usage to go through a given
network address and thus interface; or, some kind of host-based or
external firewall enforces the required access rules.

    Richard Sims

On May 12, 2006, at 6:01 AM, Large, M (Matthew) wrote:

> Hi all,
>
> I've never come across this before so I thought I'd ask you guys..
>
> A windows guy came to me a few minutes ago saying that they have a box

> which has three NICs - a production NIC, a backup NIC for TSM and 
> another NIC which faces 'outwards' as it were.
> They are complaining that TSM is listening on port 1581 on all the 
> NICs, not just the Prod/Backup NICs.
> I can understand that they would not want the TSM web client service 
> visible from this outward facing NIC, so does any know of a way round 
> this?
_____________________________________________________________

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_____________________________________________________________

<Prev in Thread] Current Thread [Next in Thread>