SSO - TSAgent on RDS servers not sending info to collector

[Tudor]

Hello Guys,

In my environment we have 5 RDS servers and local computers.

The local computers SSO is working fine. We can see the logons on the collector and on fortinet 90d.

We have installed TSAgent on each RDP server, (open the ports, enabled remote reg) etc.. but at this point is allowing only one sesion / rdp to get connection.

Please find the below low from TSagent. 

The moment testuser2 connects tesuser1 is kicked out. 

Any ideas? Please Help

06-14-2016 18:06:05 [00000988] session ID:1, username: testuser, domain: DISCOVERY 06-14-2016 18:06:05 [00000988] session ID:1 has added to session table 06-14-2016 18:06:05 [00000988] succeeded to allocate port range 1001-1200 for session 1 06-14-2016 18:06:05 [00000988] ******** packet info -- workstation: 10.1.163.125, IP address: 10.1.163.125 ******** 06-14-2016 18:06:05 [00000988] Failed to call WTSQuerySessionInformation with WTSUserName, username length is 0, error:0 06-14-2016 18:06:05 [00000988] Failed to get username for session ID:65536 06-14-2016 18:06:05 [00000988] failed to add session 65536 06-14-2016 18:07:54 [00000988] Message WTS_REMOTE_CONNECT, session ID:2 06-14-2016 18:07:54 [00000988] Failed to call WTSQuerySessionInformation with WTSUserName, username length is 0, error:0 06-14-2016 18:07:54 [00000988] Failed to get username for session ID:2 06-14-2016 18:07:57 [00000988] Message WTS_SESSION_LOGON, session ID:2 06-14-2016 18:07:57 [00000988] session ID:2, username: testuser2, domain: DISCOVERY 06-14-2016 18:07:57 [00000988] session ID:2 has added to session table 06-14-2016 18:07:57 [00000988] succeeded to allocate port range 1201-1400 for session 2 06-14-2016 18:07:57 [00000988] ******** packet info -- workstation: 10.1.163.125, IP address: 10.1.163.125 ****

[Smoetzak]

Well they searched for a long time and found out that the users connect with a port outside of the allocated port range so they aren't seen as authenticated users.

They told me to upgrade to the newer version.

We replaced the firewall, put everything on the latest firmware, but the problem remains.

I think it has something to do with the version of Citrix.

[DiamondGalant]

Smoetzak wrote:

Well they searched for a long time and found out that the users connect with a port outside of the allocated port range so they aren't seen as authenticated users.

They told me to upgrade to the newer version.

We replaced the firewall, put everything on the latest firmware, but the problem remains.

I think it has something to do with the version of Citrix.

Thanks!

We have Windows 2008 R2.