I finally got a true NAS (Network Access Storage) device. A consumer level DNS-321 device. A nice sale at Tiger direct brought this in at under $100.
A while ago I bought a Wireless-N router (Linksys E3000) with USB support to host a hard drive, but it wasn’t quite what I wanted in the end. I didn’t want to put too much burden on the router so I held off.
My goals for the NAS…
- a personal FTP server I can access from anywhere
- host my media files on the network so internally I can stream to my DNLA TV / PS3
- stream those same files also via an iTunes server
Since the DNS-321 is supposed to support that all out of the box, I figured it would be easy… NOT THE CASE.
1st Issue…
The setup instructions were written for Windows users, and I use a Mac. There was even a Windows setup disk utility I could have used.
Not a bit issue though, the web admin interface was fine with me.
2nd Issue…
SMB / Mac / resource forks. The quickest way to access your NAS files is to use the Network Share… eg over Samba share (SMB.)
I hate that Mac still does not play nice with SMB network shares, it leaves those phantom ._filename.ext files that are counter parts to the original file (e.g. filename.ext would have ._filename.ext extras.) Not every file gets this, just files that Mac appends extra info to (e.g. spotlight data I believe.)
Also, you can’t tell they are there when viewing the drive in Mac. HOWEVER, you do see them when other systems look at the files. For example, I setup UPnP share for music files (e.g. DNLA) and when I browsed music in my DNLA device, I saw all the ._ files ahead of the real files (since it’s all alphabetical.)
I ended up being able to solve that by using FTP to upload the files instead. Of course, I tried using NFS first instead of SMB (not sure if that would have even resolved the resource fork issue.), but I could not get my Mac to connect to the NFS for whatever reason, even after a couple days of reading up google-found forum docs. Other people could, I could not. Still not sure if it was an issue with the NFS server in the DNS-321 or not, but one thing was for sure… D-Link was not a help at all.
3rd Issue (the tipping point)…
Final straw before I started trying to hack the thing with the fonz fun_plug (aka ffp… touching on this later)… iTunes server did not serve my video files to iTunes clients.
Everything I read said it should, and after seeing an example of a configuration file here http://krook.net/archives/169 I decided it may be just a small tweak of the server configuration to resolve the issue.
… Long story short … I didn’t plan on hacking the DNS-321 at all, but I found it necessary. I want to tweak the iTunes server config and also setup AFP file access (to replace the SMB access and reduce the requirement for FTP.)
I’ll link to the article walking through the process next, but for now, I figured I’d share the problems I ran into first.