Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: TCP Hostname Resolving - 10.2/BSD Message-ID: <9011011949.AA13298@pan.ssec.honeywell.com> Date: 1 Nov 90 19:49:27 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 41 > I've got a 10.2 machine with bsd and aegis combo on it, and I'm having > a bizarre problem with resolving hostnames from /etc/hosts > > There's a network host that's number is 126.0.0.1, and its name is 'gateway1'. > If I type: > > % rlogin gateway1 > It tries and times out, no connection. > > If I type: > > % rlogin 126.0.0.1 > It immediately connects. 1) Check the /etc/hosts file for gateway1 (fpat or grep). The first entry is the address that the name will resolve to. You might have more than one. 2) The /etc/hosts.dir and /etc/hosts.pag files may be out-of-date / corrupt. If they exist, they're used for quick, hashed-entry access to addresses. I'm not sure whether they access the /etc/hosts or not. 3) If you're using name-server resolution (/etc/nmconfig -hostent_bind) the name-server may be what you can't access. Check for a file /etc/resolv.conf file on your node, and/or /etc/named running. From there, figure out what machine you're using for name-service (if you are using any). > If I try to access a node that requires a few gateway hops, I always get the > 'network unreachable', although routed is running, etc. Check your routing tables with '/usr/ucb/netstat -r' or '/com/tcpstat -r'. Just because routed is running doesn't mean that routes are there. Also check out your tcp address (probably '/etc/ifconfig dr0' if you're on token ring) and subnet masking (if any). Good Luck -- John Thompson (jt) Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com As ever, my opinions do not necessarily agree with Honeywell's or reality's. (Honeywell's do not necessarily agree with mine or reality's, either)