[omniORB] No connection to Naming Service from omniORB client

[Duncan Grisby]

On Friday 7 March, Christoph Thomalla wrote:

> it seems to me I encountered quite the same problem as Ron (Win2K, VC++6.0).
> I tried tnameserv.exe (JDK 1.3) and omniORB name service at different 
> ports with the same result.

[...]
> omniORB: Client opened connection to giop:tcp:255.255.255.255:65535
> omniORB: sendChunk: to giop:tcp:255.255.255.255:65535 100 bytes

This means your OS is very confused about TCP. omniORB has tried to
make a connection to the address specified for the naming service, and
the OS has reported success in opening the connection. Then omniORB
has tried to ask the OS for the address of the endpoint with
getpeername(), and has received an error, hence its reporting the
address as 255.255.255.255. When it tries to send on the socket, that
fails. Does the network work on your machine?

Cheers,

Duncan.

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