SMB FW is not able to terminate the session after received the RST ACK packet from the server

naren_nd — Tue, 14 Jan 2020 02:41:02 GMT

Happy New year to all!

It is a best practice to use the random source port. One of our customers is implementing a third party application that uses the same source and destination non-standard TCP port (50150).

The first session gets established successfully. The application tries to re-establishing another session ( after 4 seconds) using the same source and destination port if the previous session gets a break. FW considers a new session request ( SYN request) as part of the existing established session as it was neither terminated properly nor used the different source port. Therefore, the application is unable to re-established the session.

Just wondering do anyone from you came across with a similar situation? If yes then what was the resolution?

Appreciate your inputs.

Re: SMB FW is not able to terminate the session after received the RST ACK packet from the server

G_W_Albrecht — Tue, 14 Jan 2020 09:20:48 GMT

If this is a SMB FW you should post in SMB Aplliances and SMP instead ! For session timeouts, SMBs have the Advanced Setting > Aggressive Aging parameters. Find more information in sk41248 How does the Security Gateway handle Established TCP Connections?

topic Re: SMB FW is not able to terminate the session after received the RST ACK packet from the server in Spark Firewall (SMB)

SMB FW is not able to terminate the session after received the RST ACK packet from the server

Re: SMB FW is not able to terminate the session after received the RST ACK packet from the server