Windows NT Upgraded Server 2000 to 2003 R2.....

  • Thread starter Thread starter tke402
  • Start date Start date
T

tke402

.....and now I can not remote desktop into one of my DCs. I have added the
domain admin group to the "allow users to log on through terminal services"
for the domain controller security policy. However this still doesn't work.
Any ideas?

Thanks

TKE402
 
Hello tke402,

Did you enable Remote desktop on the system Properties?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> ....and now I can not remote desktop into one of my DCs. I have added
> the domain admin group to the "allow users to log on through terminal
> services" for the domain controller security policy. However this
> still doesn't work. Any ideas?
>
> Thanks
>
> TKE402
>
 
yes

"Meinolf Weber" wrote:

> Hello tke402,
>
> Did you enable Remote desktop on the system Properties?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > ....and now I can not remote desktop into one of my DCs. I have added
> > the domain admin group to the "allow users to log on through terminal
> > services" for the domain controller security policy. However this
> > still doesn't work. Any ideas?
> >
> > Thanks
> >
> > TKE402
> >

>
>
>
 
What error message do you get?

Helge

On 27 Aug., 22:16, tke402 <tke...@discussions.microsoft.com> wrote:
> yes
>
> "Meinolf Weber" wrote:
> > Hello tke402,

>
> > Did you enable Remote desktop on the system Properties?

>
> > Best regards

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

>
> > > ....and now I can not remote desktop into one of my DCs. I have added
> > > the domain admin group to the "allow users to log on through terminal
> > > services" for the domain controller security policy. However this
> > > still doesn't work. Any ideas?

>
> > > Thanks

>
> > > TKE402
 
Here's the whole error message:

"Remote Desktop Disconnected

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also poddible that network problems are
preventing your connection.

Please try connecting again later. If the problem continues to occur,
contact your administrator."

Thanks

TKE402


"Helge Klein" wrote:

> What error message do you get?
>
> Helge
>
> On 27 Aug., 22:16, tke402 <tke...@discussions.microsoft.com> wrote:
> > yes
> >
> > "Meinolf Weber" wrote:
> > > Hello tke402,

> >
> > > Did you enable Remote desktop on the system Properties?

> >
> > > Best regards

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

> >
> > > > ....and now I can not remote desktop into one of my DCs. I have added
> > > > the domain admin group to the "allow users to log on through terminal
> > > > services" for the domain controller security policy. However this
> > > > still doesn't work. Any ideas?

> >
> > > > Thanks

> >
> > > > TKE402

>
>
>
 
Did you check the Windows Firewall on the server? Can you telnet to
port 3389?

Helge

On 27 Aug., 22:52, tke402 <tke...@discussions.microsoft.com> wrote:
> Here's the whole error message:
>
> "Remote Desktop Disconnected
>
> The client could not connect to the remote computer.
>
> Remote connections might not be enabled or the computer might be too busy to
> accept new connections. It is also poddible that network problems are
> preventing your connection.
>
> Please try connecting again later. If the problem continues to occur,
> contact your administrator."
>
> Thanks
>
> TKE402
>
> "Helge Klein" wrote:
> > What error message do you get?

>
> > Helge

>
> > On 27 Aug., 22:16, tke402 <tke...@discussions.microsoft.com> wrote:
> > > yes

>
> > > "Meinolf Weber" wrote:
> > > > Hello tke402,

>
> > > > Did you enable Remote desktop on the system Properties?

>
> > > > Best regards

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

>
> > > > > ....and now I can not remote desktop into one of my DCs. I have added
> > > > > the domain admin group to the "allow users to log on through terminal
> > > > > services" for the domain controller security policy. However this
> > > > > still doesn't work. Any ideas?

>
> > > > > Thanks

>
> > > > > TKE402
 
no connection fails when I try to do that

"Helge Klein" wrote:

> Did you check the Windows Firewall on the server? Can you telnet to
> port 3389?
>
> Helge
>
> On 27 Aug., 22:52, tke402 <tke...@discussions.microsoft.com> wrote:
> > Here's the whole error message:
> >
> > "Remote Desktop Disconnected
> >
> > The client could not connect to the remote computer.
> >
> > Remote connections might not be enabled or the computer might be too busy to
> > accept new connections. It is also poddible that network problems are
> > preventing your connection.
> >
> > Please try connecting again later. If the problem continues to occur,
> > contact your administrator."
> >
> > Thanks
> >
> > TKE402
> >
> > "Helge Klein" wrote:
> > > What error message do you get?

> >
> > > Helge

> >
> > > On 27 Aug., 22:16, tke402 <tke...@discussions.microsoft.com> wrote:
> > > > yes

> >
> > > > "Meinolf Weber" wrote:
> > > > > Hello tke402,

> >
> > > > > Did you enable Remote desktop on the system Properties?

> >
> > > > > Best regards

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

> >
> > > > > > ....and now I can not remote desktop into one of my DCs. I have added
> > > > > > the domain admin group to the "allow users to log on through terminal
> > > > > > services" for the domain controller security policy. However this
> > > > > > still doesn't work. Any ideas?

> >
> > > > > > Thanks

> >
> > > > > > TKE402

>
>
>
 
any ideas?

"tke402" wrote:

> no connection fails when I try to do that
>
> "Helge Klein" wrote:
>
> > Did you check the Windows Firewall on the server? Can you telnet to
> > port 3389?
> >
> > Helge
> >
> > On 27 Aug., 22:52, tke402 <tke...@discussions.microsoft.com> wrote:
> > > Here's the whole error message:
> > >
> > > "Remote Desktop Disconnected
> > >
> > > The client could not connect to the remote computer.
> > >
> > > Remote connections might not be enabled or the computer might be too busy to
> > > accept new connections. It is also poddible that network problems are
> > > preventing your connection.
> > >
> > > Please try connecting again later. If the problem continues to occur,
> > > contact your administrator."
> > >
> > > Thanks
> > >
> > > TKE402
> > >
> > > "Helge Klein" wrote:
> > > > What error message do you get?
> > >
> > > > Helge
> > >
> > > > On 27 Aug., 22:16, tke402 <tke...@discussions.microsoft.com> wrote:
> > > > > yes
> > >
> > > > > "Meinolf Weber" wrote:
> > > > > > Hello tke402,
> > >
> > > > > > Did you enable Remote desktop on the system Properties?
> > >
> > > > > > Best regards
> > >
> > > > > > Meinolf Weber
> > > > > > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > > > > > no rights.
> > >
> > > > > > > ....and now I can not remote desktop into one of my DCs. I have added
> > > > > > > the domain admin group to the "allow users to log on through terminal
> > > > > > > services" for the domain controller security policy. However this
> > > > > > > still doesn't work. Any ideas?
> > >
> > > > > > > Thanks
> > >
> > > > > > > TKE402

> >
> >
> >
 
Back
Top