Blocking Home Network on XP

Avast Free Antivirus / Premium Security
1

It appears that Avast is blocking the transfer of information between my computers within my home network. Can someone tell me how to prevent this from happening? Thanks!

2

What kind of transfer exactly?

3

I’m running a program on computer A with workstations located on computers B & C. All have Avast. Computer A is where the data resides. When I run a data-driven operation from B or C, it times out and corrupts my database. When I turn Avast off, I don’t have the issue. I’ve excluded the folders that contain the data for the software. That didn’t work.

4

Please see this thread.

5

Thanks. But I’m not getting memory messages. I’m getting Delayed Write Faled. Windows unable to save all the data. Is it the same fix?

6

jazzloft, what version of avast are you using, exactly? Have you already updated to the latest version (4.8.1290)?

thanks
Vlk

7

I’m using Avast Pro 4.8.1229

8

I would suggest that you manually update to the latest version, right click the avast ‘a’ icon, select Updating, Program Update. Complete the update and reboot as requested at the end of the update.

Then test again, no point in trying to fault find if you are using an old version.

9

I upgraded and the same thing. I can see both my computers at the same time. I watched while I tried to process something on the workstation. It was hung up, I disabled Avast on the primary computer and the workstation immediately started responding.

10

Hung up? So is that a new thing? (I thought that the original problem was that you were getting the “Delayed write failed” popups [balloons]) but there were no hangs or anything…?

BTW can you try placing something like

\*

to the list of scanning exceptions for the Standard Shield, to see if it makes any difference?

Thanks
Vlk

11

Yes, that’s what happened. There’s a bar that shows the progress. The bar stops for a bit and then I get the write fail.

12

Thanks for this heads up. I was experiencing a similar problem when trying to save a TI backup job to a network drive (something I had been able to do prior to upgrading to v4.8.1290). I changed the IRPStackSize to 18 (actually, the IRPStackSize value did not exist in the target machine’s registry, so I created it, per MS kb177078), and now it works fine again. It pays to peruse the forums! :slight_smile: