On Dec 20, 2007, at 11:04 PM, Peter Viertel wrote:

Nsrlcpd is started as a process on the storage node when the autochanger

is enabled...   You should go to devices in NMC - look under library
tree and right button on the library to see if you can Enable it...

If nsrlcpd doesn't start you might have an issue with your storage node

config...

On the storage node you need both the client and storage node packages.. The servers file on the storage node has to have the server in it, maybe

that's not right...

For all your clients, you must have the *server* in their servers file -

not much value in having the storage node listed.

If all looks good - then perhaps the fact that fqdn's are being reported

in the log may point to an issue with dns - your client records -

including the client record for the sn should be unqualified names, the

fqdn's should be in the aliases list for the client though.

Networker is very touchy with dns because it relies a lot on dns reverse

lookups.

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 with 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