Problem looks quite simple to me to solve : you are
experiencing, like error msg is pointing out, a DNS
lookup failure to resolve 66.10.227.102 from client side.
Resolve dns lookup failure from dns, check client's dns settings
or fill 66.10.227.102 to client's host file.
HTH
TH
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD
******* h ******* 1 Rue de l'aeronef/Luchtschipstraat
****** h ****** 1140 Bruxelles/Brussel/Brussels
***** hhhh pppp *****
***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
***** h h pppp ***** 1200 Bruxelles/Brussel/Brussels
****** p ****** BELGIUM
******* p *******
********* ********* Phone : +32 (0)2 / 729.85.42
Mobile : +32 (0)498/ 94.60.85
Fax : +32 (0)2 / 729.88.30
I N V E N T Email/MSN : thierry.faidherbe(at)hp.com
Internet : http://www.hp.com/
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Abhijit Mathew
Sent: Friday, June 09, 2006 5:27 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Legato Networker 7.2
Hi Shyam,
This is what I have from the daemon.log on the client side:
01/23/06 23:00:23 nsrexecd: Warning, cannot resolve host 'IISSRV01' to
'66.10.227.102', name server may be misconfigured.
There is a whole list of these errors.
There are a couple of names for the networker server under the Aliases
field. Can I put in an IP address under the remote tab for the networker
server?
Thanks,
Abhi
________________________________
From: Shyam Hegde [mailto:hegde.shyam AT gmail DOT com]
Sent: Friday, June 09, 2006 9:55 AM
To: Abhijit Mathew
Subject: Re: [Networker] Legato Networker 7.2
Hi,
Is there anymore errors on this in /nsr/logs/daemon.log during this
event?
Check if you have any alias names for the client, which needs to be
entered in ALIASES field under REMOTE tab of the client resource
configuration.(Like server.xxx.marketresourcepartners.com or so)
Regards
Shyam
On 6/9/06, Abhijit Mathew <amathew AT marketresourcepartners DOT com> wrote:
Hi,
I am having an issue with Legato Networker 7.2. The error that I am
getting nsrexec: SYSTEM error: Connection refused
Our current network has the networker server on a different subnet
(172.16.128.X) and the client on another subnet (192.168.X.X). We are
able
to ping from both the machines to each other and nslookup is also
working
fine.
Other machines in the same subnet as the networker server do not have
the
error. I need to manually run the client having the error to do the
backup
which runs without a problem.
I have added the FQDN as well as IP address of the Networker server in
the
hosts file and \nsr\bin\res file of the client having the issue. I
restarted the networker daemons on the client after I changed the res
file.
Any steps that I missed out on? Any suggestions would be appreciated.
Thanks,
Abhi
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
