Guest newguy Posted January 4, 2008 Posted January 4, 2008 A co worker moved our dieing file server shares to a new file server. After that our users are reporting problems accessing the shares. They are saying they can only read the share but share and NTFS permission are set so they have full control over there folder. Below is the steps we think our co worked did to move the files. he is gone out of town so we can ask him for sure. I double check all share setting and they match the original file server. The other problem is we are running out of disk space on C: We have 200mb left. Not sure why he set it up that way. Would that affect the share access? This is our primary production files server so any help would be great. This file server is a member server. dieing file server is named fileserver1 New file server is named fileserver2 copied shares manually from fileserver1 to fileserver2 enabled the sharing on fileserver2 took fileserver1 down renamed fileserver2 to fileserver1 to keep dns happy
Guest Pegasus \(MVP\) Posted January 4, 2008 Posted January 4, 2008 Re: file share permissions not working "newguy" <newguy@discussions.microsoft.com> wrote in message news:A924E916-D3DE-4F95-BB45-E77DE79DB1E1@microsoft.com... >A co worker moved our dieing file server shares to a new file server. After > that our users are reporting problems accessing the shares. They are > saying > they can only read the share but share and NTFS permission are set so they > have full control over there folder. Below is the steps we think our co > worked did to move the files. he is gone out of town so we can ask him for > sure. I double check all share setting and they match the original file > server. The other problem is we are running out of disk space on C: We > have > 200mb left. Not sure why he set it up that way. Would that affect the > share > access? This is our primary production files server so any help would be > great. This file server is a member server. > > dieing file server is named fileserver1 > > New file server is named fileserver2 > > copied shares manually from fileserver1 to fileserver2 > enabled the sharing on fileserver2 > took fileserver1 down > renamed fileserver2 to fileserver1 to keep dns happy > Let's see some hard evidence about your user's access rights! 1. Log on as the problem user. 2. Assuming that Q:\Data is the problem folder, execute these commands from a Command Prompt: net user "%UserName%" /domain > c:\test.txt cacls "Q:\Data" 1>>c:\test.txt 2>>&1 dir "Q:\Data" 1>>c:\test.txt 2>>&1 md "Q:\Data\TestFolder" 1>>c:\test.txt 2>>&1 notepad c:\test.txt 3. Post the contents of this file. If you still can't work out what's wrong, check the share permissions of the share that Q:\Data is mapped to. They should be set to "full access for everyone". The command net share {ShareName} will show you the permissions when executed on your domain controller.
Recommended Posts