Looks like you have gone through many of the steps that EMC Software Support would ask you to do, I would suggest to add the Networker server and Networker client's IP, short and fully qualified names to the hosts file for each system.
What are the switches you are using when you run the save command. I recommend that you run
C:\Program Files\Legato\nsr\bin\>save -s <nw_server> -b <pool> C:\filename
C:\filename to equal a file on the root of C:\.
Yes I already added the short and long names and IP addresses of the client in the Networker server hosts file and likewise for the client's hosts file but I still had the same issue.
I actually found out that the problem was the client had 2 NIC cards with 2 IP addresses, 1 on a DMZ DNS suffix and another on a PRIVBACKUP DNS suffix and the IP address I had added in the Networker server host file had the DMZ (external) IP address. This was confirmed as we had other web server clients already added to the Networker server hosts file but on the PRIVBACKUP IP range. After changing this and saving the file, I did a DNS forward and reverse lookup from the Networker server and this resolved to the PRIVBACKUP IP address.
I then did a probe savegroup backup of this client using "savegrp -pvvv -c <FQDN of client> -g "groupname"> c:\output.txt 2>&1" which worked and then the following night this client backed up successfully to the EDL and also cloned to tape.
Thanks for your assistance.
I find it useful to test the RPC connectivity using the short name, long name and IP address from the client to the server and visa versa. You would have seen the problem immediately by having success with only the IP address while getting failures when using the shortname and longname on the client. You would have had success with all three while testing from the backup server.
rpcinfo -p <shortname>
rpcinfo -p <longname>
rpcinfo -p x.x.x.x
Note: After installing the client on a new machine, logout and then back in again to get the new PATH mappings so you can use RPCINFO.