>Hello,
>
>I have an interesting question which I am hoping sombody can explain:
>
>I have a network with 2 desktops (A,B) which I built and are identical with
>identical setups, a dell laptop (C) and a network Buffalo drive (ND).  I had
>some trouble intially getting My Network Places on A to show anything even
>though by going through view workgroup computers A would access B,C and ND. 
>Also, every other computer could access everything.  See post
>(http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.windowsxp.network_web&p=1&tid=1b24fb3a-412e-4cd6-a069-330e3b4c506a&mid=1b24fb3a-412e-4cd6-a069-330e3b4c506a
>) for more info.
>
>Anyhow, all was working perfectly, but as A and  B were new, I need to
>install virus scan etc. on them.  So I installed;
>1) Zone Labs Virus Scan and Firewall
>2) Spybot Search and Destroy
>3) Spyware Doctor
>
>on both A and B, with identical installations.
>
>Suddenly, A can see and access B,C and ND, however B&C can see A,B,C and ND,
>but somehow neither one can access A (they can see it in the workgroup and
>can see the shared folders, but cannnot access them) with the following error
>message:
>
>"Access denied.. check with network administrator"
>and then
>"Not enough server storage is available to process this command"
>
>So I did my research and found Chuck link:
>
>http://nitecruzr.blogspot.com/2006/01/look-at-complete-detail-in-error.html
>
>which led me to editing the registry IRPStackSize:
>
>http://support.microsoft.com/?id=177078
>
>and with a little trial and error came up with 16 as the magic number.  Now
>the network is working perfectly with many thanks to Chuck who has saved my
>bacon twice in 2 days.
>
>Now for the question part:
>
>If you follow the link:
>http://support.microsoft.com/?id=177078
>then microsoft says this applies to Window XP which I am running,
>but it you follow the link:
>http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2000092713243506
>
>you will see that Symantec say's that the IRPStackSize is set dynamically in
>WinXP and so you should delete the registry key to solve the problem.
>
>This interested me, so I looked at the registry in computers B&C.  Neither
>had this entry at all (they both run WinXP-all home edition).  Remebering
>that A&B have identical components and configurations, can anybody offer some
>help as to:
>
>Why did A suddenly need a IRPStackSize while B was fine without it, and as a
>bonus which software: ZoneAlarm, Spybot, or Spydoctor was the cause of the
>problem?
>
>Hope somebody out there can help educate me on this.
>
>Owen

"Chuck" wrote:

> On Sat, 30 Dec 2006 23:36:01 -0800, Obean <Ob***@discussions.microsoft.com>
> wrote:
>
> >Hello,
> >
> >I have an interesting question which I am hoping sombody can explain:
> >
> >I have a network with 2 desktops (A,B) which I built and are identical with
> >identical setups, a dell laptop (C) and a network Buffalo drive (ND).  I had
> >some trouble intially getting My Network Places on A to show anything even
> >though by going through view workgroup computers A would access B,C and ND. 
> >Also, every other computer could access everything.  See post
> >(http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.windowsxp.network_web&p=1&tid=1b24fb3a-412e-4cd6-a069-330e3b4c506a&mid=1b24fb3a-412e-4cd6-a069-330e3b4c506a
> >) for more info.
> >
> >Anyhow, all was working perfectly, but as A and  B were new, I need to
> >install virus scan etc. on them.  So I installed;
> >1) Zone Labs Virus Scan and Firewall
> >2) Spybot Search and Destroy
> >3) Spyware Doctor
> >
> >on both A and B, with identical installations.
> >
> >Suddenly, A can see and access B,C and ND, however B&C can see A,B,C and ND,
> >but somehow neither one can access A (they can see it in the workgroup and
> >can see the shared folders, but cannnot access them) with the following error
> >message:
> >
> >"Access denied.. check with network administrator"
> >and then
> >"Not enough server storage is available to process this command"
> >
> >So I did my research and found Chuck link:
> >
> >http://nitecruzr.blogspot.com/2006/01/look-at-complete-detail-in-error.html
> >
> >which led me to editing the registry IRPStackSize:
> >
> >http://support.microsoft.com/?id=177078
> >
> >and with a little trial and error came up with 16 as the magic number.  Now
> >the network is working perfectly with many thanks to Chuck who has saved my
> >bacon twice in 2 days.
> >
> >Now for the question part:
> >
> >If you follow the link:
> >http://support.microsoft.com/?id=177078
> >then microsoft says this applies to Window XP which I am running,
> >but it you follow the link:
> >http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2000092713243506
> >
> >you will see that Symantec say's that the IRPStackSize is set dynamically in
> >WinXP and so you should delete the registry key to solve the problem.
> >
> >This interested me, so I looked at the registry in computers B&C.  Neither
> >had this entry at all (they both run WinXP-all home edition).  Remebering
> >that A&B have identical components and configurations, can anybody offer some
> >help as to:
> >
> >Why did A suddenly need a IRPStackSize while B was fine without it, and as a
> >bonus which software: ZoneAlarm, Spybot, or Spydoctor was the cause of the
> >problem?
> >
> >Hope somebody out there can help educate me on this.
> >
> >Owen
>
> Owen,
>
> For my money, it'll be ZoneAlarm.  ZA has a number of functions, including
> application level filtering.  It's similar in complexity to Norton Antivirus,
> which is the best known cause of this problem.
>
> But it's not too likely that you'll ever know for sure.
>
> Just be thankful for the first guy who publicised the IRPStackSize problem.
>
> Now you COULD try to repeat the experience, if you wish.
> <http://nitecruzrmisc.blogspot.com/2006/09/troubleshooting-techniques.html>
> http://nitecruzrmisc.blogspot.com/2006/09/troubleshooting-techniques.html
>
> --
> 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.
>