Hello all,
I need your help. I have installed NFS-server on my Fedora 14.
Server is 192.168.1.101 Client is 192.168.1.100
I have stoped my iptables like this: # su -c 'service iptables stop'
in /etc/exports /home/user/temp 192.168.100/255.255.255.0(ro)
I'm not sure, that I have to write in /etc/hosts.allow and /etc/hosts.deny
From the client side I do:
# sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/
And I have got thos error: mount.nfs: access denied by server while mounting 192.168.1.101: /home/booch/Temp
Please! Help me to resolve that problem! Thank you very much in advance!
On 11/29/2010 2:11 PM, Alan Holt wrote:
Hello all,
I need your help. I have installed NFS-server on my Fedora 14.
Server is 192.168.1.101 Client is 192.168.1.100
I have stoped my iptables like this: # su -c 'service iptables stop'
in /etc/exports /home/user/temp 192.168.100/255.255.255.0 http://255.255.255.0(ro)
Should be: /home/user/temp 192.168.1.0/255.255.255.0(ro)
I'm not sure, that I have to write in /etc/hosts.allow and /etc/hosts.deny From the client side I do: # sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/
And I have got thos error: mount.nfs: access denied by server while mounting 192.168.1.101:/home/booch/Temp
Please! Help me to resolve that problem! Thank you very much in advance!
-- /בברכה, / /אלכס ברבר/ /+9 72 54 285 952 3 / /www.linuxspace.org/ http://www.linuxspace.org /--/ /Best regards./ /Alex Berber/ /+9 72 54 285 952 3/ /www.linuxspace.org/ http://www.linuxspace.org/
On Mon, 2010-11-29 at 23:11 +0200, Alan Holt wrote:
Server is 192.168.1.101 Client is 192.168.1.100
I have stoped my iptables like this: # su -c 'service iptables stop'
in /etc/exports /home/user/temp 192.168.100/255.255.255.0(ro)
Can you see the error in the IP address on the last line? i.e. That "100" is wrong, it ought to be just "1". And I suspect you need to write it more like: /home/user/temp 192.168.1.0/255.255.255.0(ro)
A complete IP address, even though the last quad is virtually a wildcard. You should read the exports man file, particularly these sections.
wildcards Machine names may contain the wildcard characters * and ?. This can be used to make the exports file more compact; for instance, *.cs.foo.edu matches all hosts in the domain cs.foo.edu. As these characters also match the dots in a domain name, the given pattern will also match all hosts within any subdomain of cs.foo.edu.
IP networks You can also export directories to all hosts on an IP (sub-) network simultaneously. This is done by specifying an IP address and netmask pair as address/netmask where the netmask can be specified in dotted-decimal format, or as a contiguous mask length (for example, either ‘/255.255.252.0’ or ‘/22’ appended to the network base address result in identical subnetworks with 10 bits of host). Wildcard characters generally do not work on IP addresses, though they may work by accident when reverse DNS lookups fail.
Alan Holt writes:
in /etc/exports /home/user/temp 192.168.100/255.255.255.0(ro)
I'm not sure, that I have to write in /etc/hosts.allow and /etc/hosts.deny
From the client side I do:
# sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/
And I have got thos error: mount.nfs: access denied by server while mounting 192.168.1.101: /home/booch/Temp
Given that you exported read-only, try mounting read-only:
sudo mount.nfs -r 192.168.1.101:/home/booch/Temp /home/booch/data/
-- Dick St. Peters, stpeters@NetHeaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY
Should be: /home/user/temp 192.168.1.0/255.255.255.0(ro)
http://192.168.1.0/255.255.255.0(ro)I'm sorry, but I can't understand ? If I will do 192.168.1.0/24 ? I will never have success, because I don't have any PC in my network with IP-address 192.168.1.0
My router is 192.168.1.1 My PC (NFS CLIENT) is 192.168.1.100 My laptop (NFS SERVER) is 192.168.1.101
Like this my DHCP giving me my addresses for home network.
So...this is my NFS-server Fedora 14: /home/booch/Temp 192.168.1.101/255.255.255.0(rw,sync,no_subtree_check)
This is my /etc/hosts.allow: portmap: 192.168.1.100/24 lockd: 192.168.1.100/24 rquotad: 192.168.1.100/24 mountd: 192.168.1.100/24 statd: 192.168.1.100/24
This is my /etc/hosts.deny: *empty*
I did restart for all services: /etc/init.d/nfs restart /etc/init.d/nfslock restart /etc/init.d/rpcbind restart
Everything is well done! But still I can't connect from my client computer.
PS: my RPC, I do not see my nfs [root@alexFedoraLinux ~]# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper
but I see the server in process.
[root@alexFedoraLinux ~]# ps -ef | grep nfs root 3660 2 0 00:00 ? 00:00:00 [nfsd4] root 3661 2 0 00:00 ? 00:00:00 [nfsd4_callbacks] root 3662 2 0 00:00 ? 00:00:00 [nfsd] root 3663 2 0 00:00 ? 00:00:00 [nfsd] root 3664 2 0 00:00 ? 00:00:00 [nfsd] root 3665 2 0 00:00 ? 00:00:00 [nfsd] root 3666 2 0 00:00 ? 00:00:00 [nfsd] root 3667 2 0 00:00 ? 00:00:00 [nfsd] root 3668 2 0 00:00 ? 00:00:00 [nfsd] root 3669 2 0 00:00 ? 00:00:00 [nfsd]
I'm going do die...
On Tue, 2010-11-30 at 00:06 +0200, Alan Holt wrote:
I'm sorry, but I can't understand ? If I will do 192.168.1.0/24 ? I will never have success, because I don't have any PC in my network with IP-address 192.168.1.0
In this instance, when you're writing an IP address with that netmask combination, you're saying *ANY* address on that subnet range.
i.e. If you wrote just 192.168.1.12 only that IP would match. But when you wrote 192.168.1.0/255.255.255.0, it means 192.168.1.0 through to 192.168.1.255. Though, practically, it usually means 192.168.1.1 through to 192.168.1.254, since the .0 and .255 ending addresses have their own special uses.
Depending on where you're using IP addresses ending with .0 or .255, you will be describing a whole subnet, rather than specific IPs.
On 11/29/2010 01:11 PM, Alan Holt wrote:
Hello all,
I need your help. I have installed NFS-server on my Fedora 14.
Server is 192.168.1.101 Client is 192.168.1.100
I have stoped my iptables like this: # su -c 'service iptables stop'
in /etc/exports /home/user/temp 192.168.100/255.255.255.0(ro)
Change the IP specified to 192.168.1.0/255.255.255.0. You've specified a completely wrong network for the hosts you list.
I'm not sure, that I have to write in /etc/hosts.allow and /etc/hosts.deny
From the client side I do:
# sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/
And I have got thos error: mount.nfs: access denied by server while mounting 192.168.1.101: /home/booch/Temp
You're also specifying an export that doesn't exist on the server. The mount command should be:
mount 192.168.1.101:/home/user/temp /local/mount/point -o ro
The stuff after the ":" must match the server's export. Also remember that mounts default to read/write while you specified read only in the exports file. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Time: Nature's way of keeping everything from happening at once. - ----------------------------------------------------------------------
I'm really really sorry, it was typing error with ip address. Like I wrote I have next addresses:
My PC (NFS-CLIENT) is 192.168.1.100 My laptop (NFS-SERVER) is 192.168.1.101
in my /etc/exports/ /home/booch/Temp 192.168.1.101/255.255.255.0(rw,sync,no_subtree_check)
where 192.168.1.101 is my NFS-server
I do my connection from the client fo the server like this: root@alexlinux:/home/booch# sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/ -rw mount.nfs: access denied by server while mounting 192.168.1.101: /home/booch/Temp
On both computers (server and client) I have the same structure of dirictories: Client: /home/booch/data Server: /home/booch/Temp
but still it's two different computers
I think that something wrong with RPC, because I do not see NFS here: [root@alexFedoraLinux ~]# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper
On 11/29/2010 02:24 PM, Alan Holt wrote:
I'm really really sorry, it was typing error with ip address. Like I wrote I have next addresses:
My PC (NFS-CLIENT) is 192.168.1.100 My laptop (NFS-SERVER) is 192.168.1.101
in my /etc/exports/ /home/booch/Temp 192.168.1.101/255.255.255.0(rw,sync,no_subtree_check)
where 192.168.1.101 is my NFS-server
I think you're confused here. The server is the machine that has the drive you want other machines to mount over the network. Are you trying to share a drive from your PC to your laptop? If so, then the PC is the server.
The exports file should only exist on the server. It tells the server which clients are allowed to mount that directory. Also, the netmask you have (regardless of which is the server) is incorrect. The last octet should be .255 if you only want to allow the machine that you've named on the line access. If you want the entire network it's on access, then the IP address should be 192.168.1.0 and the netmask set to 255.255.255.0 (allowing 192.168.1.1 through 192.168.1.254 access).
If the PC is trying to share one of its local directories with the laptop, then the PC should have an /etc/exports with the line:
/home/booch/Temp 192.168.1.101/255.255.255.255(rw,sync,no_subtree_check)
(the netmask should end with ".255" if you're trying to only share with ONE machine) and the laptop should:
mount 192.168.1.100:/home/booch/Temp /local/mountpoint -o ro
---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Careful! Ugly strikes 9 out of 10 people! - ----------------------------------------------------------------------
Thank you very much for your help! I'm sorry that I took your time. Everything is well done with my systems, all configs are good, all daemons are working well, except one!!!
I forgot to tell you, that on my NFS-server (Fedora 14) my home directory is encrypted by default. NFS is not able to connect directory that stay on encrypted partion under ext3.
Sorry for my english. Thank you for your help!
On Tue, Nov 30, 2010 at 1:16 AM, Rick Stevens ricks@nerd.com wrote:
On 11/29/2010 02:24 PM, Alan Holt wrote:
I'm really really sorry, it was typing error with ip address. Like I wrote I have next addresses:
My PC (NFS-CLIENT) is 192.168.1.100 My laptop (NFS-SERVER) is 192.168.1.101
in my /etc/exports/ /home/booch/Temp 192.168.1.101/255.255.255.0(rw,sync,no_subtree_check)
where 192.168.1.101 is my NFS-server
I think you're confused here. The server is the machine that has the drive you want other machines to mount over the network. Are you trying to share a drive from your PC to your laptop? If so, then the PC is the server.
The exports file should only exist on the server. It tells the server which clients are allowed to mount that directory. Also, the netmask you have (regardless of which is the server) is incorrect. The last octet should be .255 if you only want to allow the machine that you've named on the line access. If you want the entire network it's on access, then the IP address should be 192.168.1.0 and the netmask set to 255.255.255.0 (allowing 192.168.1.1 through 192.168.1.254 access).
If the PC is trying to share one of its local directories with the laptop, then the PC should have an /etc/exports with the line:
/home/booch/Temp 192.168.1.101/255.255.255.255(rw,sync,no_subtree_check)
(the netmask should end with ".255" if you're trying to only share with ONE machine) and the laptop should:
mount 192.168.1.100:/home/booch/Temp /local/mountpoint -o ro
- Rick Stevens, Systems Engineer, C2 Hosting ricks@nerd.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
-Careful! Ugly strikes 9 out of 10 people! -
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines