Avast free edition (7) blocking networked computers

[ComputersForLess]

Hi guys,
This is my first post here, (though I did a search to answer this question but didn't find any results) so if there's already a thread on this topic please point me in the right direction.
Here's the problem:
I run a computer service store with two locations, and we have recently switched to Avast from AVG because we like the boot-time scan.  We service a couple dozen computers a week and have been installing the AVG free edition on customers systems for about 8 years.  We would like to start installing Avast as a free antivirus solution on all these systems, but here's the thing...  It's blocking networked systems.  We do file transfers daily from customer systems to our store network system and back again.  We like Avast but are not going to use or recommend it if it has problems networking.  We, of course, know what our correct network settings are, so this is not the problem.
We've tested these problems multiple times by uninstalling Avast and then finding that the networking of computers then works perfectly.
Please don't make suggestions regarding Windows settings regarding sharing, permissions, ownership, ect...  We know these things, and network daily for a living.  Just not with Avast installed, which is a shame.
My question is this:
Is there a way to configure Avast networking parameters in the free edition to allow computers on the same network, (with the same workgroup, ect...) to identify each other and allow file transfer?  We hope that there is without too many hoops to jump through.  If it's too time consuming we'll stick with AVG since we never had a problem networking with them.

Thanks for any input.

[bob3160]

Welcome to the forum.This sounds more like a firewall issue and avast! free doesn't have a firewall.
avast! scans, it doesn't block.
How did you remove AVG from the old machines???
What firewall are you using, what's the OS, what other security programs are installed ?
The more information we have the easier it will be to find a solution.

[ComputersForLess]

Hi,

Thanks for the response.
It does sound like a firewall issue, but we don't have one installed.  Not sofware or hardware.  I didn't think the free version of Avast had a firewall.  Thanks for confirming that.
This is just one example, (the one currently on the workbench) but there have been many that we've tried... laptops and desktops... wired and wireless.
Currently, the customer laptop with a fresh install of Win XP, and no other av software but Avast ever installed.
We don't have any other security programs installed on our network system.
Our network system also has Win XP, (not a fresh install) and the previous AVG 2012 free edition was uninstalled with Revo Uninstaller, (in advanced mode to remove every registry hint and file of AVG).  Besides, we noticed that when other av software is detected by Avast upon installation, it supplies an option to install in Compatability mode.  This was not offered during our network installation...  just an express install.
So, both systems with Win XP, no other firewalls or security.
With no Avast installed the networked computers see each other beautifully with full file transfer ability.
We installed Avast on the customer laptop first.  It could still see our network system with full file transfer ability.
Next we installed Avast on our network system.  The network system does not see the laptop at all.  The laptop still sees the network system, but when trying to access the hard drive of the network, (to retrieve backed up files) we get this error message:
       ".....is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  Not enough server storage is available to process this command."

We didn't change any of our network settings or permissions.  It's the same settings we've been using for years.  We didn't change anything from when we had full networking capability before the Avast installation to testing again immediately following the Avast installation.  How can this not be something being tweaked by the Avast installation?  When we uninstall Avast, (without changing anything else) the networking immediately starts working again.

Can anyone shed light on this?

Thanks.

[CraigB]

Using revo to uninstall security software is not recommended, it might be a half decent uninstaller but it does not know the correct uninstall procedure to be followed when removing security software.

I recommend using the legitimate removal tool you'll find here http://singularlabs.com/uninstallers/security-software/ and i can guarantee you that if you run a manual search in the registry for AVG you'll still find loads of leftovers as i did on many systems, there may also be some leftovers in the hidden program data files and user app data files.

[ComputersForLess]

Thanks, but not the problem.  Revo actually uses the programs built-in uninstaller first before going into it's own advanced mode.  Are you saying that AVGs own uninstaller is not adequate to remove itself?
But we're getting off topic here. 
What about that error message when trying to connect to the network hard drive?
Am I to believe that no one else here has ever seen this problem with networking after installing Avast?

[bob3160]

Revo actually uses the programs built-in uninstaller first before going into it's own advanced mode.

It's the advanced mode that's the problem.
Correct removal procedure is to use the add/remove function first and then follow the instruction for the AV being removed
from http://singularlabs.com/uninstallers/security-software/
Each AV offers a removal tool.

[DavidR]

Not to forget, isn't the Revo Advanced mode only in the paid version ?
There is no way I'm paying for an uninstaller utility.

[CraigB]

Are you saying that AVGs own uninstaller is not adequate to remove itself?

Not just the AVG tool, they all leave remnants but they do a better job than third party removal tools imo, then i always cleanup the rest with a manual search of the registry which maybe a little more time consuming but it's the only way to be completely thorough.

Iv no idea about the networking problems your having so i'll leave it there for someone with more knowledge in that area to chip in.

[ComputersForLess]

Advanced mode is in the Revo uninstaller free version.
Again, not the problem.  Let's not shoot the CEO of Firestone for not having enough air in our tire.
It's a networking problem.  Networking is fine before Avast installation, and doesn't work after Avast installation.
The error message displayed is the key clue.  Since we're not making any changes to our settings, I've come here to ask the Avast "experts".
Put on your thinking caps people.

[Gargamel360]

Have you run the AVG tool yet?....because no matter how much you like Revo, not many here have much love for in regards to removing AV programs (as I am sure you have noticed), great for other purposes though.  And it would be a shame to move on to other suspects, and get nowhere, because an AVG remnant was responsible all along.  And this seems (by the error message) to be a Permissions issue (those are always fun), something that reeks of AV conflict, or some deeper OS problem.

Aside from that, my thinking cap says there are 2 Avast! components that scan network traffic....the Web Shield and Network Shield.  I am not sure ATM if either scan LAN traffic (since I do not have a LAN, just a single desktop, so I can't check that right now), but I would try disabling those one at a time as a troubleshooting step to see if turning them off allows the network shares.  Thats done via the UI>>Real Time Shields>>Web/Network Shields>>Stop (toward the top-right of the UI).

[ComputersForLess]

Hi Gargamel360,

Yes, we disabled the web and network shields, (in fact we disabled all 8 shields) and it made no difference.  It's the first thing we tried.
Ok, I'll run the AVG tool from the site supplied by bob3160, (thanks Bob) but I really doubt it will make a difference.  It's worth a try though.  I'll post the results.

Thanks.

[bob3160]

Yes, we disabled the web and network shields, (in fact we disabled all 8 shields) and it made no difference.

If you've taken avast out of the equation, then maybe it's time to look elsewhere.

[ComputersForLess]

Hi Bob,

We haven't taken Avast out of the equation.  In fact, Avast IS the equation.  You're missing the entire point, and why I'm posting in the AVAST forum.  Everything works without Avast installed.  In fact, everything works with every other av program we've ever used, including AVG, (which I'll probably re-install tomorrow since I don't have time to figure out what's wrong with Avast code...  that's someone elses job).

Maybe I'll just talk to Gargamel360.  At least he seems to get the picture.

We've run the AVG removal tool as suggested.  Same error message, no luck there, (I might add, as I expected) but it was worth a try.
So here's what I did just to remove any shadow of a doubt.
On the off-chance that newly installed Avast didn't like "old" shares for the network, I decided to remake them.  So, with Avast installed and updated I removed shares on the network system to the storage drives used for customer transfer.  Then rebooted.  Added the new shares, (with full permissions and control) then rebooted.  Rebooted the customer laptop in question. 
Double-checked our startup programs, and services to insure there were no programs that might interfere, (we even temporarily disabled our Quickbooks just in case).  Added Avast to list of Windows Firewall exceptions, (even though this shouldn't be necessary and was not put in that list before, but, just in case Windows firewall was blocking access for some reason). Rebooted.
Connected to the store network with the customer laptop with both wired, (local area connection and wireless).  Same workgroup.
The network computer is then seen by the laptop.  The network computer opens on the laptop and sees the various shared hard drives.  However, when trying to open the network storage hard drive it still yields the same error message, (even though full access permissions are enabled and even though the network hard drive opens when Avast isn't installed).  And there's the problem.  I already know that the Avast installation is making some change that is giving us this error message.  I'm simply here to determine if this is a known issue that can be tweaked, and if it's worth the time to do so.
This is probably a problem the software engineers at Avast will need to eventually address.  In the meantime, we will need to stick with an av program that works for us.

[ComputersForLess]

                                            *****UPDATE*****

I just found the problem and fixed it.  Tested and working great now.  You moderators and experts may want to take note of this so you can help others with this problem.

Avast changes, and in my case removed entirely, the IRPStackSize registry entry.  The default for this registry entry is (15) so even with it not present the default is 15.

For those of you encountering this error: "...is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  Not enough server storage is available to process this command" you need to modify/create the IRPStackSize registry entry.

Here's how you do it.  This needs to be done on the computer that holds the folders/drives you want to share.  Not the one trying to access the share.
Open your registry editor, (run, regedit) then go to HKEY_LOCAL_MACHINES\System\CurrentControlSet\Services\LanmanServer\Parameters.
Look for the the IRPStackSize entry.  If it's there, modify the value to 16 or higher depending on your use.  I set mine for the max value of 50.
If the entry is not there, (which was my case since Avast deleted it) then create a new one as a DWORD, and make sure your spelling is correct as such: IRPStackSize.
Then modify it again to set the value, (size) at your desired level.
Reboot.
Problem solved.
Avast, stop changing/deleting needed windows registry values please.  Or at least set to a higher level.  Please address this issue with an update.

This issue I'm sure has appeared in this forum at some point, (I can't imagine that it hasn't) but apparently it needed to resurface.

I hope this helps someone else.

[bob3160]

I'm still waiting for confirmation from a developer. I still think this has to do with your use of Revo

instead of using the removal tool.