RPC error: failed to receive

[baldymike]

Has anyone seen this message before? I am running Networker 6.1.3 on WinNT trying to connect to HP-UX v11. and I get this message which I can't find a solution to anywhere else.

 

[sdeb]

Check name resolution between client and server (even if you're sure of your DNS configuration).

The easiest way to test it is using your hosts files.

 

[baldymike]

IP communications seems to work fine between the machines but the other concern I have is that the client name is 13 chars in length. Could that cause this problem?

 

[sdeb]

I don't think so (almost in some cases where we could use the complete DNS name).

The only pre-requisite is no underscore "_".

Could you try to launch a manual backup from the client with the following options :

save -nvv -l full -b YourDestinationPool

the "n" option will only launch a preview (no backup), you can try to remove it if you want.

 

[baldymike]

Just tried that and the preview seems to work fine but if you then remove the -nvv from the command to run an actual save the following message comes back.... "Unable to receive"

 

[sdeb]

Wich version of Networker are you using, it seems that it is a known bug in version 6.1 (corrected by 6.1.1 and earlier versions).

For info :

====================================================
Title: Nsrd hangs due to RPC errors fixed in NetWorker 6.1
ID: legato5559
Solution:
Known issue. This has been fixed in NetWorker 6.1.1 and NetWorker 6.0.3. For more information please contact Legato Support about LGTpa31430.
====================================================

Check also if the "nsrexecd" daemon is really running on the client.

 

[sdeb]

Sorry ... not earlier ... later !

 

[Serbtastic]

Try launching the nsrexecd daemon on the client machine with the -i switch, and then retry the backup.

 

[NDSman]

Guys

I have had this issue and thought that if name resolution worked then that was all I needed. In fact you need to check the reverse lookups. When the server recieves a data packet from the client it does a reverse lookup on the IP to see if it matches the clients name???

See if the server can reverse lookup the cliebts IP.

 

[baldymike]

Thanks for all your replies. We have now solved the problem. We were relying on WINS to resolve the UNIX clients hostname but while this is enough for Windows, Legato appears to check the "hosts" file on the server. So adding the client to the server hosts file has solved the issue.

Thanks to all.