Hi, I’m having a some confusing issue with my Load Balanced Windows Terminal Server IP-based persistence behaviour: IP-based persistence ON: When the persistence is turned on, drainstop-ing from the SteelApp doesn’t do anything at all, the client still redirected to the node that I drain stopped, hence causing some issue during the node maintenance. Expected result: drain stopped node should no longer accept any client / user traffic at all. IP-based persistence OFF: When the persistence is turned off, one by one the node is dropping from the load balancer with the error: “Passive monitoring detected an error: Read error, Failed to read data from this node.” In red with the exclamation mark on almost all nodes. “SERIOUS Pool RDP-Farm1:3389, Node <one of the Windows TS IP>:3389: Node <one of the Windows TS IP> has failed - Read error: Connection reset by peer” Expected result: when the persistence is turned off, the node should not be dropping off the load balancer, it should stay operational with no error. Note, I'm using 2x Stingray Traffic Manager Virtual Appliance 1000 M 9.6r1. Is that the default behaviour or something wrong happens ? Thanks in advance.
... View more