remote client communication problem

[tdebrabandere]

Hello

I have a NT4 server in a remote site connected with a 256 kbps line to the main site

Legato server 613 was installed and I could manage it successfully with Networker Administrator from my workstation based in the main site

I have changed it to Legato client 613

I tried to take a backup of the remote client from the main site's Legato server 613 but there is a RPC error

Actually when I try to connect to the server from the remote client's Networker Administrator, I get the error "server servername: unable to receive"

If I try to access another Legato server from the remote client's Networker administrator, I get the error "server servername: authentication error"

There is likely a network problem, maybe some tcpip ports are not open, but only in one way as I could remotely manage Legato when the remote computer had Legato server installed

do you confirm my diagnostic ?
is there a command/tool which I can tests the ports with ?
can I change something in Legato to change the communication type ?

any advice is welcome ...

many thanks in advance for your help !

Thierry

 

[605]

I not think that there is a ports problem right now.

"Unable to receive" just means that the correcponding daemon
is not running. In this case it is nsrd, representing the NW
server. However, if it is, restart the NW services on the server.

The authentication errors may come up if your account is not registered
as remote administrator. However NW should clearly state this as well.

 

[tdebrabandere]

thanks 605

the legato server is working fine on site with about 30 local clients
anyway I have rebooted it in order to be sure

I use the same account as usual which is registered on all the legato servers administrators

I also have uninstalled the client, rebooted and reinstalled the client, but the problem persists ...

 

[605]

o.k. - next step to investigate is the name resolution. Worst case use the hosts file.

Also make sure that all variants for that client name (short and
FQDN are listed in the client's Alias list.

 

[tdebrabandere]

dns and wins resolution are working fine in both ways but adding an entry for the client in the server's host file resolved the problem !

thank you so much for your assistance