Hyperterminal vs command line telnet

Discussion in 'Linux Networking' started by Joe Bramblett, KD5NRH, Jul 20, 2004.

  1. Why should it matter?
    Using XP Pro to connect to a Debian box. In Hyperterminal, I get the login
    prompt, so I know data has been passed, but that's it. I can't seem to
    make it do anything from there, and it eventually times out. Command line
    telnet to the same box works fine. Is there a difference between the two?
    Also, when it is doing this, remote X login via Cygwin never connects.

    Both hyperterm and Cygwin will sometimes work, but there doesn't seem to be
    any rhyme or reason to when they work or fail. Am I missing something
    obvious?

    FWIW, the Debian box is plugged into a WAP, and the XP box has both
    ethernet and wireless to the same router. I've tried only using one
    connection with the other disabled, but both seem to exhibit the same
    behavior.
     
    Joe Bramblett, KD5NRH, Jul 20, 2004
    #1
    1. Advertisements

  2. Try PuTTY for telnet / ssh

    http://www.chiark.greenend.org.uk/~sgtatham/putty/


    B
     
    Brendon Caligari, Jul 21, 2004
    #2
    1. Advertisements

  3. Joe Bramblett, KD5NRH, Jul 21, 2004
    #3
  4. that makes two of us :)
     
    Brendon Caligari, Jul 21, 2004
    #4
  5. Joe Bramblett, KD5NRH

    Juhan Leemet Guest

    Who knows? Busted app? I've read that Solaris users haven't been happy
    with Hyperterm serial line connections either. Maybe it's flakey? It was a
    demo, wasn't it? I seem to recall that on OS/2 they gave you a demo
    Hyperterm and lots of pestering (popups?) to upgrade to the "real product".

    I also use PuTTY. It's a good habit to get into using ssh. Telnet is a
    security risk, since it sends username & password in cleartext! (ftp too!)
     
    Juhan Leemet, Jul 22, 2004
    #5
  6. Well, the obvious one is that hyperterminal is serial, telnet is
    ethernet.
    Yes, you get the login prompt, but you don't know if you are sending
    anything in the other direction.

    one trick is to run cu from the debian box, to the same serial port.
    cu -p /dev/ttyS0 -s 9600

    then you can type on both machines and see what happens on the other.

    Things to watch: handshake lines - set hyperterminal to handshake
    'none'.

    Do you mean it does otherwise? I'd check you are setting xhost + on
    cygwin - and giving it time to work - before attempting to connect.
     
    Robert E A Harvey, Jul 22, 2004
    #6
  7. Hyperterminal (or minicom in Linux) uses a serial link (like null modem
    cable or direct shell dialup). Typically you set up a getty of some sort
    on the destination to handle the login. There is no networking (tcp/ip)
    for such a connection, so X programs would not work on a direct shell
    login.

    Telnet (or ssh) connect over tcp/ip (ethernet connection). Putty is a
    Windows ssh (or telnet) client (ssh is much more secure, especially when
    using wireless, or public network like internet).
    You do not mention anything about a serial or modem connection, or
    configuring a getty in /etc/inittab for such a connection, so I would be
    surprised if Hyperterminal worked at all (except maybe to chat AT codes to
    a local modem on its own box). The Text-Terminal-HOWTO explains this.
     
    David Efflandt, Jul 23, 2004
    #7
  8. -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    (David Efflandt) wrote in
    Hyperterminal has an option in the connection properties for TCP/IP
    connection.

    Interestingly, everything seems to be working now, and the only thing
    that's changed is that I rebooted the Linux box today. Hyperterm
    does fine, if a bit slow, PuTTY ssh works fine, and Cygwin popped
    right up without any real delay. Now I just have to figure out what
    the heck was changed.


    -----BEGIN PGP SIGNATURE-----
    Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

    iQA/AwUBQQB9WaauO3Snl+t6EQKHHQCfSj7Hve+PSMP0RYCeCYG1D2RS/r0Anj+Y
    Ogie/viVhrOWiwNlSnrROWeb
    =O2uU
    -----END PGP SIGNATURE-----
     
    Joe Bramblett, KD5NRH, Jul 23, 2004
    #8
  9. Delays in tcp/ip are often timeouts due to tcpwrappers attempting to
    resolve a name for connecting IP. This can depend upon hosts.allow,
    hosts.deny, /etc/hosts, or if nameserver(s) in /etc/resolv.conf are not
    reachable or do not respond (like for your ISP when not connected). So
    perhaps something changed in one of those files (or local DNS if doing
    your own).
     
    David Efflandt, Jul 24, 2004
    #9
  10. (David Efflandt) wrote in
    First off, to make this easier to describe:
    catfish - Debian box, has the modem, and 100baseT to
    4-port 802.11g WAP
    bass - XP Pro box, 100baseT to WAP, and 802.11g card
    perch - XP Pro box, 802.11g only

    Everybody has everybody else in hosts, the linux box is gatewaying for
    everybody else. (But for some reason I haven't really delved into very
    much, can't see the internet at all itself...hasn't been a big issue yet,
    but suggestions are welcome) Bass is pretty much the one I use, since it's
    by far the fastest, has the best monitor, and the comfiest chair in front
    of it.

    From bass, command line or PuTTY telnet will work consistently, while
    TCP/IP connection from hyperterminal will timeout - sometimes.
    cygwin -query catfish will display pretty much the same behavior, except
    that it works more often than hyperterm. I've tried it with and without
    perch shut down, and with all possible permutations of bass's two
    connections, and it's pretty consistent, except that sometimes it will
    start working again for no apparent reason when something changes - nothing
    in particular, though.
     
    Joe Bramblett, KD5NRH, Jul 25, 2004
    #10
  11. why does bass have both a FastEthernet NIC to WAP and a wireless card?

    Try simplifying things down and testing thorougly. Disable the wireless
    card in 'bass', and replace the WAP with a cheap 8 port switch or a cross
    over cable directly in between catfish and bass.

    make the basic networking are correct.....ip, subnet mask, etc.

    try pining on the machines from each other, etc.


    B.
     
    Brendon Caligari, Jul 25, 2004
    #11
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.