2 Intern

 • 

2K Posts

November 14th, 2006 10:00

Have you tried installing the client from root login and also check of nsrexecd is running on the client.

261 Posts

November 14th, 2006 10:00

Yes. Tried from the root and nsrexecd is running. What is the .rhosts?

261 Posts

November 14th, 2006 13:00

How do I check for RPC communication?? This is my first linux box and i'm totally confused!

4 Operator

 • 

14.4K Posts

November 14th, 2006 13:00

Same way as with Windows - use rpcinfo command:

- rpcinfo -p hostname
- rpcinfo -t hostname 390113 1
- echo print | nsradmin -p 390113 -i - -s hostname

4 Operator

 • 

14.4K Posts

November 14th, 2006 13:00

.rhosts is file which gives (defines) rights to who can execure r* commands (like rsh). Don't touch that or your UNIX admin will kill you.

Can you check if you have RPC communication from server to client and vice versa? I think problem could be there (some Linux boxes have iptables enabled so communication could be blocked too).

261 Posts

November 15th, 2006 05:00

OK. when I do this:

rpcinfo -p hostname I get a long list of program, version, port ...


when I do this: rpcinfo -t hostname 390113 I get

program 390113 version 1 ready and waiting

194 Posts

November 15th, 2006 05:00

We've had problems with Linux because iptables (Linux firewall) was blocking ports used by NetWroker. This is what we do to test connectivity from both directions when we set up a new client.

On the NetWorker server (this is for Unix):Run nwadmin, select 'Options' -> 'Configure Ports...', and enter the hostname of the client as you did when you defined the client. If it works it'll pop up a window showing the ports used. If it doesn't work you'll get a messages like ''Service not available". It could be the Linux firewall has the ports blocked.

On the Linux client: Run the following command:
# savefs -s -pv
Where is the hostname of your NetWorker server. If it works it'll list the filesystems that'll be backed up.

Vic

261 Posts

November 15th, 2006 06:00

I got into the unix system. When I do these:

- rpcinfo -p hostname
- rpcinfo -t hostname 390113

I get the same error for both: '

rpcinfo: backupserver: n2a: hostname not found

4 Operator

 • 

14.4K Posts

November 15th, 2006 06:00

You did that test from server to client and from client to server, right? What do you get for nsradmin line (from server to client and vice versa)?

261 Posts

November 15th, 2006 06:00

Well I tried going to the networker server and doing the options> configure ports and got this error: 'server loopcare: unable to recieve'. i'll try the unix now

261 Posts

November 15th, 2006 06:00

I haven't tried from the unix system yet; we don't control it they do so I have to wait. I will try here in a bit when they get in. Don't know what you mean when you say 'nsradmin line' though.

261 Posts

November 15th, 2006 06:00

I will give these a try and let you know how it goes

261 Posts

November 15th, 2006 07:00

sorry, still confused. What do you mean by name resolution. After the other things I tried as recommended it seems like the unix box can't see the backupserver

4 Operator

 • 

14.4K Posts

November 15th, 2006 07:00

Name resolution?

261 Posts

November 15th, 2006 08:00

well we got it to work. Turns out that the backupserver host name and IP address needed to be inserted into the host file on the unix box
No Events found!

Top