Avast is stopping shared folders on my network!

I am running two boxes on a home wireless network. My main machine is running Vista and the other XP, both are running Avast 4 Home.

I have shared folders on the XP box that I can no longer access since I switched to Avast. I can see the XP box, I can see the shared drives, but I can’t open them I get an error message saying it is not accessible and I may not have permission to use the resource and that there isn’t enough server storage available to process the command.

If I disable ‘on access’ I still can’t open the folders BUT as soon as I uninstall Avast I can open the folders without a problem?

I like Avast and would like to carry on using it but it will have to go if I can’t access the other computer on the network.

Does anyone know how I can fix this problem?

Cheers

Peter

Please see: http://forum.avast.com/index.php?topic=29300.msg240716#msg240716

Neither the XP or Vista Boxes had the key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\IRPStackSize

I added it to both with a value of decimal 15. The problem still remains.

As I noted in the thread I pointed you to … I had to set the value higher to 18 decimal.

Ah I didn’t notice that and took the Microsoft figure. Does it nee changing on the PC that the shared folders are on or the one accessing them? I am assuming it is the one with the shared folders but thought I would check!

You need it on the PC that the shared folders reside on.

Yeehah! :o

That worked a treat. I wonder why this key isn’t looked at / added during the install process I would imagine it is causing quite a few folks to either drop shared folders or drop avast.

If you are reading this alanrf one final question on the subeject. The box with the shared folders has multiple user accounts, does this fix need doing for each user of is that a global key?

Many thanks for your help.

The change is effective for the system and will apply to all users.

The problem is not specific to any particular product that you install. In fact the problem did not occur for me when I installed avast which I have used now for some years. The problem occurred for me later when I installed my imaging recovery software (Acronis). It is a cumulative effect and really something that should be addressed by the operating system itself.

Oh… Interesting! I run Acronis on both of my machines so it looks like it is a number that needs to be extended due to more folks using it than anticipated?