Jump to content

Question about W2K3 Server and XP Clients Using Remote Desktop


Recommended Posts

Guest Adam Sandler
Posted

Hello,

 

I have a question about using mstsc.exe in a W2K3 and XP environment.

With regard to the group policy, what are all the group policies which

could affect remote connections? I have the allow logon interactively

policy set but I still get an error which states I cannot logon to a

given host when trying to use a remote desktop connection. I'm asking

because there are literally hundreds of possible group policy

settings. Does anyone know of a list of policies related to RDC and/

or terminal services? That would help troubleshooting and hunting an

pecking through all the policy options.

 

Thanks!

  • Replies 4
  • Created
  • Last Reply

Popular Days

Guest Robert L [MVP - Networking]
Posted

Re: Question about W2K3 Server and XP Clients Using Remote Desktop

 

Yes, many possibilities. This case may help,

 

The local policy of this system does not permit you to logon ....Situation: the client can logon his XP Pro using his username but he receives "The local policy of this system does not permit you to logon interactively" ...

http://www.chicagotech.net/remoteissues/tslogon1.htm

 

 

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

"Adam Sandler" <corn29@excite.com> wrote in message news:1186544124.468446.284670@x40g2000prg.googlegroups.com...

Hello,

 

I have a question about using mstsc.exe in a W2K3 and XP environment.

With regard to the group policy, what are all the group policies which

could affect remote connections? I have the allow logon interactively

policy set but I still get an error which states I cannot logon to a

given host when trying to use a remote desktop connection. I'm asking

because there are literally hundreds of possible group policy

settings. Does anyone know of a list of policies related to RDC and/

or terminal services? That would help troubleshooting and hunting an

pecking through all the policy options.

 

Thanks!

Guest Adam Sandler
Posted

Re: Question about W2K3 Server and XP Clients Using Remote Desktop

 

On Aug 8, 5:05 am, "Robert L [MVP - Networking]" <nore...@hotmail.com>

wrote:

> Yes, many possibilities. This case may help,

>

> The local policy of this system does not permit you to logon ...Situation: the client can logon his XP Pro using his username but he receives "The local policy of this system does not permit you to logon interactively" ...

> http://www.chicagotech.net/remoteissues/tslogon1.htm

 

Thanks for the reply... I changed the setting mentioned in the link

above and now, with some users, they receive this error" you do not

have access

to logon to this session". The groups for those users affected are in

the RDC-TCP properties -- yet that latest error still appears. Any

suggestions on how to fix this one?

 

This is why, in my first post, I was hoping to come across a list of

all the settings which could affect RDC. The administration of this

feature is hardly centralized and knowing directly where to go

troubleshoot would be helpful.

Guest Adam Sandler
Posted

Re: Question about W2K3 Server and XP Clients Using Remote Desktop

 

Nevermind, fixed it... the SIDs for the accounts, as listed on the

local computer's remote connection properties, were corrupted. When

they were re-added, everything worked fine. Thanks again!

Guest Robert L [MVP - Networking]
Posted

Re: Question about W2K3 Server and XP Clients Using Remote Desktop

 

Thank you for the update.

 

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

"Adam Sandler" <corn29@excite.com> wrote in message news:1186607983.504950.86230@b79g2000hse.googlegroups.com...

Nevermind, fixed it... the SIDs for the accounts, as listed on the

local computer's remote connection properties, were corrupted. When

they were re-added, everything worked fine. Thanks again!


×
×
  • Create New...