RDP Connection

[Mike]

Hi everyone

I'm evaluating the new version of 2x Application Server (6.2.528) but have come across an unusual issue that I hope someone on this forum maybe able to explain.
Firstly the environment Primary 2X Application Server is Windows 2008 Standard server with the full Application Server installed. The second server is a Windows 2003 R2 Enterprise edition server with just the agent installed.

Publishing a Windows 2008 and Windows 2003 Desktops (one from each server ) and all it's working fine.
Publish an application from the Windows 2008 server only and the application works fine (ie Internet Explorer 8.0).

This is where I have an issue, when I publish and application from the Windows 2003 server I get

To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop Users group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually.

I can eliminate the permissions as I can logon with standard RDP rights without any issues.

Any Ideas?

Regards
Mike

 

[Tom Haskell]

Hi,
If both servers are part of the farm, then you need to add same users (who will be accessing the published apps) to both server's remote desktop users group.
2X Loadbalancer is loadbalancing those servers.

Tom

 

[Mike]

Hi Tom

Thanks for the feedback the servers are both on a domain and the AD user account has been added as a local administrator (and local Remote Desktop Users Group) on both servers. I can connect to the 2nd 2x Application Server with a published desktop (indicating that the groups are correct) but not a published application.

I'm assuming that published desktop is on port 3389 on the second server. What port is being used for the published application?. I was under the impression it was also 3389 or is it ICA on 1494?

Mike

 

[Tom Haskell]

Hi Mike,
Looks like the server is AD as well.
You need to go to its local security policy and look for allow log on through terminal services , add users in that group. By default, only admins are added by default.
By the way 2X works on port 80 by default.

Tom

 

[paraffin]

I would usually say thatif you have added the AD group to the Remote Desktop users group locally on the machine that this is a Licensing issue.

Point TS to a valid license server and it should work.

 

[zippo]

I would usually say thatif you have added the AD group to the Remote Desktop users group locally on the machine that this is a Licensing issue.

Point TS to a valid license server and it should work.

It seems that you have a wrong configuration.
I suggest you send a suppoet request