windows server "The remote computer has ended the connection" TS Application Mod

[Guest Robert Toro]

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 style_emoticons//smile.gif

[Guest Vera Noest [MVP]]

Have you checked the EventLog on the server?

Have you checked the maximum number of allowed connections in

Terminal Services Configuration - rdp-tcp connection properties -

Network?

Are any GPOs applied to the server? Any recent changes there?

 

If the above doesn't give you a clue, I'd delete the rdp-tcp

connection in tscc.msc and create a new one, with the default

settings.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

=?Utf-8?B?Um9iZXJ0IFRvcm8=?= wrote on 30 apr 2009:

> 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 style_emoticons//smile.gif

[Guest Roque Martinez]

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 style_emoticons//smile.gif

>

[Guest Simon Gray]

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

 

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 style_emoticons//smile.gif

> >

[Guest Vera Noest [MVP]]

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

 

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==?=

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 style_emoticons//smile.gif

[Guest Simon Gray]

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

 

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==?=

> 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 style_emoticons//smile.gif

>

[Guest Corrie Schoonbee]

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

 

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==?=

> > 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 style_emoticons//smile.gif

> >

[Guest Vera Noest [MVP]]

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

 

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==?=

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==?=

>> > 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 style_emoticons//smile.gif