Error on Terminal Server when connecting

  • Thread starter Thread starter Asif Shah
  • Start date Start date
A

Asif Shah

Guest
I have setup a new server 2000 advanced server as a terminal server. I have
enabled the terminal server component and added the TS licensing server name
in this new server's registry.

As a test, I opened remote desktop connection and tried to connecting to
itself and i get this error:

"Because of a security error, the client could not connect to the remote
computer..."

I get the same error on any other machine trying to connect to this new
terminal server. I have two other terminal servers that have been working
fine for the longest time. I just wanted to add this third one but running
into this error.

Any ideas? Thanks.

Asif Shah
 
Re: Error on Terminal Server when connecting

Which EventIDs do you see on the TS?
Check if these help:

http://support.microsoft.com/?kbid=323597
http://support.microsoft.com/?kbid=329896
_________________________________________________________
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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
wrote on 09 apr 2008 in
microsoft.public.windows.terminal_services:

> I have setup a new server 2000 advanced server as a terminal
> server. I have enabled the terminal server component and added
> the TS licensing server name in this new server's registry.
>
> As a test, I opened remote desktop connection and tried to
> connecting to itself and i get this error:
>
> "Because of a security error, the client could not connect to
> the remote computer..."
>
> I get the same error on any other machine trying to connect to
> this new terminal server. I have two other terminal servers that
> have been working fine for the longest time. I just wanted to
> add this third one but running into this error.
>
> Any ideas? Thanks.
>
> Asif Shah
 
Re: Error on Terminal Server when connecting

Thanks for the reply. I already tried those two articles. It didnt work.

The most recent error in Event Viewer is this:

Event ID:10004
Source: DCOM

DCOM got error "Logon failure: the user has not been granted the requested
logon type at this computer. " and was unable to logon. \IWAM_XXXXXXXX in
order to run the server.

I have other warnings that say my computer name tried to connect and could
not be issued a license. Event ID 1004.
Also, Event 1003 - computer name has provided an invalid license.

I also noticed that the IUSER and IWAM accounts are not the same as my
computer name. Not sure if that matters....eg.
computer name: asif
iuser account name: iuser_asif
iwam account name: iwam_asif

The above is not the case on this server. I have a name which was before I
added it to the domain.

Any ideas??????

"Vera Noest [MVP]" wrote:

> Which EventIDs do you see on the TS?
> Check if these help:
>
> http://support.microsoft.com/?kbid=323597
> http://support.microsoft.com/?kbid=329896
> _________________________________________________________
> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> wrote on 09 apr 2008 in
> microsoft.public.windows.terminal_services:
>
> > I have setup a new server 2000 advanced server as a terminal
> > server. I have enabled the terminal server component and added
> > the TS licensing server name in this new server's registry.
> >
> > As a test, I opened remote desktop connection and tried to
> > connecting to itself and i get this error:
> >
> > "Because of a security error, the client could not connect to
> > the remote computer..."
> >
> > I get the same error on any other machine trying to connect to
> > this new terminal server. I have two other terminal servers that
> > have been working fine for the longest time. I just wanted to
> > add this third one but running into this error.
> >
> > Any ideas? Thanks.
> >
> > Asif Shah
>
 
Re: Error on Terminal Server when connecting

I believe (but not sure) that the DCOM error is unrelated. I've
seen it myself on some servers after the march security updates.
Here are troubleshooting tips:

http://www.eventid.net/display.asp?eventid=10004&eventno=11
&source=DCOM&phase=1

Event 1004 and 1003 are certainly related to your rdp problem.
But if KB article 323597 and 329896 don't solve the problem, then
I'm out of ideas.
Just to be sure: you did remove the 3 certificates from the TS, the
license from the registry of the client, and deactivated and then
reactivated the Terminal Services Licensing server by calling the
Clearinghouse, is that correct?
_________________________________________________________
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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
wrote on 10 apr 2008 in
microsoft.public.windows.terminal_services:

