save set errors after a failed backup

[harris2]

I keep getting the message "RPC error; unable to send" after an unsuccessful backup. I tried looking it up on the legato tech dbase but it doesn't seem to help. I am running 6.0.1 on an NT 4.0 client and 5.5.1 networker server on an NT 4 box. I've heard that the box has to be the same version as the clients but everything else is backing up fine except for this one client. Thanks in advance for suggestions or ideas.

 

[ag100]

Hey,

I've seen these errors in a few scenarios.. First, when you run a preview save from the backup server, what errors do you get? Can the backup server and the client ping eachother? Also, what happens when you try and run a save from the client to the server? From the client, try typing:

savefs -p -s <backup server>

From where your nsr\bin directory is...

What happens?

 

[cfowler]

RPC errors usually indicate a problem with network configuration. You might wish to check that all aliases are written correctly for the client in question. Use the RPCINFO -P command on ALL aliases for the client in question to ensure communications on all ports. You could check to see that the NIC is set to 100/full and the port on the switch the client connects through is also set to 100/full.

The probe is kinda funny. It only lets you know that communications can be established. In this particular case, if it's a problem with an alias, the probe may return correctly, but the actual save will still fail.

example: rpcinfo -p <clientname>
rpcinfo -p <clientname>.dns
rpcinfo -p <clientname>.otherdns

to be run for EACH alias the client contains

Good luck,

cfowler