[omniORB] Configuring Naming Service -> I'm VERY Confused!!!

[David Morgenlender]

I've been trying to configure the Naming Service on a new setup ... & I'm=
 VERY
VERY confused!!!

I've been successfully running an app using omniORB 2.5 with the =
following
configuration:

	Server:	VC++ 5 app running under ETS-Kernel.
		omniORB has been modified to always look for the Naming
		Service's stringified IOR in C:\OMNIORB.CFG.

	Client:	VC++ 5 DLL running under Win95.
		The Naming Service's stringified IOR is stored in the
		registry (as decribed in the documentation).
		The Naming Service runs on this system.

Yesterday, I tried duplicating this configuration, so somebody else can =
do some
development on this project.  The only difference is the Client is =
running under
NT4, not Win95.

As a first step, the new Server system was tested using my Client system.=
   It
worked fine, using an OMNIORB.CFG copied from my old Server system.

Then the new Client system was configured, running NT4.  The first try, =
the
Server couldn't find the Naming Service.  I realized I had neglected to =
create a
new OMNIORB.CFG on the Server for the newly started Naming Service
("omninames -start");  so I did so.  I used the same OMNIORB.CFG on the =
Client,
setting the OMNIORB_CONFIG environment variable appropriately.  (This is
different than the Win95 Client, which used the registry.)  IAE, the =
Server
could not find the Naming Service;  =
resolve_initial_references("NAMESERVICE")
returns a nil value.  Neither could the Client (although I'm not certain =
of the
Client).

This was confusing enough ... then I decided to look at my original =
working
system.  The IOR in the Server's OMNIORB.CFG is DIFFERENT than the value =
in the
Client's registry!!!  Furthermore, both values are different than the =
values
produced by the Naming Service!!!

I traced through the Client's initialization.  The IOR is indeed taken =
from the
expected registry key.  I haven't traced through the Server yet ... but =
it
cannot be taking the value from the registry, unknown to me, since =
ETS-Kernel
does not support a registry!

So I'm left with many unanswered questions:

1.  Why does the new system NOT work?

2.  Why does my old system work at all, given the differing IORs???

3.  How do I determine the correct IOR value for an already =
initialized/started
Naming Service?  Is it taken from the cerr output when it's next started?=
  Is it
taken from the log file?  (None of these values match the registry value =
on my
Client!)

4.  Any hints for diagnosing this?

I'm eagerly looking forward to your help!!!

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D