[famyam]

Thanks for your reply, but IRPStackSize is not the cause of this
problem. I had tested it. The error is not the same too.

Other tests:
All tests from MS Network Troubleshooting was done.
Session manager memory limits and number of concurrency process was
raised up.
All other tests in WinXP Network Problem Solver from Hans-Georg Michna
was done.
All tests from thread WinXP Losing Network Places from PCbanter.net was
done.
The "Pchuck's Network article: The NT Browser" was read.
It's not a firewall related problem. I disabled it and tested.
We use TCP/IP only and have no domain, only workgroups.
It's not a DNS problem.
All computers use one antivirus (not Norton) and at least one
anti-spyware.
It's appears to not be a Winsock or IP stack problem.
It's not a RestrictAnonymous problem.

Now I'm testing if it can be a network segment problem, isolating some
computers in one small broadcast segment.

It is a recent issue. The problem was first related to me by a user
less then a month ago.

In another small network, the problem was solved changing the workgroup
name. One by one, all computers was assigned to the new workgroup,
always testing if the problem appears. Curiously the network only work
with one configuration: one computer with WinXP Pro as master browser.
All other Windows flavors acting as master browsers caused the problem.
All other computers have the master browser function disabled (setting
the registry MaintainServerList value to No).


--
famyamPosted from http://www.pcreview.co.uk/ newsgroup access

[Chuck]

On Thu, 30 Jun 2005 12:44:54 +0100, famyam <famyam.1rftoy@> wrote:

>
>Thanks for your reply, but IRPStackSize is not the cause of this
>problem. I had tested it. The error is not the same too.
>
>Other tests:
>All tests from MS Network Troubleshooting was done.
>Session manager memory limits and number of concurrency process was
>raised up.
>All other tests in WinXP Network Problem Solver from Hans-Georg Michna
>was done.
>All tests from thread WinXP Losing Network Places from PCbanter.net was
>done.
>The "Pchuck's Network article: The NT Browser" was read.
>It's not a firewall related problem. I disabled it and tested.
>We use TCP/IP only and have no domain, only workgroups.
>It's not a DNS problem.
>All computers use one antivirus (not Norton) and at least one
>anti-spyware.
>It's appears to not be a Winsock or IP stack problem.
>It's not a RestrictAnonymous problem.
>
>Now I'm testing if it can be a network segment problem, isolating some
>computers in one small broadcast segment.
>
>It is a recent issue. The problem was first related to me by a user
>less then a month ago.
>
>In another small network, the problem was solved changing the workgroup
>name. One by one, all computers was assigned to the new workgroup,
>always testing if the problem appears. Curiously the network only work
>with one configuration: one computer with WinXP Pro as master browser.
>All other Windows flavors acting as master browsers caused the problem.
>All other computers have the master browser function disabled (setting
>the registry MaintainServerList value to No).

What value did you finally set IRPStackSize to? The Microsoft article
<http://support.microsoft.com/?id=177078> recommends starting with 11, and
increasing by 3, to a maximum of 50. You wouldn't be the first to need more
than 18. Check some earlier posts here, and see.
<http://groups-beta.google.com/groups?q=irpstacksize&qt_s=Search>

If that's truly not it, and hearing how much research you have done, maybe it's
time to try a pay call to Microsoft Support.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not a problem - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.