[omniORB] [help] [beginner] Telnet connection problem

[Matthieu Masselin]

Hello Duncan, 

Thanks for your mail, it helped me figure out what was going on - rather what was not going on. I think omniNames was not configured at all and was actually not installed, as a sudo apt-get install omniorb-nameserver solved all my problems! 

Again, thanks a lot!

Matthieu 

----- Mail original -----
De: "Duncan Grisby" <duncan at grisby.org>
À: "Matthieu Masselin" <matthieu.masselin at wandercraft.eu>
Cc: "omniorb-list" <omniorb-list at omniorb-support.com>
Envoyé: Lundi 12 Septembre 2016 14:40:33
Objet: Re: [omniORB]  [help] [beginner] Telnet connection problem

On Fri, 2016-09-09 at 17:29 +0200, Matthieu Masselin via omniORB-list
wrote:

[...]
> omniORB: Client attempt to connect to giop:tcp:localhost:2809
> omniORB: Name 'localhost' resolved: 127.0.0.1
> omniORB: Failed to connect (no peer name): 127.0.0.1

[...]
>  figured that I might have a problem with telnet. Indeed, both 
> telnet localhost 2809 
> telnet 127.0.0.1 2809 

> fail, although 
> telnet 192.168.0.44 2809 gets me to login. 

That's not a "problem with telnet". You are simply using telnet for its
ability to connect to an arbitrary TCP port. That shows that omniNames
has been configured to listen on only 192.168.0.44. It is not listening
for connections on the loopback 127.0.0.1. It should be set to listen on
the wildcard address, so it accepts connections on all its IP addresses.

How is omniNames configured?  I expect it is being given an endPoint
parameter including either the IP address 196.168.0.44, or with the
machine's hostname in it. That is wrong. The config shouldn't set
endPoint at all, allowing omniNames to set its own endPoint.

By the way, Ubuntu really needs to enter the modern era and stop
distributing a version of omniORB that was released five years ago.

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --