ADSM-L

Re: Client acceptor port on multiple NICs on WIN

2006-05-12 10:49:49
Subject: Re: Client acceptor port on multiple NICs on WIN
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 12 May 2006 10:48:43 -0400
Hi, Matthew -

TCPCLIENTAddress does what you indicate, and the optional Node
HLAddress is explicit. But those are for server-client communication,
whereas your Windows folk are apparently concerned about user browser
access, which is rather arbitrary and beyond your control in a multi-
interfaced box. This is where the OS and network administrators take
over, to enforce box access restrictions: work for them to do, less
work for you.

   Richard Sims

On May 12, 2006, at 10:28 AM, Large, M (Matthew) wrote:

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

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