[c-nsp] 2911 Terminal Server 8bits character problem

[Hughes, Scott GRE-MG]

Try using tcp port 400x instead of port 200x. 


On Mar 24, 2011, at 9:17 PM, "Chubby" <chubby_cripth at yahoo.com> wrote:

> Hi Andrew,
> 
> This is a reverse telnet session that communicate using Serial <> TCP
> 
> 0xFF is part of data payload, and I can not find a way to double the content of payload ie: "0xFF 0xFF"
> 
> The config is:
> Line 0/0/0
> No exec
> Exec-timeout 0 0
> Data-character-bits 8
> Exec-character-bit 8
> Transport input all
> Telnet transparent
> Telnet refuse-negotiation
> !
> 
> Best Regards,
> 
> Ranokarno
> Powered by NCS
> 
> On Mar 25, 2011, at 2:48 AM, Andrew Gray <4457 at blargh.com> wrote:
> 
>> This sounds like you're telnet'ing in with something other than telnet - 0xFF is the Telnet escape character - it's expecting another control code after 0xFF to negotiate options and such.  To send a single 0xFF onward, you need to double it, i.e. 0xFF 0xFF. 
>> Rano Karno writes: 
>>> the issue is whenever server make a session to terminal host and sending "FF" hexa, it seem the router did not transmit it to terminal host, thus make the system hang.
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/


NOTICE TO RECIPIENT: The information contained in this message from
Great River Energy and any attachments are confidential and intended
only for the named recipient(s). If you have received this message in 
error, you are prohibited from copying, distributing or using the
information. Please contact the sender immediately by return email and
delete the original message.