[omniORB] OmniOrb uses wrong network adapter

[Peter Danziger]

Hi,

 

we are
using OmniOrb 4.1.6 on Windows Server 2003 and 2008R2. In the last weeks, we
observed a problem with the name resolution of CORBA calls.  The involved
machines have two network adapters, one for the “normal” network and one for a
management network. In the management network, the IP packets are blocked by a
firewall. The result is, that the clients’ nslookup for the server machine
returns two IP addresses. One works, the other doesn’t. In the Windows configuration
the “normal” network adapter is at the first, the other adapter is at the
second position. So the OmniOrb most of the time uses the working adapter.

 

We have an
object reference of a CORBA service which is running on a different machine and
we are doing a call every few seconds. Most of the time, the calls work. But
from time to time, the OmniOrb uses the adapter of the management network, and
the call fails.

 

Why does
OmniOrb switch the IP address between different calls on the same CORBA object?


Is it
possible to enforce the usage of a specific network adapter?

 

Any help
appreciated.

 

Regards,

Peter

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20130409/d7b6fa9a/attachment.html>