rid@bjcong.bj.co.uk (RHIDIAN PHILLIPS) (04/10/91)
Hi, I'm porting ISODE 6.0 to the TLI transport interface. I've had some success but I'm baffled by the present situation! So far I can initiate an ftam session on the remote machine and get the message 'connected' and a prompt e.g. 'remote-machine>' Any local command executes OK. Remote commands (e.g. get file, put file etc) produce this response: TWrite called, with 2 bytes of data (0x1 and 0x0) followed by TWrite called, with 2 bytes of data (0x1 and 0x0) followed by TWrite with about 50 bytes of data (dependant on command) The responder starts to abort the connection when it receives the 1st 2 bytes. It sends some data containing the string "unexpected token indication (0x0)" to the initiator which in turn aborts the connection!. The main error message is as follows: FTAM protocol error (unspecific): unexpected token indication (0x0) Do you have any ideas as to what may be the problem? Is it a configuration or a coding error? Is it in some way a transport error? Where can I expect to find the solution? Any tips/ideas? The TLI must be working reasonably well to get a connection and session. I would expect each pdu to be at least 20 bytes long! (not 2 bytes) Thanks in advance Rhidian Phillips Rhidian Phillips : email : rid@bj.co.uk Boldon James Limited : phone : +44 (0)260 280465 Damian House : fax : +44 (0)260 298030 West Street, Congleton Cheshire CW12 1JN ENGLAND