Forum Discussion
ankuragiwal_102
May 09, 2011Nimbostratus
SNAT port collision to Windows Server
We are using FastL4 profile and we are seeing SNAT port collisions to external servers running Windows TCP/IP.
F5 reuses port as soon as it becomes available while Windows TCP/IP keeps clo...
Do you have a OneConnect profile enabled on the virtual server? If so, you could remove it to prevent LTM from re-using the serverside connections for different clients. If you're not using OneConnect, LTM shouldn't be reusing serverside connections for different clients.
If you're not using OneConnect, it might be the same client who is trying to re-use the same source port too quickly. Do you need to preserve the source port? If not, can you try setting source port to change. Or you could look into modifying the Windows TCP/IP stack to tune the time wait period.
Aaron
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects