tobiator
Goto Top

probleme mit basisordner / windows server 2003 - remotedesktopverbindung

system: windows 2k3, AD (1 Domäne), Terminalserver (inkl. Lizensierung)

ich ärgere mich jetzt seit stunden. grund:

nach dem einloggen über remotedektop können die nutzer nicht auf ihren basisiordner zugreifen. fehlermeldung: zugriff verweigert.
basisordner wurde unter den benutzereigenschaften (AD) angelegt. zusätzlich habe ich den ordner freigegeben (vollzugriff für alle).
der zugriff funktioniert aber nur, wenn ich dem nutzer administratoren-rechte gebe. bei allen anderen gruppenzugehörigkeiten verweigert er den zugriff. irgendwo gibts da ein rechtekonflikt, aber wo?

vielleicht hat ja jemand eine idee....

gruss aus bonn

tobi

Content-ID: 14074

Url: https://administrator.de/contentid/14074

Ausgedruckt am: 05.11.2024 um 19:11 Uhr

Wappel
Wappel 06.08.2005 um 09:44:37 Uhr
Goto Top
Hallo Tobi !

Ich hatte vor einiger Zeit ein ähnliches Problem mit der RPC Protokoll. Hast du zufälligerweise gerade das SP1 installiert ? Nach der Inst. ändert sich einiges an den RPC Rechten und nur noch Admins haben den vollen zugriff.

Ich habe die Lösung hier gefunden.

Hier ein wichtiger Hinweis zur Installation im Hinblick auf DCOM und Remotezugriffsrechte:

MS hat in den Release Notes zum SP1 darauf hingewiesen, daß die DCOM-Konfiguration abgeändert wird, um sie entsprechend härten zu können. Die Änderungen sind hier auch im Detail beschrieben. Wenn also nach der Installation massive Probleme im Hinblick auf den Remote-Zugriff auftreten, so sollte man die Release Notes noch einmal genau lesen und ggfs. die für DCOM eingestellten Rechte mit der MMC-Konsole dcomcnfg.msc überprüfen.

Hier ein die DCOM-Komponenten betreffender Auszug aus den Release Notes (Quelle: Microsoft):
Security Certificate Services: Effects of security enhancements to the DCOM protocol
Windows Server 2003 SP1 introduces enhanced default security settings for the DCOM protocol. Specifically, SP1 introduces more precise rights that give an administrator independent control over local and remote permissions for launching, activating, and accessing COM servers.

Windows Server 2003 Certificate Services provides enrollment and administration services by using the DCOM protocol. Certificate Services provides several DCOM interfaces to make these services available. For correct access and usage of these services, Certificate Services assumes that its DCOM interfaces are set to permit remote activation and access permissions. However, because of the enhanced default security settings for DCOM that are introduced by SP1, you may have to update these security settings to make sure of the continued availability of these services after you install SP1. The following information explains how to do this.

By default, all DCOM interfaces in Windows Server 2003 SP1 are configured to grant remote access permissions, remote launch permissions, and remote activation permissions only to administrators. However, when you upgrade to Windows Server 2003 SP1, security configuration changes are made to the global DCOM interface and to the CertSrv Request DCOM interface. These changes are made to enable Certificate Services to work correctly.

Note that any changes that have been made to the CertSrv Request DCOM interface security settings before the installation of SP1 will be lost. The SP1 installation procedure resets all previous security settings in the CertSrv Request DCOM interface to their default settings.

During the SP1 installation process, Certificate Services automatically updates the DCOM security settings as follows:
? CertSrv Request DCOM interface:
? The Everyone security group is granted local and remote access permissions.
? The Everyone security group is granted local and remote activation permissions.
? The Everyone security group is not granted local or remote launch permissions.
? DCOM Computer Restriction Settings:
? A new security group, CERTSVC_DCOM_ACCESS, is automatically created.

If the certification authority is installed on a member server, CERTSVC_DCOM_ACCESS is a computer local group, and the Everyone security group is added to it.

If the certification authority is installed on a domain controller, CERTSVC_DCOM_ACCESS is a domain local group. The Domain Users security group and the Domain Computers security group from the certification authority?s domain are added to it.
? The CERTSVC_DCOM_ACCESS security group is granted local and remote access permissions.
? The CERTSVC_DCOM_ACCESS security group is granted local and remote activation permissions.
? The CERTSVC_DCOM_ACCESS security group is not granted local or remote launch permissions.
Note that if the certification authority is installed on a domain controller, and the enterprise is made up of more than one domain, Certificate Services cannot automatically update the DCOM security settings for enrollees from outside the certification authority?s domain. Therefore, these enrollees will be denied enroll access to the certification authority.

To resolve this issue, you must manually add the users to the CERTSVC_DCOM_ACCESS security group. Because the CERTSVC_DCOM_ACCESS security group is a domain local group, you can add only domain groups to it. For example, if users and computers from another domain, a domain named Contoso, have to enroll with the certification authority, you must manually add the Contoso\Domain Users group and the Contoso\Domain Computers group to the CERTSVC_DCOM_ACCESS security group.

If any enrollees that should be authorized by the certification authority are denied authorization after the installation of SP1, you can have Certificate Services update the DCOM security settings again. To do this, run the following commands at the command prompt in the following order. Press ENTER after each command.
1. certutil ?setreg SetupStatus ?SETUP_DCOM_SECURITY_UPDATED_FLAG
2. net stop certsvc
3. net start certsvc
The DCOM_SECURITY_UPDATED_FLAG is an internal Certificate Services registry flag that indicates that the DCOM security settings were updated completely and successfully. Certificate Services checks this flag every time that it is started. The commands in the previous list reset the flag and then stop and start Certificate Services, causing it to update the DCOM security settings again.
Quelle: Microsoft

Grüße,
Michael