Sponsored Content
Top Forums UNIX for Advanced & Expert Users clnttcp_create: RPC program not registered Post 27080 by RTM on Tuesday 27th of August 2002 03:50:17 PM
Old 08-27-2002
Normally the error "RPC not registered" means the nfs daemons needed are not running on the NFS server (nfsd and mountd on a SUN NFS server).

This link to exporting filesystems on SCO may help.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

"rpc program not registered"??

Hello all, When I shut down my X86/Solaris 8, I get the following messages on the console: "rpc program not registered "...... What is mean?why?May someone can tell me :) Thanks in advance. (1 Reply)
Discussion started by: Lee
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Hi..!! I've registered because of problem..

Hi..Guys...!!! I am new on yours site, but i hope you will like me....I`ll very glad to answer on all your question! I am From England Nice day is it today, but I have a question for all...In first , how i post message to PM...???Thank you very much!Mark. G..!! (1 Reply)
Discussion started by: poluroud20
1 Replies

3. UNIX for Dummies Questions & Answers

can not get netapp to mount RPC Not registered error

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

Purpose of RPC program numbers?

Whats the purpose of the following RPC program numbers: 100249 300598 805306368 Why the above program numbers were not listed in /etc/rpc file? Is it dynamically assigned? These program numbers doesnt persist after rebooting the system. If any of the service is using this program number then... (0 Replies)
Discussion started by: ramnagaraj
0 Replies

5. Solaris

RPC: Rpcbind failure - RPC: Timed out

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

6. Solaris

Error : "RPC: Rpcbind failure - RPC: Timed out"

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

7. Solaris

RPC: Rpcbind failure - RPC: Timed out error (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

8. Red Hat

Nfs client mount RPC Error: Program not registered.

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

9. Solaris

nfs mount: RPC: Rpcbind failure - RPC: Timed out

Fails to mount the server (10.125.224.22) during installation of a software on client, throwing the below error: nfs mount: 10.125.224.22: : RPC: Rpcbind failure - RPC: Timed out nfs mount: retrying: /cdrom This happened after complete shutdown of the lab. The server came up fine but most... (1 Reply)
Discussion started by: frintocf
1 Replies
mountd(1M)																mountd(1M)

NAME
mountd - server for NFS mount requests and NFS access checks SYNOPSIS
/usr/lib/nfs/mountd [-v] [-r] mountd is an RPC server that answers requests for NFS access information and file system mount requests. It reads the file /etc/dfs/sharetab to determine which file systems are available for mounting by which remote machines. See sharetab(4). nfsd running on the local server will contact mountd the first time an NFS client tries to access the file system to determine whether the client should get read-write, read-only, or no access. This access can be dependent on the security mode used in the remoted procedure call from the client. See share_nfs(1M). The command also provides information as to what file systems are mounted by which clients. This information can be printed using the show- mount(1M) command. The mountd daemon is automatically invoked by share(1M). Only super user can run the mountd daemon. The options shown below are supported for NVSv2/v3 clients. They are not supported for Solaris NFSv4 clients. -r Reject mount requests from clients. Clients that have file systems mounted will not be affected. -v Run the command in verbose mode. Each time mountd determines what access a client should get, it will log the result to the con- sole, as well as how it got that result. /etc/dfs/sharetab shared file system table See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfssu | +-----------------------------+-----------------------------+ nfsd(1M), share(1M), share_nfs(1M), showmount(1M), nfs(4), sharetab(4), attributes(5) Since mountd must be running for nfsd to function properly, mountd is automatically started by the svc:/network/nfs/server service. See nfs(4). Some routines that compare hostnames use case-sensitive string comparisons; some do not. If an incoming request fails, verify that the case of the hostname in the file to be parsed matches the case of the hostname called for, and attempt the request again. 27 Apr 2005 mountd(1M)
All times are GMT -4. The time now is 08:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy