See below
> Dru Devore wrote: > > I am not an administrator but I will try and explain my situation. > > > > I am running a home network with a router that does not resolve names. I > > have foundation in my hosts in my client machine, foundation is the only > > computer on the network that has a static ip and this is because my > > router does not allow me to assign an ip to the a name. When I was > > running Ubuntu on the server, before I decided to change to zfs and > > OpenSolaris, I didn't could mount my nfs without the client in the hosts > > file. The thing that really confuses me why would the server need to > > resolve the name of the client? > > > > > > Dru, > > Some servers want to make sure that the name maps to an address and the > address maps back > to that same name. If that doesn't happen, the mount request can be denied. > > I'm not saying that the OpenSolaris server works that way. > > The following is a very basic set of commands which > > zpool create pool > zfs create pool/thud > zfs set sharenfs=on pool/thud Replacing the above commands with my pool name is exactly what I used. I was expecting it to not block any client. I try to map the client from the same network not through any firewall or anything. I have tried to mount it using the server name and the ip address. > > will create a share that any client can access. This will depend on your > router for denying > any inbound NFS traffic. > > At least one other responder has offered this up. > > Presently I can mount the nfs iff I have the client name in the hosts > > file but as soon as I remove the client from the hosts file I cannot > > mount the client any more. > > > > Is this on your OpenSolaris server or the Ubuntu one you mention? Sorry I should have specified. The OpenSolaris server replaced the Ubuntu server now I only have a OpenSolaris server and Ubuntu clients. I never had the client listed in the hosts file in Ubuntu. > > What are the shares you have on the server? > > Could you provide the output of the share command on your server? > > server> share landover_data@ /landover/data rw "" - at landover/mus /landover/music rw "" If I then go to the client and try to mount I get this (using both server name and address). ddevore at giskard:~$ sudo mount foundation:/landover/data /data mount.nfs: access denied by server while mounting foundation:/landover/data ddevore at giskard:~$ sudo mount 192.168.2.9:/landover/data /data mount.nfs: access denied by server while mounting 192.168.2.9:/landover/data ddevore at giskard:~$ > > > > So the question is can I get it to accept a mount without it resolving > > the client name? > > > > > > > > Yes. > > If you do not provide host names and/or dns subdomains to the share, it > will not attempt to resolve the client name. > > If you do: > > zfs set sharenfs=on pool/thud This is the one that I am using. > or > zfs set sharenfs=...@192.168.4.12:@192.168.4.13 pool/thud > > then you do not need to do a name lookup. > > If you however do: > > zfs set sharenfs=rw=alpha:beta:gamma pool/thud > or > zfs set sharenfs=rw=.foo.sun.com pool/thud > > then a name lookup will need to occur. > > If you provide the output of the share command on your server, we can > help you figure out what is going on here. > > > --- > > Dru Devore > > > > > >
