Unfortunately, yes...
I had the same issue with a client outside the firewall (a Netscreen 50).
Master server (4.5 MP3) inside could connect to outside client just fine,
until the outside client tries to "talk back" into the DMZ via a NAT'd
IP address. (Yes, even with the "no call-back" set)

The outside client still  tries to connect back to the Master's INTERNAL
(non-routable) 192.x.x.x address, even with a "REQUIRED_
INTERFACE" statement in the client's bp.conf...

Further testing proved I could telnet to and from the proper ports (13782
& 13724) both ways using hostnames, so i figured all was ok...

NOT.

The "official" answer from Veritas support was they do not support NAT.

Hopefully this is not the case for you.  Please post your resolution or
mail me directly if you get any futher with this than I did.
My temporary solution was a second NIC in the outside client machine.

TIA

/JMH

> From: Clater_A <Clater_A AT bls DOT gov>
> To: "'veritas-bu AT mailman.eng.auburn DOT edu'"
>        <veritas-bu AT mailman.eng.auburn DOT edu>
> Date: Thu, 20 Feb 2003 13:25:55 -0500
> Subject: [Veritas-bu] NBU and Checkpoint -- Again (error 25)
>
> All -
>
> I went ahead and followed along with
> http://seer.support.veritas.com/docs/248000.htm which states that ports
> 13782, 13721, 13720, 13724 and 13783 need to be open for bi-directional
> communication on the firewall.  After doing that, and selecting the no
> callback option for the client, I am getting error #25 cannot connect on
> socket.
>
>
> Has anyone run into this before?
>
>
> ac
>