"Access Denied" to network share once moved to 7..but works on XP

We have a number of users that have lost access to the network share My Documents where everything they create is redirected and stored on a Sunfire server with the data on NFS volume. We are a Xen virtual shop running Server 2003. We've just built a Server 2008 that we are going to promote to PDC.
What's more baffling is that it is happening on newly built Dell 390 Windows 7 Pro and some existing Dell W7 Pro machines but not on the old XP PCs. When it first appeared the user went from XP to 7. He still has access to the share on the XP machine but on his W7 pro he gets an "Access Denied. See your Administrator" message when trying to open MS office docs or PDFs or photos. If I log into the new W7 PC as domain admin and try and copy the documents from the share to his W7 desktop I get a "you must have permission from user to do this". When I go back to my W7 PC I have no problem moving users documents around.

User has full control of folder and all subfolders, user is the owner of folder and is an administrator on the PC. I've set up the trust center in MS Office to specifically trust the path & share that we redirect to. I've used the Take Ownership utility I found on this forum on the parent folder to no avail. I set the Local Security Policy on the W7 PC for "Network Security: LAN Manager authentication level to "Send LM & NTLM - >useNTLMv2 session security if negotiated" and rebooted.

In another case there is a user that has access to his shares on a W7 PC that was built 6 months ago but not from the one that was just built. This led us to believe that it was something about only the new W7 builds that had lost some trust in AD.
Finally just when we thought it was only the newly imaged PCs that were doing this before rolling out another W7 PC I had a user log into an existing W7 PC before plopping down the new "share killer" W7 box and she was getting the same "Access denied" message on the older W7 PC.

Hello,

A few questions:

1) Where is the share that you are trying to access? On the Windows 2003 Server?
2) Are the new windows 7 PC's on the Domain?
3) Have you checked the Advanced sharing to se if file and print sharing is enabled on the PCs?
4) Why have you touched the Local Security Policy? By default you shouldnt need to.
5) Have you already added the Windows 2008 Server to the Domain? If so, did you make sure that the Domain and Forest was at the correct functionality?
6) Have you checked AD for errors? (dcdiag/event lofgs)
7) Check the security event logs on the Server where the Share is.
8) Disable the Anti-Virus and Firewall to test.
9) Recheck the permissions of the share. Paste a screen shot if you can.

10) Are the servers local to the users or hosted on the Web? If on another site, how are they accessed? VPN?
11) If you're redirecting paths did you change the logon scrips acordingly for Windows 7?


Just a note:
Your post was very hard to read and had a lack of structure. Its easier to diagnose if the post is easy to read.


Dave

Dave:

1. Share is on Windows 2003 Server
2. All PCs have been added to the domain.
3. File and print sharing are enabled by default
4. To try and solve the issue. My friend had this issue at his company where he is director of IT and this solved the issue.
5. Yes
6. Yes. No errors relative to this issue.
7. Done. No issues.
8. Has no impact on problem
9. We have all checked the permissions several times. We are domain admins and have full rights but can't move his files from the share to his desktop.
10. We own the servers. Accessed by users via RPCs. No VPN's involved since we're all onsite.
11. The login scripts are pushed out by the Group Policy that's in force so we do not need to modify them. We only have 3 XP PCs left in the enterprise. The rest are already on 7 with the login script working fine. We even deleted the original share and recreated it and applied the permissions and problem persists.


Thanks for your tip. It was more or less a stream of consciousness.

Thank you for your answers - It sounds like you have done the basic troubleshooting!

Do you have enough CALs? Are there any other problems on the network? I still think it points to a permissions problem on the folder though.



Dave