ORB forwards to a wrong location

I have an orbd started at a virtual host (with the IP A), with some remote object registered. Box that hosts virual boxes has IP B. When client tries to connect to the ORB at A to acquire the NamingContext, ORB replies with a LocationForward message poiniting to host B and port 1049 (like if another ORB would be started at that host). NamingContext is returned successfully, but obviously I'm not able to acqure the objects, registered at the NamingContext (at ORB hosted at A) by the name.

Could anyone please 开发者_开发知识库explain what's happening? How can I access the orb hosted at A remotely?

Thanks in advance.

---

I've recently had a very similar problem. I had a setup with the ORB running on a virtual machine, and once it was starting, port 1049 at the host was opening, like it's another ORB running behind the default port. The problem in my case was the firewall, that blocked connections to this port. Once I've opened it, everything has started to work as it should.

---

I'm not sure about your specific case, but, I see this behavior regularly on unix machines with java that have a bunged up /etc/hosts file.

For instance, assume the server with the orb on it is named "server.foo.com" in dns with an ip address of 192.168.0.2, but it's /etc/hosts file says "127.0.0.1 server server.foo.com".

When a client connects to the orb using dns to resolve server.foo.com, the orb reply back with 127.0.0.1, instead of 192.168.0.2.

The fix is to change /etc/hosts to have

127.0.0.1 localhost

192.168.0.2 server server.foo.com