Networker

Re: [Networker] Backing up files in the DMZ

2004-01-15 16:35:32
Subject: Re: [Networker] Backing up files in the DMZ
From: "Ungaro, Matt" <mjungaro AT CAPITOLINDEMNITY DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Thu, 15 Jan 2004 15:31:29 -0600
Hi Yura, and everyone else. 

Thanks for the help. I figured out that for some reason, my backup server
REQUIRES me to put the host entries into the hosts file for the server to see
the clients in the DMZ. Internal works fine with DNS, but DMZ requires hosts.
Any reason why this would be? I'd love to not have to maintain a massive
hosts file. Thanks!

-----Original Message-----
From: Yura Pismerov [mailto:ypismerov AT TUCOWS DOT COM]
Sent: Thursday, January 15, 2004 11:34 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Backing up files in the DMZ


    Sorry, I missed the part that says it is Solaris.
    Use "getent hosts `hostname`" instead.

Yura Pismerov wrote:

>    Could be DNS issue as well.
>    Run "host `hostname`" on the client and make sure the name it
> returns is the same you defined in the client entry in Networker.
>    Sometimes client gets confused by bogus entries in the local
> /etc/hosts.
>
> Ungaro, Matt wrote:
>
>> Hi,
>>        We have Legato Networker 7.0 running on a Redhat Linux 9.0
>> server.
>> The Networker server is located in our internal network, and I can
>> backup and
>> restore clients in the internal network just fine. But when I attempt to
>> backup and restore clients in our DMZ, I get a message from savegrp like
>> this:
>> savefs: RPC error: Unable to send
>> savefs: cannot retrieve client resources
>>
>> I have run rpcinfo on both the client and server and can see the rpc
>> ports on
>> both systems. I have all protocols open between the client and server
>> on the
>> firewall (The firewall is Checkpoint FW-1 v4.1). The particular
>> client I am
>> working on right now is a Sun running Solaris 7 64bit with the Networker
>> client version 7.1. I am attempting to just backup the saveset All. I am
>> allowing all ports for the server to go to the client, and all ports
>> from the
>> client to go to the server, for troubleshooting purposes. Any help or
>> ideas
>> would be appreciated.
>>
>> Matt Ungaro (mjungaro AT capitolindemnity DOT com)
>> Network Specialist
>> Capitol Indemnity Corporation
>>
>> --
>> Note: To sign off this list, send a "signoff networker" command via
>> email
>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>> http://listmail.temple.edu/archives/networker.html where you can
>> also view and post messages to the list.
>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>
>>
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>