Hi, I would
like to get some help to understand why after several TCP keep-alive( set to 45
seconds for debugging ) packets I see a RST negotiation here. Are there any
suggestions to debug this ? 628 9537.122717 IP
1 IP 2 TCP admin
> listener [FIN, ACK] Seq=1 Ack=1 Win=65535 Len=0 629 9537.122731 IP
2 IP 1 TCP listener
> admin [ACK] Seq=1 Ack=2 Win=65535 Len=0 630 9537.126060 IP
2 IP 1 TCP listener
> admin [RST, ACK] Seq=1 Ack=2 Win=0 Len=0 631 9537.131393 IP
1 IP 2 TCP rec
> listener [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 632 9537.131435 IP
2 IP 1 TCP listener
> rec [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 633 9539.940822 IP
2 IP 1 TCP listener
> rec [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 634 9539.956506 IP
1 IP 2 TCP rec
> listener [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 635 9539.956516 IP
2 IP 1 TCP [TCP
Dup ACK 633#1] cslistener > direcpc-video [ACK] Seq=1 Ack=1 Win=65535 Len=0 636 9540.002582 IP
1 IP 2 TCP rec
> listener [ACK] Seq=1 Ack=1 Win=65535 Len=0 Does this have something to do with data loss ? The socket
opened from AIX to a Windows client behaves like this and the client never
receives any packets. Thanks, Mohan DISCLAIMER: |
- Prev by Date: [Wireshark-users] So what use does the "-Q" flag have?
- Next by Date: Re: [Wireshark-users] Significance of RST
- Previous by thread: [Wireshark-users] So what use does the "-Q" flag have?
- Next by thread: Re: [Wireshark-users] Significance of RST
- Index(es):