new version 17.5.2302

[REDACTED]

Posted yesterday on the french forum, 40 views, no answer.

Installed version 17.5.2302 build 17.5.3559.178 in 3 workstations (WS)
Since the installation of this version into 3 WS out of 4, the 3 WS running this version have mapping problems with windows. The 4th WS has version 12.3.2280 and does not experience any problem at all as far as mapping is concerned.
WS description with network mapping problems:
  - Windows 7 pro x64
  - mapping:
      - net use n: \\ip_server\resource password /user:user_name
  - net use responds OK after a few seconds
  - the displayed mapping looks OK
  - the file server is: linux box (OpenSuse 13.2 x86_64) running samba, distant access (internet connection hi-speed with a Fortigate 60D firewall (FW) at each end having a continuous network through a VPN)
  - having a double click on the shared network drive Windows takes a very long time searchong and display nothing except the window error stating ".. connexion already active" (!!??)
  - in a command line a  ...> dir n: command takes a very long time  between 1 and 2 minutes) and displays finally the good content but the mapped network drive is completely useless
  - doing the mapping after a previous  ...> net use n: /delete end with the same network error
  - trying a link with the distant FW using a browser never succeeds
  - the link with the local FW is OK

BUT
  - inactivating Avast in a WS with network problem solves the problem !!!!
  - the link with the distant FW is active and running again
  - When Avast is reactivated the same problems arise again

in ALL cases
  - a Windows network map on the local server (same LAN) runs without problems
  - access to the local FW is never discontinued

4th WS (Avast old version of 2016) is always up and running
When I use my own laptop (running a previous version of Avast everything runs well including Windows network mapping

Any solution ?
Please note before giving an answer that all Windows WS have been updated and before yesterday July 13 all WS were up and running since weeks before.

A. Fortuny.

[Eddy]

What shield is causing the problem ?

[REDACTED]

Honestly, I don't know.
The only thing I'm pretty sure is that when all Avast agents are disconnected everything runs well.

Antonio.

[Eddy]

Well, test and find out what shield is causing the problem.

[REDACTED]

Test conditions:
- fresh reboot
- free Avast running as usual

as expected, network mapping fails

Avast/params/components (after each component inactivation, wait 2 minutes) :
inactivate files agent for 1 hour: network mapping fails
inactivate suspect actions for 1 hour: network mapping fails
inactivate mail agent for 1 hour: network mapping fails
inactivate suspect actions for 1 hour: network mapping fails

leave all agents as they are (inactive)
using system tray, right click on Avast icon, on popup choose agents management and inactivate for one our, alla agents, no choice): all network mapping working again.

reactivate all individual agents and inactivate 1 hour using system tray: network mapping running as usual.
It looks like if individual inactivation has no effect. Only the global one using the system tray and inactivating everything sounds ok.

Antonio

[REDACTED]

Last test:

Disconnect network drive n:
Uninstall Avast
Reboot
Map network drive n: on usual location: immediate acknowledgement
manage n: drive as usual
Download and install free Avast from last download location
network drive n: has become inaccessible again

Uninstall Avast
Install another free AV
Check network drive n: everything runs fine

Antonio.