Re: Secifying RPC ip address of client

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: David Tubb (Tubb_at_discussions.microsoft.com)
Date: 12/14/04 

Date: Tue, 14 Dec 2004 06:31:07 -0800

"Eugene Gershnik" wrote:

> Chris wrote:
> > Hi,
> >
> > I was wondering if there was a way to specify an IP address to use on
> > the client side in terms of an RPC call?
>
> This is a bad question. See the thread "RPC: How to get Clients IP Address
> on the Server side" for the reason why.

Whilst I agree with your comments on "How to get Clients IP Address on the
Server side", I don't agree that this is the same situation. The server
should not care about transport layers - that's fine. The client however,
has to be concerned with transport layers, it has to create a binding with a
transport address for the server. If it has to specify remote addresses, why
shouldn't it be able to specify a local address?

In a multihomed system (or even single adapter system with multiple IP
addresses), it is important to have control over the source address being
used, there may be access control issues with reaching the server if the
choice of source address is left up to the OS (e.g. IPSEC policy on the
client or server or a router may enforce and access control list between the
client and the server).

System wide RPC parameters can be configured in
"HKLM\SYSTEM\CurrentControlSet\Services\RPC\Linkage\Bind", but this only
allows usage of specific interfaces to be controlled. It provides no control
over usage of specific IP addresses (a set of valid IP addresses is derived
from the set of IP addresses bound to the interfaces specified in this key).

>
> > In my case I have to machines (each are RPC clients), one acting as a
> > hot stand by for the other. Each machine has a static IP associated
> > with it. There is a second IP address that floats between the two
> > boxes depending on which is the active box and which is the standby.
>
> What does "floats" mean?
>
> > The problem is I do not want RPC calls coming from these boxes to go
> > out via the floating IP address. I want the static IP address to be
> > used. Both of these IPs are on the same NIC. I assume that somewhere
> > in the RPC code a bind using INADDR_ANY is being used.
> >
> > Is there anyway to specify the client side ip binding? Or to ensure
> > that the RPC calls will never go out the via the floating ip?
>
> Without knowing what "floating" IP means the general answer is to configure
> your routing table properly.
>
> --
> Eugene
>
>
>

Relevant Pages

  • Asp.net Important Topics.
    ... ASP.NET server controls contained within the page. ... A custom server control is ... can also perform validation using client script. ... Where does the Web page belong in the .NET Framework class hierarchy? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Server Access via DCOM
    ... other than setting the text for the object in the html page? ... global property setting in the IE control? ... needs a property indicating which server to connect to. ... able to start multiple instances of the client application and connect ...
    (microsoft.public.vc.atl)
  • Re: Auto-update protocol
    ... before doling it out to the client on the net. ... Would require writing a server side tool. ... I'm not worried about the client side as I can control that. ... I thought the same initially - but it was a simple scheme which did work ...
    (comp.arch.embedded)
  • Multiple Pointers, Xinput and thin clients (remote X)
    ... I have a thin client connecting to a X terminal ... server using XDMCP and gdm. ... # Module section -- this section is used to specify ... # the way multiple screens are organised. ...
    (comp.os.linux.x)
  • Re: OWC Events in .Net
    ... Events always work on the client. ... is a client control. ... unload the contents of the spreadsheet into the ... followed by the button_click event on the server. ...
    (microsoft.public.office.developer.web.components)