Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!uccba!uceng!kamat
From: kamat@uceng.UC.EDU (Govind N. Kamat)
Newsgroups: comp.sys.hp
Subject: Re: nameserver on HP9000/835
Keywords: almost works
Message-ID: <980@uceng.UC.EDU>
Date: 13 May 89 23:25:52 GMT
References: <207@dftsrv.gsfc.nasa.gov>
Distribution: usa
Organization: College of Engg., Univ. of Cincinnati
Lines: 24

In article <207@dftsrv.gsfc.nasa.gov> tomc@dftsrv.gsfc.nasa.gov (Tom Corsetti) writes:

>The server is running hp-ux 2.1, and a version of the nameserver
>obtained from the good folks at hp (binary only), with no garantees.
>Here are the symptoms of the problem: He can rlogin to his diskless
>machines without their ip address entries present in the host table.
>Everything works fine there... But, when he tries to rlogin back to
>the diskful server, he gets a message from rlogind saying that it
>couldn't resolv the hostname for ipaddress xxx.xxx.xxx.xxx (which
>is the address of the client machine he's coming from). Has anyone
>seen this behavior before?  Telnet works just fine, as does ftp.
>But rlogin doesn't.

Rlogind requires the client to be present in the host table, as a
security "feature".  This is the case with hp-ux 3.01 too.  Perhaps, it
might be changed when HP includes nameserver support officially.

I'm not sure how you can rlogin to a destination not present in the
table, since that version of hp-ux rlogin does not query the server as
it is distributed.  Unless you have the source available...
-- 
Govind N. Kamat				College of Engineering
kamat@uceng.UC.EDU			University of Cincinnati
					Cincinnati, OH 45221, USA