10 More Discussions You Might Find Interesting
1. AIX
Hello,
I was trying to find information about below rpcbind issue and how can I fix it so that, it wont happen again.
Below is the one of the vulnerability from my security team,
RPC
service name: portmapper
service protocal: udp
Portmapper found at: 327xx
service port: 327xx
... (2 Replies)
Discussion started by: system.engineer
2 Replies
2. AIX
Hi,
I am trying to implement a service on AIX based on ONCRPC protocal and I want to use a RPC library called oncrpc4j because it is a non-blocked i/o library. I found it works fine on my work machine (WIndows 7) but failed on my AIX work station. The author of oncrpc4j told me that check that... (1 Reply)
Discussion started by: derekhsu
1 Replies
3. Solaris
Hello all,
I have read just about every rpcbind not starting thread and article on the internet it seems, but I have not found a solution to my problem as of yet. I have a solaris 10 server that has been running with no problems for a while. The other day it crashed and would not boot to the gui... (2 Replies)
Discussion started by: Madrox72
2 Replies
4. Ubuntu
Hi I am trying to configure NIS client on my Ubuntu 12.04.
But I could not put portmap without uninstalling rpcbind.
Do I need to have rpcbind there on the server, or how can I have both portmap and rpcbind at same time there on the server, because it's having conflict. (1 Reply)
Discussion started by: nixhead
1 Replies
5. Linux
Hi guys,
i explain my problem:
I've FC10 64bit installed on a server Dell R410.
When i boot the system with eth0 or eth1 linked (only one eth linked), all work fine and the system start normally.
When i boot the system with eth0 + eth1 linked,
the system hang when the rpcind service... (1 Reply)
Discussion started by: andreaden
1 Replies
6. Solaris
Hello experts..
What is the meaning of " RPC : rpcbind failure" in NFS ? What would be the reason for that? How can i resolve that issue?
give me all aspects (all views)..
Thanks in advance... (1 Reply)
Discussion started by: younus_syed
1 Replies
7. UNIX for Dummies Questions & Answers
I'm just going to throw this out there because I have no clue what is causing this problem or how to fix it. selinux is not enabled nor is any sort of firewall. (To my knowledge -- I did a kickstart install with firewall --disabled )
# rpcinfo
program version netid address ... (1 Reply)
Discussion started by: Colton
1 Replies
8. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
9. AIX
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (2 Replies)
Discussion started by: mcastill66
2 Replies
10. UNIX for Advanced & Expert Users
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies
RPCBIND(8) BSD System Manager's Manual RPCBIND(8)
NAME
rpcbind -- universal addresses to RPC program number mapper
SYNOPSIS
rpcbind [-adhiLls]
DESCRIPTION
The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to
make RPC calls on a server on that machine.
When an RPC service is started, it tells rpcbind the address at which it is listening, and the RPC program numbers it is prepared to serve.
When a client wishes to make an RPC call to a given program number, it first contacts rpcbind on the server machine to determine the address
where RPC requests should be sent.
The rpcbind utility should be started before any other RPC service. Normally, standard RPC servers are started by port monitors, so rpcbind
must be started before port monitors are invoked.
When rpcbind is started, it checks that certain name-to-address translation-calls function correctly. If they fail, the network configura-
tion databases may be corrupt. Since RPC services cannot function correctly in this situation, rpcbind reports the condition and terminates.
The rpcbind utility can only be started by the super-user.
OPTIONS
-a When debugging (-d), do an abort on errors.
-d Run in debug mode. In this mode, rpcbind will not fork when it starts, will print additional information during operation, and will
abort on certain errors if -a is also specified. With this option, the name-to-address translation consistency checks are shown in
detail.
-f Do not fork and become a background process.
-h Specify specific IP addresses to bind to for UDP requests. This option may be specified multiple times and is typically necessary
when running on a multi-homed host. If no -h option is specified, rpcbind will bind to INADDR_ANY, which could lead to problems on a
multi-homed host due to rpcbind returning a UDP packet from a different IP address than it was sent to. Note that when specifying IP
addresses with -h, rpcbind will automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list.
-i ``Insecure'' mode. Allow calls to SET and UNSET from any host. Normally rpcbind accepts these requests only from the loopback
interface for security reasons. This change is necessary for programs that were compiled with earlier versions of the rpc library
and do not make those requests using the loopback interface.
-l Turn on libwrap connection logging.
-s Cause rpcbind to change to the user daemon as soon as possible. This causes rpcbind to use non-privileged ports for outgoing connec-
tions, preventing non-privileged clients from using rpcbind to connect to services from a privileged port.
-w Cause rpcbind to do a "warm start" by read a state file when rpcbind starts up. The state file is created when rpcbind terminates.
NOTES
All RPC servers must be restarted if rpcbind is restarted.
SEE ALSO
rpcinfo(8)
LINUX PORT
BSD
September 14, 1992 BSD