> Thanks for the reply. I already tried those two articles. It
> didnt work.
>
> The most recent error in Event Viewer is this:
>
> Event ID:10004
> Source: DCOM
>
> DCOM got error "Logon failure: the user has not been granted the
> requested logon type at this computer. " and was unable to
> logon. \IWAM_XXXXXXXX in order to run the server.
>
> I have other warnings that say my computer name tried to connect
> and could not be issued a license. Event ID 1004.
> Also, Event 1003 - computer name has provided an invalid
> license.
>
> I also noticed that the IUSER and IWAM accounts are not the same
> as my computer name. Not sure if that matters....eg.
> computer name: asif
> iuser account name: iuser_asif
> iwam account name: iwam_asif
>
> The above is not the case on this server. I have a name which
> was before I added it to the domain.
>
> Any ideas??????
>
> "Vera Noest [MVP]" wrote:
>
>> Which EventIDs do you see on the TS?
>> Check if these help:
>>
>> http://support.microsoft.com/?kbid=323597
>> http://support.microsoft.com/?kbid=329896
>> _________________________________________________________
>> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
>> wrote on 09 apr 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > I have setup a new server 2000 advanced server as a terminal
>> > server. I have enabled the terminal server component and
>> > added the TS licensing server name in this new server's
>> > registry.
>> >
>> > As a test, I opened remote desktop connection and tried to
>> > connecting to itself and i get this error:
>> >
>> > "Because of a security error, the client could not connect to
>> > the remote computer..."
>> >
>> > I get the same error on any other machine trying to connect
>> > to this new terminal server. I have two other terminal
>> > servers that have been working fine for the longest time. I
>> > just wanted to add this third one but running into this
>> > error.
>> >
>> > Any ideas? Thanks.
>> >
>> > Asif Shah
 
Re: Error on Terminal Server when connecting

I did that except deactivated and reactivated the licensing server. You think
that might fix it?

"Vera Noest [MVP]" wrote:

> I believe (but not sure) that the DCOM error is unrelated. I've
> seen it myself on some servers after the march security updates.
> Here are troubleshooting tips:
>
> http://www.eventid.net/display.asp?eventid=10004&eventno=11
> &source=DCOM&phase=1
>
> Event 1004 and 1003 are certainly related to your rdp problem.
> But if KB article 323597 and 329896 don't solve the problem, then
> I'm out of ideas.
> Just to be sure: you did remove the 3 certificates from the TS, the
> license from the registry of the client, and deactivated and then
> reactivated the Terminal Services Licensing server by calling the
> Clearinghouse, is that correct?
> _________________________________________________________
> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> wrote on 10 apr 2008 in
> microsoft.public.windows.terminal_services:
>
> > Thanks for the reply. I already tried those two articles. It
> > didnt work.
> >
> > The most recent error in Event Viewer is this:
> >
> > Event ID:10004
> > Source: DCOM
> >
> > DCOM got error "Logon failure: the user has not been granted the
> > requested logon type at this computer. " and was unable to
> > logon. \IWAM_XXXXXXXX in order to run the server.
> >
> > I have other warnings that say my computer name tried to connect
> > and could not be issued a license. Event ID 1004.
> > Also, Event 1003 - computer name has provided an invalid
> > license.
> >
> > I also noticed that the IUSER and IWAM accounts are not the same
> > as my computer name. Not sure if that matters....eg.
> > computer name: asif
> > iuser account name: iuser_asif
> > iwam account name: iwam_asif
> >
> > The above is not the case on this server. I have a name which
> > was before I added it to the domain.
> >
> > Any ideas??????
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Which EventIDs do you see on the TS?
> >> Check if these help:
> >>
> >> http://support.microsoft.com/?kbid=323597
> >> http://support.microsoft.com/?kbid=329896
> >> _________________________________________________________
> >> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> >> wrote on 09 apr 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > I have setup a new server 2000 advanced server as a terminal
> >> > server. I have enabled the terminal server component and
> >> > added the TS licensing server name in this new server's
> >> > registry.
> >> >
> >> > As a test, I opened remote desktop connection and tried to
> >> > connecting to itself and i get this error:
> >> >
> >> > "Because of a security error, the client could not connect to
> >> > the remote computer..."
> >> >
> >> > I get the same error on any other machine trying to connect
> >> > to this new terminal server. I have two other terminal
> >> > servers that have been working fine for the longest time. I
> >> > just wanted to add this third one but running into this
> >> > error.
> >> >
> >> > Any ideas? Thanks.
> >> >
> >> > Asif Shah
>
 
