UNSOLVED

changalrai

updated

16 years ago

C

changalrai

1 Rookie

•

100 Posts

0

3366

July 16th, 2010 19:00

Cannot access nsr server `abc.com`

Hi all,

this was the error message i got,

i did some trouble shooting steps but no luck,

1. ping from both server and client successful

2. nslookup forward and reverslookup & nsrports from server to client from client storage nodes and vise versa,

3. i deleted nsr temp files and restarted nsr services.from client side,

4. i deleted nsr/res/nsrla.res file and restarted services. from client side

5. i updated server file in client end all server alieas names.

5. i updated 7.4.2 client version.

6. server version 7.4.2 sever verion.

but no luck, still its failing for the same error.

and also i checked probe test, its failed.network

from client end error.

C:\>save -s backupservername c:\drive
Warning: Could not determine job id: Cannot create jobs message channel.. Contin
uing ...
save: using `C:\drive for `c:\drive'
NSR server : RPC receive operation failed.  A network connection could
not be established with the host.
save: waiting 30 seconds then retrying
NSR server : RPC receive operation failed.  A network connection could
not be established with the host.
save: waiting 37 seconds then retrying
NSR server : RPC receive operation failed.  A network connection could
not be established with the host.
save: waiting 44 seconds then retrying

from server end error.

2 retries attempted
savefs: SYSTEM error: Name resolution failed for the host with IP address: <10.1.1.5>
savefs: Cannot access nsr server ` .com'
savefs : failed.

  • changalrai

    1 Rookie

    •

    100 Posts

    562

    0

    Posted July 16th, 2010 20:00

    sorry,

    networker server version : 7.4.5 Buld 726 enterprise edition.

  • dugans1

    2 Intern

    •

    186 Posts

    562

    0

    Posted July 18th, 2010 16:00

    Have you tried disabling any active firewalls on the client?

    All i can think is maybe there is a port blockage on the client stopping the coms ports 7937-9936

    Also try disabling virus for the test.

  • Daniea3

    123 Posts

    562

    0

    Posted July 19th, 2010 03:00

    Hi,

       Does this client or server has multiple NIC? If Networker server has multiple NIC, specify the NetWorker server backup NIC in the "Server network interface" field.

    Regards,

    Arun

  • R_Friberg

    34 Posts

    562

    0

    Posted July 19th, 2010 12:00

    Hi,

    I have never seen NetWorker report a name resolution failure if there wasn't a problem with it. So check again, and you can always try using the hosts-files to see if that resolves your issue.

    Regards

    Rickard