Terminal services suddenly have stopped working..

July 17, 2007

Hi.. There is a problem in only one of our servers..

The thing is that everything was working fine.. I had some users in the

terminal server users group and they were connecting to this server..

But today, I don't know what happened, everytime I try to connect to this

server, I get an error:

To log on to this remote computer, you must have Terminal Server User Access

permissions on this computer. By default members of the Remote Desktop Users

group have these permissions. If you are not a member of the Remote Desktop

Users group or another group another group that has these permissions, you

must be granted these permissions manually.

Also I went to the event log of the server and I can see that everytime a

user tries to connect, there is a system warning:

The terminal services could not locate a license server. Confirm that all

license servers on the network are registered in WINS\DNS, accepting network

requests, and the Terminal Services Licensing Service is running.

I checked users were in the correspondent groups, I also tried the solutions

at

http://support.microsoft.com/kb/329896/en-us

and http://support.microsoft.com/kb/306578/en-us

But still I have the same problem.. Can someone help me solve this please??

Thanks..

July 17, 2007

Re: Terminal services suddenly have stopped working..

I am not sure if the event in the event log is related to your logon

failure. I would suggest checking all the policy values that may deny you

logon to server. For example:

- Computer management - users properties - Terminal Services Profile - Deny

logon to Terminal Server.

- If it is domain user, go to AD for user properties and check the same.

- Secpol.msc - user rights assignments - allow logon through terminal

services.

You might want to logon to console of the server and verify that your token

includes "Remote Desktop Users" by typing "whoami /groups".

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"averied" <averied@discussions.microsoft.com> wrote in message

news:00920095-2732-408E-B33E-F75490185C71@microsoft.com...

> Hi.. There is a problem in only one of our servers..

>

> The thing is that everything was working fine.. I had some users in the

> terminal server users group and they were connecting to this server..

>

> But today, I don't know what happened, everytime I try to connect to this

> server, I get an error:

>

> To log on to this remote computer, you must have Terminal Server User

> Access

> permissions on this computer. By default members of the Remote Desktop

> Users

> group have these permissions. If you are not a member of the Remote

> Desktop

> Users group or another group another group that has these permissions, you

> must be granted these permissions manually.

>

> Also I went to the event log of the server and I can see that everytime a

> user tries to connect, there is a system warning:

>

> The terminal services could not locate a license server. Confirm that all

> license servers on the network are registered in WINS\DNS, accepting

> network

> requests, and the Terminal Services Licensing Service is running.

>

> I checked users were in the correspondent groups, I also tried the

> solutions

> at

> http://support.microsoft.com/kb/329896/en-us

>

> and http://support.microsoft.com/kb/306578/en-us

>

> But still I have the same problem.. Can someone help me solve this

> please??

>

> Thanks..

July 18, 2007

Re: Terminal services suddenly have stopped working..

Thanks for ur answer...

Actually I also checked all the things u mention in ur post, and it's all

ok...

I don't know if this can be helpful... but I can connect using the followin

command:

"mstsc /console /v:servername"

But if I make a common TS connection I get the errors I metioned...

Thanks.

"Mahesh Lotlikar [MS]" wrote:

> I am not sure if the event in the event log is related to your logon

> failure. I would suggest checking all the policy values that may deny you

> logon to server. For example:

>

> - Computer management - users properties - Terminal Services Profile - Deny

> logon to Terminal Server.

> - If it is domain user, go to AD for user properties and check the same.

> - Secpol.msc - user rights assignments - allow logon through terminal

> services.

>

> You might want to logon to console of the server and verify that your token

> includes "Remote Desktop Users" by typing "whoami /groups".

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "averied" <averied@discussions.microsoft.com> wrote in message

> news:00920095-2732-408E-B33E-F75490185C71@microsoft.com...

> > Hi.. There is a problem in only one of our servers..

> >

> > The thing is that everything was working fine.. I had some users in the

> > terminal server users group and they were connecting to this server..

> >

> > But today, I don't know what happened, everytime I try to connect to this

> > server, I get an error:

> >

> > To log on to this remote computer, you must have Terminal Server User

> > Access

> > permissions on this computer. By default members of the Remote Desktop

> > Users

