08-27-2002
clnttcp_create: RPC program not registered
s/o=SCO 5.05 openserver
hi, i have a problem with a mount between 2 servers
i can see the mounted files, but i canīt open it if the file is a *.dbf,
if i try to a "dbf" file with fox for unix the error is (the system has reached the maximum number of blocks)
mount -f NFS server:/example1 /example2
message error= RPC not registered, server not respondig------ iīm not sure whatīs that mean
thanks for any help
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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..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
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
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
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
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
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
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
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
nfs(7) Miscellaneous Information Manual nfs(7)
NAME
nfs, NFS - network file system
DESCRIPTION
The Network File System (NFS) allows a client node to perform transparent file access over the network. By using NFS, a client node oper-
ates on files residing on a variety of servers and server architectures, and across a variety of operating systems. File access calls on
the client (such as read requests) are converted to NFS protocol requests and sent to the server system over the network. The server
receives the request, performs the actual file system operation, and sends a response back to the client.
NFS operates in a stateless manner using remote procedure calls (RPC) built on top of an external data representation (XDR) protocol. The
RPC protocol enables version and authentication parameters to be exchanged for security over the network.
A server grants access to a specific file system to clients by adding an entry for that file system to the server's file.
A client gains access to that file system using the command to request a file handle for the file system (see mount(1M)). (A file handle
is the means by which NFS identifies remote files.) Once a client mounts the file system, the server issues a file handle to the client
for each file (or directory) the client accesses. If the file is removed on the server side, the file handle becomes stale (dissociated
with a known file), and the server returns an error with set to
A server can also be a client with respect to file systems it has mounted over the network; however, its clients cannot directly access
those file systems. If a client attempts to mount a file system for which the server is an NFS client, the server returns with set to The
client must mount the file system directly from the server on which the file system resides.
The user ID and group ID mappings must be the same between client and server. However, the server maps UID 0 (the superuser) to UID -2
before performing access checks for a client. This process prevents gaining superuser privileges on remote file systems.
RETURN VALUE
Generally, physical disk I/O errors detected at the server are returned to the client for action. If the server is down or inaccessible,
the client receives the message:
where is the hostname of the NFS server. The client continues resending the request until it receives an acknowledgement from the server.
Therefore, the server can crash or power down, and come back up without any special action required by the client. The client process
requesting the I/O will block, but remains sensitive to signals (unless mounted with the option) until the server recovers. However, if
mounted with the option, the client process returns an error instead of waiting indefinitely.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
exportfs(1M), share(1M), mount(1M), mount_nfs(1M), nfsd(1M), mount(2), fstab(4), dfstab(4).
nfs(7)