[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::terminal_servers

Title:Terminal Servers
Notice:See Note 2 for Directory of important notes. Please use keywords.
Moderator:LAVC::CAHILLON
Created:Tue May 14 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3547
Total number of notes:12300

3424.0. "Unwanted Characters from TELNET CLIENT connections" by CSC32::L_DEGROFF () Tue Jan 28 1997 20:40

    Customer has a UNIX host connected to a DS700 port 1 configured as a
    dedicated TELNET port with session set to binary, only output flow
    control, and port type soft.  The DS700 port 1 makes a TELNET connection
    to a DS90TL remote access port 1, TELNET SERVER characteristic set to
    none, which provides a connection to a serial device which the UNIX box
    sends/received data from.  The problem is that when the UNIX box connects
    to the DS700 port, it seeds a data stream, 00707 0D.  The DS700 port then
    reponds with a 00707 ^M.  The ^M is causing problems with the customer's
    program.  He wants to know what it is and how to stop this character from
    being sent.  If he triggers the port connection by a LOCAL> CONNECT PORT
    1 command, the characters are not sent.  But, he does not want to start
    the connection this way because it would require monitoring the connection
    to make reconnections the same way if the link should go down.
    
    What are the characters ^M and how can the customer stop them from
    being sent to his UNIX host.
    
    Thanks
    
    Larry De Groff
T.RTitleUserPersonal
Name		DateLines
3424.1IROCZ::D_NELSONDave Nelson LKG1-3/A11 226-5358Wed Jan 29 1997 20:0951
RE: .0
    
>    What are the characters ^M and how can the customer stop them from
>    being sent to his UNIX host.
    
Ctrl-M is a carriage-return (control charracters are often represented with
the "^" prefix).  You should look at the Telnet Session characteristics on both
DECservers.  There are displays of the form:

Local> sho port 1 telnet client char

Port  1

Profile:                Character
Echo:                      Remote    Newline From Term:           <CR>
Toggle Echo:                   ^E    Newline From Host:         <CRLF>
Binary:                  Disabled    Newline To Term:           <CRLF>
Xmit Char Size:                 8    Newline To Host:           <CRLF>
Rcv Char Size:                  8    Input Flow Control:       Enabled
Signal Req:               Enabled    Output Flow Control:      Enabled
IP:                   +s +f    ^Y    Verification:             Enabled
SYNCH:                +s -f    ^X    Switch Character:         Enabled
AYT:                  -s -f    ^T    Quote:                       None
AO:                   -s +f    ^O    Terminal Type:            UNKNOWN
EOR:                  -s -f  None
BRK:                  -s -f  None
                                    
and

Local> sho port 1 telnet server char

Port  1

Xmit Char Size:                 8    Newline From Term:         <CRLF>
Rcv Char Size:                  8    Newline From Host:         <CRLF>
IP:                          None    Newline To Term:           <CRLF>
AYT:                         None    Newline To Host:             <CR>
AO:                          None    EC:                          None
EOR:                         None    EL:                          None
NOP:                         None    BRK:                        Break
PPP Hot Key:                 None    SLIP Hot Key:                None
Echo Negotiation:        Initiate

Local> 

You want to diddle with the "Newline" stuff.

Regards,

Dave
3424.2NEWLINE char set to NONECSC32::L_DEGROFFMon Feb 03 1997 13:084
    All the NEWLINE characteristics are set to <NONE>.  Before setting them
    to NONE, the customer was getting a whole stream of characters back.
    
    Larry