5

I'm having a pretty bizarre problem with a Terminal Services server used for RemoteApp. In our network the server works as it should, but at a client's office if two users log in simultaneously, the first one gets disconnected as the other one connects. The users belong to the same group but have individual users. The similar configuration works fine for all other clients.

About the server, it's Windows 2008 SP2, no AD, SSL encrypted connections. Event viewer shows no useful information.

Any hints where to start debugging? Do you need more info about the setup?

EDIT: Ok, so the problem has resurfaced with another pair of clients. Similar setup: two users, one group, more than enough CALs. Could this be a problem in the client side firewall/NAT?

6
  • 2
    Is there a chance the client used to connect is configured to connect to the console? One logs on, the other is logged off?
    – Mitch
    Nov 25, 2011 at 0:08
  • The clients connect through TS Web Access, so no console access. Nov 25, 2011 at 7:04
  • When you are attempting from within your network, are you using TS Web access as well?
    – iainlbc
    Nov 28, 2011 at 16:58
  • Sounds like the "Restrict each user to a single session" setting in the TS Configuration GUI or GPO, seems odd that it would only affect external users, perhaps there is a setting specific to web-access (if you are not using that for internal tests)
    – iainlbc
    Nov 28, 2011 at 17:09
  • @iainlbc No, we use mstsc to administer the server. We have tried to simulate the problem with TSWA from our network but couldn't reproduce. Note that the server is hosted elsewhere, not in out network. Dec 1, 2011 at 15:29

1 Answer 1

2
+25

You might not have enough User/Device CALs to host all of the concurrent connections. Terminal Services by default will allow two connections for administrative purposes. If it's a very small office, this problem may manifest itself sporadically as the users inadvertently play "musical chairs" with the two allotted spots.

To check licensing, go to Start menu -> Administrative Tools -> Terminal Services -> Terminal Services Configuration. In the console tree, click Licensing Diagnosis and it will tell you how many CALs you have available (above the two freebies). In the Licensing section it should indicate how the server is licensed and where the license server is located (in your case it may be localhost).

1
  • I checked the Licensing status, and there are (roughly 2x) more available licenses than there are users on the server, so this can't be the reason. Dec 1, 2011 at 15:33

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .