Terminal Services Manager not connecting to a 2003 Server

October 7, 2007

I have one 2003 Standard server that will not accept a connection from

Terminal Services Manager. The message on TSM is 'You could not be

authenticated on this server.' All other 2003 and 2000 servers are accepting

connections from TSMs on different stations. This 2003 server was upgraded

from 2000 a little while back. When it was a 2000 server, it accepted TSM

connections. I *am* able to Remote Desktop successfully to this server, just

not to TSM to it in order to manage connections, etc.

Any thoughts?

Thanks,

David

October 7, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

Which account are you using when you try to connect to the server? A

local or a domain Administrator account?

Any errors or warnings in the EventLog on the servers involved?

_________________________________________________________

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

<davidtheweb@discussions.microsoft.com> wrote on 07 okt 2007 in

microsoft.public.windows.terminal_services:

> I have one 2003 Standard server that will not accept a

> connection from Terminal Services Manager. The message on TSM

> is 'You could not be authenticated on this server.' All other

> 2003 and 2000 servers are accepting connections from TSMs on

> different stations. This 2003 server was upgraded from 2000 a

> little while back. When it was a 2000 server, it accepted TSM

> connections. I *am* able to Remote Desktop successfully to this

> server, just not to TSM to it in order to manage connections,

> etc.

>

> Any thoughts?

>

> Thanks,

> David

October 8, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

I'm using a domain admin account to connect with the server, and nothing

appears in the eventlogs when I try to connect, not even in the security log.

"Vera Noest [MVP]" wrote:

> Which account are you using when you try to connect to the server? A

> local or a domain Administrator account?

> Any errors or warnings in the EventLog on the servers involved?

> _________________________________________________________

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

> <davidtheweb@discussions.microsoft.com> wrote on 07 okt 2007 in

> microsoft.public.windows.terminal_services:

>

> > I have one 2003 Standard server that will not accept a

> > connection from Terminal Services Manager. The message on TSM

> > is 'You could not be authenticated on this server.' All other

> > 2003 and 2000 servers are accepting connections from TSMs on

> > different stations. This 2003 server was upgraded from 2000 a

> > little while back. When it was a 2000 server, it accepted TSM

> > connections. I *am* able to Remote Desktop successfully to this

> > server, just not to TSM to it in order to manage connections,

> > etc.

> >

> > Any thoughts?

> >

> > Thanks,

> > David

>

October 8, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

OK, I've done some googling through the posts in the old W2K and NT

Terminal Services newsgroups, and this problem seems to be specific

for servers which had an in-place upgrade from W2K to 2003.

I found 2 possible causes and their solutions:

* Remote registry service isn't running on the target server

* change this registry key:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

\AllowRemoteRPC

to a value of REG_DWORD 1

A reboot is required.

Check them out, and I would appreciate it if you could post the

results here!

_________________________________________________________

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

<davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007 in

microsoft.public.windows.terminal_services:

> I'm using a domain admin account to connect with the server, and

> nothing appears in the eventlogs when I try to connect, not even

> in the security log.

>

> "Vera Noest [MVP]" wrote:

>

>> Which account are you using when you try to connect to the

>> server? A local or a domain Administrator account?

>> Any errors or warnings in the EventLog on the servers involved?

>> _________________________________________________________

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

>> <davidtheweb@discussions.microsoft.com> wrote on 07 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I have one 2003 Standard server that will not accept a

>> > connection from Terminal Services Manager. The message on

>> > TSM is 'You could not be authenticated on this server.' All

>> > other 2003 and 2000 servers are accepting connections from

>> > TSMs on different stations. This 2003 server was upgraded

>> > from 2000 a little while back. When it was a 2000 server, it

>> > accepted TSM connections. I *am* able to Remote Desktop

>> > successfully to this server, just not to TSM to it in order

>> > to manage connections, etc.

>> >

>> > Any thoughts?

>> >

>> > Thanks,

>> > David

October 11, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

I have not had the chance to test this on my 2003 server yet. I did put this

registry key in the HKLM registry on 2 XP SP2 computers, and it restored the

ability for TSM to interact with them. I think this answered the question,

but I will followup with the 2003 test later, as well.

"Vera Noest [MVP]" wrote:

> OK, I've done some googling through the posts in the old W2K and NT

> Terminal Services newsgroups, and this problem seems to be specific

> for servers which had an in-place upgrade from W2K to 2003.

>

> I found 2 possible causes and their solutions:

>

> * Remote registry service isn't running on the target server

> * change this registry key:

> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

> \AllowRemoteRPC

> to a value of REG_DWORD 1

>

> A reboot is required.

>

> Check them out, and I would appreciate it if you could post the

> results here!

> _________________________________________________________

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

> <davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007 in

> microsoft.public.windows.terminal_services:

>

> > I'm using a domain admin account to connect with the server, and

> > nothing appears in the eventlogs when I try to connect, not even

> > in the security log.

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Which account are you using when you try to connect to the

> >> server? A local or a domain Administrator account?

> >> Any errors or warnings in the EventLog on the servers involved?

> >> _________________________________________________________

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

> >> <davidtheweb@discussions.microsoft.com> wrote on 07 okt 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I have one 2003 Standard server that will not accept a

> >> > connection from Terminal Services Manager. The message on

> >> > TSM is 'You could not be authenticated on this server.' All

> >> > other 2003 and 2000 servers are accepting connections from

> >> > TSMs on different stations. This 2003 server was upgraded

> >> > from 2000 a little while back. When it was a 2000 server, it

> >> > accepted TSM connections. I *am* able to Remote Desktop

> >> > successfully to this server, just not to TSM to it in order

> >> > to manage connections, etc.

> >> >

> >> > Any thoughts?

> >> >

> >> > Thanks,

> >> > David

>

October 11, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

OK, thanks for your feedback, David!

_________________________________________________________

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

<davidtheweb@discussions.microsoft.com> wrote on 11 okt 2007 in

microsoft.public.windows.terminal_services:

> I have not had the chance to test this on my 2003 server yet. I

> did put this registry key in the HKLM registry on 2 XP SP2

> computers, and it restored the ability for TSM to interact with

> them. I think this answered the question, but I will followup

> with the 2003 test later, as well.

>

> "Vera Noest [MVP]" wrote:

>

>> OK, I've done some googling through the posts in the old W2K

>> and NT Terminal Services newsgroups, and this problem seems to

>> be specific for servers which had an in-place upgrade from W2K

>> to 2003.

>>

>> I found 2 possible causes and their solutions:

>>

>> * Remote registry service isn't running on the target server

>> * change this registry key:

>> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

>> \AllowRemoteRPC

>> to a value of REG_DWORD 1

>>

>> A reboot is required.

>>

>> Check them out, and I would appreciate it if you could post the

>> results here!

>> _________________________________________________________

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

>> <davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I'm using a domain admin account to connect with the server,

>> > and nothing appears in the eventlogs when I try to connect,

>> > not even in the security log.

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Which account are you using when you try to connect to the

>> >> server? A local or a domain Administrator account?

>> >> Any errors or warnings in the EventLog on the servers

>> >> involved?

>> >> _________________________________________________________

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

>> >> <davidtheweb@discussions.microsoft.com> wrote on 07 okt 2007

>> >> in microsoft.public.windows.terminal_services:

>> >>

>> >> > I have one 2003 Standard server that will not accept a

>> >> > connection from Terminal Services Manager. The message on

>> >> > TSM is 'You could not be authenticated on this server.'

>> >> > All other 2003 and 2000 servers are accepting connections

>> >> > from TSMs on different stations. This 2003 server was

>> >> > upgraded from 2000 a little while back. When it was a

>> >> > 2000 server, it accepted TSM connections. I *am* able to

>> >> > Remote Desktop successfully to this server, just not to

>> >> > TSM to it in order to manage connections, etc.

>> >> >

>> >> > Any thoughts?

>> >> >

>> >> > Thanks,

>> >> > David

October 12, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

In follow up, I am still unable to connect to the 2003 server using TSM,

although this solution, the registry key AllowRemoteRPC, restored

connectivity to XP machines. I also checked the Remote Registry in Services

and found that to be running. I have 2 other servers that were upgraded from

2000 to 2003, that did not suffer this problem. I've checked the problem

