Unsolved

This post is more than 5 years old

1 Rookie

 • 

27 Posts

2085

June 4th, 2012 18:00

Unable to connect to server Networker 7.4sp5

We have an admin that is trying to Clone some saved sets for off-site storage.

When she selects the "source saved sets to clone" - she gets the "Error" Unable to connect to server

The Target Clone Media Pool is selected.

Any thoughts on where to start or suggestions?

Please advise.

Thanks.

-John

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

June 5th, 2012 05:00

I doubt he will get more meaningful messages from the GUI. Let the admin use CLI and see what additional error messages can be obtained (including daemon log).

544 Posts

June 10th, 2012 00:00

Hi John,

Hard to say without more info as mentioned by Crvelin, But my first reaction at that time will to check the communication between the client and backup server.

Try to do the following from the backup server to the networker client ( using short name and FQDN name):

  • check hosts-file if you can find the client
  • ping
  • nslookup
  • rpcinfo -p

   If this all works, try to do the following from the client to the backup server ( using short name and FQDN name): 

  • check hosts-file if you can find the backup server
  • check server file under the nsr directory if the backup server is added there
  • ping
  • nslookup
  • rpcinfo -p

Make sure that all these tests has been checked using the shotrname and the FQDN name. Also make sure that the firewall ports ( if exits ) are opened.

These checks should give you a clue if it is connectivity or communication issue. Otherwise please try the cloning via command prompt in verbose mode which may gives you more information and messages.

Hope this helps you. Waiting your updates.

Thanks,

Ahmed Bahaa

1 Rookie

 • 

27 Posts

June 13th, 2012 10:00

Thanks for getting back to me.

They backup server is where the Networker Backup software is installed.

I was able to get the rpcinfo - that was it - is it the daemon.raw file that you are looking for -  it does have a FW on - but this has been working - not sure what else to try.

Where am I gonig to find the other files?

This is the same from both the fqdn and host name

program vers proto   port

    100000    2   tcp   7938

    100000    2   udp   7938

    390436    1   tcp   8762

    390435    1   tcp   9204

    390113    1   tcp   7937

    390402    1   tcp   9001

    390115    1   tcp   9722

    390103    2   tcp   9421

    390109    2   tcp   9421

    390110    1   tcp   9421

    390120    1   tcp   9421

    390109    2   udp   9434

    390105    5   tcp   8653

    390105    6   tcp   8653

    390107    5   tcp   8880

    390107    6   tcp   8880

    390433    1   tcp   8922

    390104  105   tcp   9776

    390104  205   tcp   8802

    390104  305   tcp   9868

    390104  405   tcp   8697

    390430    1   tcp   8352

    390429  101   tcp   8468

    390104  505   tcp   8515

    390104  605   tcp   9562

    390104  705   tcp   9129

    390104  805   tcp   8588

    390104  905   tcp   8430

   program vers proto   port

    390104  905   tcp   8430

    390104  805   tcp   8588

    390104  705   tcp   9129

    390104  605   tcp   9562

    390104  505   tcp   8515

    390429  101   tcp   8468

    390430    1   tcp   8352

    390104  405   tcp   8697

    390104  305   tcp   9868

    390104  205   tcp   8802

    390104  105   tcp   9776

    390433    1   tcp   8922

    390107    6   tcp   8880

    390107    5   tcp   8880

      4397    1   tcp    603

      4397    1   udp    601

    390105    6   tcp   8653

    390105    5   tcp   8653

    390109    2   udp   9434

    390120    1   tcp   9421

    390110    1   tcp   9421

    390109    2   tcp   9421

    390103    2   tcp   9421

    390115    1   tcp   9722

Why does it work sometimes and not others?

Thanks.

John

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

June 14th, 2012 06:00

It is possible that fw is blocking whole range used NW so this sometimes works and some other times it does not. NW can be fully automated including cloning jobs so if backup admins are doing clones on regular basis they should schedule it which won't address original issue, but you won't get there as you do now.

No Events found!

Top