i am going insane trying to telnet into a tomsrtbt booted machine.  it
seems like there were some complications, but i can't figure out what
the heck is going on and it is driving me crazy.

i un-commented the telnet and the HUP line in the rc.custom.gz file, and
that appeared to work.  then, i try to telnet in from another machine.
it just hangs after this:

Connected to 192.168.1.10.
Escape character is '^]'.

digging through the FAQ, i find that i need some 'mode character' and
'set binary' settings for telnet.  however, if i just run telnet, then
type 'mode character', it says i need to be connected before i can set
that.  i try and connect, and then it hangs.  damn.  digging through
some really old list messages, i find reference to sticking these
options in a file (but it doesn't mention what file).  i make a wild
guess and add this to my ~/.telnetrc:

192.168.1.10  mode character
    set binary

this seems to be used, but it doesn't make any difference to the telnet
session, it still hangs in exactly the same place.

the machine i am trying to telnet FROM is a redhat-6.2 machine, and the
toms is tomsrtbt-1.7.259, which i think is as recent as it gets.

whats the deal here?  i have looked up and read everything i can find as
i'm SURE this must be somethign obvious that i am missing, but nothing
seems to make any difference at all, it still hangs in the same place.

fwiw, i don't even seem to be able to do:

telnet 127.0.0.1 from the tomsrtbt machine directly.  very, very weird.
it hangs with a line that reads something like:

localhost (127.0.0.1) 23 (telnet) open

also, escaping out and closing the session completely screws up the
telnetd process on the tomsrtbt machine, i need to restart it manually.
sigh.  i'm so sure i have done this with an older version of tomsrtbt.

i CAN telnet from the tomsrtbt machine to another machine, the same
machine as i'm trying to telnet in from.

as always, any help would be enormously appreciated.

-- 

    CraigL->Thx();
    Be Developer ID: 5852
    Check out <http://www.begeek.com/>!


Reply via email to