server against them and have not found a solution yet.

"Vera Noest [MVP]" wrote:

> OK, thanks for your feedback, David!

> _________________________________________________________

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

> <davidtheweb@discussions.microsoft.com> wrote on 11 okt 2007 in

> microsoft.public.windows.terminal_services:

>

> > I have not had the chance to test this on my 2003 server yet. I

> > did put this registry key in the HKLM registry on 2 XP SP2

> > computers, and it restored the ability for TSM to interact with

> > them. I think this answered the question, but I will followup

> > with the 2003 test later, as well.

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> OK, I've done some googling through the posts in the old W2K

> >> and NT Terminal Services newsgroups, and this problem seems to

> >> be specific for servers which had an in-place upgrade from W2K

> >> to 2003.

> >>

> >> I found 2 possible causes and their solutions:

> >>

> >> * Remote registry service isn't running on the target server

> >> * change this registry key:

> >> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

> >> \AllowRemoteRPC

> >> to a value of REG_DWORD 1

> >>

> >> A reboot is required.

> >>

> >> Check them out, and I would appreciate it if you could post the

> >> results here!

> >> _________________________________________________________

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

> >> <davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I'm using a domain admin account to connect with the server,

> >> > and nothing appears in the eventlogs when I try to connect,

> >> > not even in the security log.

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> Which account are you using when you try to connect to the

> >> >> server? A local or a domain Administrator account?

> >> >> Any errors or warnings in the EventLog on the servers

> >> >> involved?

> >> >> _________________________________________________________

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

> >> >> <davidtheweb@discussions.microsoft.com> wrote on 07 okt 2007

> >> >> in microsoft.public.windows.terminal_services:

> >> >>

> >> >> > I have one 2003 Standard server that will not accept a

> >> >> > connection from Terminal Services Manager. The message on

> >> >> > TSM is 'You could not be authenticated on this server.'

> >> >> > All other 2003 and 2000 servers are accepting connections

> >> >> > from TSMs on different stations. This 2003 server was

> >> >> > upgraded from 2000 a little while back. When it was a

> >> >> > 2000 server, it accepted TSM connections. I *am* able to

> >> >> > Remote Desktop successfully to this server, just not to

> >> >> > TSM to it in order to manage connections, etc.

> >> >> >

> >> >> > Any thoughts?

> >> >> >

> >> >> > Thanks,

> >> >> > David

>

October 13, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

From which system are you running Terminal Services Manager, from

another 2003 server, or from an XP computer with the 2003 Adminpak?

If the latter, have you made sure that you run the latest version

of the 2003 adminpak?

If that doesn't help, I've run out of ideas. I don't know if it is

the in-place upgrade which causes this, but they are always tricky.

_________________________________________________________

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

<davidtheweb@discussions.microsoft.com> wrote on 12 okt 2007 in

microsoft.public.windows.terminal_services:

> In follow up, I am still unable to connect to the 2003 server

> using TSM, although this solution, the registry key

> AllowRemoteRPC, restored connectivity to XP machines. I also

> checked the Remote Registry in Services and found that to be

> running. I have 2 other servers that were upgraded from 2000 to

> 2003, that did not suffer this problem. I've checked the

> problem server against them and have not found a solution yet.

>

> "Vera Noest [MVP]" wrote:

>

>> OK, thanks for your feedback, David!

>> _________________________________________________________

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

>> <davidtheweb@discussions.microsoft.com> wrote on 11 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I have not had the chance to test this on my 2003 server yet.

>> > I did put this registry key in the HKLM registry on 2 XP SP2

>> > computers, and it restored the ability for TSM to interact

>> > with them. I think this answered the question, but I will

>> > followup with the 2003 test later, as well.

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> OK, I've done some googling through the posts in the old W2K

>> >> and NT Terminal Services newsgroups, and this problem seems

>> >> to be specific for servers which had an in-place upgrade

>> >> from W2K to 2003.

>> >>

>> >> I found 2 possible causes and their solutions:

>> >>

>> >> * Remote registry service isn't running on the target server

>> >> * change this registry key:

>> >> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

>> >> \AllowRemoteRPC

>> >> to a value of REG_DWORD 1

>> >>