> > group have these permissions. If you are not a member of the Remote

> > Desktop

> > Users group or another group another group that has these permissions, you

> > must be granted these permissions manually.

> >

> > Also I went to the event log of the server and I can see that everytime a

> > user tries to connect, there is a system warning:

> >

> > The terminal services could not locate a license server. Confirm that all

> > license servers on the network are registered in WINS\DNS, accepting

> > network

> > requests, and the Terminal Services Licensing Service is running.

> >

> > I checked users were in the correspondent groups, I also tried the

> > solutions

> > at

> > http://support.microsoft.com/kb/329896/en-us

> >

> > and http://support.microsoft.com/kb/306578/en-us

> >

> > But still I have the same problem.. Can someone help me solve this

> > please??

> >

> > Thanks..

>

July 18, 2007

Re: Terminal services suddenly have stopped working..

That suggests a licensing problem, since console sessions never use

a TS CAL. That would explain the EventLog entry, which warns that

your TS cannot locate a TS Licensing Server.

Do you have a TS Licensing Server installed and activated?

If so, the TS obviously cannot find it.

You can configure the preferred TS Licensing Server on the TS in

Terminal Services Configuration, or use a GPO.

_________________________________________________________

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?YXZlcmllZA==?= <averied@discussions.microsoft.com> wrote

on 18 jul 2007 in microsoft.public.windows.terminal_services:

> Thanks for ur answer...

>

> Actually I also checked all the things u mention in ur post, and

> it's all ok...

>

> I don't know if this can be helpful... but I can connect using

> the followin command:

>

> "mstsc /console /v:servername"

>

> But if I make a common TS connection I get the errors I

> metioned...

>

> Thanks.

>

> "Mahesh Lotlikar [MS]" wrote:

>

>> I am not sure if the event in the event log is related to your

>> logon failure. I would suggest checking all the policy values

>> that may deny you logon to server. For example:

>>

>> - Computer management - users properties - Terminal Services

>> Profile - Deny logon to Terminal Server.

>> - If it is domain user, go to AD for user properties and check

>> the same. - Secpol.msc - user rights assignments - allow logon

>> through terminal services.

>>

>> You might want to logon to console of the server and verify

>> that your token includes "Remote Desktop Users" by typing

>> "whoami /groups".

>>

>> --

>> This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>>

>> "averied" <averied@discussions.microsoft.com> wrote in message

>> news:00920095-2732-408E-B33E-F75490185C71@microsoft.com...

>> > Hi.. There is a problem in only one of our servers..

>> >

>> > The thing is that everything was working fine.. I had some

>> > users in the terminal server users group and they were

>> > connecting to this server..

>> >

>> > But today, I don't know what happened, everytime I try to

>> > connect to this server, I get an error:

>> >

>> > To log on to this remote computer, you must have Terminal

>> > Server User Access

>> > permissions on this computer. By default members of the

>> > Remote Desktop Users

>> > group have these permissions. If you are not a member of the

>> > Remote Desktop

>> > Users group or another group another group that has these

>> > permissions, you must be granted these permissions manually.

>> >

>> > Also I went to the event log of the server and I can see that

>> > everytime a user tries to connect, there is a system warning:

>> >

>> > The terminal services could not locate a license server.

>> > Confirm that all license servers on the network are

>> > registered in WINS\DNS, accepting network

>> > requests, and the Terminal Services Licensing Service is

>> > running.

>> >

>> > I checked users were in the correspondent groups, I also

>> > tried the solutions

>> > at

>> > http://support.microsoft.com/kb/329896/en-us

>> >

>> > and http://support.microsoft.com/kb/306578/en-us

>> >

>> > But still I have the same problem.. Can someone help me solve

>> > this please??

>> >

>> > Thanks..

July 18, 2007

Re: Terminal services suddenly have stopped working..

Thanks for ur answer...

I don't know what's going on here.. I have 4 other servers, and none of them

has given this problem.. I've never had to modify nothing...

Just in this one server I don't know what has happened since yesterday, I'm

getting this messages..

Yesterday I activated the TS license server in the server with the problem,

and I did what's written in the KB solutions I mention in my first thread.. I

