Use the real time monitoring to see what protocols & ports it's trying to communicate on. Open 2 ISA MMC's and have one listening on the localhost network, and the other on the internal network Monitor them both when BEX is trying to communicate and the protocols and ports should be apparent. S ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Ross Sent: Thursday, April 06, 2006 5:33 PM To: ISA Mailing List Subject: [isalist] Re: Backup Exec 10 and ISA 2004 im having the same problem. ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Moffat Sent: Thursday, April 06, 2006 3:32 PM To: ISA Mailing List Subject: [isalist] Re: Backup Exec 10 and ISA 2004 Use the real time monitoring to see what protocols & ports it's trying to communicate on. S ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Bret Hanson Sent: Thursday, April 06, 2006 5:31 PM To: ISA Mailing List Subject: [isalist] Backup Exec 10 and ISA 2004 I have ISA 2004EE running on Windows 2003 R2 - I am trying to do backups with Backup Exec 10 via a remote agent. I installed the remote agent locally on the ISA box. When I try to browse to the ISA box in BEX I can't it. I allowed ISA to listen on port 10000tcp incoming from the BEX server with no luck. The support person I spoke with at SymantecVeritas didn't even know what ISA server was. I can't be the only one in the world trying to back up ISA 2004 with Backup Exec 10. Can anyone shed some light on this? Bret Hanson Systems Administrator Yunker Industries, Inc.