Somewhere along the line, I realized I could no longer network. Try this, try that, still can't network. Remove AVS. I connect. Remove a few other things. Reinstall AVS. I can still connect. Great.
Then the other day, once again, I notice I cannot network. Go through MSCONFIG (Sysinternals Autoruns actually), & start disabling drivers & services & whatnot. Disable just about everything, but still cannot network.
Remove AVS once again. Network returns.
Reinstall AVS. Cannot connect.
I had known about the MS article mentioned in the other thread & was sure that I had entered the required registry entry, & that I had it set at 50, its maximum value.
Was perusing the Acronis faqs & this one caught my eye.
After I installed Acronis True Image 9.0 Home, I cannot access shared folders that reside on this computer. What's wrong?
The problem is that Microsoft Lanman Server has a fixed limit on the quantity of filters it supports. Since Acronis True Image 9.0 Home installs some filters to support backups, the total number of filters can exceed the server's limit. The same problem may occur after the installation of an antivirus product and is described in the Microsoft Knowledge Base Article 177078.
So this "Microsoft Lanman Server", what ever it is & whatever it does. Acronis affects it. Maybe Ghost also? Antivirus programs may affect it. Who knows what else.
I have Acronis True Image installed. And Ghost. And an Antivirus.
So at this point, I liken Microsoft Lanman Server to the old Win98 resources. Once Win98 resources were depleted (& it is not odd for that to happen), then things no longer work correctly. Once too many programs are using up these Lanman Server "filters", then things no longer work correctly.
So it is not a single program, Norton or AVS, that is causing these problems, but rather the use of many such programs that use (uses up) these resources (filters) that causes this problem.
If it is common enough, you would think MS would have made an update to account for this by now.
Anyhow, long story short, I look in the registry, & the referenced value is NOT there? Huh? I create it, reboot, & my network is back. Complete with AVS & True Image & Ghost.
(Perhaps somewhere along the line, I restored to a point before the registry entry existed? And at the time of the earlier thread, I could have sworn I added the registry entry, yet I was still unable to connect?)
#2. "RE: Not enough server storage to process command - Revisit" In response to FZbar (Reply # 1)
Here is registry entry for lan man server
1. Click Start > Run.
2. Type regedit.exe and then click OK.
3. Navigate to the following key:
4. Look for the IRPStackSize value. If the value does not
exist, you must create it:
a. Right-click in the right pane, point to New, and then click
b. Type IRPStackSize and then press Enter. Type the value
exactly as shown; it is case-sensitive.
5. In the right pane, double-click the IRPStackSize value to
enter edit mode.
6. Change the Base to decimal.
7. In the Value Data box, type 11.
8. Close the Registry Editor.
#3. "RE: Not enough server storage to process command - Revisit" In response to DJC (Reply # 2)
Yes, I defined my IRPStackSize to 15 & it worked just
I had done this a long time ago when I had this problem &
it solved it. What I don't understand is what changed about
NAV that caused it again recently. I had not done any
restores on the system in a several years.
All's well that ends well.