>> >> A reboot is required.

>> >>

>> >> Check them out, and I would appreciate it if you could post

>> >> the results here!

>> >> _________________________________________________________

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

>> >> <davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007

>> >> in microsoft.public.windows.terminal_services:

>> >>

>> >> > I'm using a domain admin account to connect with the

>> >> > server, and nothing appears in the eventlogs when I try to

>> >> > connect, not even in the security log.

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> Which account are you using when you try to connect to

>> >> >> the server? A local or a domain Administrator account?

>> >> >> Any errors or warnings in the EventLog on the servers

>> >> >> involved?

>> >> >> _________________________________________________________

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

>> >> >> <davidtheweb@discussions.microsoft.com> wrote on 07 okt

>> >> >> 2007 in microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > I have one 2003 Standard server that will not accept a

>> >> >> > connection from Terminal Services Manager. The message

>> >> >> > on TSM is 'You could not be authenticated on this

>> >> >> > server.' All other 2003 and 2000 servers are accepting

>> >> >> > connections from TSMs on different stations. This 2003

>> >> >> > server was upgraded from 2000 a little while back.

>> >> >> > When it was a 2000 server, it accepted TSM connections.

>> >> >> > I *am* able to Remote Desktop successfully to this

>> >> >> > server, just not to TSM to it in order to manage

>> >> >> > connections, etc.

>> >> >> >

>> >> >> > Any thoughts?

>> >> >> >

>> >> >> > Thanks,

>> >> >> > David

October 17, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

From any station, the server doesn't connect. This would definitely be a

good find for a number of sysadmins. I've compared the registry to the

registry on another upgraded machine that's working, but didn't get anywhere.

I also deleted the RDP connection in Terminal Configurations and rebuilt it,

but that didn't resolve the issue.

"Vera Noest [MVP]" wrote:

> From which system are you running Terminal Services Manager, from

> another 2003 server, or from an XP computer with the 2003 Adminpak?

> If the latter, have you made sure that you run the latest version

> of the 2003 adminpak?

> If that doesn't help, I've run out of ideas. I don't know if it is

> the in-place upgrade which causes this, but they are always tricky.

>

> _________________________________________________________

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

> <davidtheweb@discussions.microsoft.com> wrote on 12 okt 2007 in

> microsoft.public.windows.terminal_services:

>

> > In follow up, I am still unable to connect to the 2003 server

> > using TSM, although this solution, the registry key

> > AllowRemoteRPC, restored connectivity to XP machines. I also

> > checked the Remote Registry in Services and found that to be

> > running. I have 2 other servers that were upgraded from 2000 to

> > 2003, that did not suffer this problem. I've checked the

> > problem server against them and have not found a solution yet.

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> OK, thanks for your feedback, David!

> >> _________________________________________________________

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

> >> <davidtheweb@discussions.microsoft.com> wrote on 11 okt 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I have not had the chance to test this on my 2003 server yet.

> >> > I did put this registry key in the HKLM registry on 2 XP SP2

> >> > computers, and it restored the ability for TSM to interact

> >> > with them. I think this answered the question, but I will

> >> > followup with the 2003 test later, as well.

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> OK, I've done some googling through the posts in the old W2K

> >> >> and NT Terminal Services newsgroups, and this problem seems

> >> >> to be specific for servers which had an in-place upgrade

> >> >> from W2K to 2003.

> >> >>

> >> >> I found 2 possible causes and their solutions:

> >> >>

> >> >> * Remote registry service isn't running on the target server

> >> >> * change this registry key:

> >> >> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

> >> >> \AllowRemoteRPC

> >> >> to a value of REG_DWORD 1

> >> >>

> >> >> A reboot is required.

> >> >>

> >> >> Check them out, and I would appreciate it if you could post

> >> >> the results here!

> >> >> _________________________________________________________

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

> >> >> <davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007

> >> >> in microsoft.public.windows.terminal_services:

> >> >>

> >> >> > I'm using a domain admin account to connect with the

> >> >> > server, and nothing appears in the eventlogs when I try to

> >> >> > connect, not even in the security log.

> >> >> >

> >> >> > "Vera Noest [MVP]" wrote:

> >> >> >

