We have a Windows Server 2003 Std Edition server (SP2) running MS SQL
2005 and McAfee ePO services. I have NW Client 4.91.4 loaded on the
server and have logged into Novell. The BM Client Trust Key is loaded
and some of the ePO processes work (e.g., I'm able to download latest
DAT file) as long as I'm logged into Novell. (NOTE: If my server isn't
logged ino Novell, I can't download the DAT file and update my Master
Repository.)

However, my ePO "MyAvert Threat Advisory" is not able to connect to
McAfee and update the "Latest Available Dat: or Engine:" information.
Any ideas as to what could be preventing the ePO from contacting McAfee
for the Advisory information?


BM 39. SP1 Filter for ePO
************************************************** ****************
SInt SAddress Packet Proto DPort SPort
PRIVATE XXX.XXX.XX.XXX All Access TCP <All> <All>

ackFilt stFilt DInt DAddress
0 1 PUBLIC 208.187.212.0/255.255.255.0
************************************************** ****************


I have the ePO Server Settings - Proxy Settings as follows:
************************************************** ****
Type: Use one proxy server for all protocols
Proxy server settings: Proxy server: XXX.XXX.XX.XXX
Port: 8080

Proxy authentication: Use HTTP proxy authentication
User name: .cn=AdminName,o=OName

Exclusions: 208.187.212.*
************************************************** ****


--