isode network program not following route table

[Thomas F. Blich]

We have this legacy program that was written using the libisode.a isode-8.0 library. When this program tries to connect to the host, it goes out the wrong interface. Telnet's, Pings, and FTPs go to the correct interface as specified using the "Default" route which points to a router. The interface it's trying to connect out of is just a 100MB switch that creates a backup backbone. I always thought that network traffic must follow the routing table. I guess that was a bad assumption. Does anybody know about isode? Is there a way to force this traffic over the correct interface?

Thanks

[John Bolene]

Way back when, the only interface available was the 10 mb lan.

It could be that the software can only communicate with the default lan interface (the one that is normally shipped with the machine), and not a 2nd card that has been installed.

Maybe an upgrade of software is required or at least a recompile?

[Thomas F. Blich]

Turns out this library was trying to communicate over the first available entry that matched the hostname in the /etc/hosts file. I arranged the order so the 10MB lan card entry came first. That appeared to do the trick.