Conference netcad::hub_mgnt

2446.0. "DS90TL - TELNET PARAMETERS" by GIDDAY::JEFFERY (Net Manager) Thu Jun 29 1995 06:33

    
    		(CROSS-POSTED IN TOOK::TERMINAL_SERVERS)
    
    Customer has been using an Emulex terminal server to provide a tcp
    connection from a 'black box' to the host application in a Vax/VMS
    system. During the installation of this system we suggested that they
    use a DS90TL instead of the Emulex.
    
    The TCP transport on the VAX is "TCPware" from process software.
    
    They have not been able to get the DS90TL to pass the application
    commands to the blackbox without error.
    
    The sequence that we see is :-
    
    1. Connect request from VAX -> designated server port and socket #2011
    2. Connect Accept from DS90TL -> VAX.
    3. Command sequence from VAX to blackbox (about 64 bytes)
    4. Blackbox executes the command and returns a status message to the
       Vax. The status message (about 128 bytes) back to the VAX is modified
       while transiting the DS90TL and the following string is added to the 
       tail of the expected message:-
    
    	FF FB 03 FF FD 03 FF FB 05 FF FD 19
    
     The command response packet (complete):-

	AA 00 04 00 8F 04 08 00 2B A0 C8 DB 08 00 45 00
        00 34 00 80 00 00 1E 06 55 52 89 14 9A 67 89 14
        9A 62 07 DB 07 2C 30 86 DA 02 66 04 36 01 50 18
        06 00 A9 24 00 00 FF FB 03 FF FD 03 FF FB 05 FF 
        FD 19 

    At this point the application gives up. This same sequence works
    without error on the Emulex terminal server.
    
    We have tried many combinations of telnet parameters/ port parameters
    in the DS90TL without any noticeable change.
    
    Is the above sequence recognisable by anyone as an expected data stream
    in these circumstances? If so, could you please suggest a way that we
    can set the DS90TL parameters so that it will act in the same manner as
    the Emulex? 
    
    					Thanks,
    						Roger.
    

    RE: .0
    
    Answered in TOOK::TERMINAL_SERVERS.