Hi Yad, The configuration you describe would be recommended for any services which you run with IP Transparency. When IP Transparency is enabled, your SteelApp will preserve the client source address when it connects to the server. The server will then use it's default gateway to respond. This default gateway must be the server side IP Address in your Traffic IP Group. The Keep-Together option ensures that the Front-End and Back-End VIPs are always raised on the same Traffic Manager. By default IP Transparency is disabled and SteelApp connects to the server using it's own IP Address. This is probably why your testing works as expected. If you were to enable IP Transparency on the pool, then you would require a Back-End VIP and for your servers to use this VIP as their default gateway. If you do not require IP Transparency then leave it disabled. If you do want to use it, then you might also want to check out the NAT / IP Forwarding options under System -> Networking. The servers will not be able to use SteelApp as a normal router unless you enable one or more of the options there. Cheers, Mark ... View more

This is covered in the User Guide in chapter 6: "Traffic IP Groups and Fault Tolerance" under the heading "Interface-to-Subnet Mapping" if you want to do a little reading. Long story short though, on your STM, if you navigate to: Services > Traffic IP Groups, under "Traffic IP Networks" there is a section called "Network Settings".  From here you can create additional subnets and define which interfaces they should live on.  So long as your upstream routing (and local routing table / default route) are all plumbed correctly, this will work: ... View more

Hi Yad, VNC will create a new listener for each display port. So port 0 will run on 5900, port 1 on 5901, etc. If you want to connect to a service listening on port 3, then your service should use port 5903. In terms of protocol, you should use either "generic server first", or "generic streaming". Cheers, Mark ... View more