also open a MMC snap in, and added group policies, and I added the name of

the 2 licence servers I have activated, I also did a gpupdate from the

command line after this..

I still get the same message... Any other thing that can be happening??

"Vera Noest [MVP]" wrote:

> That suggests a licensing problem, since console sessions never use

> a TS CAL. That would explain the EventLog entry, which warns that

> your TS cannot locate a TS Licensing Server.

> Do you have a TS Licensing Server installed and activated?

> If so, the TS obviously cannot find it.

> You can configure the preferred TS Licensing Server on the TS in

> Terminal Services Configuration, or use a GPO.

>

> _________________________________________________________

> 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?YXZlcmllZA==?= <averied@discussions.microsoft.com> wrote

> on 18 jul 2007 in microsoft.public.windows.terminal_services:

>

> > Thanks for ur answer...

> >

> > Actually I also checked all the things u mention in ur post, and

> > it's all ok...

> >

> > I don't know if this can be helpful... but I can connect using

> > the followin command:

> >

> > "mstsc /console /v:servername"

> >

> > But if I make a common TS connection I get the errors I

> > metioned...

> >

> > Thanks.

> >

> > "Mahesh Lotlikar [MS]" wrote:

> >

> >> I am not sure if the event in the event log is related to your

> >> logon failure. I would suggest checking all the policy values

> >> that may deny you logon to server. For example:

> >>

> >> - Computer management - users properties - Terminal Services

> >> Profile - Deny logon to Terminal Server.

> >> - If it is domain user, go to AD for user properties and check

> >> the same. - Secpol.msc - user rights assignments - allow logon

> >> through terminal services.

> >>

> >> You might want to logon to console of the server and verify

> >> that your token includes "Remote Desktop Users" by typing

> >> "whoami /groups".

> >>

> >> --

> >> This posting is provided "AS IS" with no warranties, and

> >> confers no rights.

> >>

> >> "averied" <averied@discussions.microsoft.com> wrote in message

> >> news:00920095-2732-408E-B33E-F75490185C71@microsoft.com...

> >> > Hi.. There is a problem in only one of our servers..

> >> >

> >> > The thing is that everything was working fine.. I had some

> >> > users in the terminal server users group and they were

> >> > connecting to this server..

> >> >

> >> > But today, I don't know what happened, everytime I try to

> >> > connect to this server, I get an error:

> >> >

> >> > To log on to this remote computer, you must have Terminal

> >> > Server User Access

> >> > permissions on this computer. By default members of the

> >> > Remote Desktop Users

> >> > group have these permissions. If you are not a member of the

> >> > Remote Desktop

> >> > Users group or another group another group that has these

> >> > permissions, you must be granted these permissions manually.

> >> >

> >> > Also I went to the event log of the server and I can see that

> >> > everytime a user tries to connect, there is a system warning:

> >> >

> >> > The terminal services could not locate a license server.

> >> > Confirm that all license servers on the network are

> >> > registered in WINS\DNS, accepting network

> >> > requests, and the Terminal Services Licensing Service is

> >> > running.

> >> >

> >> > I checked users were in the correspondent groups, I also

> >> > tried the solutions

> >> > at

> >> > http://support.microsoft.com/kb/329896/en-us

> >> >

> >> > and http://support.microsoft.com/kb/306578/en-us

> >> >

> >> > But still I have the same problem.. Can someone help me solve

> >> > this please??

> >> >

> >> > Thanks..

>

July 18, 2007

Re: Terminal services suddenly have stopped working..

So after those changes you made, you still get the "cannot locate

Licensing Server" Event?

I'd start to verify that you really have a discovery problem by

running lsview from the Resource Kit on this TS.

You write that you added the 2 Licensing Servers in a local policy

on the TS. Are you sure that you don't have domain-wide policy

which overrides this?

Are there any other Event warnings, about network issues, group

policy issues, etc?

And which SP are you running on the TS?

If you're still on SP1, check this:

922508 - Terminal Servers cannot locate the license servers when

you use the "Use the specified Terminal Server license servers"

policy setting

http://support.microsoft.com/?kbid=922508

_________________________________________________________

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?YXZlcmllZA==?= <averied@discussions.microsoft.com> wrote

