![]() Is there a way to either force the system to automatically update the permissions rather than caching them, or to manually do so? Is this a bug that is addressed by a service pack, or is this a "by-design" feature? However, the change in permissions will not be displayed on the server until the administrator logs off, then logs back on. For example, if a user is actually denied access to a folder, the cached permission granting them access may be displayed on the server, but the client will be unable to access the folder. The most perplexing thing is that clients (end-users) connecting to the shared folders can see the actual permissions. This causes the administrator to believe that there are different permissions on the folders than the actual, effective permissions that the clients see. Pressing "F5" (Refresh) in Windows Explorer does not refresh the permissions. The permissions for the shared folders are ONLY modified by one Administrator logged into this box. I am 100% certain that no other users or administrators are modifying the permissions. Log Off of your RDP session, and connect again. Z:Ĭhoose a folder that is shared, right-click and go to Properties, then click the Security tab. Go to the disk hosting the shared drives in Windows Explorer, e.g. I have discovered that staying logged in to the Windows Server 2003 box over Remote Desktop Protocol (RDP) causes security permissions in Windows Explorer to become outdated, like the server is caching the permissions that were there previously. The 2003 box is not the Domain Controller / Active Directory host Active Directory is run on a server outside our control but we believe it is Server 2008 R2. It hosts numerous shared folders with various permissions. ![]() I have a Windows Server 2003 box acting as a file server.
0 Comments
Leave a Reply. |