Date: Fri, 13 Nov 1998 06:14:00 -0700 (MST) From: Diana Eichert <deichert@wrench.com> To: Andy Farkas <andyf@speednet.com.au> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: no more telnet Message-ID: <Pine.BSF.3.91.981113060845.4998A-100000@ts.shopnet.com> In-Reply-To: <Pine.BSF.4.01.9811140059540.685-100000@aniwa.sky>
next in thread | previous in thread | raw e-mail | index | archive | help
I'd recommend running sshd as your main remote login process and only use telnet within tcpwrappers as last resort. Of course if you don't have it running now, it will promote a trip to the console. If you telnet into your system from Win there is an ssh addon to teraterm for a no cost alternative. diana On Sat, 14 Nov 1998, Andrew McNaughton wrote: > On Fri, 13 Nov 1998, Andy Farkas wrote: > > > Could somebody please explain why I can't get into one of my systems? I > > am getting a 'telnetd: All network ports in use.' message when I try to > > telnet to port 23, but other services are ok. Tcp_wrappers is installed. > > > > The machine went down unexpectantly due to power failure, and came back up > > in its current state. I have never seen that message before. Is a trip > > to the console the only way?? > > When i saw the subject line I thought someone was gloating over getting > rid of telnet having installed something like ssh as a replacement. > > Installing ssh won't save you a trip to the console if it's currently > required, since you need access before you can install ssh. Once you're > back up though you might consider installing ssh and running it as a > daemon, (not through inetd) so that it acts as a backup access method in > case your problem returns. > > Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.981113060845.4998A-100000>