4 Operator

 • 

1.3K Posts

November 26th, 2014 22:00

Hi Ahmed,

    Have seen this do it more than often. You will have to create the temp client instance manually using the nsradmin command with the NetWorker services down. Or you could put the old name back, create the client instance for the temp name and do the renaming of the server again. I assume you would choose the first option easier i.e. creating the temp client instance using nsradmin, here are the steps.

- assuming you are on windws - nsradmin -d path_where_networker_is_installed/nsr/res/nsrdb

- create type: nsr client; name: new_temp_name; aliases: new_temp_name.domain.com

- yes

- quit

- start the services.

13 Posts

November 26th, 2014 23:00

Thanks a lot. It works for this step and the Networker Backup and Recover service is now up, but i cannot access the NMC and i get the error:

Problem contacting server new_temp_name.domain.com: Connection reset.

What could be the reason for that?

4 Operator

 • 

1.3K Posts

November 27th, 2014 00:00

Is you NMC installed on a separate machine ? If yes, update the hosts file on the NMC server.

13 Posts

November 27th, 2014 00:00

No it's installed on the same machine

4 Operator

 • 

1.3K Posts

November 27th, 2014 02:00

Not entirely sure, but you might have to re-install the NMC after the rename is done.

2.4K Posts

November 27th, 2014 03:00

Before your reinstall NMC may I suggest that you first try to connect via "http://localhost:9000".

13 Posts

December 4th, 2014 00:00

I found the solution for the NMC. you must run the command gstconfig from the NMC installation path and the hostname for the NMC will be updated. without that even if you connect with http://localhost:9000 it will not work.

Thanks all for the support

1 Message

February 27th, 2015 09:00

Thanks for posting your solution Ahmed. I too was unable to connect to the NMC until I ran the 'gstconfig' command from C:\Program Files\EMC Networker\Management\GST\bin.

1 Message

October 16th, 2017 12:00

t

y

No Events found!

Top