Re: Error on Terminal Server when connecting

No guarantees, but it's the recommended action.
_________________________________________________________
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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
wrote on 10 apr 2008 in
microsoft.public.windows.terminal_services:

> I did that except deactivated and reactivated the licensing
> server. You think that might fix it?
>
> "Vera Noest [MVP]" wrote:
>
>> I believe (but not sure) that the DCOM error is unrelated. I've
>> seen it myself on some servers after the march security
>> updates. Here are troubleshooting tips:
>>
>> http://www.eventid.net/display.asp?eventid=10004&eventno=11
>> &source=DCOM&phase=1
>>
>> Event 1004 and 1003 are certainly related to your rdp problem.
>> But if KB article 323597 and 329896 don't solve the problem,
>> then I'm out of ideas.
>> Just to be sure: you did remove the 3 certificates from the TS,
>> the license from the registry of the client, and deactivated
>> and then reactivated the Terminal Services Licensing server by
>> calling the Clearinghouse, is that correct?
>> _________________________________________________________
>> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
>> wrote on 10 apr 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > Thanks for the reply. I already tried those two articles. It
>> > didnt work.
>> >
>> > The most recent error in Event Viewer is this:
>> >
>> > Event ID:10004
>> > Source: DCOM
>> >
>> > DCOM got error "Logon failure: the user has not been granted
>> > the requested logon type at this computer. " and was unable
>> > to logon. \IWAM_XXXXXXXX in order to run the server.
>> >
>> > I have other warnings that say my computer name tried to
>> > connect and could not be issued a license. Event ID 1004.
>> > Also, Event 1003 - computer name has provided an invalid
>> > license.
>> >
>> > I also noticed that the IUSER and IWAM accounts are not the
>> > same as my computer name. Not sure if that matters....eg.
>> > computer name: asif
>> > iuser account name: iuser_asif
>> > iwam account name: iwam_asif
>> >
>> > The above is not the case on this server. I have a name which
>> > was before I added it to the domain.
>> >
>> > Any ideas??????
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Which EventIDs do you see on the TS?
>> >> Check if these help:
>> >>
>> >> http://support.microsoft.com/?kbid=323597
>> >> http://support.microsoft.com/?kbid=329896
>> >> _________________________________________________________
>> >> 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?QXNpZiBTaGFo?=
>> >> <AsifShah@discussions.microsoft.com> wrote on 09 apr 2008 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > I have setup a new server 2000 advanced server as a
>> >> > terminal server. I have enabled the terminal server
>> >> > component and added the TS licensing server name in this
>> >> > new server's registry.
>> >> >
>> >> > As a test, I opened remote desktop connection and tried to
>> >> > connecting to itself and i get this error:
>> >> >
>> >> > "Because of a security error, the client could not connect
>> >> > to the remote computer..."
>> >> >
>> >> > I get the same error on any other machine trying to
>> >> > connect to this new terminal server. I have two other
>> >> > terminal servers that have been working fine for the
>> >> > longest time. I just wanted to add this third one but
>> >> > running into this error.
>> >> >
>> >> > Any ideas? Thanks.
>> >> >
>> >> > Asif Shah
 
Re: Error on Terminal Server when connecting

Still dosent work. I deactivated and reactivated the licensing server and it
still gives me that error.

