Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mynmynmyn]

I'm using a DNS-320, which I upgraded from 2.02 to official firmware 2.03. After this my softlinks do not work correct on my network share in windows 8.

I made softlinks to directories on my NAS. Eg.    ln -s /mnt/HD/HD_a2/dir1/dir2 shortcut
On my network share I was able to jump in Windows 8 Explorer to     "/mnt/HD/HD_a2/dir1/dir2"   using doubleclick on     "shortcut"
Since I upgrades to 2.03 I get an error message on double clicking on    "shortcut"     -> something like "I have not rights to access shortcut" (message is in german)

But I'm able to access "/mnt/HD/HD_a2/dir1/dir2" directly by clicking every directory. Softlink and directory have the same rights granted, same owner and group ...

I'm using another DNS-320, which is currently running on the older firmware 2.02. With this NAS I don't have the problem.

Could it be that there is a problem in firmeare 2.03 using softlinks on a networt share in windows 8?

[albert]

Have you try recreating the sym-link or network share?

[mynmynmyn]

Yes I did. Deleted symlink, recreated it (with ln-command but also with WinSCP (graphical tool)) / changed the owner,so i had to reenter user/pw for acccessing network share in Windows... No changes at all - everytime errormessage.

I did the same thing also with my other box, which is running the older firmware 2.02. Everything worked fine.

I also tried to downgrade the box from 2.03 to 2.02 -> symlink then worked correctly. Seems definitly to be a problem with firmware 2.03. But I can't stay with this downgrade, because now I have a problem with the web-admin interface. Can't manage my network-shares, because the table with  sharenames don't open anymore.

I upgraded once again to 2.03 -> now my webadmin works correctly -> but I have once again the problem with symlinks.

This is frustrating
wolfgang

[albert]

Apparently the problem is due to update in Samba (smbd) version after upgrading to firmware 2.03. The only solution is to include 3 additional keywords in /etc/samba/smb.conf and restart smbd.

Code: [Select]

unix extensions = no
follow symlinks = yes
wide links = yes


[mynmynmyn]

Hi Albert.

These little 3 lines do the trick - now my symlinks work correctly. Thank you so much!

But how can I make these changes permanently? Every time I reboot the box, smb.conf seem to get initialised and my changes get lost.

I'm actualy starting a script every time after booting to correct the smb.conf - but I think there must be a better way to fix that permanently.

Code: [Select]

# Enable symlinks for samba to correct changes in firmware 2.03
smbconf=/etc/samba/smb.conf
smbconf_tmp=/etc/samba/smb.conf.tmp

rm -f $smbconf_tmp
i=1
while read line
do
if [ $i == 2 ] #After [ global ] add the three lines, afterwards all other stuff of smb.conf
then
  echo "unix extensions = no" >> $smbconf_tmp
  echo "follow symlinks = yes" >> $smbconf_tmp
  echo "wide links = yes" >> $smbconf_tmp
fi
        echo $line >> $smbconf_tmp  #Create the smb.conf.tmp file
let "i=$i+1"
done < $smbconf

#replace smb.conf with new file
rm -f $smbconf
mv $smbconf_tmp $smbconf


[albert]

You're welcome, glad it resolve your problem.

For permanent fix, just edit /etc/samba/smb.conf manually and copy it to /usr/local/config directory. This copy will in turn be copy back to /etc/samba on every NAS reboot and use by smbd.

The only thing I'm not sure is whether the 3 lines will remain intact when changes are made on the Account Management menu.