This is the summary of what steps I took to resolve the above mentioned
issue.

1) Shutdown networker and ran 'nsrck -F'
2) Client machine believed it was 2 different FQDN names, fixed in
network control panel.
3) DNS for client name had correct forward but wrong reverse, fixed in
DNS.
4) Removed extra and now wrong alias entry in the client setup on the
server.

After the above 4 items had been completed I tested the client again and
it is now properly saving at other levels and is no longer complaining
about the 'No save sets with this name were found' message..

Thanks to all who offered suggestions,

Brendan Sandes
Philippe Lamare
Terry Lemons
Davina Treiber


--
"Want to be truly exceptional?
Be a touch insane...
You need a little bit of insanity to do great things." -Henry Rollins
----------------------------------------
Kent Holloway - Systems Engineer - Onvoy
----------------------------------------

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=