snicoud@ATC.BOEING.COM (Stephen Nicoud) (07/20/89)
I've got a problem with the Explorer choosing chaosnet to access a host when it should use TCP/IP. Here's the situation. My group's net is linked to another group's via two tcp/ip routers. We run tcp/ip and chaos here and they do likewise over there. We can only talk to each other via tcp/ip. So far so good. We maintain separate namespaces. We have our hosts, they have their hosts. Additionally, to our namespace, we add only those hosts from the other group that are their namespace servers (with only tcp/ip addresses and services). They do likewise by adding only the hosts that are our namespace servers. We also add the appropriate namespace class objects and modify the namespace search list. Now, if I want to access an Explorer in the other group, and that Explorer is not one of their namespace servers, my Explorer uses the host object provided by the other group's namespace. But that object contains a chaos address and since the desirability for chaos is higher than tcp/ip the connect is attempted via chaosnet and thus fails. Bad news. 8^( Somehow my Explorer needs to realize to try the connection via tcp/ip and not chaosnet. We would prefer not to have duplicate entries in both namespaces or change the medium/service desirability, so short of that, any ideas on a solution?