Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:mac_osx_users 2011/08/16 17:37 | howto:mac_osx_users 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| This page is intended to offer some guidance to Mac users. The DNS-323 natively supports SAMBA (Windows) shares and so technically this means it supports Mac users, but there are a few things that you can do to make your lives a little easier! | This page is intended to offer some guidance to Mac users. The DNS-323 natively supports SAMBA (Windows) shares and so technically this means it supports Mac users, but there are a few things that you can do to make your lives a little easier! | ||
| - | NOTE: There have been a lot of complaints about SMB access since Snow Leopard. There seems to be some confusion about TCP ports for SMB file shares, but if you're explicit when you try to connect that may solve your problem. From the Finder, CMD+K pops up the 'Connect to Server' dialogue where you can enter the share name, or IP address of the server. For the DNS-323, using SMB from a Snow Leopard Mac, use something like "smb://192.168.99.99:139", or "smb://mydns323:139". | + | NOTE: There have been a lot of complaints about SMB access since Snow Leopard. There seems to be some confusion about TCP ports for SMB file shares, but if you're explicit when you try to connect that may solve your problem. From the Finder, CMD+K pops up the 'Connect to Server' dialogue where you can enter the share name, or IP address of the server. For the DNS-323, using SMB from a Snow Leopard Mac, use something like "[[smb://192.168.99.99:139]]", or "[[smb://mydns323:139]]". |
| ===== SAMBA vs. AFP ===== | ===== SAMBA vs. AFP ===== | ||
| Line 55: | Line 55: | ||
| The additional benefit of modifying SAMBA this way rather than installing the Fonz Fun-plug is that the Linux system has not been modified and you do not run the risk of damaging your file system when restarting the DNS-323 because you are not running Linux from the hard disk which prevents proper unmounting of the drive. | The additional benefit of modifying SAMBA this way rather than installing the Fonz Fun-plug is that the Linux system has not been modified and you do not run the risk of damaging your file system when restarting the DNS-323 because you are not running Linux from the hard disk which prevents proper unmounting of the drive. | ||
| + | |||
| Line 61: | Line 62: | ||
| * Install FFP 0.5. Basically, download fun_plug and fun_plug.tgz from the following site and copy them to "Volume_1" of the DNS-323, then reboot. FFP 0.5 installs itself and you can telnet in. | * Install FFP 0.5. Basically, download fun_plug and fun_plug.tgz from the following site and copy them to "Volume_1" of the DNS-323, then reboot. FFP 0.5 installs itself and you can telnet in. | ||
| - | * Here are the instructions for installing FFP and configuring SSH (http://wiki.dns323.info/howto:ffp) | + | * Here are the instructions for installing FFP and configuring SSH (http://dns323.kood.org/howto:ffp) |
| - | * Install optware, following these instructions: (http://wiki.dns323.info/howto:optware) | + | * Install optware, following these instructions: (http://dns323.kood.org/howto:optware) |
| * The optware startup script specified on the optware how-to page works, you just need to comment out the lines that echo details to the log. They really serve no purpose. If you want them, just specify the LOGFILE variable at the top of the script. You can't skip this step... it ties /opt to your ipkg opt directory. | * The optware startup script specified on the optware how-to page works, you just need to comment out the lines that echo details to the log. They really serve no purpose. If you want them, just specify the LOGFILE variable at the top of the script. You can't skip this step... it ties /opt to your ipkg opt directory. | ||
| * Be sure to add the path directive from the script to the /ffp/etc/profile file, since we installed FFP 0.5. If you don't, you'll have to manually locate "ipkg" as well as all of the other binaries that you install under /mnt/HD_a2/opt/. | * Be sure to add the path directive from the script to the /ffp/etc/profile file, since we installed FFP 0.5. If you don't, you'll have to manually locate "ipkg" as well as all of the other binaries that you install under /mnt/HD_a2/opt/. | ||
| Line 115: | Line 116: | ||
| * If you can't see the processes, try executing "/opt/etc/init,d.S20dbus start", and "avahi-daemon" manually to see if there are some errors. | * If you can't see the processes, try executing "/opt/etc/init,d.S20dbus start", and "avahi-daemon" manually to see if there are some errors. | ||
| * So, if everything worked, now when you open Finder in OSX, you should see a line under "Shared" for each service that you created. If you click on the AFP service, it will try to connect via AFP and you can choose "connect as" to specify a user/pass combo. If you click on the SAMBA service, it should immediately connect via SAMBA and/or let you click "connect as" to specify your Network Access credentials. The key here is that the delay is gone, because the SMB and AFP services are explicitly defined :) | * So, if everything worked, now when you open Finder in OSX, you should see a line under "Shared" for each service that you created. If you click on the AFP service, it will try to connect via AFP and you can choose "connect as" to specify a user/pass combo. If you click on the SAMBA service, it should immediately connect via SAMBA and/or let you click "connect as" to specify your Network Access credentials. The key here is that the delay is gone, because the SMB and AFP services are explicitly defined :) | ||
| - | |||
| ===== Time Machine backups to SMB shares (no hacks required!) ===== | ===== Time Machine backups to SMB shares (no hacks required!) ===== | ||
