• February 22, 2025, 10:22:04 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Host entry for nfs server?  (Read 6236 times)

gasman

  • Level 1 Member
  • *
  • Posts: 20
Host entry for nfs server?
« on: June 26, 2009, 02:30:31 PM »

Hi,
Will the nfs server accept the syntax of 192.168.2.0/24 for the whole subnet to have access.?
I have a device that I cannot set with a static ip address, and so I need to allow for any ip address in the 192.168.2.1 - 19.168.2.99 range.

I have tried the syntax and get permission denied when trying to mount the share on the device.
There is no log for the nfs server, so I do not know what might be the problem.

I'm also a linux novice.

TIA
Logged

D-Link Multimedia

  • Poweruser
  • Level 7 Member
  • **
  • Posts: 1066
    • D-link Systems, Inc.
Re: Host entry for nfs server?
« Reply #1 on: June 26, 2009, 05:32:51 PM »

Yes it accepts 0/24 for entire subnets. I just confirmed it on my unit.

Make sure you select your folder. If it still doesn't work list out your settings on here.
Logged

gasman

  • Level 1 Member
  • *
  • Posts: 20
Re: Host entry for nfs server?
« Reply #2 on: June 27, 2009, 06:40:19 AM »

Thanks for testing that. My settings are as below



Result from telnet session is

$ mount -t nfs 192.168.2.101:/Volume_1/Music /storage/disks/nas1
mount: 192.168.2.101:/Volume_1/Music failed, reason given by server: Permission
denied
$

ip 101 is the NAS with the Music folder under Volume_1


« Last Edit: June 27, 2009, 06:47:47 AM by gasman »
Logged

D-Link Multimedia

  • Poweruser
  • Level 7 Member
  • **
  • Posts: 1066
    • D-link Systems, Inc.
Re: Host entry for nfs server?
« Reply #3 on: June 28, 2009, 09:44:52 PM »

you need to mount the REAL path. not the Volume_1
Logged

gasman

  • Level 1 Member
  • *
  • Posts: 20
Re: Host entry for nfs server?
« Reply #4 on: June 29, 2009, 03:10:14 AM »

Ok, I will try that. The other path did appear to work, which is why I got confused.

Thank you.

you need to mount the REAL path. not the Volume_1
Logged