When attempting to utilise j-Interop with OpenNMS in WMI lookups. We have encountered a bug which doesn't occur on Windows DCOM implementations.
The issue appears to relate to the the process that occurs when a connection is being established. The DCOM server sends back a packet with all interfaces ip addresses and hostnames within, to instruct the Client where to connect to. The j-interop imlpementation does not appear to go through all the interfaces / or resolution of hostnames to attempt a connection and only appears to try the ip address that is returned. This causes an issue when attempting to connect over NAT networks as the ip address headers are rewritten not the payload so the only way to actually connect to the DCOM services is via hostname entries/or DNS. Since this process does not appear to take place no connection can be established.
Log in to post a comment.