[omniORB] FW: Problem w/ Client/Server Communication Across LAN With Client
/Server NameServices
Smith, Wayne
wsmith2@titan.com
Tue Oct 15 20:49:01 2002
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C27483.E2B29F50
Content-Type: text/plain;
charset="iso-8859-1"
I am trying to get a client to communicate with a server on a different
workstation with both workstations running omniNames locally. I'm running
omniORB Version 280 on Solaris 2.5.1. When I use:
genior IDL:omg.org/CosNaming/NamingContext:1.0 serverhost port#
NameService
I get one IOR: <IOR1>
and in omni/logs/omniNames on the serverhost I get another IOR: <IOR2>
When, on the client, I try
nameclt -advanced bind_context NameServer <IOR1>
eg3clt returns:
When I try
nameclt -advnced bind_context NameServer <IOR2>
eg3clt runs correctly.
Everytime omniNames is started on the server a different IOR is created. Is
there any way for the NameService to be started with the same IOR everytime?
I've tried NAMESERVICE <IOR1> in the server omniORB.cfg. I've tried <IOR2>
in the server omniORB.cfg.
------_=_NextPart_001_01C27483.E2B29F50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>FW: Problem w/ Client/Server Communication Across LAN With =
Client/Server NameServices</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=3D2>I am trying to get a client to communicate with a =
server on a different workstation with both workstations running =
omniNames locally. I'm running omniORB Version 280 on Solaris 2.5.1. =
When I use:</FONT></P>
<P> <FONT SIZE=3D2>genior =
IDL:omg.org/CosNaming/NamingContext:1.0 serverhost port# =
NameService</FONT>
</P>
<P><FONT SIZE=3D2>I get one IOR: <IOR1></FONT>
</P>
<P><FONT SIZE=3D2>and in omni/logs/omniNames on the serverhost I get =
another IOR: <IOR2></FONT>
</P>
<P><FONT SIZE=3D2>When, on the client, I try </FONT>
</P>
<P> <FONT SIZE=3D2>nameclt =
-advanced bind_context NameServer <IOR1></FONT>
</P>
<P><FONT SIZE=3D2>eg3clt returns:</FONT>
</P>
<P><FONT SIZE=3D2>When I try</FONT>
</P>
<P> <FONT SIZE=3D2>nameclt =
-advnced bind_context NameServer <IOR2></FONT>
</P>
<P><FONT SIZE=3D2>eg3clt runs correctly.</FONT>
</P>
<P><FONT SIZE=3D2>Everytime omniNames is started on the server a =
different IOR is created. Is there any way for the NameService to be =
started with the same IOR everytime? I've tried NAMESERVICE =
<IOR1> in the server omniORB.cfg. I've tried <IOR2> in the =
server omniORB.cfg. </FONT></P>
</BODY>
</HTML>
------_=_NextPart_001_01C27483.E2B29F50--