Find the answer to your Linux question:
Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    [SOLVED] SAMBA follies

    Thought I wasn't a noob to Samba any more, but I'm being bitten again...

    Home network with 3 Win7 boxes and one elderly Fedora 11 box (heloise) which has been running Samba well for several years. I've just built and started configuring a new Fedora 14 box (abelard) to replace heloise, but can't get the Win7 boxes to see shares on it.

    Windows Explorer on the Win7 boxes can see abelard, and they can see the two shares I've created on it, but if I double-click on a share I get the "Windows cannot access" dialog.

    I've set a Samba password for one user (ralph), the same as that user's login password, and set the "smb password file" entry to point to the resulting .tdb file.

    All IP addresses are static (via Static DHCP), everybody can ping everybody, I can ssh from a Win7 box to abelard via Putty, and the network operates cleanly in all other respects. Here's my smb.conf:

    # Samba config file created using SWAT
    # from UNKNOWN (
    # Date: 2011/05/07 11:25:27

    workgroup = MSHOME
    smb passwd file = /var/lib/samba/private/passdb.tdb
    server string = Samba Server Version %v
    log level = 2
    log file = /var/log/samba/log.%m
    max log size = 50
    cups options = raw

    comment = Home Directories
    path = /home/ralph
    valid users = ralph
    read only = No
    browseable = No

    comment = All Printers
    path = /var/spool/samba
    printable = Yes
    browseable = No

    path = /home/ralph/Public
    valid users = ralph
    read only = No

    path = /home/ralph
    valid users = ralph
    read only = No

    Suggestions appreciated.

  2. #2
    OK, found it...this was the first time SELinux bit me. Changing it to permissive cleared the problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts