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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server name change zaps some clients

Status
Not open for further replies.

goony

Technical User
Joined
Apr 15, 2003
Messages
170
Location
US
Changed the IP nodename of my server, but did not change the address or the domain. Used Legato Tech Bulletin 396 as a guide.

Changed /nsr/res/servers file on all clients to reflect new nodename, stop/restart daemon on the clients.

Changed the DNS entry on my site from 'oldname' to 'newname'.

All client records in server have "nodename" and "nodename.mydomain.com" in Preferences --> Alias.

Afterwards, some clients backup just fine, others fail - here is a failed backup:

[tt]--- Unsuccessful Save Sets ---

* dbtest:All 2 retries attempted
* dbtest:All permission denied
* dbtest:All 02/26/05 01:22:17 nsrexec: savefs -s bullwinkle -c dbtest -g 2100 -p -l full -R -v
* dbtest:All Cannot connect to nsrexecd on client dbtest.mydomain.com and .rhosts permissions
* dbtest:All do not allow rsh.
* dbtest:All Permission denied[/tt]

Any guesses? I'm checking what I think are the 'typical' items, but no luck thus far.

Thanks!
 
Ehhh... forget the post. I found that some of the clients did not get their nsrexecd's stopped/started after the /nsr/res/servers file was edited with the new name.

Sorry for the trouble...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top