Path: utzoo!utgpu!attcan!uunet!ginosko!gem.mps.ohio-state.edu!apple!sun-barr!rutgers!columbia!close.columbia.edu!ji
From: ji@close.columbia.edu (John Ioannidis)
Newsgroups: comp.unix.i386
Subject: Re: Logging in to 386/ix via telnet over, TCP/IP
Keywords: login fails, rlogin, ftp, etc.
Message-ID: <6533@columbia.edu>
Date: 5 Oct 89 04:08:16 GMT
References: <2316@uceng.UC.EDU>
Sender: news@columbia.edu
Reply-To: ji@cs.columbia.edu (John "Heldenprogrammer" Ioannidis)
Organization: Columbia University Department of Computer Science
Lines: 19

In article <2316@uceng.UC.EDU> dmocsny@uceng.UC.EDU (daniel mocsny) writes:
>Though I can telnet to the very ends of the earth, the ends of the
>earth cannot telnet back to me. My machine hastens to answer the
>distant calls with login: and password: prompts, but though remoteuser
>types them with the diligence of the most faithful scribe, my machine
>can only rasp the reply "login incorrect".
>

I was plagued by the same problem for a couple of weeks, then in a
vision I saw the light. Running strings(1) on /etc/telnetd revealed
that the sucker was exec-ing a program called /etc/netlogin. Running
it from my terminal showed a similar behavior to /bin/login. So I
moved /etc/netlogin to /etc/foobar, then copied over /bin/login to
/etc/netlogin and now I can telnet to my heart's content. I can't
guarantee that there will be no side effects, though.

> >Dan Mocsny >dmocsny@uceng.uc.edu

/ji