Monday, February 25, 2013 3:41 PM
I have a very strange issue. There is one single file (on a win2k3 storage server network share / ntfs+share permissions) inside a shared folder which causes troubles in terms of permissions on one particular pc for each domain user. The issue is directly linked to the name (probabily also the full path) of this file. If I rename the file on the server the problems are not showing up anymore. If I delete the file on the server and create a new simple file (just one character inside) with the same name the issue is present again.
- Even though the permissions (ntfs+share) for this file is set to modify for a whole AD-group (where this user is beside othes a member) he can see the file on the share (is a mapped drive), he cannot open the file (it's a 1,5 MB .dat file like a .txt file though). Gets some permission issue warning from notebpad++.
- He also cannot rename the file.
- he can't even copy a file to that share if the name is the same. if the file is named differently he can copy the file form local pc to the server share location.
- if the file is renamed server-side the user can do everything as expected
- as long the file has the name in carge the user cannot see permisisons etc if he right-clicks permissoins of the file. He can do so for any other file in the same location and also for this file when renamed.
This issue only occurs since the user got a new notebook (which actually isn't freshly setup, a domain profile of another user wasn't deleted is still in place). But it has to be connected to some global notebook setting (HKLM or so) since even logging in with a different user on the same notebook the issue perssists. In the same time a different user and the user in charge connected from a different machine (same username and domain membership login) has no issue at all.
Any idea what this can be? I also thought of offline cache but this shouldn't go through different user profiles, should it? We do not use server-based profiles.
Kind regards, Dieter
Tuesday, February 26, 2013 8:25 AMModerator
Thursday, February 28, 2013 9:10 AM
Hi, I have fixed my problem even though I haven't figured out the ecaxt reason, but I want to share my exprience.
- This issue has something to do with the MS Offline Folder functionality. The user must have had done something with offline folder synch where this file in charge, beside a lot of others, was part of the offline to be synched objects.
- disabeling offline folders allowed me to deal again with that file in charge.
- re-enabeling offline folders again brought up the error. We had to delete the offline folder cache located under C:\Windows\CSC. This is a bit tricky since this is a very protected folder. I gained Owner of the folder and deleted the content of it....
- after a restart this cache was recreated but now my issue was solved.
We also have figured out that the issue only occured on a specific path like \\servername\share\file but not on the very same file with FWDN \\servername.domain.tld\share\file (first is netbios, second is dns). And the error occured for each and any user on this computer, this probabily because the Offline Folder Cache is something general once it is to be found under C:\windows\csc and not inside the user profile.
As I said, what exactely caused the issue we never figured out, but we brought it down to offline folders.
- Marked As Answer by Dieter Tontsch, mobileX Thursday, February 28, 2013 9:10 AM
Friday, March 01, 2013 3:11 AMModerator
- Edited by Tracy CaiMicrosoft Contingent Staff, Moderator Friday, March 01, 2013 3:12 AM