TCP option lost when traffic go through TCP type Load Balance(LB) Vserver:
1. Clients send TCP syn to NetScaler with TCP option segment: 

2. Backend Servers do not receive TCP handshake with TCP option segment from NetScaler:

Configure the LB Virtual Server with "ANY" protocol, which makes NetScaler transparently forwards the client's TCP connection directly to the backend server without employing an intermediate TCP proxy. 

In CLI :

add service LBsvc_ANY <VIP> ANY <Port> -gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport NO -sp OFF -cltTimeout 120 -svrTimeout 120 -CKA NO -TCPB NO -CMP NO
add lb vserver LBvs_ANY ANY <Server_IP> <Port> -persistenceType NONE -cltTimeout 120
bind lb vserver LBvs_ANY LBsvc_ANY

NOTE: Existing LB Virtual Server is NOT support to change Protocol settings. You need to create a new LB virtual server with desired protocol: ANY. For more Load Balance Virtual Server info, click Configuration Guide to create LB Virtual Server

---

Problem Cause

In the context of a TCP-type LB Virtual Server, it's important to note that NetScaler establishes separate TCP connections with both the client and the backend server. Consequently, any TCP options configured on the client side will not be shared or applied to the backend server connection. This segregation of connections ensures distinct handling of client and server communication within the network infrastructure.