On Mon, 14 Nov 2005 22:27:02 -0800, Yuggie <Yuggie@discussions.microsoft.com>
wrote:
>"Chuck" wrote:
>
>> On Sun, 13 Nov 2005 19:28:02 -0800, Yuggie <Yuggie@discussions.microsoft.com>
>> wrote:
>>
>> >Hi, all
>> >
>> >I have a strange problem. There are three Windows XP Pro computers. Local
>> >WinXP with SP2, NTFS. Remote system WinXP SP1, NTFS. Third machine is WinXP
>> >SP2.
>> >
>> >There is a shared folder on the remote system. User A is the power user on
>> >this machine. He also has all permissions except 'Full Control" against this
>> >shared folder and its sub-folders. However, user A couldn't access some
>> >sub-folders in this shared folder ( he can open the sub-folder but see no
>> >content in this sub-folder). I even reset the permission for this folder to
>> >full control, but didn't work. I logged on as administrator on the local
>> >machine but had the same problem (can't see the contents in some folders)
>> >even if I am the administrator for both systems.
>> >
>> >I created a test sub-folder under the shared folder, I created a text file
>> >under the new subfolder. I keyed in some text into the file and exited the
>> >text editor, the icon of the text file disappeared from file explorer
>> >immediately after I close the editor. Then I can't see any content under this
>> >folder again! However, all the existing content and the new text file can be
>> >seen on remote and Third system, no matter whom you log in as.
>> >
>> >Any help will be highly appreciated. Thanks.
>> >
>> >Yuggie
>>
>> Yuggie,
>>
>> This sounds like corrupt NTFS permissions to me. The solution, that we've found
>> in the past, is to run "cacls" to reset permission on the problem folders.
>> <http://nitecruzr.blogspot.com/2005/09/server-access-authorisation.html>
>> http://nitecruzr.blogspot.com/2005/0...orisation.html
>Hi, Chuck
>
>Thanks for the reply.
>
>I changed the permission in both Security tag and "cacle". I saw the
>permission for the folder was everyone/full control on the remote machine.
>However, I still couldn't see any content under the shared folder on the
>remote system when I used the local machine.
>
>I upgraded the remote machine to SP2 and ran disk check, it didn't help.
>
>Then I unplug the hard drive and put it into a good WinXP machine. I share
>the same folders and I can see all folders from the local machine.
>
>So I have to rebuild the remote machine. Hope it help.
>
>Thans again for the info.
>
>Yuggie
Yuggie,
I presume that this is a workgroup setup? If so, take my advice about multiple
tests as literally as possible, but don't overdo. With workgroups, I
acknowledge that you cannot duplicate access from every computer to every
computer. Just do the best that you can. That's why I like domains.
You have some files / folders that can be seen accessed, and some that can't?
Is this still after running cacls? If you run cacls to just list permissions,
does it show any difference between the ones that can, and the ones that can't,
be accessed?
Your original report mentions "User A", and you, having this problem. Do your
specific problem folders equal his, or are they different?
There is one other known problem which is related to your symptoms. Don't take
the exact symptoms described in here too literally, this problem is much more
versatile than this article would suggest.
http://support.microsoft.com/kb/895900/
Moving the hard drive to another server was an excellent bit of diagnosis, and
points, primarily, to a problem with the server (host computer containing hard
drive). Now, dig deeper. Try accessing the files that could, and couldn't be
accessed originally, from more than 1 client (you have 3 computer, so use 1 as a
server, and 2 as clients). Then put the drive back into the original host, and
do the same. See if client has anything at all to do with the problem too. And
check both "User A" and yourself, again, in all cases.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/0...-tutorial.html
I'll give you the advice, but you gotta do the leg work. Develop multiple tests
cases, and compare results.
Rebuilding a computer might be the final answer, but make sure that you know
exactly where the problem is first. Don't rebuild the wrong computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/0...ghborhood.html
And learn to bottom post. Help me to help you.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/0...tml#TopPosting
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.