[omniORB] Newbie: Debugging NamingService bootstapping

[David Morgenlender]

Tom,

>I am trying to get the bootstrap mechanism to work on my application.  =
My
>Naming Service is running on NT 4.0 and my client on PharLap ETS.  If I =
set
>the IOR in my omniORB2.cfg everything is ok, but if I try to use the
>bootstrap service I fail.
>
>My cfg file contains a single line ORBInitialHost 192.168.0.1
>
>Using a network monitor I can see my client sending a message to
>192.168.0.1 port 900 as expected.  My NT responds - resetting the
>connection - the client gets a COMM_FAILURE in boostrapSK.cc
>
>I would like to get some help on debugging techniques.

I'm also running using NT4 & ETS.  However, in my case, the server is on =
ETS &
the client on NT4.  I have run into problems getting Naming Service =
access
configured properly, but it's always been user error, e.g. forgetting to =
update
an OMNIORB.CFG file after a change.  However, I haven't tried the =
bootstrap
mechanism.

As far as debugging, both my server & client are VC++ 5 apps.  When =
necessary, I
run 2 instances of VC++, so I can debug both server & client.  The only =
problem
I've found in doing so is if I try to start the 2nd instance of VC++ for =
a
specific workspace ... the first instance of VC++ will now open the 2nd
workspace, leaving no way to debug the original project.  However, if I =
open the
2nd VC++ instance without specifying a workspace, a 2nd instance is =
started & I
can then specify whatever workspace I want from within the 2nd VC++ =
instance.=20

=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