> >> >> >> Which account are you using when you try to connect to

> >> >> >> the server? A local or a domain Administrator account?

> >> >> >> Any errors or warnings in the EventLog on the servers

> >> >> >> involved?

> >> >> >> _________________________________________________________

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

> >> >> >> <davidtheweb@discussions.microsoft.com> wrote on 07 okt

> >> >> >> 2007 in microsoft.public.windows.terminal_services:

> >> >> >>

> >> >> >> > I have one 2003 Standard server that will not accept a

> >> >> >> > connection from Terminal Services Manager. The message

> >> >> >> > on TSM is 'You could not be authenticated on this

> >> >> >> > server.' All other 2003 and 2000 servers are accepting

> >> >> >> > connections from TSMs on different stations. This 2003

> >> >> >> > server was upgraded from 2000 a little while back.

> >> >> >> > When it was a 2000 server, it accepted TSM connections.

> >> >> >> > I *am* able to Remote Desktop successfully to this

> >> >> >> > server, just not to TSM to it in order to manage

> >> >> >> > connections, etc.

> >> >> >> >

> >> >> >> > Any thoughts?

> >> >> >> >

> >> >> >> > Thanks,

> >> >> >> > David

>

November 14, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

Ok, finally got a solution for an Upgraded 2000 to 2003 Server. In addition

to having the HKLM\System\CurrentControlSet\Control\Terminal

Server\TSAdvertise DWORD set to 1,

You also want to have the

HKLM\System\CurrentControlSet\Control\SecurePipeServer\Winreg read permission

for the local service.

I have also posted this solution on my follow-up thread, in order to ease

the finding of the solution for anyone in need.

"davidtheweb" wrote:

> From any station, the server doesn't connect. This would definitely be a

> good find for a number of sysadmins. I've compared the registry to the

> registry on another upgraded machine that's working, but didn't get anywhere.

> I also deleted the RDP connection in Terminal Configurations and rebuilt it,

> but that didn't resolve the issue.

>

> "Vera Noest [MVP]" wrote:

>

> > From which system are you running Terminal Services Manager, from

> > another 2003 server, or from an XP computer with the 2003 Adminpak?

> > If the latter, have you made sure that you run the latest version

> > of the 2003 adminpak?

> > If that doesn't help, I've run out of ideas. I don't know if it is

> > the in-place upgrade which causes this, but they are always tricky.

> >

> > _________________________________________________________

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

> > <davidtheweb@discussions.microsoft.com> wrote on 12 okt 2007 in

> > microsoft.public.windows.terminal_services:

> >

> > > In follow up, I am still unable to connect to the 2003 server

> > > using TSM, although this solution, the registry key

> > > AllowRemoteRPC, restored connectivity to XP machines. I also

> > > checked the Remote Registry in Services and found that to be

> > > running. I have 2 other servers that were upgraded from 2000 to

> > > 2003, that did not suffer this problem. I've checked the

> > > problem server against them and have not found a solution yet.

> > >

> > > "Vera Noest [MVP]" wrote:

> > >

> > >> OK, thanks for your feedback, David!

> > >> _________________________________________________________

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

> > >> <davidtheweb@discussions.microsoft.com> wrote on 11 okt 2007 in

> > >> microsoft.public.windows.terminal_services:

> > >>

> > >> > I have not had the chance to test this on my 2003 server yet.

> > >> > I did put this registry key in the HKLM registry on 2 XP SP2

> > >> > computers, and it restored the ability for TSM to interact

> > >> > with them. I think this answered the question, but I will

> > >> > followup with the 2003 test later, as well.

> > >> >

> > >> > "Vera Noest [MVP]" wrote:

> > >> >

> > >> >> OK, I've done some googling through the posts in the old W2K

> > >> >> and NT Terminal Services newsgroups, and this problem seems

> > >> >> to be specific for servers which had an in-place upgrade

> > >> >> from W2K to 2003.

> > >> >>

> > >> >> I found 2 possible causes and their solutions:

> > >> >>

> > >> >> * Remote registry service isn't running on the target server

> > >> >> * change this registry key:

> > >> >> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

> > >> >> \AllowRemoteRPC

> > >> >> to a value of REG_DWORD 1

