Forum Discussion
NimbostratusUsing Client and Server TCP profiles when you have users coming in over WAN connections
In my environment we support users in branch offices over VPN connections. Are there any good guidelines or best practices documented on how to use the TCP profiles (client/server) on the Virtual server configuration? Would you perhaps consider setting the client side to tcp-wan-optimized to deal with the higher latency and the server side to TCP since the web servers are on a 1 GB Lan connection?
I realize there is probably not going to be one right perfect answer but just looking for some input.
thanks!
5 Replies
What_Lies_Bene1Cirrostratus
I think what you've suggested is the approach most people take. I'd stick to that unless you have some need not to, such as links or networks that are high latency and/or lossy/unreliable/variable. Keep in mind the far end network as well as the WAN connections themselves; if users LAN connections are wireless it'll have an impact regardless of how good/stable the VPN is.
Of course, if you want to accommodate different types of links or far-end networks you might need dedicated Virtual Servers to allow the use of different client-side profiles.
Where HTTP traffic is concerned I'd suggest it's better to tweak compression and caching settings rather than TCP ones.
afedden_1985Cirrus
what your thinking is a very good way to start. For server side I would use tcp-lan-optimized. Thats what we do but most of our WAN links are pretty fast so I disabled Nagle's Algorithm on the copy of the tcp-wan-optimized profile we use and its working well for us.
- What_Lies_Bene1Worth noting if you disable Nagle you should probably enable Delayed ACKs.
hightower_mSounds good. Appreciate the input!
- What_Lies_Bene1You're welcome.
