Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!ames!ucsd!sdcsvax!ucsdhub!esosun!seismo!uunet!onm3b2!danno
From: danno@onm3b2.UUCP (dan notov)
Newsgroups: comp.protocols.tcp-ip
Subject: r* Command Incompatibilities?
Message-ID: <306@onm3b2.UUCP>
Date: 2 Feb 89 15:41:12 GMT
Reply-To: danno@3b2.UUCP (dan notov)
Organization: Ogilvy & Mather Advertising, Inc.
Lines: 21

I am running the following on a TCP/IP network:
	An AT&T 3B2/310 SVR3.1 with WIN/3B
	An AT&T 6386E WGS SVR3.1 with Micom/Interlan NP622A

I have found that rlogin from the 3B2 to the 386 always prompts me for a
password.  Is this normal?  I do have both hosts defined in
/etc/hosts.equiv and ~/.rhosts,  so I'm wondering if there is a problem
elsewhere.  However, the remote shell commands work properly.

On another network with a VAX/VMS & 3B2/UNIX (both WIN s/w),  rlogin works as
advertised.

Is there some incompatibility between the MICOM & WIN versions of these
commands?  Inquiring minds want to know...

--
danno

Daniel S. Notov
Ogilvy & Mather, Inc.
New York, NY				uunet!onm3b2!danno