08-16-2012
This got resolved by editing "/etc/security/access.conf" ( by giving access to all the users)......I am not sure if this is the correct solution (or) is it a workaround.
10 More Discussions You Might Find Interesting
1. Solaris
Hi....I just changed the hostnname on some of my servers.., changing the NIS master hostname first...
I was able to bring the NIS master back up but when I tried to si - to a different group of users, I got the following error message:
RPC failure on yp operation
Anyone knows what else I... (1 Reply)
Discussion started by: Remi
1 Replies
2. AIX
We have windows clients that access drawing files shared from our AIX server using NFS. The Windows clients are intermittently unable to open files or access the system. For some reason restarting the rpc.lockd temporarily resolves the problem. However, that is the only clue I have to what the... (1 Reply)
Discussion started by: theologic
1 Replies
3. UNIX for Dummies Questions & Answers
getting "NFS mount: netapp : RPC: Program not registered" error
searched the site but none of the fixes from previous threads are helping (2 Replies)
Discussion started by: calamine
2 Replies
4. Solaris
I have been told to disable the rpc processes such as rstat and rusers on some servers for security concerns, what if I am running NFS on those servers. Would it affect the NFS since both rstat and rusers are nfs daemons??
I MUST have the NFS running on the server. Can I disable rstat and rusers... (2 Replies)
Discussion started by: mitsurughi
2 Replies
5. Solaris
Hello!
I have a Linux nfs server (called server100 below) with a export nfs. My problem is that the Solaris client (called client100 below) doesn't seems to like it. In the Solaris syslog I got following messages (and after a while the solaris client behave liked its hanged/to buzy). Also see... (3 Replies)
Discussion started by: sap4ever
3 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. Solaris
while i trying to mount from NAS i have this messages
mount -F nfs -o rw 172.16.110.13:/tremabkup /tremabkup
nfs mount: 172.16.110.13: : RPC: Rpcbind failure - RPC: Timed out
nfs mount: retrying: /tremabkup
nfs mount: 172.16.110.13: : RPC: Rpcbind failure - RPC: Timed out
nfs mount:... (2 Replies)
Discussion started by: thecobra151
2 Replies
8. Solaris
Hello I am having an issue with a server SUN FIRE T2000 (Solaris 10).
First of all the server didn't boot normaly so I did a full restoration of the file systems.
Now the server boot, most of the services are available (not all the services), but I keep on seeing
RPC: Rpcbind failure -... (4 Replies)
Discussion started by: feg
4 Replies
9. Solaris
C: Rpcbind failure - RPC: Timed out error (solaris)
hello an nfs server on my sun fire v440 is not responding , i get the error bellow and lots of my networking services are not reponding, please helppppp its an emergency
RPC: Rpcbind failure - RPC: Timed out
i also get
NFS server... (2 Replies)
Discussion started by: feg
2 Replies
10. Red Hat
Hello,
I was having few issues on my linux box, I am getting this error whenever I tried to mount a share on a client linux host.
# mount -t nfs 10.10.4.150:/data/pops_sva /mnt
mount: mount to NFS server '10.10.4.150' failed: RPC Error: Program not registered.
#
I see the error and I... (4 Replies)
Discussion started by: bobby320
4 Replies
LEARN ABOUT REDHAT
ypserv.conf
YPSERV.CONF(5) Reference Manual YPSERV.CONF(5)
NAME
ypserv.conf - configuration file for ypserv and rpc.ypxfrd
DESCRIPTION
ypserv.conf is an ASCII file which contains some options for ypserv. It also contains a list of rules for special host and map access for
ypserv and rpc.ypxfrd. This file will be read by ypserv and rpc.ypxfrd at startup, or when receiving a SIGHUP signal.
There is one entry per line. If the line is a option line, the format is:
option: <argument>
The line for an access rule has the format:
host:domain:map:security
All rules are tried one by one. If no match is found, access to a map is allowed.
Following options exist:
files: 30
This option specifies, how many database files should be cached by ypserv. If 0 is specified, caching is disabled. Decreasing this
number is only possible, if ypserv is restarted.
trusted_master: server
If this option is set on a slave server, new maps from the host server will be accepted as master. The default is, that no trusted
master is set and new maps will not be accepted.
Example:
trusted_master: ypmaster.example.org
xfr_check_port: [<yes>|no]
With this option enabled, the NIS master server have to run on a port < 1024. The default is "yes" (enabled).
The field descriptions for the access rule lines are:
host IP address. Wildcards are allowed.
Examples:
131.234. = 131.234.0.0/255.255.0.0
131.234.214.0/255.255.254.0
domain specifies the domain, for which this rule should be applied. An asterix as wildcard is allowed.
map name of the map, or asterisk for all maps.
security
one of none, port, deny:
none always allow access.
port allow access if from port < 1024. Otherwise do not allow access.
deny deny access to this map.
FILES
/etc/ypserv.conf
SEE ALSO
ypserv(8), rpc.ypxfrd(8)
WARNINGS
The access rules for special maps are no real improvement in security, but they make the life a little bit harder for a potential hacker.
BUGS
Solaris clients don't use privileged ports. All security options which depend on privileged ports cause big problems on Solaris clients.
AUTHOR
Thorsten Kukuk <kukuk@suse.de>
YP Server October 2002 YPSERV.CONF(5)