[TriLUG] NFS on Fedora 13: how to register NFS with RPC?
Tim Jowers
timjowers at gmail.com
Sat Dec 18 18:15:54 EST 2010
Thanks everyone. yum upgrade fixed it. (;-)
Merry Christmas to all,
TimJowers
On Sat, Dec 18, 2010 at 10:04 AM, Matt Pusateri
<mpusateri at wickedtrails.com> wrote:
> Is portmap running as well?
>
>
> Matt P.
>
> On Dec 18, 2010, at 9:05 AM, Tim Jowers wrote:
>
>> Anyone set up NFS on Fedora 13? I get:
>>
>> [tim at monsterfc ~]$ showmount -e 192.168.2.101
>> clnt_create: RPC: Program not registered
>>
>> The above is on the computer where I am setting up NFS server. I get
>> this message also when I run showmount on a Ubuntu system on the same
>> LAN; so, I'm guess I don't have NFS configured properly.
>>
>> Any ideas?
>>
>> Thanks,
>> TimJowers
>>
>> Ref:
>> [tim at monsterfc ~]$ showmount -e 192.168.2.101
>> clnt_create: RPC: Program not registered
>> [tim at monsterfc ~]$ ifconfig
>> eth1 Link encap:Ethernet HWaddr 00:16:76:7F:AA:44
>> inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0
>> inet6 addr: fe80::216:76ff:fe7f:aa44/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:1141712 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:1002594 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:850364455 (810.9 MiB) TX bytes:183270319 (174.7 MiB)
>> Interrupt:21 Base address:0x6000
>>
>> lo Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> inet6 addr: ::1/128 Scope:Host
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:31802 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:31802 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:2418353 (2.3 MiB) TX bytes:2418353 (2.3 MiB)
>>
>> [tim at monsterfc ~]$ service nfs status
>> rpc.svcgssd is stopped
>> rpc.mountd (pid 1475) is running...
>> nfsd (pid 1472 1471 1470 1469 1468 1467 1466 1465) is running...
>> rpc.rquotad (pid 1460) is running...
>>
>> [tim at monsterfc ~]$ sestatus
>> SELinux status: disabled
>>
>> [tim at monsterfc ~]$ service iptables status
>> /etc/init.d/iptables: line 53: /etc/sysconfig/iptables-config: Permission denied
>>
>> [tim at monsterfc ~]$ su
>> Password:
>> [root at monsterfc tim]# service iptables status
>> Table: filter
>> Chain INPUT (policy ACCEPT)
>> num target prot opt source destination
>>
>> Chain FORWARD (policy ACCEPT)
>> num target prot opt source destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> num target prot opt source destination
>>
>> [tim at monsterfc ~]$ cat /etc/exports
>> /home 192.168.0.0/32(ro,root_squash,insecure)
>> /home/tim 192.168.100.0/32(rw,sync,no_root_squash)
>> /home/NFS-share */26(rw,sync)
>>
>> [tim at monsterfc ~]$ cat /etc/hosts.deny
>> #
>> # hosts.deny This file contains access rules which are used to
>> # deny connections to network services that either use
>> # the tcp_wrappers library or that have been
>> # started through a tcp_wrappers-enabled xinetd.
>> #
>> # The rules in this file can also be set up in
>> # /etc/hosts.allow with a 'deny' option instead.
>> #
>> # See 'man 5 hosts_options' and 'man 5 hosts_access'
>> # for information on rule syntax.
>> # See 'man tcpd' for information on tcp_wrappers
>> #
>> [tim at monsterfc ~]$ cat /etc/hosts.allow
>> #
>> # hosts.allow This file contains access rules which are used to
>> # allow or deny connections to network services that
>> # either use the tcp_wrappers library or that have been
>> # started through a tcp_wrappers-enabled xinetd.
>> #
>> # See 'man 5 hosts_options' and 'man 5 hosts_access'
>> # for information on rule syntax.
>> # See 'man tcpd' for information on tcp_wrappers
>> #
>> --
>> This message was sent to: M. Pusateri <mpusateri at wickedtrails.com>
>> To unsubscribe, send a blank message to trilug-leave at trilug.org from that address.
>> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
>> Unsubscribe or edit options on the web : http://www.trilug.org/mailman/options/trilug/mpusateri%40wickedtrails.com
>> TriLUG FAQ : http://www.trilug.org/wiki/Frequently_Asked_Questions
>
> --
> This message was sent to: timjowers <timjowers at gmail.com>
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that address.
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web : http://www.trilug.org/mailman/options/trilug/timjowers%40gmail.com
> TriLUG FAQ : http://www.trilug.org/wiki/Frequently_Asked_Questions
>
More information about the TriLUG
mailing list