2003 Terminal Services Maximum Connections is disabled(greyed out)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

First, is there a forum for Terminal 2003?
Now the problem. We installed a new 2003 Terminal server. The radio button
for specifying the number of maximum connections is disabled. We have tried
working with the GPO to allow multiple connections, but only one user is
allowed to connect at a time. It is not user specific. If one person logs
out, then another can login, but one ONE connection at a time. The maximum
connections is disable, but indicates "1" conneciton.
What am I missing here? Licenses are being issued as the person connects.
Any info would be great!

Brock

(e-mail address removed)
 
The TS forum with the highest traffic is
microsoft.public.windows.terminal_services
The trend is towards version-independent newsgroups.

Your problem sounds weird!
How is your domain setup? AD? What is the role of the TS in the
domain? Have you checked with GPresult which GPOs are affecting
the TS?

Is there anything in the EventLog?
Just to cover all the possibilities: have you checked your server
CAL licensing situation, in Control Panel - Licensing applet?
 
Vera,

This is a clean build of a new Win2k3 on a new Dell 1850. Domain is running
in 2000 mixed mode. We have a running 2000 terminal server, and this server
is supposed to be it's replacement. This server is doing nothing except TS.

There is nothing in the event log. After a complete re-install, the max
connections is greyed out and set to 1. We assume this is why we can only
connect 1 at a time, but why can't we change that setting. Nothing is
configured in the local GP of the TS, just fresh default install. Even if we
set the max connection in the local GP it still doesn't change it. We were
able to edit the registry manually to chang ethe number, but them if we even
clicked on the "Network Adaptor" tab in the RDP properties, the whole
properties box would disapear and the TSCC windo would disapear also, but
everything else seemed to work. Obviously, we'd rather not put it into
production that way.
 
You write:
... if we even
clicked on the "Network Adaptor" tab in the RDP properties, the
whole properties box would disapear...
Click to expand...

This is definitively not as it should be! Have you updated the NIC
driver with the latest version from Dell or the NIC manufacturer?
Or even tried to swap the NIC with another one?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Yes, we have the most current version of the NIC drivers loaded. Again, we
only get that behavior if we manually edit the registry to allow more
connections.

I have found that if the machine is not a member of the domain that we are
able to access the max connections. But I have gone over the default GP and
the only things we have defined are password rules and not allowing XP SP2 to
be installed, nothing else is even defined. Is there some hidden TS GP that
is not part of the default GP? And if so how do I find it and edit it. Also,
wouldn't it affect our Win2k TS also, not just our 2k3 box?

Shawn
 
I would run gpresult to check which policies are affecting your
server.
And the setting can be found here:

Computer Configuration\Administrative Templates\Windows Components
\Terminal Services
Limit number of connections

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Back
Top