File sharing working one way

Byteguy wrote:

Tried it. Same results, but the actual error message is "not enough
server storage is available to process this command"

And this is why having the exact text of an error message is important. If
you'd told us this in the first place...

From MVP Ron Lowe - This error indicates that you are falling foul of the
IRPStackSize bug. The problem is on the machine you are attempting to
connect to, not the machine where you see the error message. On the
computer you are attempting to connect to, check the event viewer for an
event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize back
to the default (15 ). Perform the following steps:

1. Start regedit.
2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters.
3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it with type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about this,
too:

Antivirus Software May Cause Event ID 2011 (Q177078) -
http://support.microsoft.com/default...b;EN-US;177078

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Byteguy wrote:

Tried it. Same results, but the actual error message is "not enough
server storage is available to process this command"

And this is why having the exact text of an error message is important. If
you'd told us this in the first place...

From MVP Ron Lowe - This error indicates that you are falling foul of the
IRPStackSize bug. The problem is on the machine you are attempting to
connect to, not the machine where you see the error message. On the
computer you are attempting to connect to, check the event viewer for an
event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize back
to the default (15 ). Perform the following steps:

1. Start regedit.
2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters.
3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it with type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about this,
too:

Antivirus Software May Cause Event ID 2011 (Q177078) -
http://support.microsoft.com/default...b;EN-US;177078

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

On Jul 11, 10:44*am, Malke wrote:
Byteguywrote:
Tried it. Same results, but the actual error message is "not enough
server storage is available to process this command"

And this is why having the exact text of an error message is important. If
you'd told us this in the first place...

From MVP Ron Lowe - This error indicates that you are falling foul of the
IRPStackSize bug. The problem is on the machine you are attempting to
connect to, not the machine where you see the error message. On the
computer you are attempting to connect to, check the event viewer for an
event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize back
to the default (15 ). Perform the following steps:

* 1. Start regedit.
* 2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters.
* 3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it with type DWORD and ensure the case is correct).
* 4. Change the base to decimal, set the value to 15, and click OK.
* 5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about this,
too:

Antivirus Software May Cause Event ID 2011 (Q177078) -http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

On Jul 11, 10:44*am, Malke wrote:
Byteguywrote:
Tried it. Same results, but the actual error message is "not enough
server storage is available to process this command"

And this is why having the exact text of an error message is important. If
you'd told us this in the first place...

From MVP Ron Lowe - This error indicates that you are falling foul of the
IRPStackSize bug. The problem is on the machine you are attempting to
connect to, not the machine where you see the error message. On the
computer you are attempting to connect to, check the event viewer for an
event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize back
to the default (15 ). Perform the following steps:

* 1. Start regedit.
* 2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters.
* 3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it with type DWORD and ensure the case is correct).
* 4. Change the base to decimal, set the value to 15, and click OK.
* 5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about this,
too:

Antivirus Software May Cause Event ID 2011 (Q177078) -http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

Byteguy wrote:

I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Byteguy wrote:

I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

On Jul 11, 1:38*pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

On Jul 11, 1:38*pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

Byteguy wrote:
On Jul 11, 1:38 pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.
FYI, I don't use Norton. Too much of a system hog.
Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. Keep
trying all the way to 50.

--
Lem -- MS-MVP

Apollo 11 - 40 years ago this month:
http://www.nasa.gov/mission_pages/ap...0th/index.html

Byteguy wrote:
On Jul 11, 1:38 pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.
FYI, I don't use Norton. Too much of a system hog.
Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. Keep
trying all the way to 50.

--
Lem -- MS-MVP

Apollo 11 - 40 years ago this month:
http://www.nasa.gov/mission_pages/ap...0th/index.html

On Jul 11, 3:37*pm, Lem lemp40@unknownhost wrote:
Byteguywrote:
On Jul 11, 1:38 pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.
FYI, I don't use Norton. Too much of a system hog.
Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. *Keep
trying all the way to 50.

--
Lem -- MS-MVP

Apollo 11 - 40 years ago this month:http://www.nasa.gov/mission_pages/ap...0th/index.html

Took your suggestions. No change.
The funny thing is, it used to work. We're on a peer-to-peer network
here. From this computer, I can see the others and their files with
no problems at all
They can see this computer and the shared folders. Anything below the
folder level they cannot see. BUT: they can print to the printer
attached to this computer.
It appears that permissions are not passing down below the folder
level, even though I'm using simple file sharing.

On Jul 11, 3:37*pm, Lem lemp40@unknownhost wrote:
Byteguywrote:
On Jul 11, 1:38 pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.
FYI, I don't use Norton. Too much of a system hog.
Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. *Keep
trying all the way to 50.

--
Lem -- MS-MVP

Apollo 11 - 40 years ago this month:http://www.nasa.gov/mission_pages/ap...0th/index.html

Took your suggestions. No change.
The funny thing is, it used to work. We're on a peer-to-peer network
here. From this computer, I can see the others and their files with
no problems at all
They can see this computer and the shared folders. Anything below the
folder level they cannot see. BUT: they can print to the printer
attached to this computer.
It appears that permissions are not passing down below the folder
level, even though I'm using simple file sharing.

On Jul 11, 3:37*pm, Lem lemp40@unknownhost wrote:
Byteguywrote:
On Jul 11, 1:38 pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.
FYI, I don't use Norton. Too much of a system hog.
Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. *Keep
trying all the way to 50.

--
Lem -- MS-MVP

Apollo 11 - 40 years ago this month:http://www.nasa.gov/mission_pages/ap...0th/index.html

Took your suggestions. No change.
The funny thing is, it used to work. We're on a peer-to-peer network
here. From this computer, I can see the others and their files with
no problems at all
They can see this computer and the shared folders. Anything below the
folder level they cannot see. BUT: they can print to the printer
attached to this computer.
It appears that permissions are not passing down below the folder
level, even though I'm using simple file sharing.

On Jul 11, 3:37*pm, Lem lemp40@unknownhost wrote:
Byteguywrote:
On Jul 11, 1:38 pm, Malke wrote:
Byteguywrote:
I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.
FYI, I don't use Norton. Too much of a system hog.
Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!http://www.elephantboycomputers.com/#FAQ

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. *Keep
trying all the way to 50.

--
Lem -- MS-MVP

Apollo 11 - 40 years ago this month:http://www.nasa.gov/mission_pages/ap...0th/index.html

Took your suggestions. No change.
The funny thing is, it used to work. We're on a peer-to-peer network
here. From this computer, I can see the others and their files with
no problems at all
They can see this computer and the shared folders. Anything below the
folder level they cannot see. BUT: they can print to the printer
attached to this computer.
It appears that permissions are not passing down below the folder
level, even though I'm using simple file sharing.