problem backing up my F.W 1

[RCNetAdmin]

I have a sun machine that is my NG Fire wall.
I was backing up my F.W and my DMZ with veritas.

After updating all patches to the Sun spark 250 I am able to back up the DMZ but not the F.W.

I receive a TCP/IP acknowledge with no problem, and then the session is closed with no errors.
When try to access the external lag answer the backup server instead of the internal one.

Please help.

 

[daFranze]

what does your Firewall Protocoll tell you? I guess patches/updates closed some ports...

Regards
-- Franz
Sorry I'm not a native spaeker, I'm from Munich, Germany - "Home of the Whopper", oh no, "Home of the Oktoberfest" ;-)
Solaris System Manager; I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[RCNetAdmin]

Thank you Franz,

This is the problem.
The F.W as a F.W accepts the session.
In the TCP/IP session when doing snoop, I see session request from the Veritas.
The request is done to the internal lag of the F.W.
Then the F.W returns a replay from the external lag. In the end the session is closed with no errors as a normal TCP/IP session is closed.
In the F.W rules I granted access to the backup.
Is it possible that the ports that you are talking about were closed in the Solaris??

Thanks

RC

 

[daFranze]

>> Is it possible that the ports that you are talking about were closed in the Solaris??

ports are opened/closed by
a) the configfiles
b) the firewall (ie. ip-filter)

You have to find out WHO has "disabled" these ports; I suggest to allow backupserver ANY acces to the internal FW interface at any port and from any port back to any port on backupserver; if this works the FW closed something, if not some configfiles got an update with a patch and closed some ports, but this would be a funny day of searching...

Regards
-- Franz
Sorry I'm not a native spaeker, I'm from Munich, Germany - "Home of the Whopper", oh no, "Home of the Oktoberfest" ;-)
Solaris System Manager; I used to work for Sun Microsystems Support (EMEA) for 5 years