[omniORB] omniNames only available from localhost

[Sebastian Bickel]

Dear list,

I hava a problem. I started omniNames with the following command:
/usr/local/bin/omniNames -start 2809 &

It is readable only from localhost properly. On other hosts in my network no connection is
established. If I sniff my TCP connection, only a SYN flag is send form the Client to the
NameService and nothing happens.

I found an entry in the FAQ describing Redhat has a problem with bad /etc/hosts files.
(http://www.omniorb-support.com/omniwiki/FrequentlyAskedQuestions#head-
1011b41836defb2e978bc7d6d57fcc384283cae1)

I think, that should not be a problem in my case, but here you have my /etc/hosts file to
correct (I'm using Opensuse 10.1!):

#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#

127.0.0.1 localhost

# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts

10.1.1.7 cserver.domain.my cserver


Can anybody explain my that fault or need I omniMapper for tha case. If so; how do I need to
configure?

The documentation of omni is very small. So I could not found anything in the documentation.
Sorry!


Greetings and thanks for everybody's help!



Sebastian

[JiangWei]

Try setup your host's firewall

And using netstat to check LISTEN entry

[Sebastian Bickel]

> Try setup your host's firewall
>
> And using netstat to check LISTEN entry
>

Hello,

I already deactivate it, but it did not work yesterday. (With a ativated firewall, there has been
a TCP-RST-Flag from the Server, after activation the server did not respond [I only saw a
SYN-packet sent from Client to Server with no response; but the name service was still
connectable through localhost.] )

Sorry, that I forgot to write that in my last mail. Today, it worked without any problems. I did
not modify any parameters, ... . Very strange; but no it works. Java Client nameservice
lookup still does not work, but this is a JAVA resolving problem.


Thanks for your help.

Greetings from Stuttgart / Germany


Sebastian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060727/14f4d29b/attachment-0001.htm

[Duncan Grisby]

On Wednesday 26 July, "Sebastian Bickel" wrote:

> I hava a problem. I started omniNames with the following command:
> /usr/local/bin/omniNames -start 2809 &
>
> It is readable only from localhost properly. On other hosts in my
> network no connection is established. If I sniff my TCP connection,
> only a SYN flag is send form the Client to the NameService and nothing
> happens.

Most likely, your machine has a firewall that is blocking the connection
attempts. You might try running omniNames with -ORBtraceLevel 25 to see
if it is seeing any connections coming in, but I don't think you'll see
any.

> I found an entry in the FAQ describing Redhat has a problem with bad /etc/hosts files.
> (http://www.omniorb-support.com/omniwiki/FrequentlyAskedQuestions#head-
> 1011b41836defb2e978bc7d6d57fcc384283cae1)

That's only relevant to ancient versions of omniORB.

Cheers,

Duncan.

--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --