84567f0d   
   From: usenet@umbral.org.uk   
      
   "sgifford@suspectclass.com"  wrote:   
      
   > Ah, you are right.  Here is the same packet dump from Ethereal, which   
   > shows that information.  It looks right to me.   
   >   
   > 1  0.000000   CLIENT > SERVER  TCP  56110 > http [SYN]   
   >    Seq=3D2831951746 Win=3D65535 Len=3D0 MSS=3D1400   
   >   
   > 2  0.000035   SERVER > CLIENT  TCP  http > 56110 [SYN, ACK]   
   >    Seq=3D3972120946 Ack=3D2831951747 Win=3D5840 Len=3D0 MSS=3D1460   
   >   
   > 3  0.213543   CLIENT > SERVER  TCP  56110 > http [ACK]   
   >    Seq=3D2831951747 Ack=3D3972120947 Win=3D65535 Len=3D0   
      
   Can you show the full packet dumps in hex or whatever?  I've just seen a   
   problem where a Cisco PIX in front of the client was setting the Ack-number   
   non-zero in the SYN, and ipfilter on the server refused to establish state   
   because it expected Ack-number=0, with the result that the ACK got blocked   
   so the server just kept sending the SYN/ACK.   
      
   --   
   Ronan Flood    
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)