on 18 jul 2007 in microsoft.public.windows.terminal_services:

> Thanks for ur answer...

>

> I don't know what's going on here.. I have 4 other servers, and

> none of them has given this problem.. I've never had to modify

> nothing...

>

> Just in this one server I don't know what has happened since

> yesterday, I'm getting this messages..

>

> Yesterday I activated the TS license server in the server with

> the problem, and I did what's written in the KB solutions I

> mention in my first thread.. I also open a MMC snap in, and

> added group policies, and I added the name of the 2 licence

> servers I have activated, I also did a gpupdate from the command

> line after this..

>

> I still get the same message... Any other thing that can be

> happening??

>

> "Vera Noest [MVP]" wrote:

>

>> That suggests a licensing problem, since console sessions never

>> use a TS CAL. That would explain the EventLog entry, which

>> warns that your TS cannot locate a TS Licensing Server.

>> Do you have a TS Licensing Server installed and activated?

>> If so, the TS obviously cannot find it.

>> You can configure the preferred TS Licensing Server on the TS

>> in Terminal Services Configuration, or use a GPO.

>>

>> _________________________________________________________

>> 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?YXZlcmllZA==?= <averied@discussions.microsoft.com>

>> wrote on 18 jul 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > Thanks for ur answer...

>> >

>> > Actually I also checked all the things u mention in ur post,

>> > and it's all ok...

>> >

>> > I don't know if this can be helpful... but I can connect

>> > using the followin command:

>> >

>> > "mstsc /console /v:servername"

>> >

>> > But if I make a common TS connection I get the errors I

>> > metioned...

>> >

>> > Thanks.

>> >

>> > "Mahesh Lotlikar [MS]" wrote:

>> >

>> >> I am not sure if the event in the event log is related to

>> >> your logon failure. I would suggest checking all the policy

>> >> values that may deny you logon to server. For example:

>> >>

>> >> - Computer management - users properties - Terminal Services

>> >> Profile - Deny logon to Terminal Server.

>> >> - If it is domain user, go to AD for user properties and

>> >> check the same. - Secpol.msc - user rights assignments -

>> >> allow logon through terminal services.

>> >>

>> >> You might want to logon to console of the server and verify

>> >> that your token includes "Remote Desktop Users" by typing

>> >> "whoami /groups".

>> >>

>> >> --

>> >> This posting is provided "AS IS" with no warranties, and

>> >> confers no rights.

>> >>

>> >> "averied" <averied@discussions.microsoft.com> wrote in

>> >> message

>> >> news:00920095-2732-408E-B33E-F75490185C71@microsoft.com...

>> >> > Hi.. There is a problem in only one of our servers..

>> >> >

>> >> > The thing is that everything was working fine.. I had some

>> >> > users in the terminal server users group and they were

>> >> > connecting to this server..

>> >> >

>> >> > But today, I don't know what happened, everytime I try to

>> >> > connect to this server, I get an error:

>> >> >

>> >> > To log on to this remote computer, you must have Terminal

>> >> > Server User Access

>> >> > permissions on this computer. By default members of the

>> >> > Remote Desktop Users

>> >> > group have these permissions. If you are not a member of

>> >> > the Remote Desktop

>> >> > Users group or another group another group that has these

>> >> > permissions, you must be granted these permissions

>> >> > manually.

>> >> >

>> >> > Also I went to the event log of the server and I can see

>> >> > that everytime a user tries to connect, there is a system

>> >> > warning:

>> >> >

>> >> > The terminal services could not locate a license server.

>> >> > Confirm that all license servers on the network are

>> >> > registered in WINS\DNS, accepting network

>> >> > requests, and the Terminal Services Licensing Service is

>> >> > running.

>> >> >

>> >> > I checked users were in the correspondent groups, I also

>> >> > tried the solutions

>> >> > at

>> >> > http://support.microsoft.com/kb/329896/en-us

>> >> >

>> >> > and http://support.microsoft.com/kb/306578/en-us

>> >> >

>> >> > But still I have the same problem.. Can someone help me

>> >> > solve this please??

>> >> >

>> >> > Thanks..

July 18, 2007

RE: Terminal services suddenly have stopped working..