Any more ideas?

"Vera Noest [MVP]" wrote:

> No guarantees, but it's the recommended action.
> _________________________________________________________
> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> wrote on 10 apr 2008 in
> microsoft.public.windows.terminal_services:
>
> > I did that except deactivated and reactivated the licensing
> > server. You think that might fix it?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> I believe (but not sure) that the DCOM error is unrelated. I've
> >> seen it myself on some servers after the march security
> >> updates. Here are troubleshooting tips:
> >>
> >> http://www.eventid.net/display.asp?eventid=10004&eventno=11
> >> &source=DCOM&phase=1
> >>
> >> Event 1004 and 1003 are certainly related to your rdp problem.
> >> But if KB article 323597 and 329896 don't solve the problem,
> >> then I'm out of ideas.
> >> Just to be sure: you did remove the 3 certificates from the TS,
> >> the license from the registry of the client, and deactivated
> >> and then reactivated the Terminal Services Licensing server by
> >> calling the Clearinghouse, is that correct?
> >> _________________________________________________________
> >> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> >> wrote on 10 apr 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Thanks for the reply. I already tried those two articles. It
> >> > didnt work.
> >> >
> >> > The most recent error in Event Viewer is this:
> >> >
> >> > Event ID:10004
> >> > Source: DCOM
> >> >
> >> > DCOM got error "Logon failure: the user has not been granted
> >> > the requested logon type at this computer. " and was unable
> >> > to logon. \IWAM_XXXXXXXX in order to run the server.
> >> >
> >> > I have other warnings that say my computer name tried to
> >> > connect and could not be issued a license. Event ID 1004.
> >> > Also, Event 1003 - computer name has provided an invalid
> >> > license.
> >> >
> >> > I also noticed that the IUSER and IWAM accounts are not the
> >> > same as my computer name. Not sure if that matters....eg.
> >> > computer name: asif
> >> > iuser account name: iuser_asif
> >> > iwam account name: iwam_asif
> >> >
> >> > The above is not the case on this server. I have a name which
> >> > was before I added it to the domain.
> >> >
> >> > Any ideas??????
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> Which EventIDs do you see on the TS?
> >> >> Check if these help:
> >> >>
> >> >> http://support.microsoft.com/?kbid=323597
> >> >> http://support.microsoft.com/?kbid=329896
> >> >> _________________________________________________________
> >> >> 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?QXNpZiBTaGFo?=
> >> >> <AsifShah@discussions.microsoft.com> wrote on 09 apr 2008 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > I have setup a new server 2000 advanced server as a
> >> >> > terminal server. I have enabled the terminal server
> >> >> > component and added the TS licensing server name in this
> >> >> > new server's registry.
> >> >> >
> >> >> > As a test, I opened remote desktop connection and tried to
> >> >> > connecting to itself and i get this error:
> >> >> >
> >> >> > "Because of a security error, the client could not connect
> >> >> > to the remote computer..."
> >> >> >
> >> >> > I get the same error on any other machine trying to
> >> >> > connect to this new terminal server. I have two other
> >> >> > terminal servers that have been working fine for the
> >> >> > longest time. I just wanted to add this third one but
> >> >> > running into this error.
> >> >> >
> >> >> > Any ideas? Thanks.
> >> >> >
> >> >> > Asif Shah
>
 
Re: Error on Terminal Server when connecting

No, I'm sorry, if those KB articles don't solve it, I haven't the
faintest idea what the problem can be.
_________________________________________________________
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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
wrote on 13 apr 2008 in
microsoft.public.windows.terminal_services:

