Here's a "fun" update.
After various resets and attempts at making this work, suddenly all OTHER domain accounts work normally, and now just the one I've been working with still cannot access anything locally. And what makes it so strange and illogical is that this domain account has MORE permissions on the local machine than other domain accounts. What a screwy operating system.
Hi Ogre11, I had the same problem. The only way that I found to work around it is to give your network login name local administrator privileges. Don't worry about having too many privileges, because in Win 7 giving a user admin privileges is not like it was in previous versions of windows. You will only really have a small subset of admin privileges. You still won't even be able to modify printer setups. So login to your machine as local administrator, you may need to create a local account with the same name as your network login name and password. If you switch users to your admin account after you have logged in to your domain account, you may be able to see the domain user in the list of users. Then give that local account or the domain account if you can see it, admin privileges. Sorry if this is not very clear, I cant remember the exact process that I used to get access to my C drive, I did this over 3 months ago, but it works fine now.
While logging on the the domain normally I've only run across two local process errors. The first is when I copyied some backup files over to the new computer after the join to the domain I can no longer modify them at all. Not sure if this is a permissions problem. Another is the Performance manager crashes every time i start it now.
Thank you again for the ideas.
After using the AppLocker to manually allow permissions to domain users to run programs in the Windows directory, and then turning on the AppLocker permissions, and then explicitly turning on the service for App Locker, it seems to work. That one domain account still wouldn't work, but others did, so I ended up deleting that domain account and re-creating it. Now all seems to work okay. Strange, but okay.
Heh.
An update, in case anyone else has this problem. The fix didn't keep. It worked for awhile, but after a day and a few log ons and log offs, its back.
Log in as network administrator on the client PC.
Right click on the C: drive, go to security, click on advanced, click on the ownership tab, choose the network admin account, click on the "apply to sub folders" check box
Apply, wait for it to finish then ok.
Your network admin now has ownership of all the files on the C: drive and also has full permissions on it, If you set a deny security entry anywhere else it will take precedence, but as the owner you can manually change that too.
Regards, P.
I had the same problem as Ogre11 and the only way that I could fix it was to give complete ownership AND R/W access to ALL files on the local C drive as SaintAurther describes. It opens up a bit of a security hole, but it was the only thing that worked. And, by the way, I was connecting to a 64bit 2008 R2 server from a 64bit Windows 7 Pro workstation.
It seems that sharing through a drive also means you need to share the entire drive in some cases. I was just telling someone how to share the entire drive the other day. I'm not sure if taking ownership is required if you allow for sharing permissions using the Security tab. Yes it's a bit of a security risk but sometimes it's the only way. Instructions for sharing an entire drive in the link below.
HDD sharing
Quote