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.