> Still dosent work. I deactivated and reactivated the licensing
> server and it still gives me that error.
>
> Any more ideas?
>
> "Vera Noest [MVP]" wrote:
>
>> No guarantees, but it's the recommended action.
>> _________________________________________________________
>> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
>> wrote on 10 apr 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > I did that except deactivated and reactivated the licensing
>> > server. You think that might fix it?
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> I believe (but not sure) that the DCOM error is unrelated.
>> >> I've seen it myself on some servers after the march security
>> >> updates. Here are troubleshooting tips:
>> >>
>> >> http://www.eventid.net/display.asp?eventid=10004&eventno=11
>> >> &source=DCOM&phase=1
>> >>
>> >> Event 1004 and 1003 are certainly related to your rdp
>> >> problem. But if KB article 323597 and 329896 don't solve the
>> >> problem, then I'm out of ideas.
>> >> Just to be sure: you did remove the 3 certificates from the
>> >> TS, the license from the registry of the client, and
>> >> deactivated and then reactivated the Terminal Services
>> >> Licensing server by calling the Clearinghouse, is that
>> >> correct?
>> >> _________________________________________________________
>> >> 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?QXNpZiBTaGFo?=
>> >> <AsifShah@discussions.microsoft.com> wrote on 10 apr 2008 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Thanks for the reply. I already tried those two articles.
>> >> > It didnt work.
>> >> >
>> >> > The most recent error in Event Viewer is this:
>> >> >
>> >> > Event ID:10004
>> >> > Source: DCOM
>> >> >
>> >> > DCOM got error "Logon failure: the user has not been
>> >> > granted the requested logon type at this computer. " and
>> >> > was unable to logon. \IWAM_XXXXXXXX in order to run the
>> >> > server.
>> >> >
>> >> > I have other warnings that say my computer name tried to
>> >> > connect and could not be issued a license. Event ID 1004.
>> >> > Also, Event 1003 - computer name has provided an invalid
>> >> > license.
>> >> >
>> >> > I also noticed that the IUSER and IWAM accounts are not
>> >> > the same as my computer name. Not sure if that
>> >> > matters....eg. computer name: asif
>> >> > iuser account name: iuser_asif
>> >> > iwam account name: iwam_asif
>> >> >
>> >> > The above is not the case on this server. I have a name
>> >> > which was before I added it to the domain.
>> >> >
>> >> > Any ideas??????
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> Which EventIDs do you see on the TS?
>> >> >> Check if these help:
>> >> >>
>> >> >> http://support.microsoft.com/?kbid=323597
>> >> >> http://support.microsoft.com/?kbid=329896
>> >> >> _________________________________________________________
>> >> >> 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?QXNpZiBTaGFo?=
>> >> >> <AsifShah@discussions.microsoft.com> wrote on 09 apr 2008
>> >> >> in microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > I have setup a new server 2000 advanced server as a
>> >> >> > terminal server. I have enabled the terminal server
>> >> >> > component and added the TS licensing server name in
>> >> >> > this new server's registry.
>> >> >> >
>> >> >> > As a test, I opened remote desktop connection and tried
>> >> >> > to connecting to itself and i get this error:
>> >> >> >
>> >> >> > "Because of a security error, the client could not
>> >> >> > connect to the remote computer..."
>> >> >> >
>> >> >> > I get the same error on any other machine trying to
>> >> >> > connect to this new terminal server. I have two other
>> >> >> > terminal servers that have been working fine for the
>> >> >> > longest time. I just wanted to add this third one but
>> >> >> > running into this error.
>> >> >> >
>> >> >> > Any ideas? Thanks.
>> >> >> >
>> >> >> > Asif Shah
 
Re: Error on Terminal Server when connecting

Do you think it might be a OS problem?

Anyone else?????

"Vera Noest [MVP]" wrote:

