HP OpenVMS Systems

Large TCP/IP Sequence Numbers?

» close window

The Question is:

 
Running TCP/IP V5.0, VAX OpenVMS V7.2.
Problems with the TCP/IP connection when the sequence number sent to the VAX reaches the maximum signed int value (2.147.483.647).
Corresponding a sniffer the TCP/IP server (PC) sends seq.no. 2.147.483.167  .. 2.147.483.679 (512 Byte). The VAX acknowledges only seq.no. 2.147.483.167.
PC: 2.147.483.679 .. 2.147.484.191  -> VAX acknowledges 2.147.483.167 again.
That continues until the PC starts to resend the packets beginning with 2.147.483.167, the same procedure restarts until the VAX resets the TCP/IP connection.
Is there any known problem (signed/unsigned int) concerning the VAX TCP/IP V5.0 sequence/ack numbers?
Thanks!
 
 

The Answer is :

 
  First, please move to V5.0A -- a similar problem was identified
  in TCP/IP V5.0 on OpenVMS VAX, and was then fixed in V5.0A.
 
  If the problem persists, please contact the Compaq Customer Support
  Center -- while this report has been passed along to the TCP/IP
  Services Engineering team, please contact the support center directly
  to report this and to provide any needed additional details.
 
  Please see topic 3799 for a similar (but not directly related)
  discussion of sequence numbers.
 
 

  

     

     
answer written or last revised on ( 3-MAR-2000 )
     
» close window