Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Backup DMZ

Status
Not open for further replies.

ptitechatt

Technical User
Jun 1, 2005
9
FR
I ve some trouble to restore files from server to a client in DMZ.

Here is the symptom:

Backup:
client initiated backup OK!
Server initiated backup OK!

Recover:
Client initiated recover OK!
Server initiated recover KO...

There is some TCP connection on port 445 and 139 denied on the firewall....
Networker doesn't need these ports normally ?

any help help should be good...

I have a networker 7.2.2 server & client

If sommebody can tell me what config he has in order to backup & recover their client in DMZ

THX very much
 
From Networker Documantation:

*schnipp*
NetWorker daemons get assigned to 'secure ports' between 512 and 1023. nsrexecd is the exception to this rule. Part of the reason that we don't have specific ports assigned to our daemons comes from the fact that we are using RPC and Portmapper.
Secure ports are ports below 1024. The term 'secure' comes from the fact that these ports will only allow programs that are started by root to attach to them. In this way a program coming in from the outside is able to connect to these ports and be reasonably sure that a hacker is not on the other side ready to wreak havoc. So when nsrd gets started, since it is started by root - it is able to attach to a secure port. Then - when a save starts to send it's data to the server, it can be assured that the process on the other side of that port is something secure - i.e., started by root.
If you want to turn off ports or close ports, you are doing this so people 'outside' the firewall can't get in. The ports are still open to processes inside the firewall. This means that NetWorker will still request ports from 512-1023. If you close any of these ports - and NetWorker happens to grab the one that's closed - then the clients outside the firewall will not be able to communicate.
There is no way to run NetWorker in an environment with a firewall that closes off ANY port between 512 and 1023. You can close these ports for specific IP addresses - which could be used to allow NetWorker clients to communicate - while any others are omitted.
*schnipp*

Cheers Novelli
Novell Master CNE + CDE
 
There is no communication with ports between 512-1023 so I don't understand what dos it me...

Can you be more explicit?

excuse mu poor english I m french.

And the problem is not a save stream but a recover stream.
In the winworkr GUI, I ve got some cabalyst characters like
@-U%
and that all.
When I do a recover from command line, I ve got somme ommunication then it abort...

Thx in advance

Why all my save session are going on and my recover sessions are so bad...?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top