[xseedman]

I enabled Simple file sharing and even rebooted the computer and checked. The problem still is there.

[TerryNet]

Possible Fix for corruption “Access Denied” Problem:

Using notepad create a file named FIXANON.REG with the following contents:

------------------- cut after this line -------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"restrictanonymous"=dword:00000000
------------------- cut before this line -----------------

Double click on the file and say Yes to the merge into registry question.

Restart and see if this helps with the access issue.

[xseedman]

I checked the registry and found that the Data for Reg_Dword was already 0x000000 (0).
I made and ran the file you suggested, and checked the registry again and it was no different.
Tried to access the folder from a network computer and the results were the same.

My original post indicated that I could see the folder, but not access the files in it.

The error message when I try from a network computer to access the folder is:

\\George\C on GH Desktop is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Not enough server storage is available to process this command.

I know the folder in question (as well as others) have been set up for sharing and have been given permission.

Not knowing for sure I would guess that this was a permissions related thing and what you suggested was an attempt to eleminate one possible reason.

[JohnWill]

- Start, Run, REGEDIT
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameter s
- Edit the IRPStackSize
- Set it to a DWORD value of 15 (or more, valid range 11-50)
- NOTE: If IRPStackSize doesn't exist, create a new DWORD entry for it
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
- Set the PagedPoolSize to 0
- Exit REGEDIT and reboot

[xseedman]

The suggestion in the last post by JohnWill worked.

A big thanks to him and TerryNet for all their suggestions and effort in helping resolve this.

Hope I can return the favor to someone someday.

[TerryNet]

Glad we could help you. We should have asked for the exact error message earlier; would have saved a lot of guessing and probing.

[JohnWill]

Yep, soon as I saw that, I reached right in my bag of tricks for that script.