I have built a CORBA event service client with omniOrb and Python. I had the same issue with a Java client. I\'m very certain I\'m experiencing the same thing as this post bec
I fixed this issue by adding the following line to my firewall script
ip6tables -A INPUT -i lo -j ACCEPT
I ended up figuring out that since I'm on a different subnet than the server, the ORB as publishing the wrong IP address, and couldn't figure out the route back to my client when an even triggered.
I ended up changing the config file at /etc/omniORB.cfg and changing the value of the "endPointPublish" property to the IP address on the server's subnet!