Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) how to prevent hangup after raw TCP session?
Thanks for the quick response. I sent in the feature request last night.
Cisco has had this capability (using the /stream option on the telnet
command) for at least 5 years. Guess I can't get rid of that Cisco stuff
yet...
At 07:47 PM 7/31/97 -0700, Kevin Smith wrote:
>At 03:57 PM 7/31/97 -0700, Richard Johnsson wrote:
>>When I dial into my Max 4002/PRI/K56 (5.0Ap16/tk.m40) and do a raw tcp
>>session (terminal server command "tcp host port") the Max hangs up the
>>modem connection when the tcp session is closed by the far end. Is there
>>any way to make it just return me to the terminal server prompt instead of
>>hanging up?
>
>Not with the way it is implemented.
>
>For the purpose of optimization, the terminal server session is destroyed
>when you initiate the raw-tcp session. This saves a lot of memory, and
>allows us to have a full box of tcp-clear sessions without running out of
>memory.
>
>It might be possible to re-create the termsrv session after disconnecting
>from tcp-clear, but at this point, that would require an RFE....
>
>>When a telnet session is closed by the far end the caller is returned to
>>the prompt, but telnet puts control sequences in my data stream.
>
>Transparent or binary mode telnet might help....but you'd still get the
>telnet handshake/negotiate stuff in the start and end of the sessions.
>
>
>Kevin
>
>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: