Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:change_share_name 2008/05/01 10:08 | howto:change_share_name 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== WARNING ===== | ===== WARNING ===== | ||
| **//NOTE - Saving the configuration file in Unix format (LF terminators rather than CRLF) is CRITICAL//** | **//NOTE - Saving the configuration file in Unix format (LF terminators rather than CRLF) is CRITICAL//** | ||
| - | * With firmware 1.04 there are reports (see this [[http://forum.dsmg600.info/t1993-Bricked-dns-323%3F.html|thread]]) that uploading a CRLF formatted configuration causes the web server, telnet, and other mechanisms for reconfiguring the unit to fail on reboot; further in these cases the hardware reset procedure did not work either. While other solutions might exist; the only confirmed fix required serial access. | + | * With firmware 1.04 there are reports (see this [[http://dns323.kood.org/forum/t1993-Bricked-dns-323%3F.html|thread]]) that uploading a CRLF formatted configuration causes the web server, telnet, and other mechanisms for reconfiguring the unit to fail on reboot; further in these cases the hardware reset procedure did not work either. While other solutions might exist; the only confirmed fix required serial access. |
| + | **//Mac-Users also NOTE: //** | ||
| + | * With firmware 1.07 and Safari 3.2.1 I also broke my webfrontend when trying to do what's described here, even though my files hat the correct line-ending! Fortunately I had ffp with telnet installed and could recover the webfrontend as described in [[http://dns323.kood.org/forum/viewtopic.php?pid=13670#p13670|this post]]. Didn't try to change the share-name eversince (2009-05-17, c_t). | ||
| + | |||
| + | |||
| ===== Edit Configuration Settings ===== | ===== Edit Configuration Settings ===== | ||
| Line 21: | Line 26: | ||
| ---- | ---- | ||
| + | |||
| + | **//Is this obsolete for newer firmwares?//** | ||
| + | * My revision B1 with v1.08 firmware DNS-323 produced a binary configuration backup, where the string was impossible to identify... | ||
| + | => The file is GZIP compressed. Add an appropriate file extension (.GZ/.GZIP) and open with an archive utility or gzip command line. | ||
| **//Is it possible to create more shares than just one per volume?//** | **//Is it possible to create more shares than just one per volume?//** | ||
| Line 29: | Line 38: | ||
| **//Technical Details//** | **//Technical Details//** | ||
| - | * The DNS-323 settings for SMB shares are stored on the actual drive being mapped (once a new share has been created or the default share settings updated). With telnet access the file /mnt/HD_a4/.systemfile/.smb.ses stores the relevant details (substitute HD_b4 for Volume_2). This file can be directly edited bypassing the configuration download/upload above. Rather than renaming the share using the Samba option "browseable = No" seems like a nice approach. Unfortunately; this setting works but "confuses" the web page for configuring shares; YMMV with various extra Samba options in this file. | + | * The DNS-323 settings for SMB shares are stored on the actual drive being mapped. With telnet access you can access the file /mnt/HD_a4/.systemfile/.smb.ses stores the relevant details (substitute HD_b4 for Volume_2). This file can be directly edited bypassing the configuration download/upload above. The file will not exist if you have not changed the settings for the default share or created a new share for the volume (default settings are embedded in binary files in the DNS-323 firmware). You can force creation of the file by deleting and recreating the default share (or by adding a new share). |
| + | * Rather than renaming the share using the Samba option "browseable = No" seems like a nice approach. Unfortunately; this setting works but "confuses" the web page for configuring shares; YMMV with various extra Samba options in this file. | ||
