Re: TS 2003 Server in Application mode only allows 2 connections

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

There have been a couple of similar posts here during the last year
or so, and in all cases, the problem was caused by a GPO.
Run the Resultant Set of Policies to find out which GPO is causing
this. The setting you are looking for is:

Administrative Templates\Windows Components\Terminal Services
"Limit number of connections"

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?RGFycnlsIEI=?= <Darryl B@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 09 okt 2006 in
microsoft.public.windows.terminal_services:

I am trying to figure out why this 2003 member server can only
have 2 remote connections at a time (like it's running in Admin
mode). This is a W2k3 server running in Application
compatibility mode. I have a TS License Server installed on the
same machine with 35 TS Per-Device CALs installed, and 5 left to
issue. My target users are in the Remote Desktop Users group,
The Licenses server is activated with available CALs and the TS
server can communicate with the TS License server (They're on
the same server). In fact, the Licensing server has handed out a
couple of TS licenses while I've been trying to troubleshoot
this issue. When I try to adjust the connection count on the
Network Adapter tab of the TS Configurations Properties window,
the ability to set Unlimited connections is greyed-out, but
appears to be set to limit "max connections" to 2. I've checked
my GPO settings for the local machine and I don't see any
settings configured that should block more than 2 users.
When users are denied access (all on XP clients), they get the
standard error: The client could not connect to the remote
computer. Remote connection might not be enabled or the computer
might be too busy to accept new connections. It is also possible
that network problems are prevent your connection. * BTW, This
error is returned as soon as the connect button is hit, so it
doesn't appear that there is any negotiation going on with the
server before the error is returned*

The problem is NOT machine specific. If I terminate one of the
TS connections I am using, a pc that had been returning the
above error is immediately able to establish a TS session with
the TS server.

Any ideas or suggestions are appreciated.
-darryl
.

Quantcast