[H-GEN] [Debian hamm] Help!

[Daehenoc]

Hello everybody - thanks to Rob for slinging the dual P5 mobo to me - at
the meeting last Sat I got it up and running with 2 * 166 MMx + 64 Mb ram

Plesantries aside, i'll confess my ignorance and state my problem: 
Something screwey is going on with telnetd (and pppd) debian was set up @
humbug to connect to the humbug network, all o.k. BUT i've now got the
computer home, on my 192.168.1.x network. What happens is this: when I try
and telnet into this debian machine from other machines, a connection is
made, but you don't get the login: prompt. (telneting to the machine from
itself works, 'tho) When I try and run in.telnetd manually, I get this:

fred:~# in.telnetd
in.telnetd: getpeername: Socket operation on non-socket

and this:

fred:~# in.telnetd -debug
bind: Address already in use

Is this usual?

I think that I hunted down most of the network settings (/etc/networks,
/etc/hosts, /etc/init.d/network...) but I don't know if i've made all the
requisite changes (am I just showing my linux ignorance here? :)


wvdial is great! It got all my scripting O.K. to connect to questnet, but
when it gets to the point to start pppd, pppd spits the dummy and raves on
about not recieving a clean 7-bit LCP response (I think) causing pppd to
return an error, causing wvdial to drop the connection. doh. I was advised
to install minicom and make the connection to questnet, then exit minicom
without dropping connection (after initiating a ppp connection) and then
try firing up pppd (to see if wvdial was telling pppd crap). That's what
i'm in the process of doing now.

help?

Greg Vickers,
PC technician experienced in:
Research and Development, Quality Assurance and On-site/In-house Service

... Daehenoc ... a.k.a The Gingerbread Man