Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: evan@ssyx.ucsc.edu (Evan Schaffer)
Newsgroups: comp.sys.sun
Subject: Resolving telnet/rlogin protocol error problems
Message-ID: <8812201647.AA15806@ssyx.ucsc.edu>
Date: 30 Dec 88 18:01:40 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
Original-Date: Tue, 20 Dec 88 08:47:52 PST
X-Sun-Spots-Digest: Volume 7, Issue 82, message 3 of 18

Let me summarize the steps we've taken to resolve the
telnet/rlogin/protocol error problems we've been having during our 4.0
upgrade:

1. route add default your-gateway 1
   do this early on in /etc/rc.local

2. set your subnet mask and and broadcast address properly

3. DO NOT use aliases (pet host names) in your /etc/hosts.equiv and
.rhosts files. This is the kicker. This caused a lot of problems,
seemingly having nothing to do with /etc/hosts.equiv or .rhosts.

Users note perceived performance increases since the upgrade.