> No, I'm sorry, if those KB articles don't solve it, I haven't the
> faintest idea what the problem can be.
> _________________________________________________________
> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> wrote on 13 apr 2008 in
> microsoft.public.windows.terminal_services:
>
> > Still dosent work. I deactivated and reactivated the licensing
> > server and it still gives me that error.
> >
> > Any more ideas?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> No guarantees, but it's the recommended action.
> >> _________________________________________________________
> >> 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?QXNpZiBTaGFo?= <AsifShah@discussions.microsoft.com>
> >> wrote on 10 apr 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > I did that except deactivated and reactivated the licensing
> >> > server. You think that might fix it?
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> I believe (but not sure) that the DCOM error is unrelated.
> >> >> I've seen it myself on some servers after the march security
> >> >> updates. Here are troubleshooting tips:
> >> >>
> >> >> http://www.eventid.net/display.asp?eventid=10004&eventno=11
> >> >> &source=DCOM&phase=1
> >> >>
> >> >> Event 1004 and 1003 are certainly related to your rdp
> >> >> problem. But if KB article 323597 and 329896 don't solve the
> >> >> problem, then I'm out of ideas.
> >> >> Just to be sure: you did remove the 3 certificates from the
> >> >> TS, the license from the registry of the client, and
> >> >> deactivated and then reactivated the Terminal Services
> >> >> Licensing server by calling the Clearinghouse, is that
> >> >> correct?
> >> >> _________________________________________________________
> >> >> 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?QXNpZiBTaGFo?=
> >> >> <AsifShah@discussions.microsoft.com> wrote on 10 apr 2008 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Thanks for the reply. I already tried those two articles.
> >> >> > It didnt work.
> >> >> >
> >> >> > The most recent error in Event Viewer is this:
> >> >> >
> >> >> > Event ID:10004
> >> >> > Source: DCOM
> >> >> >
> >> >> > DCOM got error "Logon failure: the user has not been
> >> >> > granted the requested logon type at this computer. " and
> >> >> > was unable to logon. \IWAM_XXXXXXXX in order to run the
> >> >> > server.
> >> >> >
> >> >> > I have other warnings that say my computer name tried to
> >> >> > connect and could not be issued a license. Event ID 1004.
> >> >> > Also, Event 1003 - computer name has provided an invalid
> >> >> > license.
> >> >> >
> >> >> > I also noticed that the IUSER and IWAM accounts are not
> >> >> > the same as my computer name. Not sure if that
> >> >> > matters....eg. computer name: asif
> >> >> > iuser account name: iuser_asif
> >> >> > iwam account name: iwam_asif
> >> >> >
> >> >> > The above is not the case on this server. I have a name
> >> >> > which was before I added it to the domain.
> >> >> >
> >> >> > Any ideas??????
> >> >> >
> >> >> > "Vera Noest [MVP]" wrote:
> >> >> >
> >> >> >> Which EventIDs do you see on the TS?
> >> >> >> Check if these help:
> >> >> >>
> >> >> >> http://support.microsoft.com/?kbid=323597
> >> >> >> http://support.microsoft.com/?kbid=329896
> >> >> >> _________________________________________________________
> >> >> >> 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?QXNpZiBTaGFo?=
> >> >> >> <AsifShah@discussions.microsoft.com> wrote on 09 apr 2008
> >> >> >> in microsoft.public.windows.terminal_services:
> >> >> >>
> >> >> >> > I have setup a new server 2000 advanced server as a
> >> >> >> > terminal server. I have enabled the terminal server
> >> >> >> > component and added the TS licensing server name in
> >> >> >> > this new server's registry.
> >> >> >> >
> >> >> >> > As a test, I opened remote desktop connection and tried
> >> >> >> > to connecting to itself and i get this error:
> >> >> >> >
> >> >> >> > "Because of a security error, the client could not
> >> >> >> > connect to the remote computer..."
> >> >> >> >
> >> >> >> > I get the same error on any other machine trying to
> >> >> >> > connect to this new terminal server. I have two other
> >> >> >> > terminal servers that have been working fine for the
> >> >> >> > longest time. I just wanted to add this third one but
> >> >> >> > running into this error.
> >> >> >> >
> >> >> >> > Any ideas? Thanks.
> >> >> >> >
> >> >> >> > Asif Shah
>
 
Back
Top