remote control "error 5 - access is denied"
in [Terminal Services]
|
From: RizFra on 24 Feb 2006 06:29 EUREKA!!!! Hi TP... the permission were (apparently) OK... So ... I've tried to restore default permission in Access Control for RDP-Tcp (RDP-Tcp Properties in Permission tab Advanced Button) and now it's OK Thanks 10000000000000000000 for your suggests and tanks to Vera tooo Bye Guys Francesco "TP" wrote: > Error 5 - Access is denied comes from not having the Remote > Control Permission on the connection object. > > I suggest that you re-verify permissions. Here are the steps: > > 1. Open up tscc.msc, right-click RDP-Tcp, Properties. > > 2. On the permissions tab, click the Advanced button. > > 3. Click on each entrie in the list one at a time, and click the > Edit button to check the permissions. > > 4. Write down each user/group that has the Remote Control > permission checked. If you have any Deny entries, write those > user/groups down as well, because they will override the Allows. > > 5. Logon as the problem user and open up a command prompt. > > 6. Type whoami /groups > > 7. Compare the list of groups with the one you wrote down above. > Make sure the user is in at least one of the groups that have the > Remote Control permission, and is NOT a member of one that > has a Deny Remote Control entry. > > Thanks. > > -TP > > RizFra wrote: > > Dear Vera, > > the SHADOW Command don't work too... tel error is teh same > > > > Remote control failed. Error code 5 > > Error [5]:Access is denied. > > > > It's like a permission/right problem; are you agree? > > > > There's another way to verify or to set access permission? > > The server is domain member but it's not affected by group policy > > > > Thaks > > Francesco > > > > > >
From: TP on 24 Feb 2006 06:42 You are very welcome. Glad you were able to correct the problem. It seems that every once in a while the connection object permissions get messed up. Even though they appear correct, the server behaves as if they are set wrong. Based on what you have said I think this is what happened to you. By clicking the default button you caused the server to rewrite the security key using the default permissions. FYI, the security is stored here: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\Security -TP RizFra wrote: > EUREKA!!!! > > Hi TP... > the permission were (apparently) OK... > > So ... I've tried to restore default permission in Access Control for > RDP-Tcp (RDP-Tcp Properties in Permission tab Advanced Button) and > now it's OK > > Thanks 10000000000000000000 for your suggests and tanks to Vera tooo > > Bye Guys > Francesco >
From: RizFra on 24 Feb 2006 08:10 great TP Other precious information... Have a fine day bye Francesco "TP" wrote: > You are very welcome. > > Glad you were able to correct the problem. > > It seems that every once in a while the connection object > permissions get messed up. Even though they appear > correct, the server behaves as if they are set wrong. > > Based on what you have said I think this is what happened > to you. By clicking the default button you caused the > server to rewrite the security key using the default > permissions. FYI, the security is stored here: > > HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\Security > > -TP > > RizFra wrote: > > EUREKA!!!! > > > > Hi TP... > > the permission were (apparently) OK... > > > > So ... I've tried to restore default permission in Access Control for > > RDP-Tcp (RDP-Tcp Properties in Permission tab Advanced Button) and > > now it's OK > > > > Thanks 10000000000000000000 for your suggests and tanks to Vera tooo > > > > Bye Guys > > Francesco > > > >
From: Vera Noest [MVP] on 24 Feb 2006 10:19 Woow, that's weird! I never knew that. Thanks, TP! _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net SQL troubleshooting: http://sql.veranoest.net *----------- Please reply in newsgroup -------------* "TP" <tperson.knowspamn(a)mailandnews.com> wrote on 24 feb 2006: > You are very welcome. > > Glad you were able to correct the problem. > > It seems that every once in a while the connection object > permissions get messed up. Even though they appear > correct, the server behaves as if they are set wrong. > > Based on what you have said I think this is what happened > to you. By clicking the default button you caused the > server to rewrite the security key using the default > permissions. FYI, the security is stored here: > > HKLM\SYSTEM\CurrentControlSet\Control\Terminal > Server\WinStations\RDP-Tcp\Security > > -TP > > RizFra wrote: >> EUREKA!!!! >> >> Hi TP... >> the permission were (apparently) OK... >> >> So ... I've tried to restore default permission in Access >> Control for RDP-Tcp (RDP-Tcp Properties in Permission tab >> Advanced Button) and now it's OK >> >> Thanks 10000000000000000000 for your suggests and tanks to Vera >> tooo >> >> Bye Guys >> Francesco
From: TP on 24 Feb 2006 10:33 It has happened to me once or twice years ago. I would play with the permissions, and then weird stuff would happen like it would say I needed to be granted the right to logon, when I knew I already had the correct rights. I pretty much ignored it, but over the years I have been noticing people post problems where it seems like they have set the correct permissions, yet they still have problems. You know what I mean, the ones where they make the user a member of Remote Desktop Users, grant logon locally rights, etc., and they still have some strange permissions-related error. -TP Vera Noest [MVP] wrote: > Woow, that's weird! I never knew that. Thanks, TP! > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > SQL troubleshooting: http://sql.veranoest.net > *----------- Please reply in newsgroup -------------* >
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: Remote Desktop Connection Next: TSWeb AuthenticationLevel |