Dumb terminal connection now telnet

From: ALLEN, David (David.ALLEN_at_eur.crowncork.com)
Date: 05/26/04

  • Next message: srinath rajagopalan: "Unscubscribe" 
    To: sunmanagers@sunmanagers.org
Date: Wed, 26 May 2004 16:16:42 +0100

    Hi,

    I have some more info concerning the terminal server problem! I don't know
    why it did not occur to me to do this previously, but using telnet
    6.52.9.104 2048 enables me to telnet into the prime terminal server from our
    old 2.6 box. Typing exactly the same command from our new Solaris 9 box I
    get

    telnet: Unable to connect to remote host: Connection refused

    i.e. I can telnet into the terminal server using the old 2.6 machine but not
    the new 9 machine. Why?

    I am sure this is the crux of the problem and why all my dumb terminals no
    longer work. As I said in an earlier email, from the Solaris 9 box I can
    telnet into other servers, print servers, hubs etc.

    Thanks in advance for any help.

    David

    -----Original Message-----
    From: Terry L Moore [mailto:tmoore@redwood.rsc.raytheon.com]
    Sent: Tuesday, May 25, 2004 3:06 PM
    To: David.ALLEN@eur.crowncork.com
    Subject: Re: Dumb terminal connection

    It's not a bug, it's a feature! Solaris 9 comes with some things turned off

    that may have been on in Solaris 8. I think a look at "man ttymon" might
    clear
    this up for you. Basically, you need to get something listening to the
    ports
    that can provide a login prompt and handle the initial communication setup.

    ttymon and it's associated programs referenced in the man page will do that.
                             Terry
                             
    > From: "ALLEN, David" <David.ALLEN@eur.crowncork.com>
    > Date: Tue, 25 May 2004 13:47:11 +0100
    > Subject: Dumb terminal connection
    >
    > Hi,
    >
    > We recently replaced our E450 running Solaris2.6 with a V250 running
    Solaris
    > 9, and all our dumb terminals which connect via terminal servers can no
    > longer connect. ie we cannot even get a login prompt. Logging into another
    > 2.6 box from one of the dumb terminals still works.
    >
    > The new machine is using the same ip address as the old one. Any ideas how
    > to regain connection?
    >
    > Thanks in advance.
    >
    > David
    >
    >
    >
    > CONFIDENTIALITY NOTICE
    > The information contained in this e-mail is intended only for the
    > confidential use of the above named recipient. If you are not the intended
    > recipient or person responsible for delivering it to the intended
    recipient,
    > you have received this communication in error and must not distribute or
    > copy it. Please accept the sender's apologies, notify the sender
    > immediately by return e-mail and delete this communication. Thank you.
    > _______________________________________________
    > sunmanagers mailing list
    > sunmanagers@sunmanagers.org
    > http://www.sunmanagers.org/mailman/listinfo/sunmanagers

    CONFIDENTIALITY NOTICE
    The information contained in this e-mail is intended only for the
    confidential use of the above named recipient. If you are not the intended
    recipient or person responsible for delivering it to the intended recipient,
    you have received this communication in error and must not distribute or
    copy it. Please accept the sender's apologies, notify the sender
    immediately by return e-mail and delete this communication. Thank you.
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: srinath rajagopalan: "Unscubscribe"

    Relevant Pages

    • Re: virtual consoles
      ... the Console to a few Terminal servers, ... ethernet connection, or whatever. ... I was thinking of using a terminal server to connect several terminals ...
      (comp.os.vms)
    • Re: virtual consoles
      ... the Console to a few Terminal servers, ... I was thinking of using a terminal server to connect several terminals ... the serial connections are going to printers or console connections, ...
      (comp.os.vms)
    • Re: Terminal Services Licenses
      ... call Microsoft Support again. ... > Open Licences are installed on a Terminal Server in Terminal ... They are per devices licences. ... > That means we reset about 45 terminals every 3 months. ...
      (microsoft.public.windows.terminal_services)
    • Re: Terminal Server Licensing issues
      ... I posted here because it may be an issue with a W2K Terminal Server in a W2K3 environment that I may not know about and not necessarily a swing migration issue. ... I recently migrated an SBS2000 network to an SBS2K3 Premium using the swing method. ... I have installed Terminal Services licensing on the new SBS2K3 box and reactivated the W2K Terminal CAL's for my terminal clients. ... It has stopped issuing licenses to the client terminals and the client terminals are now being denied log on access. ...
      (microsoft.public.windows.server.sbs)
    • Re: Suggestion for a lexical (login mode via TCPIP)
      ... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
      (comp.os.vms)