1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Strange samba/symlink problem

Discussion in 'Linux & Open Source' started by whitecrook, 8 Apr 2010.

  1. whitecrook

    Sgarrista

    Joined: 22 Aug 2005

    Posts: 8,423

    Location: Clydebank

    Setup:

    freenas 192.168.1.250 sharing via samba \\192.168.1.250\data1
    debian 192.168.1.119 mounting freenas at /mnt/data1
    debian sharing via samba [homes] share followsymlinks yes, widelinks yes
    ln -s /mnt/data1/Video /home/whitecrook/popcorn

    and laptop 192.168.1.124 winxp mounted /home/whitecrook on Y:\

    Problem is I get 'access denied' when trying to access y:\popcorn

    I can access as whitecrook from terminal i.e. symlink works. permissions are 777 everywhere.

    But can't access the symlink 'popcorn' which points to my video folder on my freenas box via windows. hich s a pain as I need to run yamj pointing at this directory. (as /home/whitecrook/popcorn is where the web server points)

    Now there are various ways around this in terms of popcorn/yamj etc, but my query is on the symlink issue? Any ideas? Things I could try?

    Code:
    ls -lh /home/whitecrook | grep popcorn
    lrwxrwxrwx  1 root root   17 2010-04-07 23:50 popcorn -> /mnt/data1/Video/
    drwxrwxrwx  4 whitecrook whitecrook  16K 2010-03-31 22:48 popcorn_old
    
    Code:
    [homes]
       comment = Home Directories
       browseable = yes
       follow symlinks = yes
       read only = No
       create mask = 0700
       directory mask = 0700
       wide links = Yes
    
    
    Code:
    ls -lh /mnt | grep data1
    drwxrwxrwx 11 whitecrook whitecrook    0 2010-04-07 23:09 data1
    
    
     
  2. tntcoder

    Mobster

    Joined: 7 Apr 2004

    Posts: 4,213

    Just a guess, but Windows might not be liking the root owned symlink (not sure how windows uses 777 permissions?), I mean you are definitely having a permissions problem and it looks like a sensible place to start.

    I would suggest as a starting point using 'smbpasswd -a' to add a samba user, and try using those credentials on the windows box.

    Also check the samba log files for anything of relevance.

    Tricky one to narrow down :p

    EDIT: Also a hunch, add: "unix extensions = no" to your global area of the samba config. Google suggests it may help with symlink issues.
     
    Last edited: 8 Apr 2010