Robert Thurlow wrote: > Matt Cohen wrote: > >> We have two servers: >> >> 1) 10.97.1.1 - Solaris 10 with a zfs fileystem called /storage/nfs/client. >> >> I've set the sharenfs property on this fs as follows: >> sharenfs=rw=192.168.0.111,root=192.168.0.111 >> >> 2) 192.168.0.111 - Redhat WS 4. Trying to mount >> 10.97.1.1:/storage/nfs/client at /mnt/client >> >> >From the 192.168.0.111 Redhat server I issued the following: >> >> mount -t nfs 10.97.1.1:/storage/nfs/client /mnt/client >> >> I've tried different variations, including specifying nfs version 3. >> Everytime, I get the same error, "mount: 10.97.1.1:/storage/nfs/client >> failed, reason given by server: Permission denied" >> > > Hi Matt, > > I would expect that this is because you're using the numeric > address in the share on the Solaris server. Solaris will do > a reverse IP lookup and test the name against the share lists. > The best way to figure out what the server will see is to > log in remotely from the client and see what 'who am i' > returns as the remote machine name, e.g.: > >
Another point here is that syntactically, to state that you want to share to a network or a numeric address, you would do: sharenfs=...@192.168.0.111,ro...@192.168.0.111 Which still isn't going to work because as I said in the earlier post, you can not do a single numeric address. Well, you could as: sharenfs=...@192.168.0.111/32,ro...@192.168.0.111/32 But what I think Rob is alluding to above is that you've effectively told the system to export a host named "192.168.0.111". I.e., we will do a reverse host lookup on the string "192.168.0.111" and not find a match.