OK, I have installed the latest patch for Solaris (J0850559) and it doesn't
affect what happens when I attempt a backup.  For those who answered with
advice about which ports to open in the firewall, it isn't a port issue.
It's a gateway issue.  The firewall already allows the proper ports through,
but the client BPCD insists on trying to bind to the firewall port which is
refused by the firewall.  If anyone is willing to either look at my trace
log to figure this out or to send me a trace log of a successful backup
through their firewall for comparison (Solaris client with Netbackup 3.4),
I'd be really really grateful.  So far, Veritas support is striking out.
And I have sent them the trace logs so they have all the information I have.

Follow up:  Is anyone using 3.4 through a firewall?  I've seen a couple of
messages conerning 3.2 and firewalls.  I thought 3.4 was more firewall
friendly.

Thanks in advance...


Dana Bourgeois
Slam Dunk Networks 
Digital Mechanic & Network Janitor
1.650.632-5543
1.650.996-5687  [cell]


> From: Dana Bourgeois <Dana AT slamdunknetworks DOT com>
> To: "'veritas-bu AT Eng.Auburn DOT EDU'" <veritas-bu AT Eng.Auburn DOT EDU>
> Date: Wed, 24 Jan 2001 14:03:16 -0800 charset="iso-8859-1"
> Subject: [Veritas-bu] connecting to bpcd through a Checkpoint 4.x Firewall
on Solaris
> 
> I have a lot of experience with Legato but little with Veritas.  I have an
> application server in my DMZ.  We use NAT.  Netbackup Datacenter 3.4,
> Solaris 2.6.  I can trace the bpcd on the client in the DMZ and watch it
> fail.  It is trying to bind a port on the firewall rather than communicate
> through to the master (how it would do that I don't know because I've
never
> seen a successful gateway trace).  It knows about the master - I can see
it
> read all the config files and resolve the master's IP address
successfully.
> I am installing the latest patch - J0850559 - on the server and client and
> will see if that fixes this problem.  While I am doing that, does anyone
> have a similar problem they have solved?  Any ideas?
> 
> 
> Dana Bourgeois
> Slam Dunk Networks 
> Digital Mechanic & Network Janitor
> 1.650.632-5543
> 1.650.996-5687  [cell]