Organization: The Emerald Isle BBS, Tucson, AZ (602) 749-8638
Lines: 26
In a message of <Nov 08 15:48> (Mark Huth) writes to All:
MH>David, your explaination is quite clear. My problem however is that
MH>TCP/IP isn't finding the global nameservers.
Getting to the nameserver and to other machines are two different issues. The fact that you can ping the nameserver and get it to resolve names for you doesn't necessarily get you access to the host whose name you've resolved.
MH> For example, lets say I
MH>want to telnet from my pc to an account at Yale. Whenever I attempt to
MH>do this, I get an error which tells me that the network isn't
MH>accessible (or words to that effect!).
It's been my experience that "network unreachable" messages are routing problems not nameserving problems. You may need to add a default route to your setup so that you traffic to the Yale machine is handed off to a router that knows where Yale is.
MH> If I log onto one of the
MH>university machines and attempt to make the same telnet
MH>connection....it connects right away.
The university machines probably have the correct routing established.
