Any ideas? Users get disconnected all the time, so cant really just have them start a new session and lose all their work thats currently running on their first connection/server. if I disconnect my session and try to reconnect, the Fortigate will load balance me and put me on TS2, but the Session Directory tries to connect me to my existing session on TS1 and fails.Ĭan't figure out how to get this working. However, I can't get Session Directory to work. The users connect from their homes to the external NATd ip address of the cluster. It is a requirement that the TS Gateway farm can communicate between gateway servers. They also use Session Directory, so if a user gets disconnected, they get placed back on the same server. Cluster operation mode (multicast / unicast): If the gateway servers have multiple network adapters, use unicast cluster operation mode. I set up the virtual IP address (external), added the two Terminal Servers as "Real servers" and it works just fine. Currently have two (2003) Terminal Servers running as VMs using Microsoft NLB (in multicast mode) to cluster the two together. In an effort to stop that, I wanted to use the Fortigate's 200D 5.2.6fw Load Balancing using Least Session option instead of NLB. I've noticed in wireshark, that NLB is spewing packets to every computer on the LAN all day, every day. The users connect from their homes to the external NAT'd ip address of the cluster. They also use Session Directory, so if a user gets disconnected, they get placed back on the same server. Currently have two (2003) Terminal Servers running as VMs using Microsoft NLB (in multicast mode) to cluster the two together. I've inherited a bit of an outdated mess that I'm working towards solving, but first things first.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |