<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16945" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2>The normal endPoint option is sufficient if you expect
clients to connect only on one interface. The ORB will then listen only on
this interface and encode the related endpoint into all IORs. The
endPointPublish option can be used to publish a certain endpoint but to listen
on all interfaces.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2>This business only gets tricky if you have clients on
both interfaces, which have no connectivity to the "other"
interface. </FONT></SPAN><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2>I could solve this with an interceptor, which can tweak
outgoing IORs depending on which client they are dedicated for. But this
solution is not portable.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2>Regards, Wernke</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=936270512-15012010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> omniorb-list-bounces@omniorb-support.com
[mailto:omniorb-list-bounces@omniorb-support.com] <B>On Behalf Of </B>Luke
Deller<BR><B>Sent:</B> 15 January 2010 09:52<BR><B>To:</B>
'jenskristianvilladsen@gmail.com';
'omniorb-list@omniorb-support.com'<BR><B>Subject:</B> Re: [omniORB] omniorb
configuration multiple network cards<BR></FONT><BR></DIV>
<DIV></DIV>
<P><FONT face=Arial color=navy size=2>Hi Michiel,<BR><BR>I have seen a problem
just like this too. By default omniorb will bind to all interfaces, which is
what we want. The problem is the IP address which is placed into object
references: by default omniorb will pick the IP address of the first interface
it finds, which in my case was the wrong one. Object references sent to the
client did not work for the client because it could not access the IP address
contained within the object reference.<BR><BR>To resolve the issue, I used the
endPointPublish configuration option to control which IP address was placed
into object references (see the documentation for how to use this
option).<BR><BR>Regards,<BR>Luke.<BR></FONT></P>
<P>
<HR tabIndex=-1 align=center width="100%" SIZE=2>
<FONT face=Tahoma size=2><B>From</B>: omniorb-list-bounces@omniorb-support.com
<OMNIORB-LIST-BOUNCES@OMNIORB-SUPPORT.COM><BR><B>To</B>:
omniorb-list@omniorb-support.com
<OMNIORB-LIST@OMNIORB-SUPPORT.COM><BR><B>Sent</B>: Fri Jan 15 18:23:45
2010<BR><B>Subject</B>: Re: [omniORB] omniorb configuration multiple network
cards <BR></FONT>
<P></P>I have had the same problem when adding extra network card. It seems
that it binds to either one of them or some global network. Try disable one of
the network card and try it once more. I am aware that it is not a solution,
just a fix<BR><BR>On 14-01-2010 10:50, Michiel Soede wrote:
<BLOCKQUOTE cite=mid:COL106-W16C8F99033A8757C11AB30D86A0@phx.gbl
type="cite"><STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
Hi,<BR> <BR>I'm using a corba servers using omniorb 4.1.2 on a debian
(amd64) linux system.<BR>A Windows PC (also using omniorb 4.1.2) client is
communicating with it.<BR> <BR>Recently I added a second ethernet card,
and the client cannot find the server anymore.<BR> <BR>what could be
wrong?<BR> <BR>best regards,<BR>Michiel<BR> <BR> <BR><BR>
<HR>
Hotmail: Trusted email with powerful SPAM protection. <A
href="http://clk.atdmt.com/GBL/go/196390707/direct/01/" target=_new
moz-do-not-send="true">Sign up now.</A> <PRE wrap=""><FIELDSET class=mimeAttachmentHeader></FIELDSET>
_______________________________________________
omniORB-list mailing list
<A class=moz-txt-link-abbreviated href="mailto:omniORB-list@omniorb-support.com">omniORB-list@omniorb-support.com</A>
<A class=moz-txt-link-freetext href="http://www.omniorb-support.com/mailman/listinfo/omniorb-list">http://www.omniorb-support.com/mailman/listinfo/omniorb-list</A>
</PRE></BLOCKQUOTE><BR><PRE>**********************************************************************************************
Important Note
This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this email. If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this email are not necessarily the views of IRESS Market Technology Limited.
It is the duty of the recipient to virus scan and otherwise test the information provided before loading onto any computer system.
IRESS Market Technology Limited does not warrant that the information is free of a virus or any other defect or error.
**********************************************************************************************
</PRE></BLOCKQUOTE></BODY></HTML>