UNSOLVED

dhill1

updated

20 years ago

D

dhill1

1 Rookie

•

14 Posts

0

4037

November 28th, 2006 01:00

Client cannot connect to Networker server

Hi,

We have installed the 7.3.2 update to our NetWorker server, since this update the clients are not able to see the server when opening NetWorker user, the following message appears:

No NetWorker servers can be found.

The networker server has not changed its hostname or IP address and is within the servers file on the clients trying to connect to it, the networker server is also present in the clients hosts file.

Have a missed something here?

I look forward to your assistance.

Rgrds

Darren.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1672

    0

    Posted November 28th, 2006 03:00

    Let's try with some basic things: if you go to cmd line on client and do recover -s can you connect and browse server? If not upgrade client too to 7.3.2 and try same.
  • Jodi-2015

    17 Posts

    1672

    0

    Posted November 28th, 2006 04:00

    It sounds like you're using a Windows client. Go to start, run and enter winworkr -s name_of_networker_server. This should open the Networker User window.
  • dhill1

    1 Rookie

    •

    14 Posts

    1672

    0

    Posted November 28th, 2006 08:00

    This worked but for future reference why did it not work originally?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1682

    0

    Posted November 28th, 2006 08:00

    Originally perhaps your old link in shortcut had -s added - something ppl used to do in past. Not sure about your servers file, but some versions (no idea what) check servers file and go against server listed inside.
  • dhill1

    1 Rookie

    •

    14 Posts

    1682

    0

    Posted November 28th, 2006 08:00

    OK thanks very much for your help.
  • glhooper

    15 Posts

    324

    0

    Posted April 18th, 2007 14:00

    Reading about it now in the admin guide. Thanks for pointing me in the right direction.
  • glhooper

    15 Posts

    324

    0

    Posted April 18th, 2007 14:00

    Networker version 7.3.2 jumbo build 386
    Client version is the same version
    All Windows 2003 Sp1

    EMC installed this with very little in the way of training and I have not been to class yet, so I am a noob on this product. I don't see nsrauth in the command reference guide, so not sure how to enable. thanks for your help
  • glhooper

    15 Posts

    1682

    0

    Posted April 18th, 2007 14:00

    yep. I didn't want to give out my company's host server name so I edited that.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1682

    0

    Posted April 18th, 2007 14:00

    Judging by error you are on 7.3.x. Do you have nsrauth enabled on server (and storage nodes)?
  • glhooper

    15 Posts

    1682

    0

    Posted April 18th, 2007 14:00

    I am getting this same error on only one client. All other clients work fine. Here is the output from recover -s

    Warning: could not establish job id with jobd. Continuing on.
    Invalid argument
    Cannot create jobs message channel.
    recover: Cannot start session with server : RPC receive operation failed. A network connection could not be established with the host.

    Yet I can ping the host server just fine and the host server has a newly registered local host for this client. When I click on the client entry under Local Hosts in the NMC, I get this:

    Program not registered

    I have available client licenses for this client, so I don't think it is a licensing issue. Would appreciate any tips. Thanks