DSM-G600, DNS-3xx and NSA-220 Hack Forum

I'm having a really strange problem and I hope someone out there can help me out.

While trying to track down an issue while connecting to 323s from Ubuntu Intrepid it was discovered that the version of the Samba server used in the 1.0.5 firmware has a bug in the way it handles DFS paths which manifested itself by not allowing updates to existing files.  You can create new files, delete old files fine, but you can't change an existing file.  Intrepid's version of the client now uses the new functionality if the server indicates it has it, but in our case the server lies as it's implementation if broken.  There's currently no way of turning the new functionality off at the client but you can do so at the server on the 323 by adding

msdfs root = no

to the samba server.  This is achieved by saving the system config from tools -> system in the web front-end, appending the above line to the end of the ;[global] section of the file and then reloading the changed config.  This worked brilliantly and all my problems were solved.

So the linux guys have no patched the client to allow a mount option of nodfs which does the same thing but requires no access to the server.  While trying to test that the new patch works I needed to reverse out my server config from the 323 which is where my problems start.  Re-saving the config, removing my additional line, and restoring to the 323 broke the web front end.  I can't get to it at all.  I get a "connection refused" from firefox and a "connection interrupted" from IE.  My router's registering the san, I can ping it, and I can mount it fine (other than the original problem)

So I had to reset the 323 with my trusty paper clip.  All is well except now I don't have the msdfs line in my 323 config and I don't want to install the patched kernel on my prod machines until it's been released officially, so I run through the exercise again.  Save, patch, restore -> hosed web interface.

Did a hard reset back to factory defaults again and this time saved the config out and loaded it straight back up without making any changes; hosed web!

I did this successfully in the first place but now I can't load the config backup without breaking the web interface (and I'm stuck with not being able to update existing files again) and I've no idea why.

Has anyone else seen this behaviour, or have any recommendations for how to go about investigating what's going on?

Regards,

mipper