I can share files on D: but not on C: on combined Wireless and Wir

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running XP Pro on all three computers. The laptop and one desktop are
connected to a linksys router via wireless connection. The other desktop is
wired to the router. I have reloaded the wired desktop because I had this
same problem before. After loading the system with software I could share
files on both drives. I loaded and installed several hardware devices and
the software that supported the devices. I can no longer share any files or
folders on C:. Drive D: has no problem sharing file and folders. Any shares
that I setup on drive C: are seen by the other two computers in Network
Places. When the other computers try to access the shares I get the
following notice. "\\Computername\Sharename 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." Below this
statement is "Not enough server storage is availible to process this
command". I do not have any third party antivirus or firewalls installed. I
have run the Network Wizard several times on all of the computers. All of
the computers are on the same workgroup. From the wired desktop I can access
all shares on the other computers. I cannot access the Shared Folder on the
wired desktop from the other computers either. The other computers have
Norton Internet Security and Norton SystemWorks installed. I have set up
these to trust the IP range for my network. I looked at the System
Events/System folder in Computer Management There are several Error events
that have the Source SVR and the Event as 2011. I followed the help for the
event to it's help information. It advises to check the IrpFileSize in the
registry. No such entry existed where they said it was. A search of the
registry also turned up no results. I created the appropriate entry where
they advised it should be. I set the default value of 15. This did not
work. I increased the value by 5 each time until I reached 30. Still no
success. I looked at the permissions set for the D: drive and compared them
to the folder I tried to share. There were some differences. The
"Computername\Users was listed three times on the D: drive and only once on
the Shared folder. Two of the entries had Special permissions. None of the
entries on the D: drive were inherited. All of the entries on the Shared
folder were inherited. I can't think of any more information to provide here
but if more information is needed I will try to provide it. Thank you in
advance.
 
I am running XP Pro on all three computers. The laptop and one desktop are
connected to a linksys router via wireless connection. The other desktop is
wired to the router. I have reloaded the wired desktop because I had this
same problem before. After loading the system with software I could share
files on both drives. I loaded and installed several hardware devices and
the software that supported the devices. I can no longer share any files or
folders on C:. Drive D: has no problem sharing file and folders. Any shares
that I setup on drive C: are seen by the other two computers in Network
Places. When the other computers try to access the shares I get the
following notice. "\\Computername\Sharename 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." Below this
statement is "Not enough server storage is availible to process this
command". I do not have any third party antivirus or firewalls installed. I
have run the Network Wizard several times on all of the computers. All of
the computers are on the same workgroup. From the wired desktop I can access
all shares on the other computers. I cannot access the Shared Folder on the
wired desktop from the other computers either. The other computers have
Norton Internet Security and Norton SystemWorks installed. I have set up
these to trust the IP range for my network. I looked at the System
Events/System folder in Computer Management There are several Error events
that have the Source SVR and the Event as 2011. I followed the help for the
event to it's help information. It advises to check the IrpFileSize in the
registry. No such entry existed where they said it was. A search of the
registry also turned up no results. I created the appropriate entry where
they advised it should be. I set the default value of 15. This did not
work. I increased the value by 5 each time until I reached 30. Still no
success. I looked at the permissions set for the D: drive and compared them
to the folder I tried to share. There were some differences. The
"Computername\Users was listed three times on the D: drive and only once on
the Shared folder. Two of the entries had Special permissions. None of the
entries on the D: drive were inherited. All of the entries on the Shared
folder were inherited. I can't think of any more information to provide here
but if more information is needed I will try to provide it. Thank you in
advance.

It's IRPStackSize.

What registry value did you create? Please be precise - spelling and case are
critical here.
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html
 
Chuck said:
It's IRPStackSize.

What registry value did you create? Please be precise - spelling and case are
critical here.
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html

Under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
I right clicked in the blank area, selected "New\String Value. A new AB file
was listed named "New Value #1" I changed this to IrpStackSize. I then
double clicked it and the Edit String window opened. In the "Value data"
line I started with an entry of 15 then increased it by 5 until I reached 30
and gave up.
 
Under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
I right clicked in the blank area, selected "New\String Value. A new AB file
was listed named "New Value #1" I changed this to IrpStackSize. I then
double clicked it and the Edit String window opened. In the "Value data"
line I started with an entry of 15 then increased it by 5 until I reached 30
and gave up.

Try IRPStackSize, not IrpStackSize.
 
Chuck said:
Try IRPStackSize, not IrpStackSize.

Chuck,

Thank you for your help. Your advice on changing the case of the text was
initially not helpful. I thought about the way I entered the registry entry.
I entered it as a new "String Value". After trying your recommended
correction I was still unable to view the shares. I looked at the other
entries in the registry folder and most were DWORD entries. I created a
DWORD entry for IRPStackFile with a decimal value of 30. This worked. To
minimize the memory use I changed it from 30 to 15. The shares did not work.
Increasing to 20 did work. I have no idea what the different entry types
mean but I am finally happy that I can share the files I need. Three months
I have spent on this problem. I've talked to Dell, Microsoft and many of the
vendors of my software and hardware. Your help will let this obsessive
computer geek to finally go to sleep without dwelling on what else to try to
fix this problem. Thanks for being there.
 
Chuck,

Thank you for your help. Your advice on changing the case of the text was
initially not helpful. I thought about the way I entered the registry entry.
I entered it as a new "String Value". After trying your recommended
correction I was still unable to view the shares. I looked at the other
entries in the registry folder and most were DWORD entries. I created a
DWORD entry for IRPStackFile with a decimal value of 30. This worked. To
minimize the memory use I changed it from 30 to 15. The shares did not work.
Increasing to 20 did work. I have no idea what the different entry types
mean but I am finally happy that I can share the files I need. Three months
I have spent on this problem. I've talked to Dell, Microsoft and many of the
vendors of my software and hardware. Your help will let this obsessive
computer geek to finally go to sleep without dwelling on what else to try to
fix this problem. Thanks for being there.

You're quite welcome. Thank you for letting us know what the resolution was,
because your report may help the next guy in your situation.

And I annotated my article, to make the precise nature of this registry value a
bit more obvious. Your report WILL help the next guy.
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html
 
Back
Top