Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!ll-xn!mit-eddie!genrad!decvax!decwrl!amdcad!amd!pesnta!phri!roy
From: roy@phri.UUCP
Newsgroups: net.unix-wizards
Subject: Problems with rlogin
Message-ID: <2460@phri.UUCP>
Date: Wed, 22-Oct-86 12:13:26 EDT
Article-I.D.: phri.2460
Posted: Wed Oct 22 12:13:26 1986
Date-Received: Thu, 23-Oct-86 23:59:04 EDT
Reply-To: roy@phri.UUCP (Roy Smith)
Organization: Public Health Research Inst. (NY, NY)
Lines: 23


	Recently, a strange problem has cropped up with rlogin.  We've got
a Vax-11/750 running 4.2BSD and a bunch of Sun-3's running Sun 3.0 Unix.
One of our Sun-3/50's (adenine) can't rlogin to the vax.  It used to work
fine, but then for no apparant reason it stopped working.  Rebooting
adenine seemed to have fixed the problem, but then it came back.  The
symptoms are:

	If I try to rlogin from adenine to the vax, I get "connection timed
out".  I can rlogin from the vax to adenine, however.  All the other suns
can rlogin to the vax without problems and I can also rlogin from adenine
to some other sun and from there I can rlogin to the vax.  Telnet from
adenine directly to the vax works fine.

	I'm stumped.  My guess is that the is a pty that's hung up and for
some reason the triple (localhost=adenine, remotehost=vax, protocol=rlogin)
always finds that same pty.  Why that should happen I have no idea, nor do
I know how to go about testing this theory or fixing the problem.  Any
ideas?
-- 
Roy Smith, {allegra,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016