I frequently have the exact same problem.  One way I've been able to
make it work is to create a host entry for that host in the /etc/hosts
file.  Once the client backups successfully once you can remove the host
entry and everything works as it should.  It would probably be a good
idea to keep a host entry for each client, but it's annoying to have to
unnecessarily maintain those entries.  If DNS forward/reverse works from
both client and server it should work.  I never had this problem until
6.x then it got worse with 6.1.2.

Joel

-----Original Message-----
From: Oscar NOSPAM Olsson [mailto:spam1 AT QBRANCH DOT SE] 
Sent: Monday, June 23, 2003 11:48 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] client not registered problem

On Mon, 23 Jun 2003, Jack Lyons wrote:

JL> Was a backup job running when you added the client.  Have you
rebooted the
JL> server.

No, and no. I did restart the networker software, which solved the
problem.

JL> I believe I had a similar issue and was told by Legato Support that
it can
JL> sometimes take a long time to register a client if a job is running.
I
JL> believe rebooting the server fixed it.

Well, in either case that's just fucked up. :) Dynamic Reconfiguration,
anyone? :P

//Oscar

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=