[krewemiester]

Unable to access shared files from main computer via windows network. Although I can access the computer and the folders are visible from all the machines networked, including the main computer, I cannot open them. I am also unable to access those file from “my network places” on the same machine they are located.
Error: “ …not accessible. You might not have permission to use this network resource. ~ Not enough server storage is available to process this command”
The files are set to share, I am administrator. The computer [Gateway w/3.2Mhz] has ample storage [ 3 GB ram, 500 GB internal HD, 500 GB external (shared).
Problem occurred after I merged two partitions to redistribute space.
I am still able to access shared folders and files located on all the other networked machines.

[Mike0001]

Looks like the access rights are wrong. Try running cacls from a command prompt

cacls foldername /t /e /g user:r

where user is either guest or whatever username you are using to share.

[krewemiester]

I ran the cacls but need help deciphering. do I need to write some code or make registry adjustments? I created a screen shot of the cacls command.

Thank you for your assistance

[Carbon]

You can increase the IRPStackSize value. You must first add this value to the following key if it is not already present: HKEY_LOCAL_MACHINE SYSTEM\CurrentControlSet\Services\LanmanServer\Par ameters

Value Name: IRPStackSize
Data Type: DWORD
Default: 0x4
Maximum: 0xC

Increasing this value requires some memory from the non-allocated memory pool, but the impact should not be noticeable.

NOTE: It is not always advisable to set the IRPStackSize value to its maximum of 12. Generally, you should start the value at 4 and work your way up, increasing the value by 1 each time. The problem may still occur if the value is too high.

This error message may also occur after installing or uninstalling virus-scanning software. You may want to remove the virus-scanning software or increase the IRPStackSize if you need to use the software.

[Mike0001]

Originally Posted by krewemiester

I ran the cacls but need help deciphering. do I need to write some code or make registry adjustments? I created a screen shot of the cacls command.

Thank you for your assistance

Sorry, where I put "foldername" you have to insert the path to your shared folder! You are just getting the help text in your screen shot.

cacls shared /t /e /g mike:r

change the access list on folder "shared"; /t changes it on all subfiles and subfolders; /e edits the access list rather than replace it; /g mike:r grant user mike read access.

cacls shared

print out the access list for folder "shared"

[krewemiester]

This is unchartered territory for me so I beg your patients. I ran a command CALCS k:\ where K is a new hard drive I installed to be shared across the network. I had enabled all sharing and editing rights on the sharing properties. In the meantime I had disabled all sharing from a partitioned drive H that I had formerly shared. attached are the screen shots from those cmd inquiries. I am vexed!

Is there anyway I can alter these permissions through the administrative tools?

[krewemiester]

I have made the regedits, to no success. Still looking for alternative fix(s)

[Mike0001]

Originally Posted by krewemiester

This is unchartered territory for me so I beg your patients. I ran a command CALCS k:\ where K is a new hard drive I installed to be shared across the network. I had enabled all sharing and editing rights on the sharing properties. In the meantime I had disabled all sharing from a partitioned drive H that I had formerly shared. attached are the screen shots from those cmd inquiries. I am vexed!

k: has read access for Everyone, h: has read and write access for everyone.

However, the contents may have lower access rights. What you need to do now is run

cacls k:\ /t /e /g everyone:r

Now see if that solves the sharing issue.

[Mike0001]

Originally Posted by Carbon

You can increase the IRPStackSize value. You must first add this value to the following key if it is not already present: HKEY_LOCAL_MACHINE SYSTEM\CurrentControlSet\Services\LanmanServer\Par ameters

Value Name: IRPStackSize
Data Type: DWORD
Default: 0x4
Maximum: 0xC

M$ gives the range 11-50 for this parameter, default 15. I am puzzled!

[Carbon]

Originally Posted by Mike0001

M$ gives the range 11-50 for this parameter, default 15. I am puzzled!

The document I got that info from said it applied to NT Server, I assumed they were the same as XP uses the NT kernel, but apparently XP raises the maximum to 50.

If the problem persists after you complete the preceding procedure, try to increase the value of IRPStackSize even more up to a maximum value for Windows 2000/XP of 50 (0x32 hex).
If you are running Windows NT 4.0, and the problem persists after you complete the preceding procedure, you may have to apply Windows NT Service Pack 4 or Service Pack 5.

Guess that's what I get for reading outdated documentation ;)