0

I have a server where it completes the TCP handshake and client sends Client Hello and server responds with Ack. after this suddenly Server Sends REST ACK.

I expect that on receiving REST ACK, client should have closed the connection. but in client machine i still see connection is in established state (#netstate.exe -an | findstr :sourceport)

why is connection still in established even after a long time? is there a way to close that connection? i tried sending fin-ack as well but the connection is intact and only goes away with timeout.

asked Feb 21, 2025 at 11:17
2
  • Does the client in fact receive the RST? (That is, is the RST allowed through all of the firewalls involved? Could it be that one of the firewalls loses track of connection state and stops allowing packets through?) And related to that, are you sure the RST is sent by the server and not by a firewall impersonating that server? Commented Feb 21, 2025 at 16:08
  • yes client received RST as I am capturing it on the client machine. yes, i have a program that is sending reset on behalf of another program in the server machine. Commented Feb 22, 2025 at 7:03

0

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.