If you are running recover from the client it could happen that client is trying to connect to itself... try from command prompt:
recover -s

If that fails, check daemon.log on backup server (and client) if you get any errors at that time.

Another thing to try after is
recover -s -c

Make sure that aliases are set for each NIC (plus usual ping and rpcinfo tests are working).

Above commands should give you some idea why is this failing. If they both fail start sniffer or netstat on backup server to see if client is connecting at all at the server. It could be that for some reason network route is going in some strange direction (I doubt as you would see probably other problems then with backup as well).

I too think you either have the system trying to run as its own server then you start recover....

Have you tried editing the "Networker User" menu option to have the Networker Server Hardcoded to ensure it starts correctly.

Right click "Networker User" in the menu, select Properties..... the place the "-s server" after the command outside the Quotes....

"C:\Program Files\Legato\nsr\bin\winworkr.exe" -s

e.g
"C:\Program Files\Legato\nsr\bin\winworkr.exe" -s nsrsvr1

SUCCESS!!! Thank you BOTH for the posts. I did a little of each. I hardcoded the name of my backupserver with the -s in the properties part which made it faster. When I did the recover -s I found my problem. Turns out these five servers need to use domain lableing. For example, I have one called chmdc1. It's on a lan so the alias had to read the lan name (chmdc1.xxx.xxx) and after I did that everything worked just fine!! Thanks so much again.