[Fwd: Re: echo-client and echo-server on different physical machines, referencing echo.ref]

[Keith Christian <keithchristian yahoo com>]

-------- Original Message --------
Subject: Re: echo-client and echo-server on different physical machines, 
referencing echo.ref
Date: Thu, 19 Oct 2006 06:49:02 -0600
From: Keith Christian <keithchristian yahoo com>
To: KC.Gmail <kcc1967 gmail com>
References: <4536EDBB 3060407 yahoo com> 
<5eb4b0650610182100k293b1d80o5a1696c668a237f mail gmail com>

> On 10/19/06, Keith Christian <keithchristian yahoo com> wrote:
>
> > I recently downloaded and successfully compiled the echo example from
> > orbit-docs.tar.gz on a Debian Sarge system.  The echo-client and
> > echo-server tests ran fine.  (I don't see a version number, but the
> > orbit-docs/examples/echo/Makefile datestamp is 2004-07-09 09:34:54.
> >
> > Since the echo-client and echo-server ran OK on the same machine, the
> > paragraph in this web page was interesting:
> >
> > http://www.gnome.org/projects/ORBit2/orbit-docs/orbit/x182.html
> >
> > <<<If you want to have fun now, compile orbit on a different machine,
> > make echo-client on the different machine, move  echo.ref  from the
> > first machine to the second and run echo-client: eh voila -
> > client/server over tcp/ip with the same code that ran using unix sockets
> > on a single machine.>>>
> >
> > However, even after copying the echo.ref file as explained in the above
> > web page, echo-client could not connect to echo-server.
> >
> > Has this been fixed, or are there ways to troubleshoot this?  I'd like
> > to experiment with echo-client and echo-server on different machines,
> > I'm sure it's possible.
> >
> > Thanks.
> >
> > =======Keith
> >
> > _______________________________________________
> > orbit-list mailing list
> > orbit-list gnome org
> > http://mail.gnome.org/mailman/listinfo/orbit-list
KC.Gmail wrote:
> I had similar problem before when I start learning ORBit2.
> There is one issue which may solve your problem.
> ORBit2 (CORBA) client use hostname to resolve server's information.
> So if your server has hostname, abc.xyz.com, make sure
> your client can connect to server by using 'abc.xyz.com'.
> IP address is NOT enough.
>
> Also you can use
>
>      ior-decode-2 `cat echo.ref`
>
> to check both hostname and port number used on server.
> Do you have firewall blocking the port ?
>
>
> Regards
> KC

Thanks for the info, KC. Here's the output of ior-decode-2:


Thu Oct 19 06:39:47 (keith jupiter)
/usr/src/orbit-docs/examples/echo>ior-decode-2 `cat echo.ref`
Object ID: IDL:Echo:1.0
IOP_TAG_GENERIC_IOP: GIOP 1.2[UNIX]
jupiter:/tmp/orbit-keith/linc-65cf-0-77d1d6eb78145

IOP_TAG_INTERNET_IOP: GIOP 1.2 jupiter:36684
    object_key (28)
'00000000ec9d465329ab3579314dd979c6fd258601000000027e8470'

IOP_TAG_ORBIT_SPECIFIC: usock /tmp/orbit-keith/linc-65cf-0-77d1d6eb78145
IPv6 port 0
    object_key (28)
'00000000ec9d465329ab3579314dd979c6fd258601000000027e8470'

IOP_TAG_MULTIPLE_COMPONENTS:
    IOP_TAG_COMPLETE_OBJECT_KEY: object_key (28)
'00000000ec9d465329ab3579314dd979c6fd258601000000027e8470'

    Unknown component 0x1


I don't have a FQDN for this machine, just a hostname "jupiter."  No
firewalls, just a few machines connected to an SMC 4 port router.  I
looked up Debian's suggested method of setting the FQDN:
(http://www.debian.org/doc/manuals/reference/ch-gateway.en.html.)  I'll
have to try that.

TML in a subsequent message states this problem is fixed in CVS.  I'll
have to get the source and compile when I have more time and check this
inter-machine communication using echo-client/echo-server again soon.

=======Keith