Your Terminal server cannot get to a license server

If you do not have a license server with valid licenses installed then you

will have to install a terminal License server with appropriate licenses.

If you do have a license server installed, and you have licenses purchased,

they you may have the Terminal Server in the wrong mode for the type of

license that you have.

Also if the Terminal Server cannot get to a license server then you may have

to tell it where the license server is.

Thanks

"averied" wrote:

> Hi.. There is a problem in only one of our servers..

>

> The thing is that everything was working fine.. I had some users in the

> terminal server users group and they were connecting to this server..

>

> But today, I don't know what happened, everytime I try to connect to this

> server, I get an error:

>

> To log on to this remote computer, you must have Terminal Server User Access

> permissions on this computer. By default members of the Remote Desktop Users

> group have these permissions. If you are not a member of the Remote Desktop

> Users group or another group another group that has these permissions, you

> must be granted these permissions manually.

>

> Also I went to the event log of the server and I can see that everytime a

> user tries to connect, there is a system warning:

>

> The terminal services could not locate a license server. Confirm that all

> license servers on the network are registered in WINS\DNS, accepting network

> requests, and the Terminal Services Licensing Service is running.

>

> I checked users were in the correspondent groups, I also tried the solutions

> at

> http://support.microsoft.com/kb/329896/en-us

>

> and http://support.microsoft.com/kb/306578/en-us

>

> But still I have the same problem.. Can someone help me solve this please??

>

> Thanks..

July 20, 2007

Re: Terminal services suddenly have stopped working..

On Jul 18, 10:32 pm, Rob (Microsoft)

<RobMicros...@discussions.microsoft.com> wrote:

> Your Terminal server cannot get to a license server

>

> If you do not have a license server with valid licenses installed then you

> will have to install a terminal License server with appropriate licenses.

>

> If you do have a license server installed, and you have licenses purchased,

> they you may have the Terminal Server in the wrong mode for the type of

> license that you have.

>

> Also if the Terminal Server cannot get to a license server then you may have

> to tell it where the license server is.

>

> Thanks

>

> "averied" wrote:

> > Hi.. There is a problem in only one of our servers..

>

> > The thing is that everything was working fine.. I had some users in the

> > terminal server users group and they were connecting to this server..

>

> > But today, I don't know what happened, everytime I try to connect to this

> > server, I get an error:

>

> > To log on to this remote computer, you must have Terminal Server User Access

> > permissions on this computer. By default members of the Remote Desktop Users

> > group have these permissions. If you are not a member of the Remote Desktop

> > Users group or another group another group that has these permissions, you

> > must be granted these permissions manually.

>

> > Also I went to the event log of the server and I can see that everytime a

> > user tries to connect, there is a system warning:

>

> > The terminal services could not locate a license server. Confirm that all

> > license servers on the network are registered in WINS\DNS, accepting network

> > requests, and the Terminal Services Licensing Service is running.

>

> > I checked users were in the correspondent groups, I also tried the solutions

> > at

> > http://support.microsoft.com/kb/329896/en-us

>

> > and http://support.microsoft.com/kb/306578/en-us

>

> > But still I have the same problem.. Can someone help me solve this please??

>

> > Thanks..- Hide quoted text -

>

> - Show quoted text -

try lsview (freely downlodable) or on windows resource kit to see if

the Ts servers sees a TS license server.

if not manually ad a ts server to the registry.

hope this helps,

see ya

http://www.bjornbats.nl

all the latest SBC & virtual news

MCSE+S,CCEA,CCIA,Vmware VCP,Softgrid Admin

http://www.ardenceguru.com

for all your ardence questions

Sign In

Terminal services suddenly have stopped working..

Recommended Posts

Guest averied

Popular Days

Popular Days

Guest Mahesh Lotlikar [MS]

Guest averied

Guest Vera Noest [MVP]

Guest averied

Guest Vera Noest [MVP]

Guest Rob (Microsoft)

Guest bjornbats

Similar Content

Local Security Authority Process Stop working

my second monitor stopped working

my pc is restarting suddenly

Terminal server error

With Default Terminal set to Windows Terminal - Use start-process to launch PWSH in the Windows Console Host

Browse

Activity

Site Info