After following Lag-na’s sticky I’ve gotten a little further.
Doing steps 1 through 7 got me:
Last system mount error
mount: wrong fs type, bad option, bad superblock on //10.0.1.1/JUMP, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so
After changing the flag option to what Lag-na suggested I got:
Last system mount error
mount: cannot mount block device //10.0.1.1/JUMP read-only
When I set the account up i selected read and right. So I’m not sure where this message is coming from. Please see attached images for anything that I might have missed.
The directory name should be just the name found when connecting to the ip? Or should it be the path?
Last system mount error
mount: block device //10.0.1.1/AirportNAS is write-protected, mounting read-only mount: cannot mount block device //10.0.1.1/AirportNAS read-only
Many thanks Lag-na. That did the trick! I used some other work around too that got it to mount with ssh but disappeared after a day or so. So I tried your suggestion on ntlmssp for OS X and it has worked. I want to try from a clean install before I add this to the sticky.
The code below didn’t work. The web UI would just hang.
nounix,sec=ntlmssp
Just to be clear…
I set the airport extreme up with an account.
The Airport’s attached hard drive in my case is named AirportNAS which is what I used for the remote directory.