Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 615
  • Last Modified:

Office 2010 SMB2 STATUS_ACCESS_DENIED using DFSN

Hi guys,

Wondering if anyone can help us out here.  We are currently testing Win7x64/office2010x32 Windows build.  We are currently experiencing a strange problem when browsing with a user setup with redirected folders desktop/my docs.  

We are running DFSN for all users who are still on XP/office 2003 and they do not appear to have any problems.  When a user logs in to win7 and opens either outlook or word, if they for word open a file, they get a popup - connecting to: \\domain\FR$  which is the root share for all users redirected folders.  This lasts for up to a minute then displays the windows explorer window.  If you leave word open, it's fine after that. but if you close the application open it again it seems to flush any cached information for windows explorer.

Same with Outlook when attaching files  again when browsing.  This does not affect other applications i.e. wordpad or paint.  so it does look to be an Office 2010 Std issue.

I have attached some netmon smb traces showing STATUS_ACCESS_DENIED captures where it appears to hang.  I have checked the FR$ share (which is everyone) with special permissions on security to allow each user & admin access to only their folders (MS recommended setup)

If anyone is able to help diagnose this issue as we are hoping to roll out ASAP with 7 but want to be able to resolve this issue before we do.
NetMon.bmp
0
macleandata
Asked:
macleandata
1 Solution
 
macleandataAuthor Commented:
Cracked it!!!!  

As stated in the traces it related to a permissions error.  Thinking the root had everyone full share permissions would give users the relevant permissions, I did not think of the NTFS permissions.  Looking at the authenticated users advanced permissions, I noticed the traverse/file execute permission was un-ticked, and looking back at MS docs for permissions, it states to tick thi option.  After doing this, it resolved the issue.

Macleandata
0
 
LeeTutorretiredCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now