RE: "The remote computer has ended the connection" TS Application

Tech-Archive recommends: Fix windows errors by optimizing your registry



Then I have to ask exactly the same questions:

Have you verified that the licensing mode of the TS matches
the type of licenses on the TS Licensing Server (Per Device /
Per User)?
Have you checked the number of allowed connections on the
network tab of the rdp-tcp connection properties?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Services
RDS troubleshooting: http://ts.veranoest.net

=?Utf-8?B?Q29ycmllIFNjaG9vbmJlZQ==?=
<CorrieSchoonbee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 28 sep 2009
in microsoft.public.windows.terminal_services:

Hi there

We are experiencing exactly the same issue. Only 1 connection
at a time is allowed. There is no event log entries on the
Terminal server

Any suggestions?

Thanks



"Simon Gray" wrote:

Yes, licensing mode is per User as per the licensing server and
connections is set to unlimited.
The problem is not that it won't accept more than 1 connection,
but that it wont accept any more connections once a connection
has been made (and then logged out). The only way to get the
ability to connect back is to reboot. The problem seems well
documented after the installation of SP1 for Server2003 but I'm
already at SP2.

Simon

"Vera Noest [MVP]" wrote:

Have you verified that the licensing mode of the TS matches
the type of licenses on the TS Licensing Server (Per Device /
Per User)?
Have you checked the number of allowed connections on the
network tab of the rdp-tcp connection properties?

_________________________________________________________
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?U2ltb24gR3JheQ==?=
<SimonGray@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 24 jul 2009 in
microsoft.public.windows.terminal_services:

Guys, I have an identical problem - the server was working
fine yesterday morning. Then RDP connections failed. After
a reboot I can only get the first session to connect and
then no more connections.

Did you get a fix to this without wiping the server?

Simon

"Roque Martinez" wrote:

Hi Robert, Did you find the solution? I�´m the same
problem...

"Robert Toro" wrote:

Looking for any help here as I have been going crazy
researching this issue and any help would be appreciated
as my client has been down for almost a week.

Here's the scenario:

Windows Server 2003 SP2
Terminal Services in Application Mode
Terminal Services Licensing Server on the same machine -
activated and 100 Per User CALS installed

The server has been working in TS App mode fine for 7
months now with no issues.

Then last week, one by one every connected user was
logged off to the point where the server will only
accept one connection via RDP and all subsequent users
are given the error: "The remote computer has ended the
connection" immediately upon trying to connect.

To the best of my knowledge no patches/services packs/
software have been installed on the server in a month
prior to this issue.

I suspected that the issue had to do with Licensing so I
installed the TS License Server on another machine and
completed the activation and CAL installs, pointed the
Terminal Server to the new licensing server with no
change.

Next, I installed the Terminal Server role from
Add/Remove Windows components, rebooted, and reinstalled
and configured to point at the new Licensing Server with
no change

Finally, I reinstalled service pack 2, rebooted, and the
problem is still identical - the first user can connect
once the machine is rebooted and all subsequent users
are given the error message above.

I've removed the client machines as a factor since the
same issue occurs when connecting from XP, Vista, Server
2003, as well as Server 2000.

Short of rebuilding the entire server, which will take
days including the software installation and config, I
am out of ideas.

Help :)
.



Relevant Pages

  • Re: Unable to use Terminal Server CALs purchased
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Configuration" and that double clicking on the "RDP" connection ... I'm not sure how many Windows User CALs are installed. ... If I go to the CP and click on "Licensing", ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to use Terminal Server CALs purchased
    ... Instead I de-activated the License server that was running on the terminal ... and that double clicking on the "RDP" connection would get you into ... I'm not sure how many Windows User CALs are installed. ... window from which I can chose my "Licensing Mode". ...
    (microsoft.public.windows.terminal_services)
  • Re: CALS do not work
    ... By installing Terminal Services, under Add Windows components. ... Did you reboot the server after installing TS? ... Check the number of allowed connections on the rdp-tcp connection - ... I then installed the Terminal Server Licensing on the 2003 ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Licensing over Citrix issuing problem
    ... the refuses everything else giving the no additional connection licences are ... Terminal Server Licensing on server SUKDDC01 has not been activated. ... Im sure its the TS Licensing as we have TWO Citrix Servers and BOTH dont ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to log on to TS
    ... in which the TS can work without a TS Licensing ... initial OS installation, then removed again after a couple of ... preinstalled on the server. ... >> And do you really mean that you installed Terminal Services? ...
    (microsoft.public.windows.terminal_services)