> > >> >>

> > >> >> A reboot is required.

> > >> >>

> > >> >> Check them out, and I would appreciate it if you could post

> > >> >> the results here!

> > >> >> _________________________________________________________

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

> > >> >> <davidtheweb@discussions.microsoft.com> wrote on 08 okt 2007

> > >> >> in microsoft.public.windows.terminal_services:

> > >> >>

> > >> >> > I'm using a domain admin account to connect with the

> > >> >> > server, and nothing appears in the eventlogs when I try to

> > >> >> > connect, not even in the security log.

> > >> >> >

> > >> >> > "Vera Noest [MVP]" wrote:

> > >> >> >

> > >> >> >> Which account are you using when you try to connect to

> > >> >> >> the server? A local or a domain Administrator account?

> > >> >> >> Any errors or warnings in the EventLog on the servers

> > >> >> >> involved?

> > >> >> >> _________________________________________________________

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

> > >> >> >> <davidtheweb@discussions.microsoft.com> wrote on 07 okt

> > >> >> >> 2007 in microsoft.public.windows.terminal_services:

> > >> >> >>

> > >> >> >> > I have one 2003 Standard server that will not accept a

> > >> >> >> > connection from Terminal Services Manager. The message

> > >> >> >> > on TSM is 'You could not be authenticated on this

> > >> >> >> > server.' All other 2003 and 2000 servers are accepting

> > >> >> >> > connections from TSMs on different stations. This 2003

> > >> >> >> > server was upgraded from 2000 a little while back.

> > >> >> >> > When it was a 2000 server, it accepted TSM connections.

> > >> >> >> > I *am* able to Remote Desktop successfully to this

> > >> >> >> > server, just not to TSM to it in order to manage

> > >> >> >> > connections, etc.

> > >> >> >> >

> > >> >> >> > Any thoughts?

> > >> >> >> >

> > >> >> >> > Thanks,

> > >> >> >> > David

> >

November 14, 2007

Re: Terminal Services Manager not connecting to a 2003 Server

Good job, David, I'm glad that you've been able to solve your

problem, and thanks for sahring the solution with us!

_________________________________________________________

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

<davidtheweb@discussions.microsoft.com> wrote on 14 nov 2007 in

microsoft.public.windows.terminal_services:

> Ok, finally got a solution for an Upgraded 2000 to 2003 Server.

> In addition to having the

> HKLM\System\CurrentControlSet\Control\Terminal

> Server\TSAdvertise DWORD set to 1,

>

> You also want to have the

> HKLM\System\CurrentControlSet\Control\SecurePipeServer\Winreg

> read permission for the local service.

>

> I have also posted this solution on my follow-up thread, in

> order to ease the finding of the solution for anyone in need.

>

> "davidtheweb" wrote:

>

>> From any station, the server doesn't connect. This would

>> definitely be a good find for a number of sysadmins. I've

>> compared the registry to the registry on another upgraded

>> machine that's working, but didn't get anywhere.

>> I also deleted the RDP connection in Terminal Configurations

>> and rebuilt it,

>> but that didn't resolve the issue.

>>

>> "Vera Noest [MVP]" wrote:

>>

>> > From which system are you running Terminal Services Manager,

>> > from another 2003 server, or from an XP computer with the

>> > 2003 Adminpak? If the latter, have you made sure that you run

>> > the latest version of the 2003 adminpak?

>> > If that doesn't help, I've run out of ideas. I don't know if

>> > it is the in-place upgrade which causes this, but they are

>> > always tricky.

>> >

>> > _________________________________________________________

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

>> > <davidtheweb@discussions.microsoft.com> wrote on 12 okt 2007

>> > in microsoft.public.windows.terminal_services:

>> >

>> > > In follow up, I am still unable to connect to the 2003

>> > > server using TSM, although this solution, the registry key

>> > > AllowRemoteRPC, restored connectivity to XP machines. I

>> > > also checked the Remote Registry in Services and found that

>> > > to be running. I have 2 other servers that were upgraded

>> > > from 2000 to 2003, that did not suffer this problem. I've

>> > > checked the problem server against them and have not found

>> > > a solution yet.

>> > >

>> > > "Vera Noest [MVP]" wrote:

