[Ace-users] NamingService behind proxy not working as expected
castro.manuel at gmail.com
Tue Feb 12 04:10:53 CST 2008
we've got a problem with a NamingService accessed from an external
client. I'm sure it's not a TAO bug, but a misconfiguration of ours.
We bought the "TAO Developer's Guide 1.4a", but we couldn't find the
Any help will be welcome.
Thanks in advance.
TAO VERSION: 1.5
ACE VERSION: 5.5
HOST MACHINE and OPERATING SYSTEM: Windows2003 Server SP2
TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
WindowsXP Prof.2002 SP2
COMPILER NAME AND VERSION (AND PATCHLEVEL): VC++2005 8.0.50727.762
THE $ACE_ROOT/ace/config.h FILE
#define ACE_HAS_VERSIONED_NAMESPACE 0
#define ACE_HAS_STANDARD_CPP_LIBRARY 1
#define ACE_MUST_HELP_DLOPEN_SEARCH_PATH 1
AREA/CLASS/EXAMPLE AFFECTED: NamingService
DOES THE PROBLEM AFFECT:
EXECUTION? Yes, TAO
OTHER (please specify)?
Host name supplied in IORs is not always the expected one
A CORBA client application connects from outside of our network.
NamingService is running as a service, at machine 184.108.40.206 with the
following registry entry for "TaoNamingServiceOptions" key:
-m 0 -ORBListenEndpoints iiop://external.domain.es:15000/portspan=299&hostname_in_ior=external.domain.es
All traffic to external.domain.es is redirected to machine
Wireshark is sniffing at 220.127.116.11 host.
When client application connects, and sniffing GIOP protocolo, we
get a first response:
This is ok.
Then client application asks for MinDevControl_Factory proxy, but
the response includes the following:
So the client can't connect to 18.104.22.168 since it's an internal IP.
We thing the response should include something like:
No workaround so far.
More information about the Ace-users