[omniORB] Failure to connect on Windows 2008 Server

[Duncan Grisby]

On Tuesday 1 September, Mike Richmond wrote:

[...]
> I've also tried using tcpAddress.cc from omniORB 4.1.4.  Tracing from
> that shows:
> 
> 09/01/09 09:53:16: ORBImpl: omniORB: Client attempt to connect to
> giop:tcp:<MyMachine>:9905 (INFO)
> 09/01/09 09:53:17: ORBImpl: omniORB: Name '<MyMachine>' resolved:
> <IPv6 6to4 address> (INFO)

Ah, I hadn't realised you were using a host name in your IORs.

Are you sure it's a 6to4 address, and not a link-local address (i.e. one
that starts fe80)?  I've seen the problem that resolving the machine's
own name on Windows 2008 can return a useless link-local address,
leading to the problem you see.

> 09/01/09 09:53:18: ORBImpl: omniORB: Failed to connect (no peer
> name): <IPv6 6to4 address> (INFO)
> 09/01/09 09:53:18: ORBImpl: omniORB: Name '<MyMachine>' resolved:
> <IPv4 address> (INFO)
> 09/01/09 09:53:18: ORBImpl: omniORB: Client opened connection to
> giop:tcp:<IPv4 address>:9905 (INFO)
> 
> which seems to show that it's the 6to4 address which is a problem.  I
> guess we should look to use 4.1.4, but would you expect any problems
> from just dropping tcpAddress.cc into a 4.1.3 source tree?

You'd be much better off using the full 4.1.4 release, but I would
expect it to work to drop tcpAddress.cc into the tree as you have done.

Cheers,

Duncan.

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