>> > >

>> > >> OK, thanks for your feedback, David!

>> > >> _________________________________________________________

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

>> > >> <davidtheweb@discussions.microsoft.com> wrote on 11 okt

>> > >> 2007 in microsoft.public.windows.terminal_services:

>> > >>

>> > >> > I have not had the chance to test this on my 2003 server

>> > >> > yet.

>> > >> > I did put this registry key in the HKLM registry on 2

>> > >> > XP SP2

>> > >> > computers, and it restored the ability for TSM to

>> > >> > interact with them. I think this answered the question,

>> > >> > but I will followup with the 2003 test later, as well.

>> > >> >

>> > >> > "Vera Noest [MVP]" wrote:

>> > >> >

>> > >> >> OK, I've done some googling through the posts in the

>> > >> >> old W2K and NT Terminal Services newsgroups, and this

>> > >> >> problem seems to be specific for servers which had an

>> > >> >> in-place upgrade from W2K to 2003.

>> > >> >>

>> > >> >> I found 2 possible causes and their solutions:

>> > >> >>

>> > >> >> * Remote registry service isn't running on the target

>> > >> >> server * change this registry key:

>> > >> >> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

>> > >> >> \AllowRemoteRPC

>> > >> >> to a value of REG_DWORD 1

>> > >> >>

>> > >> >> A reboot is required.

>> > >> >>

>> > >> >> Check them out, and I would appreciate it if you could

>> > >> >> post the results here!

>> > >> >> ________________________________________________________

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

>> > >> >> <davidtheweb@discussions.microsoft.com> wrote on 08 okt

>> > >> >> 2007 in microsoft.public.windows.terminal_services:

>> > >> >>

>> > >> >> > I'm using a domain admin account to connect with the

>> > >> >> > server, and nothing appears in the eventlogs when I

>> > >> >> > try to connect, not even in the security log.

>> > >> >> >

>> > >> >> > "Vera Noest [MVP]" wrote:

>> > >> >> >

>> > >> >> >> Which account are you using when you try to connect

>> > >> >> >> to the server? A local or a domain Administrator

>> > >> >> >> account? Any errors or warnings in the EventLog on

>> > >> >> >> the servers involved?

>> > >> >> >> _____________________________________________________

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

>> > >> >> >> <davidtheweb@discussions.microsoft.com> wrote on 07

>> > >> >> >> okt 2007 in

>> > >> >> >> microsoft.public.windows.terminal_services:

>> > >> >> >>

>> > >> >> >> > I have one 2003 Standard server that will not

>> > >> >> >> > accept a connection from Terminal Services

>> > >> >> >> > Manager. The message on TSM is 'You could not be

>> > >> >> >> > authenticated on this server.' All other 2003 and

>> > >> >> >> > 2000 servers are accepting connections from TSMs

>> > >> >> >> > on different stations. This 2003

>> > >> >> >> > server was upgraded from 2000 a little while back.

>> > >> >> >> > When it was a 2000 server, it accepted TSM

>> > >> >> >> > connections.

>> > >> >> >> > I *am* able to Remote Desktop successfully to

>> > >> >> >> > this

>> > >> >> >> > server, just not to TSM to it in order to manage

>> > >> >> >> > connections, etc.

>> > >> >> >> >

>> > >> >> >> > Any thoughts?

>> > >> >> >> >

>> > >> >> >> > Thanks,

>> > >> >> >> > David

Sign In

Terminal Services Manager not connecting to a 2003 Server

Recommended Posts

Guest davidtheweb

Popular Days

Popular Days

Guest Vera Noest [MVP]

Guest davidtheweb

Guest Vera Noest [MVP]

Guest davidtheweb

Guest Vera Noest [MVP]

Guest davidtheweb

Guest Vera Noest [MVP]

Guest davidtheweb

Guest davidtheweb

Guest Vera Noest [MVP]

Similar Content

Why hasn’t Server Manager changed?

Terminal server error

error 7005 (Service Control Manager)

Windows Server 2003 R2 UNEXPECTED SHUTDOWN DUE TO BUGCHECK ERROR

How to troubleshoot Terminal Server issues?

Browse

Activity

Site Info