[isalist] Re: Backup Exec 10 and ISA 2004

  • From: "Steve Moffat" <steve@xxxxxxxxxx>
  • To: "ISA Mailing List" <isalist@xxxxxxxxxxxxx>
  • Date: Thu, 6 Apr 2006 19:45:16 -0300

http://www.ISAserver.org
-------------------------------------------------------

Thy festering gob need shutting....:))

-----Original Message-----
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Greg Mulholland
Sent: Thursday, April 06, 2006 7:46 PM
To: ISA Mailing List
Subject: [isalist] Re: Backup Exec 10 and ISA 2004

http://www.ISAserver.org
-------------------------------------------------------
  
wow i only know how to copy and paste but that cut thing sounds
schweeet!

Steve Moffat wrote:
>
> *I learnt how to cut and paste years ago...**J***
>
> * *
>
> ----------------------------------------------------------------------
> --
>
> *From:* isalist-bounce@xxxxxxxxxxxxx
> [mailto:isalist-bounce@xxxxxxxxxxxxx] *On Behalf Of *Thor (Hammer of 
> God)
> *Sent:* Thursday, April 06, 2006 6:37 PM
> *To:* ISA Mailing List
> *Subject:* [isalist] Re: Backup Exec 10 and ISA 2004
>
> Well, look who knows so much, eh? :-p
>
> t
>
>
> On 4/6/06 2:18 PM, "Steve Moffat" <steve@xxxxxxxxxx 
> <mailto:steve@xxxxxxxxxx>> spoketh to all:
>
> *What ports should be opened on a Firewall?
> *
> When backing up a server through a firewall with Backup Exec, there 
> are several ports that need to be opened on the firewall.
>
> First, the NDMP port (port 10000 by default) needs to be opened on the

> firewall. This is an outbound port only, and the media server is 
> talking to the remote agent on this port.
>
> Second, all ports specified in the *Enable media server TCP dynamic 
> port range* option need to be opened in the incoming range on the 
> firewall.
>
> Third, all ports specified in the *Enable remote agent TCP dynamic 
> port range* option need to be opened in the outgoing range on the 
> firewall.
>
> *Note:* If there are problems attaching to a server behind a firewall,

> it is recommended that the logs on the firewall be examined for any 
> "access denied" messages for communicating over these ports.
>
> ----------------------------------------------------------------------
> --
>
> *From:* isalist-bounce@xxxxxxxxxxxxx
> [mailto:isalist-bounce@xxxxxxxxxxxxx]
> <mailto:isalist-bounce@xxxxxxxxxxxxx%5D> *On Behalf Of *Bret Hanson
> *Sent:* Thursday, April 06, 2006 5:58 PM
> *To:* ISA Mailing List
> *Subject:* [isalist] Re: Backup Exec 10 and ISA 2004
>
> Its TCP traffic.
>
> ----------------------------------------------------------------------
> --
>
>
> *From:* isalist-bounce@xxxxxxxxxxxxx
> <mailto:isalist-bounce@xxxxxxxxxxxxx>
> [mailto:isalist-bounce@xxxxxxxxxxxxx]
> <mailto:isalist-bounce@xxxxxxxxxxxxx%5D> *On Behalf Of *Steve Moffat
> *Sent:* Thursday, April 06, 2006 3:48 PM
> *To:* ISA Mailing List
> *Subject:* [isalist] Re: Backup Exec 10 and ISA 2004 *TCP or UDP 
> tho....or both...Symantec are sneaky*
>
> ----------------------------------------------------------------------
> --
>
> *From:* isalist-bounce@xxxxxxxxxxxxx
> [mailto:isalist-bounce@xxxxxxxxxxxxx]
> <mailto:isalist-bounce@xxxxxxxxxxxxx%5D> *On Behalf Of *Bret Hanson
> *Sent:* Thursday, April 06, 2006 5:38 PM
> *To:* ISA Mailing List
> *Subject:* [isalist] Re: Backup Exec 10 and ISA 2004
>
> I see that the [Enterprise] Default Rule is blocking traffic on port 
> 10000 - even though I have allowed it in the Firewall Policy.
>
> ----------------------------------------------------------------------
> --
>
>
> *From:* isalist-bounce@xxxxxxxxxxxxx
> <mailto:isalist-bounce@xxxxxxxxxxxxx>
> [mailto:isalist-bounce@xxxxxxxxxxxxx]
> <mailto:isalist-bounce@xxxxxxxxxxxxx%5D> *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]
> <mailto:isalist-bounce@xxxxxxxxxxxxx%5D> *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.
>
------------------------------------------------------
List Archives: //www.freelists.org/archives/isalist/  
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp 
ISA Server Articles and Tutorials:
http://www.isaserver.org/articles_tutorials/ 
ISA Server Blogs: http://blogs.isaserver.org/ 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
------------------------------------------------------
To unsubscribe visit http://www.isaserver.org/pages/isalist.asp 
Report abuse to listadmin@xxxxxxxxxxxxx 

------------------------------------------------------
List Archives: //www.freelists.org/archives/isalist/
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server Articles and Tutorials: http://www.isaserver.org/articles_tutorials/
ISA Server Blogs: http://blogs.isaserver.org/
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
To unsubscribe visit http://www.isaserver.org/pages/isalist.asp
Report abuse to listadmin@xxxxxxxxxxxxx

Other related posts: