Re: PPC login puzzle

["Steve Iribarne (GMail)" <netstv@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]

On 3/31/07, Charles Krinke <ckrinke@istor.com> wrote:
>
> Seems to me thing you can do is find out why the telnet session is being
> rejected.  Have you done an ethernet capture?
>
> <snip....>
> It is interesting that 'telnet localhost' fails in a similar way as telnet
> across the



Ok.. This tells me it's a telnet problem.  So either the telentd isn't
starting up properly on this system OR there is some weird rights thing that
you have setup differently on both systems.

Are you using anything like busybox?  Which telnet are you using.  It's
killing me because I know I have run into this same problem.  But I am old
and I forgot what I did.  I had this problem about 3 years ago.. ugh.

To me it was something with securetty or the like.  There is a config file
that allows telnet or not.  Another thing to try is to load telnetd with
more options.  I think there is "-a debug" you can turn on and that will
turn on the authentication debugging... "-D report" should also help you
out.

I'm sure it has something to do with root not being able to logon or maybe
it's the blank password.  Create a password for root and see if that helps.

-stv


network, and I appreciate your kind hints, especially about the log file and
> /var/log/syslog helps a bit on this problem.
>
> When trying to telnet accross the network, syslog says
>
> in.telnetd[]: connect from x.x.x.x
>
> But entering root doesnt work and the host then says:
> sff1 login: root
> Login incorrect
>
> There are no further errors on the 8541. When trying to 'telnet
> localhost', syslog says
>
> in.telnetd[]: connect from 127.0.0.1
>
> But neither completes the login, so although there is a clue here, the
> logical path to conclusion is still escaping me a little bit.
>
> I can see that both targets have the same /etc/xinted.d/telnet file and it
> contains:
>
> service telnet
> {
> flags  = REUSE
> socket_type = stream
> protocol = tcp
> wait  = no
> user  = root
> server  = /usr/sbin/in.telnetd
> server_args = -h
> log_on_failure += USERID
> }
>
> which I think is reasonable in this situation. So, this begs the question
> of what other things still bear on this type of problem. Again, I appreciate
> your taking the time to help me understand a bit more of how this fits
> together.
>
> Charles
>
>
>


-- 
/*
* Steve Iribarne
* Software Engineer
* (aka Grunt)
*/

[-- Attachment #2: Type: text/html, Size: 3086 bytes --]