Strange request

[joburg]

A dumb question - while busy with OE my firewall popped up and asked if I accept these changes:

Filename: C:\Program Files\Alwil Software\Avast4\ASHMAISV.EXE
---- New modules: 2 ----
C:\PROGRAM FILES\LOGITECH\MOUSEWARE\SYSTEM\LGMOUSHK.DLL
C:\WINDOWS\SYSTEM\ASYCFILT.DLL

Could this be from Avast?

[Lisandro]

Which firewall are you using?
The first dll seems legit, it's from Logitech Mouseware. But why it's being asked to connect by ashmaisv.exe?
The second, maybe you can google to find more info.
Seems that 'shared components' are trying to connect and, that time, the program that made the 'first' request was avast mail service, probably because you're downloading emails.
Oh, another question, did you change, recently, the Logitech drivers for your mouse?

[joburg]

Thanks Tech, I’m using Sygate. You’ve put my question in a nutshell, why ashmaisv.exe? I make a point of it to first of all google-it with dif wording formats to check if a quick solution pops up.
The “'first' request” may well be the answer there and my Logitech setup untouched for many years.
I’ve not received the request again after I did not accept the first request originally.

[Lisandro]

my Logitech setup untouched for many years.
I’ve not received the request again after I did not accept the first request originally.

Sometimes, shared componens, even not changed, interact each other in such strange way that similar questions could appear from the firewall.
Anyway, it's good that it was not asked again 

[szc]

Some brief info about the second one (ASYCFILT.DLL) can be found in here:

http://www.liutilities.com/products/wintaskspro/dlllibrary/asycfilt

Quote:

Description:
asycfilt.dll is a module used by Microsoft OLE (Object Linking and Embedding).

[joburg]

Thanks sZc, at least I know now it is a safe file.

[DavidR]

Whilst the actual asycflit.dll file may well be a legitimate file, the questions really should be what was using it and for what purpose and what either file would have to do with ashMaiSv.exe?

This may well be a case of Sygates know issue with local host loopback proxies and confusing what was the originating program?

But you are probably ok.