Discussion Locked

AV scan in NAI Gauntlet firewall

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Is anyone using Network Associates (PGP-McAfee) Gauntlet firewall for NT? The virus scanning module quit working with message "AVClientInit Failed, error: 1" Email won't come in unless scanning is disabled at this point.

3 replies

by niru

Step 1:

(a) Bring up you "User Manager for Domains".

(b) Pull down user menu and select "Select Domain..".

(c) In the Domain edit box, type in the local machine name, then click OK. You should see GauntletProxy as one of users.

(d) Change user GauntletProxy's password to another valid one and remember it.

Step 2:

(a) Open control panel

(b) Select Services.

(c) Open every Gauntlet* service EXCEPT GauntletMasterService and GauntletAuthsrv (all Proxies that use Gauntlet Proxy user as a startup)

(d) After opening, you will see "log on" group, change the password of GauntletProxy as the same one chosen under "User Manager for Domains".

Step 3:

(a) Run dcomcnfg.exe in command line.

(b) Double click "avscan" inthe listbox.

(c) Select "Identity page" in the avscan properties.

(d) Change GauntletProxy's password as the same one chosen under "User Manager for Domains".

Step 4:

Reboot

And you will follow the same procedure for all proxies

CAUTIONS

If you change the password for one proxy and not the others, it may render Gauntlet Firewall non-functional. You should not change the "GauntletMasterService" and "GauntletAuthsrv" password.

MORE INFORMATION

To check if avscan has failed to initialize, you can go to NT Task Manager and look for avscan. If avscan does not appear under the task manager and you have enabled avscan for any proxy you should follow above procedure

by rigneyma

Thanks for your answer. I'm definitely experiencing some kind of DCOM authentication error as you mention. I tried the password change on a test firewall that was working %100. The password change actually caused the DCOM error to occur. A full reinstall of Gauntlet does not cure the DCOM issue either. In addition to the Gauntlet log error I also get a DCOM error in the NT event log "access denied starting a DCOM server". I've found no help on the MS site. Any other thoughts are appreciated.

This discussion is closed to new replies.