rpcinfo: can't contact portmapper 1

[TekMan01]

Hello fellow legato:

I have question about usage of rpcinfo command, that I suddendly not able to get rpcinfo from my clients where I usually can without any errors. Here is the message from rpcinfo:

can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecified error)

I have reboot the backup server many times but, whenever I try to use rpcinfo I still get the same error.

Have anyone ever encounter this problem?

Many thanks for your helpful hints....

 

[605]

At least it would help if you state the OS and the NW version.

 

[TekMan01]

SunOS: Solaris 8
NW: 6.1.3

 

[605]

Most likely the nsrd daemons start too early (before
nsrexecd did fully 'initialize'). To prove this, please
proceed as follows:
- stop all NW daemons
- start nsrexecd from the command line
- wait about 30 seconds
- then start nsrd

If this will cure your problem, you should modify your file
etc/rc2.d/S95networker by adding the command "/usr/bin/sleep 30"
after nsrexecd has been started.

 

[TekMan01]

I have tried your recommendation, but I still get the same error.

 

[605]

Strange. Have a look at /var/adm/messages and see whether the
OS has noted a problem.

 

[wallace88]

On the server, run rpcinfo -p (backup server). Does this work? This will tell you if the portmapper on the server is active. What's the output?

Similarily go to a client and run:

rpcinfo -p (client name)
rpcinfo -p (server name)

Which one works? Test this on various clients.

Has there been any changes just prior to the start of this problem? Is there a firewall between your backup server and clients, and if so, has it allowed enough ports opened for NetWorker operations?

 

[TekMan01]

To 605:

I have checked /var/adm and look into and found nothing relate to this cause. Is there any particular file you would suggest me to take a look at? I have look at messages file

To wallace88:

I have tried your suggestion, and here is what I have found...

rpcinfo to itself

# rpcinfo -p [Backup server]
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100229 1 tcp 32771 metad
100230 1 tcp 32772 metamhd
390113 1 tcp 7937 nsrexec
390103 2 tcp 9864 nsrd
390109 2 tcp 9864 nsrstat
390110 1 tcp 9864 nsrjb
390103 2 udp 9865 nsrd
390109 2 udp 9865 nsrstat
390110 1 udp 9865 nsrjb
390107 5 tcp 8773 nsrmmdbd
390107 6 tcp 8773 nsrmmdbd
390105 5 tcp 9681 nsrindexd
390105 6 tcp 9681 nsrindexd
390104 105 tcp 8650 nsrmmd
390104 205 tcp 9559 nsrmmd
390104 305 tcp 8467 nsrmmd

rpcinfo to a client the same server

# rpcinfo -p [To backup client from backup server]
program vers proto port service
100000 2 tcp 7938 rpcbind
100000 2 udp 7938 rpcbind
390113 1 tcp 7937 nsrexec


rpcinfo from the same client that the server probed to

C:\>rpcinfo -p [From backup client to backup server]
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390113 1 tcp 7937
390103 2 tcp 9864
390109 2 tcp 9864
390110 1 tcp 9864
390103 2 udp 9865
390109 2 udp 9865
390110 1 udp 9865
390107 5 tcp 8773
390107 6 tcp 8773
390105 5 tcp 9681
390105 6 tcp 9681
390104 105 tcp 8650
390104 205 tcp 9559
390104 305 tcp 8467
rpcinfo: can't contact portmapper: Remote system error - Connection timed out

 

[ravashaak]

I know you reported your OS as being Solaris 8. Is that on the server or on the client(s)?

 

[TekMan01]

OS with Solaris 8 is the NW backup server and the client that getting rpcinfo problem is Windows.

 

[LGTObug]

Hi,

On the client stop the nsrexecd service and start again with the -s option and -D9 for debug mode.

nsrexecd -s <servername> -D9 &

Post the output. Attention, it could get very large

Looks like your Client can't contact the portmapper (Port111) on the Backupserver.

Did you check DNS or Hosts Files?

Run the rpcinfo -p Tests at the client and server with shortname and after this with FQDN (full qualified domain name)

Are there the same results?

 

[ravashaak]

If the client Windows version is XP, are you running ICF (Internet Connection Firewall)? If so (or if running other software client firewalls), try disabling it.

 

[TekMan01]

thank you all for help. I found the problem, which was causing by firewall enabled at our backup server. IP filter script problem.

 

[wallace88]

Didn't I ask you if you had a firewall???