Clients can't connect to Backup Server

[Mouktar]

Hello All;

We had one backup server on Win2K, and backup clients. We decomission it, and bring another server (Win2K3) and configure it as our backup server, with new license activations, and start it all over again.
Clients were modified again by reinstalling the application via the add/remove program and specified the new servername.

The group backups are working fine, and we can nightly backup clients from the server side.

But when we try to restore or backup something from the client side and open the network user program, it fails and states "no network server is found" and closes the program.

Any ideas what is preventing the client from seeing the server?

It is not a Host Name for sure.

Thanks in advance...

 

[Rexxy]

has the networker server name changed ? if so, then its most likely just the servers file on the clients that needs to be updated to reflect the new nsr server system name.

bring up the dos prompt and run the following
c:\> recover -s nsrservername

does this work ??

if this is also failing, are there any firewalls between the new nsr server and the clients ?

 

[Novelli]

Hi,

look at the .../res directory of the client on each hoist for the file servers and add the new servername inside

Cheers Novelli
Novell Master CNE + CDE

http://www.eckertweb.de

 

[Mouktar]

All ../res files have the correct server name, and everything else looks good. The server can obviously connect to clients and back them up, but it is just that networker user program can't find the backup server, and terminates.

I finally get a way around this by editing the registry under the current user\softwre\legato, and add the server name there, which was blank.

It works now, and the networker user program connects to it successfully.

Thanks all.

 

[Rexxy]

but networker user etc all use the /nsr/res/servers file, if there is more than one system listed you will also get this issue.

 

[605]

Forget about the servers file for a while and follo Rexxy's instructions.

If the servername does not work, try "-s ip_address".

 

[Mouktar]

The servers file only contains the correct backup server, and still was not working until I modified the registry.

This recover -s nsrservername also works fine, but the networker user program still fails to open and connect to the server.

 

[new2me]

I didn't read everyone's comment... so from your client side in the cmd prompt enter each and what happen?

winworkr -s bkup_server_name

winworkr -s bkup_server_ip


client side hosts file what is the bkup_server_name & IP...

 

[605]

If the name can be resolved, both commands are equal.

If you use hosts files, the must point to the same info, of course.