No, you're right. Some multihomed hosts get their wires crossed and start
replying on a *different* interface. This is their bug, not ours, and there
is absolutely no work around we could do. It sounds like the host had it's
head on backwards and was using a different IP as it's primary. That IP
didn't have a route to the PM, hence telnet failed, along with everything
else. Even if the PM could get a packet to the host (it did, you could
open an *incoming* telnet) the return packets would have the wrong IP in
the header. And UDP isn't an open connection, it is one way. So I'll bet
the host was sending the packets back on the wrong interface and they never
even found the PM. And if they had, with the wrong IP in the header they'd
be ignored because of security.
-MZ
-- Livingston Enterprises Technical Support Phone: 800-458-9966 FAX: 510-426-8951 support@livingston.com <http://www.livingston.com/> 6920 Koll Center Parkway #220, Pleasanton, CA 94566