Samba Howto: OSX10.5.8, Linux, WinXB, Win7 shares

*Samba Howto: OSX10.5.8, Linux, WinXB, Win7 share*
After several day of research and trial and error i found a solution, so that the Finder of OSX 10.5.8 shows all samba3 shares (irrespective of the operating system) in the left sidebar below the category SHARES.
My local home network consists of an iMac 6.1 (OSX10.5.8), a MacBook 3.1 (OSX10.5.8), a Synology DSXXX (Linux), a VMWare Win7 (testing environment), a VMWare WinXP (testing environment) and Linksys WRT54GL (firmware Tomato 1,27).
On both Mac and the DS209 I don't use the built-in Samba systems!! Instead I use Samba 3.2.15 from macports on both Macs and on my Synology DSXXX I use Samba 3.2.15 from ipkg. On Windows 7 and Windows XP I use the built-in systems.
_Install macports Samba3_
DO NOT ACTIVATE THE BUILT-IN SAMBA!!!
*Important note*: The portfile of samba3 has a bug. Therefore you have to open the portfile (in a text editor) and add tow lines of code (see below). You will find the macport-samba3-portfile under
/opt/local/var/macports/sources/rsync.macports.org/release/ports/net/samba3/Port file
Change the original portfile from
system "installnametool ${changeline} ${destroot}${prefix}/bin/tdbtool"
system "installnametool ${changeline} ${destroot}${prefix}/bin/testparm"
livecheck.type regex
to
system "installnametool ${changeline} ${destroot}${prefix}/bin/tdbtool"
system "installnametool ${changeline} ${destroot}${prefix}/bin/testparm"
+system "installnametool ${changeline} ${destroot}${prefix}/sbin/smbd"+
+system "installnametool ${changeline} ${destroot}${prefix}/sbin/nmbd"+
livecheck.type regex
Afterwards you can install samba3 using the normal macport commands (or Porticus).
_Create a smb.conf_
After the installation create a smb.conf file under /opt/local/etc/samba3. (I will present only the \[global\] section of my smb.conf.)
Note: replace <specification> with specifications of your computer system
--begin smb.conf
\[global\]
workgroup = WORKGROUP
netbios name = <computername, see system-preferences->Filesharing>
server string = <computername, see system-preferences->Filesharing>
hosts allow = 192.XXX.X. localhost
socket options = TCP_NODELAY
\# use my synology ds209 as wins server
wins server = 192.XXX.XXX.XXX
name resolve order = wins lmhosts hosts bcast
\# my imac/macbook never gets local master browser
domain master = no
local master = no
preferred master = no
os level = 0
winbind enum users = yes
winbind enum groups = yes
idmap uid = 10000-110000
idmap gid = 96000-196000
max smbd processes = 10
security = user
map to guest = Bad User
encrypt passwords = yes
passdb backend = smbpasswd
smb passwd file = /opt/local/var/db/smb/smbpasswd
log file = /opt/local/var/log/smb/log.%m
log level = 0
max log size = 50
--end \[global\] sector smb.conf
_Test your samba installation_
Now you can test your samba server running as daemon using the commandline:
/opt/local/sbin/smbd -D
/opt/local/sbin/nmbd -D
Check if your samba server configuration works:
ps -ax | grep smbd
ps -ax | grep nmbd
If the samba server runs well, stop it:
/opt/local/bin/smbcontrol smbd shutdown
/opt/local/bin/smbcontrol nmbd shutdown
_Create LaunchDaemon files_
Build a wrapper file and a LaunchDaemon file in order to start the samba sever automatically at boot time. (I modified the wrapper and plist files from a official macports mysql installation.)
--beginn wrapper script
#!/bin/sh
\# MacPorts generated daemondo support script
\# Init
prefix=/opt/local
\# Start
Start()
/opt/local/sbin/smbd -D
/opt/local/sbin/nmbd -D
\# Stop
Stop()
/opt/local/bin/smbcontrol nmbd shutdown
/opt/local/bin/smbcontrol smbd shutdown
\# Restart
Restart()
Stop
Start
\# Run
Run()
case $1 in
start ) Start ;;
stop ) Stop ;;
restart) Restart ;;
* ) echo "$0: unknown argument: $1";;
esac
\# Run a phase based on the selector
Run $1
--end wrapper script
--beginn LaunchDaemon script
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Debug</key>
<false/>
<key>Label</key>
<string>org.macports.samba3</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/opt/local/bin/daemondo</string>
<string>--label=samba3</string>
<string>--start-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>start</string>
<string>;</string>
<string>--stop-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>stop</string>
<string>;</string>
<string>--restart-cmd</string>
<string>/opt/local/etc/LaunchDaemons/org.macports.samba3/samba3.wrapper</string >
<string>restart</string>
<string>;</string>
<string>--pid=none</string>
</array>
<key>RunAtLoad</key>
<false/>
</dict>
</plist>
--end LaunchDaemon script
_Install the wrapper and the plist files_
Create a directory using the commandline:
mkdir -p /opt/local/etc/LaunchDaemons/org.macports.samba3/
Save both files in the new created directory.
Call the wrapper script samba3.wrapper.
Call the plist script org.macports.samba3.plist.
Change to the following directory:
cd /Library/LaunchDaemons/
Create a symlink to the samba3 plist script:
ln -s /opt/local/etc/LaunchDaemons/org.macports.samba3/org.macports.samba3.plist
Load the plist file using launchctl on the commandline:
launchctl -w load /Library/LaunchDaemons/org.macports.samba3.plist
Now smbd and nmbd should start at boot time.
_Create a samba WINS server_
*Important note*: ONLY ON SYSTEM IN A LOCAL NETWORK SHOULD BE A WINS SERVER!!
If you don't have a Synology DSXXX try to run one of the OSX10.5.8 system as a WINS server or use a Linux box.
Chance therefore the smb.conf file from above in the following way:
replace <specification> with specification of your computer-system
--begin snb.conf
\[global\]
workgroup = WORKGROUP
netbios name = <computername, see system-preferencies->Filesharing>
server string = <computername, see system-preferencies->Filesharing>
hosts allow = 192.XXX.XXX. localhost
socket options = TCP_NODELAY
local master = no
\# my synology ds209 works as wins server
wins support = yes
name resolve order = wins lmhosts hosts bcast
dns proxy = yes
\# my synology ds209 works as local master browser
domain master = no
local master = yes
preferred master = yes
os level = 65
winbind enum users = yes
winbind enum groups = yes
idmap uid = 10000-110000
idmap gid = 96000-196000
max smbd processes = 10
security = user
map to guest = Bad User
encrypt passwords = yes
passdb backend = smbpasswd
smb passwd file = /opt/etc/samba/smbpasswd
log file = /opt/var/samba/log.%m
log level = 0
max log size = 50
--end \[global\] sector smb.conf
If you have a Synology DSXXX install samba 3.2.15 using ipkg. I won't here explain how you can install ipkg on a DSXXX. You will find a lot of information about this topic in different synology support, wiki and forums sites.
*Important note*: DO NOT ACTIVATE THE BUILT-IN SAMA SYSTEM!!
After you have installed the ipkg samba 3.2.15 on your DSXXX use the smb.conf file above in order
to create a WINS Server on your DSXXX. (Hint: You will find the netbios name and the server string using the Webinterface Disk Station Manager 2.X -> Network -> Servername.)
*Addtional Note 1*: I really think that you can run every linux box as a WINS Server, because the Synology operating system is linux (as far as I know).
*Addtional Note 2*: On my Linksys WRT54GL I use static DHCP for all components of my local network.
*Addtional Note 3*: I Have filled in Router Name (MyRouter), Hostname (MyRouter) and Domain Name (myzone.com) under Router Identification in Tomato 1.27. (Without this I couln't find my Linksys WRT54GL via full qualified domain name.)
Kind regards, maninfo

in laptop pc with arch i have installed somewhat in gnome under System-->administration called "shared folder". Maybe this sort of software override manual configuration in /etc/samba/smb.conf?
Something like that is probably standing in ubuntu as well i suppose..
Last edited by jacopastorius82 (2010-11-03 22:13:53)

Similar Messages

  • "samba-discovery". An automounter script for windows shares

    Hi.
    At the last lan party I found it quite annoying to mount samba shares by hand all the time (as I don't use a smb capable browser with fuse like dolphin or the like). So here's what I've come up with. Explenations on how it works are at the start of the script. You can also download it directly from here. Basically you run it and anything available on the lan will be tidily mounted to /mnt/samba-discovery/*.
    #!/bin/bash
    # Hi and welcome to this samba/windows share automounting script.
    # It will:
    # - Scan the network for windows/samba hosts.
    # - Mount all their available guest shares
    # - If rerun it will check if all shares are still accesible
    # - Unmount everything if you use the -u option
    # It will not:
    # - Work on password protected shares. No idea what will happen,
    # I guess mount.cifs will spit an error but the script will continue
    # Run it without options to mount/rescan, use -u to unmount everything.
    # Before running it please specify the options below.
    # Post questions on the Archlinux forum: http://bbs.archlinux.org/viewtopic.php?pid=596979#p596979
    # MOST IMPORTANTLY: If it eats all your files for breakfast, it's none
    # of my responsibility! It should be quite safe though because it's
    # always checking if a dir is empty before deleting it.
    ### Options
    # Specify the name of your network adapter (e.g. eth0):
    netiface='eth0'
    # Specify which range of IPs you're interested in (less is faster)
    lowend=1
    highend=20
    ### Code
    # Prepare samba-discovery folder
    if [[ ! -d /mnt/samba-discovery/ ]]; then
    mkdir /mnt/samba-discovery
    fi
    # Unmount all shares and clean up directories using -u
    umountcount=0
    uhostcount=0
    if [[ $1 == "-u" ]]; then
    shopt -s nullglob dotglob
    dirs=(/mnt/samba-discovery/*)
    (( ${#dirs[@]} )) || sharefolders=1
    shopt -u nullglob dotglob
    if [[ ! $sharefolders == 1 ]]; then
    for i in /mnt/samba-discovery/*/*; do
    umount "$i" 2>/dev/null
    cd "$i" 2>/dev/null
    shopt -s nullglob dotglob
    files=(*)
    (( ${#files[*]} )) || dirempty=1
    shopt -u nullglob dotglob
    if [[ ! $dirempty == 1 ]]; then
    echo ">>> warning: target directory not empty although share unmounted"
    echo ">>> aborting. please investigate directory:"
    echo " $i"
    exit 1
    else
    dirempty=0
    rm -R "$i"
    echo " share on $i unmounted, folder removed."
    ((umountcount++))
    fi
    done
    for i in /mnt/samba-discovery/*; do
    umount "$i" 2>/dev/null
    cd "$i" 2>/dev/null
    shopt -s nullglob dotglob
    files=(*)
    (( ${#files[*]} )) || dirempty=1
    shopt -u nullglob dotglob
    if [[ ! $dirempty == 1 ]]; then
    echo ">>> warning: target directory not empty although all shares unmounted"
    echo ">>> aborting. please investigate directory:"
    echo " $i"
    exit 1
    else
    dirempty=0
    rm -R "$i"
    echo " parent folder $i removed."
    ((uhostcount++))
    fi
    done
    echo "-> Removed $umountcount shares and $uhostcount parent folders"
    exit 0
    else
    echo "no parent folder found, nothing to unmount"
    exit 0
    fi
    fi
    # Normal run. Scan for shares which are no longer on the network...
    if [[ ! $1 == "" ]]; then
    echo "Invalid option. Aborted"
    exit 1
    fi
    shopt -s nullglob dotglob
    dirs=(/mnt/samba-discovery/*)
    (( ${#dirs[@]} )) || sharefolders=1
    shopt -u nullglob dotglob
    if [[ ! $sharefolders == 1 ]]; then
    echo ':: Cleaning up orphaned shares...'
    cleancount=0
    for i in /mnt/samba-discovery/*/*; do
    if [[ ! $(ls $i 2>/dev/null) ]]; then
    umount "$i" 2>/dev/null
    cd "$i" 2>/dev/null
    shopt -s nullglob dotglob
    files=(*)
    (( ${#files[*]} )) || dirempty=1
    shopt -u nullglob dotglob
    if [[ ! $dirempty == 1 ]]; then
    echo ">>> warning: target directory not empty although share unmounted"
    echo ">>> aborting. please investigate directory:"
    echo " $i"
    exit 1
    else
    dirempty=0
    rm -R "$i"
    echo " share on $i no longer accesible, removed."
    ((cleancount++))
    fi
    else
    if [[ ! $(cat /proc/mounts | grep "cifs" | awk '{print $2}' | grep $i) ]]; then
    cd "$i" 2>/dev/null
    shopt -s nullglob dotglob
    files=(*)
    (( ${#files[*]} )) || dirempty=1
    shopt -u nullglob dotglob
    if [[ ! $dirempty == 1 ]]; then
    echo ">>> warning: target directory not empty although nothing mounted there"
    echo ">>> aborting. please investigate directory:"
    echo " $i"
    exit 1
    else
    dirempty=0
    rm -R "$i"
    echo " nothing mounted on $i, removed."
    ((cleancount++))
    fi
    fi
    fi
    done
    echo "-> Cleaned out $cleancount shares"
    fi
    # ... and then scan for new hosts and mount shares
    echo ':: Scanning for new hosts and shares...'
    netaddr=$(ifconfig eth0 | grep "inet addr" | awk '{print $2}' | awk -F ":" '{print $2}' | awk -F "." '{print $1"."$2"."$3}')
    hostcount=0
    sharecount=0
    for ((ip=$lowend; ip<=$highend; ip++)); do
    printf " scanning $netaddr.$ip...\r"
    if (( $(nmap -PN -p139,445 "$netaddr.$ip" | grep -e "139/tcp open" -e "445/tcp open" | wc -l) == 2 )); then
    hostwinname="$( nmblookup -A $netaddr.$ip | grep "<00>" | grep -v "<GROUP>" | awk '{print $1}')"
    hostdirname="$(echo $hostwinname | tr [:upper:] [:lower:])"
    echo " found $hostwinname on $netaddr.$ip"
    IFS=$'\n' shares=($(smbclient -N -gL \\\\$netaddr.$ip\\ 2>&1 | grep -e "Disk|" | grep -v '\$' | awk -F "|" '{print $2}'))
    for share in ${shares[*]}; do
    sharedir="$(echo $share | sed s/\ /_/g | tr [:upper:] [:lower:])"
    if [[ "$(cat /proc/mounts | grep ",unc=\\\\\\\\$netaddr.$ip\\\\$share,")" ]]; then
    echo " share "$share" already mounted in /mnt/samba-discovery/$hostdirname/$sharedir"
    else
    if [[ ! -d "/mnt/samba-discovery/$hostdirname" ]]; then
    mkdir "/mnt/samba-discovery/$hostdirname"
    #echo "$hostwinname:$hostdirname:$netaddr.$ip" >> /mnt/samba-discovery/$hostdirname/ip.txt
    fi
    if [[ ! -d "/mnt/samba-discovery/$hostdirname/$sharedir" ]]; then
    mkdir "/mnt/samba-discovery/$hostdirname/$sharedir"
    else
    cd "/mnt/samba-discovery/$hostdirname/$sharedir"
    shopt -s nullglob dotglob
    files=(*)
    (( ${#files[*]} )) || dirempty=1
    shopt -u nullglob dotglob
    if [[ ! $dirempty == 1 ]]; then
    echo ">>> warning: mounting directory not empty although share not mounted!"
    echo ">>> aborting. please investigate directory:"
    echo " /mnt/samba-discovery/$hostdirname/$sharedir"
    exit 1
    fi
    dirempty=0
    fi
    mount "//192.168.1.$ip/$share" "/mnt/samba-discovery/$hostdirname/$sharedir" -o guest 2>/dev/null
    echo " mounted "$share" in /mnt/samba-discovery/$hostdirname/$sharedir"
    ((sharecount++))
    fi
    done
    ((hostcount++))
    fi
    done
    echo "-> Mounted $sharecount shares from $hostcount hosts."
    # Remove samba-discovery folder if it is empty
    if [[ -d /mnt/samba-discovery/ ]]; then
    cd "/mnt/samba-discovery/"
    shopt -s nullglob dotglob
    files=(*)
    (( ${#files[*]} )) || sambadirempty=1
    shopt -u nullglob dotglob
    if [[ sambadirempty == 1 ]]; then
    rm -R /mnt/samba-discovery/
    fi
    fi
    Here's some sample output of how it will look, including one orphaned share and a new one on a rerun of the script:
    [root@Mothership samba-discovery]# /home/medja/scripts/samba-discovery
    :: Cleaning up orphaned shares...
    share on /mnt/samba-discovery/blackrabbit/conflict_denied_ops no longer accesible, removed.
    -> Cleaned out 1 shares
    :: Scanning for new hosts and shares...
    found BLACKRABBIT on 192.168.1.2
    share CD-Images already mounted in /mnt/samba-discovery/blackrabbit/cd-images
    share CD-Images2 already mounted in /mnt/samba-discovery/blackrabbit/cd-images2
    share Filme already mounted in /mnt/samba-discovery/blackrabbit/filme
    share Filme2 already mounted in /mnt/samba-discovery/blackrabbit/filme2
    mounted Music Library in /mnt/samba-discovery/blackrabbit/music_library
    found MOTHERSHIP on 192.168.1.4
    share space already mounted in /mnt/samba-discovery/mothership/space
    found EEE on 192.168.1.5
    share SharedDocs already mounted in /mnt/samba-discovery/eee/shareddocs
    -> Mounted 1 shares from 3 hosts.
    Last edited by Shapeshifter (2009-08-07 18:51:05)

    thanks a lot, i wanted to write that script for a long time, but never got around. one thing though, you shouldn't mount stuff in a subfolder of /mnt because /mnt itself should be kept for such purposes (unix file hierarchy standards, afaik)
    but that should be easily fixed by myself
    cheers
    Phil
    Last edited by Heller_Barde (2009-08-07 21:42:46)

  • Retain SAMBA permissions while migrating from linux to solaris 10 x86

    Hello,
    We are migrating a system from Redhat to Solaris 10 x86 and this has brought up a question on how we can restore our SAMBA files and retain our permissions that are associated by the users name rather then their numeric ID(UID/GID). So far my research hasnt produced anything that gives a solid answer to how we do this and is it even possible.
    The problem is that Windows user and group accounts are mapped locally per host by default. That mapping is defined as the accounts are referenced, so unless there is a way to guarantee the order of accounts being referenced, the mappings from Windows SIDs to Unix UIDs will be different between old and new.
    If the data restoration option we choose for the new server is naive and restores only by UID and GID, the permissions in the ACLs will not map to the correct Windows accounts. We either must find a restoration option which restores permissions by name rather than ID or we must create a script which can automate pushing the ACLs into the restored filesystem correctly by name.
    Initially I thought ufsdump could handle this but we are on ext3 filesystem going to vxfs. I have read a little on star but havent heard about it before. Has anyone used star for backup/restore for the purpose of retaining ACL ownership/permissions? It seems like its an old utility, maybe not used much anymore. Does anyone have a utility they have used for this purpose?
    Your help is much appreciated!!
    LR

    The problem is that Windows user and group accounts are mapped locally per host by default. That mapping is defined as the accounts are referenced, so unless there is a way to guarantee the order of accounts being referenced, the mappings from Windows SIDs to Unix UIDs will be different between old and new.Is there anyway that you can sanitize and post a small snippet of what's going on with the mapping files? I think I can follow this but I'm a bit confused by the username/UID thing since usually if a username is defined in /etc/passwd than the files will display the username. If a username is not defined in /etc/passwd then the ls command will revert to just showing the numbers which I take it is what you don't want to happen.
    If you could also sanitize and post even one of the acl's that might help clear up that portion of the problem as well.
    alan

  • Daul boot mac osx10.5 and linux.. how?

    hey guys,
    i have 24' imac 2.8Ghz not the brand new ones, but the newer ones?
    and im wondering how i can put ubuntu on it...
    is it the same process using bootcamp and installing windows? (not that i have done that)
    or how is it done?
    i wonder if i can just pop the live cd in and install seeing as mac and linux are both build on top of unix..
    any help would be appreciated
    thanks in advance.

    I'm running Kubuntu as a virtual machine through Parallels. It's very nice. I have BootCamp set up on my laptop running Windows XP, and that works fine, too. After using each for a while now, I'd have to say I prefer the VM setup, but I'm too lazy to switch the laptop over. I plan to install Windows 7 on my iMac after about Service Pack 2 or so.

  • Howto: PROMISE/SATA on Linux!

    Hello Linux users, want to get your PROMISE SATA Disk controller working on Linux?
    There are two options, option two it proberly best for beginners/newbes!
    Option One: Patch the kernel (Tested on 2.4.23)
    Download this file: http://www.busybox.net/pdc-ultra-1.00.0.10.tgz
    Login as su - (root)
    Copy or move it to:
    /usr/src/
    And Untar with:
    tar fzxv pdc-ultra-1.00.0.10.tgz
    then you will have pdc-ultra.patch in /usr/src/
    Then patch your kernel:
    cat pdc-ultra.patch | patch -p0 -N
    Then you will get patching file ... blah blah...
    patching file linux-2.4.23/drivers/scsi/Makefile
    More......
    When done, just goto: /usr/src/linux , configure your kernel.
    Make sure SCSI Disk support , SCSI Generic support is Built-in. under SCSI Support.
    Then you will find the Promise SATA Driver under SCSI Low level drivers, make it a Module or Built-in.
    Then install the kernel and modules, reboot.
    Login as yourself, then su - (root)
    Now to test if it works:
    cat /proc/scsi/pdc-ultra/*
    If you get something like this:
    PROMISE SATA150 Series Linux Driver v1.00.0.10
    Adapter1 - SATA 378  [ IRQ17 ]
    Drive    -
       3 : WDC WD1200JD-00FYB0   Channel2/Master 120034MB  UDMA5
    (Your drive should be listed here)
    Then it woks, congrats!  
    And you'll find your drive under /dev/sda (Most likely)
    fdisk /dev/sda and the press "p"+"enter" to print partitons if you have any!
    The number of cylinders for this disk is set to 14593.
    There is nothing wrong with that, but this is larger than 1024,
    and could in certain setups cause problems with:
    1) software that runs at boot time (e.g., old versions of LILO)
    2) booting and partitioning software from other OSs
       (e.g., DOS FDISK, OS/2 FDISK)
    Command (m for help): p
    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    Command (m for help):
    Option two: Build a kernel module from the source.
    Note!
    You must build a kernel with scsi support first, as above without the Promis Drivers, as we are not patchig the kernel.
    Then download this file:
    http://www.promise.com/support/file/driver/1_SATALINUXSRC1.00.0.8.zip
    Copy or move it to /tmp/
    unzip 1_SATALINUXSRC1.00.0.8.zip
    then cd ultra-1.0.8/
    Then run following:
    make clean
    make
    make install
    This should build and install a kernel module.
    Then run:
    insmod pdc-ultra   (PC may "stop responding" a few sec then return to normal)
    Now to test if it works:
    cat /proc/scsi/pdc-ultra/*
    If you get something like this:
    PROMISE SATA150 Series Linux Driver v1.00.0.10
    Adapter1 - SATA 378  [ IRQ17 ]
    Drive    -
       3 : WDC WD1200JD-00FYB0   Channel2/Master 120034MB  UDMA5
    (Your drive should be listed here)
    Then it woks, congrats!  
    And you'll find your drive under /dev/sda (Most likely)
    fdisk /dev/sda and the press "p"+"enter" to print partitons if you have any!
    The number of cylinders for this disk is set to 14593.
    There is nothing wrong with that, but this is larger than 1024,
    and could in certain setups cause problems with:
    1) software that runs at boot time (e.g., old versions of LILO)
    2) booting and partitioning software from other OSs
       (e.g., DOS FDISK, OS/2 FDISK)
    Command (m for help): p
    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    Command (m for help):
    This was made in the hope of helping others, so don't yell at me if you can't get it to work. Ask me a Question instead and I will try to help you as the best I can.   :hypecrite:
    Cheers,
    Kevin
    -- Gentoo Linux roxx!

    Hi !
    Check with these pdf's
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2498bf90-0201-0010-4884-83568752a857
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6945da7d-0c01-0010-1792-dd7b5d87235c
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d149ec34-0d01-0010-4791-db4f1d864576
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/607ebbd5-6555-2a10-e285-c2cbec4ebafd
    <b>for these JARs msbase.jar, mssqlserver.jar, msutil.jar</b> Check these pdf's
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
    <b>Find this doc for JDBC drivers-</b>https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
    (msbase.jar, mssqlserver.jar, msutil.jar).
    Driver:
    com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection for MS SQL Server:
    jdbc:microsoft:sqlserver://<server>:1433;databaseName=<dbname>
    If you are using the new SQL Server 2005 jdbc driver (sqljdbc.jar). Setup is basically the same, except the driver is now:
    com.microsoft.sqlserver.jdbc.SQLServerDriver
    And the URL is slightly different as well:
    jdbc:sqlserver://host:1433;DatabaseName=name
    <b>Check This thread discuss the same for these jars</b>
    MS SQL Server jdbc Driver installation on XI
    how to connect sql server through WAS
    Thanks!!

  • How doi install osx10.6 over linux mint 14 on imack7.1 i have disc?

    i insert the disc and it comes up windows support,boot camp installer

    First you must have a Mac that is capable of starting up from Mac OS X 10.6. If it came originally with a later version then it will not run 10.6.
    What is necessary is a 10.6 installation DVD in order to start from (either the original that came with the Mac or a retail one which is still available from Apple). Then you use Disk Utility to reformat the hard drive as Mac OS Extended (Journaled) with GUID partition table. After this you install 10.6.
    You can look up the model at one of the following links and see which Mac OS X was originally installed.
    http://www.everymac.com/
    http://mactracker.ca/

  • Connect to win7 share

    Hi all,
    Just got my first mac a few days ago and it has been great, up till now.
    I'm having some trouble with file sharing.
    I CAN see the mac folders from the PC, but when trying to connect to the PC from the mac, no luck.
    In Finder I go to "connect to server..." I write smb://ipofpc, I enter the username and password and I can see a list of all the shares on the PC. When I pick a share and click Ok I get an error message "There was an error connecting to the server. Check the server name or IP address..."
    I tried some things I found on the net, but nothing has worked up till now.
    Any ideas? I'm lost!
    Thank you!

    For testing purposes, try
    [global]
    workgroup = WORKGROUP
    server string = wicked yo
    netbios name = bigbro
    security = share
    ; the line below is important! If you have permission issues make
    ; sure the user here is the same as the user of the folder you
    ; want to share
    guest account = franky
    username map = /etc/samba/smbusers
    name resolve order = hosts wins bcast
    wins support = no
    [videos]
    path = /media/Videos
    available = yes
    browsable = yes
    public = yes
    writable = yes
    [pictures]
    path = /home/franky/Pictures
    available = yes
    browsable = yes
    public = yes
    writable = yes
    [music]
    path = /home/franky/Music
    available = yes
    browsable = yes
    public = yes
    writable = yes
    [torrents]
    path = /home/franky/Torrents
    available = yes
    browsable = yes
    public = yes
    writable = yes
    Also, disable password enabled sharing in Windows 7. If it works, you can go from there to get password sharing again.

  • Samba problems between two linux computers

    I have a laptop with arch with this smb.conf
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # For a step to step guide on installing, configuring and using samba,
    # read the Samba-HOWTO-Collection. This may be obtained from:
    # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
    # Many working examples of smb.conf files can be found in the
    # Samba-Guide which is generated daily and can be downloaded from:
    # http://www.samba.org/samba/docs/Samba-Guide.pdf
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = WORKGROUP
    # server string is the equivalent of the NT Description field
    server string = Samba Server
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = user
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ; hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    load printers = yes
    # you may wish to override the location of the printcap file
    ; printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ; printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ; printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ; guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *
    ; password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ; realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ; passdb backend = tdbsam
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting.
    # Note: Consider carefully the location in the configuration file of
    # this line. The included file is read at that point.
    ; include = /usr/local/samba/lib/smb.conf.%m
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ; interfaces = 192.168.12.2/24 192.168.13.2/24
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ; local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ; os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ; domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ; preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ; domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ; logon script = %m.bat
    # run a specific logon batch file per username
    ; logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    # %L substitutes for this servers netbios name, %U is username
    # You must uncomment the [Profiles] share below
    ; logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ; wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ; wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ; add user script = /usr/sbin/useradd %u
    ; add group script = /usr/sbin/groupadd %g
    ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ; delete user script = /usr/sbin/userdel %u
    ; delete user from group script = /usr/sbin/deluser %u %g
    ; delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
    wins support = no
    [homes]
    comment = Home Directories
    browseable = yes
    writable = yes
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ; comment = Network Logon Service
    ; path = /usr/local/samba/lib/netlogon
    ; guest ok = yes
    ; writable = no
    ; share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;[Profiles]
    ; path = /usr/local/samba/profiles
    ; browseable = no
    ; guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = yes
    # Set public = yes to allow user 'guest account' to print
    guest ok = no
    writable = no
    printable = yes
    # This one is useful for people to share files
    ;[tmp]
    ; comment = Temporary file space
    ; path = /tmp
    ; read only = no
    ; public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = no
    ; printable = no
    ; write list = @staff
    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;[fredsprn]
    ; comment = Fred's Printer
    ; valid users = fred
    ; path = /homes/fred
    ; printer = freds_printer
    ; public = no
    ; writable = no
    ; printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;[fredsdir]
    ; comment = Fred's Service
    ; path = /usr/somewhere/private
    ; valid users = fred
    ; public = no
    ; writable = yes
    ; printable = no
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ;[pchome]
    ; comment = PC Directories
    ; path = /usr/pc/%m
    ; public = no
    ; writable = yes
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    ;[public]
    ; path = /usr/somewhere/else/public
    ; public = yes
    ; only guest = yes
    ; writable = yes
    ; printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;[myshare]
    ; comment = Mary's and Fred's stuff
    ; path = /usr/somewhere/shared
    ; valid users = mary fred
    ; public = no
    ; writable = yes
    ; printable = no
    ; create mask = 0765
    [Themes]
    path = /home/du/Themes
    available = yes
    browsable = yes
    public = yes
    writable = yes
    and another pc with ubuntu with this smb.conf
    # Sample configuration file for the Samba suite for Debian GNU/Linux.
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options most of which
    # are not shown in this example
    # Some options that are often worth tuning have been included as
    # commented-out examples in this file.
    # - When such options are commented with ";", the proposed setting
    # differs from the default Samba behaviour
    # - When commented with "#", the proposed setting is the default
    # behaviour of Samba but the option is considered important
    # enough to be mentioned here
    # NOTE: Whenever you modify this file you should run the command
    # "testparm" to check that you have not made any basic syntactic
    # errors.
    # A well-established practice is to name the original file
    # "smb.conf.master" and create the "real" config file with
    # testparm -s smb.conf.master >smb.conf
    # This minimizes the size of the really used smb.conf file
    # which, according to the Samba Team, impacts performance
    # However, use this with caution if your smb.conf file contains nested
    # "include" statements. See Debian bug #483187 for a case
    # where using a master file is not a good idea.
    #======================= Global Settings =======================
    [global]
    ## Browsing/Identification ###
    # Change this to the workgroup/NT-domain name your Samba server will part of
    workgroup = WORKGROUP
    # server string is the equivalent of the NT Description field
    server string = %h server (Samba, Ubuntu)
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable its WINS Server
    # wins support = no
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # This will prevent nmbd to search for NetBIOS names through DNS.
    dns proxy = no
    # What naming service and in what order should we use to resolve host names
    # to IP addresses
    ; name resolve order = lmhosts host wins bcast
    #### Networking ####
    # The specific set of interfaces / networks to bind to
    # This can be either the interface name or an IP address/netmask;
    # interface names are normally preferred
    ; interfaces = 127.0.0.0/8 eth0
    # Only bind to the named interfaces and/or networks; you must use the
    # 'interfaces' option above to use this.
    # It is recommended that you enable this feature if your Samba machine is
    # not protected by a firewall or is a firewall itself. However, this
    # option cannot handle dynamic or non-broadcast interfaces correctly.
    ; bind interfaces only = yes
    #### Debugging/Accounting ####
    # This tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/log.%m
    # Cap the size of the individual log files (in KiB).
    max log size = 1000
    # If you want Samba to only log through syslog then set the following
    # parameter to 'yes'.
    # syslog only = no
    # We want Samba to log a minimum amount of information to syslog. Everything
    # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
    # through syslog you should set the following parameter to something higher.
    syslog = 0
    # Do something sensible when Samba crashes: mail the admin a backtrace
    panic action = /usr/share/samba/panic-action %d
    ####### Authentication #######
    # "security = user" is always a good idea. This will require a Unix account
    # in this server for every user accessing the server. See
    # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
    # in the samba-doc package for details.
    # security = user
    # You may wish to use password encryption. See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
    encrypt passwords = true
    # If you are using encrypted passwords, Samba will need to know what
    # password database type you are using.
    passdb backend = tdbsam
    obey pam restrictions = yes
    # This boolean parameter controls whether Samba attempts to sync the Unix
    # password with the SMB password when the encrypted SMB password in the
    # passdb is changed.
    unix password sync = yes
    # For Unix password sync to work on a Debian GNU/Linux system, the following
    # parameters must be set (thanks to Ian Kahan <<[email protected]> for
    # sending the correct chat script for the passwd program in Debian Sarge).
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    # This boolean controls whether PAM will be used for password changes
    # when requested by an SMB client instead of the program listed in
    # 'passwd program'. The default is 'no'.
    pam password change = yes
    # This option controls how unsuccessful authentication attempts are mapped
    # to anonymous connections
    map to guest = bad user
    ########## Domains ###########
    # Is this machine able to authenticate users. Both PDC and BDC
    # must have this setting enabled. If you are the BDC you must
    # change the 'domain master' setting to no
    ; domain logons = yes
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of the user's profile directory
    # from the client point of view)
    # The following required a [profiles] share to be setup on the
    # samba server (see below)
    ; logon path = \\%N\profiles\%U
    # Another common choice is storing the profile in the user's home directory
    # (this is Samba's default)
    # logon path = \\%N\%U\profile
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of a user's home directory (from the client
    # point of view)
    ; logon drive = H:
    # logon home = \\%N\%U
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the script to run during logon. The script must be stored
    # in the [netlogon] share
    # NOTE: Must be store in 'DOS' file format convention
    ; logon script = logon.cmd
    # This allows Unix users to be created on the domain controller via the SAMR
    # RPC pipe. The example command creates a user account with a disabled Unix
    # password; please adapt to your needs
    ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
    # This allows machine accounts to be created on the domain controller via the
    # SAMR RPC pipe.
    # The following assumes a "machines" group exists on the system
    ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
    # This allows Unix groups to be created on the domain controller via the SAMR
    # RPC pipe.
    ; add group script = /usr/sbin/addgroup --force-badname %g
    ########## Printing ##########
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    # load printers = yes
    # lpr(ng) printing. You may wish to override the location of the
    # printcap file
    ; printing = bsd
    ; printcap name = /etc/printcap
    # CUPS printing. See also the cupsaddsmb(8) manpage in the
    # cupsys-client package.
    ; printing = cups
    ; printcap name = cups
    ############ Misc ############
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting
    ; include = /home/samba/etc/smb.conf.%m
    # Most people will find that this option gives better performance.
    # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
    # for details
    # You may want to add the following on a Linux system:
    # SO_RCVBUF=8192 SO_SNDBUF=8192
    # socket options = TCP_NODELAY
    # The following parameter is useful only if you have the linpopup package
    # installed. The samba maintainer and the linpopup maintainer are
    # working to ease installation and configuration of linpopup and samba.
    ; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
    # Domain Master specifies Samba to be the Domain Master Browser. If this
    # machine will be configured as a BDC (a secondary logon server), you
    # must set this to 'no'; otherwise, the default behavior is recommended.
    # domain master = auto
    # Some defaults for winbind (make sure you're not using the ranges
    # for something else.)
    ; idmap uid = 10000-20000
    ; idmap gid = 10000-20000
    ; template shell = /bin/bash
    # The following was the default behaviour in sarge,
    # but samba upstream reverted the default because it might induce
    # performance issues in large organizations.
    # See Debian bug #368251 for some of the consequences of *not*
    # having this setting and smb.conf(5) for details.
    ; winbind enum groups = yes
    ; winbind enum users = yes
    # Setup usershare options to enable non-root users to share folders
    # with the net usershare command.
    # Maximum number of usershare. 0 (default) means that usershare is disabled.
    ; usershare max shares = 100
    # Allow users who've been granted usershare privileges to create
    # public shares, not just authenticated ones
    usershare allow guests = yes
    #======================= Share Definitions =======================
    # Un-comment the following (and tweak the other settings below to suit)
    # to enable the default home directory shares. This will share each
    # user's home director as \\server\username
    [homes]
    comment = Home Directories
    browseable = yes
    writable = yes
    # By default, the home directories are exported read-only. Change the
    # next parameter to 'no' if you want to be able to write to them.
    read only = no
    # File creation mask is set to 0700 for security reasons. If you want to
    # create files with group=rw permissions, set next parameter to 0775.
    ; create mask = 0700
    # Directory creation mask is set to 0700 for security reasons. If you want to
    # create dirs. with group=rw permissions, set next parameter to 0775.
    ; directory mask = 0700
    # By default, \\server\username shares can be connected to by anyone
    # with access to the samba server. Un-comment the following parameter
    # to make sure that only "username" can connect to \\server\username
    # The following parameter makes sure that only "username" can connect
    # This might need tweaking when using external authentication schemes
    ; valid users = %S
    # Un-comment the following and create the netlogon directory for Domain Logons
    # (you need to configure Samba to act as a domain controller too.)
    ;[netlogon]
    ; comment = Network Logon Service
    ; path = /home/samba/netlogon
    ; guest ok = yes
    ; read only = yes
    ; share modes = no
    # Un-comment the following and create the profiles directory to store
    # users profiles (see the "logon path" option above)
    # (you need to configure Samba to act as a domain controller too.)
    # The path below should be writable by all users so that their
    # profile directory may be created the first time they log on
    ;[profiles]
    ; comment = Users profiles
    ; path = /home/samba/profiles
    ; guest ok = no
    ; browseable = yes
    ; create mask = 0600
    ; directory mask = 0700
    [printers]
    comment = All Printers
    browseable = yes
    path = /var/spool/samba
    printable = yes
    guest ok = no
    read only = yes
    create mask = 0700
    # Windows clients look for this share name as a source of downloadable
    # printer drivers
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/printers
    browseable = yes
    read only = yes
    guest ok = no
    # Uncomment to allow remote administration of Windows print drivers.
    # You may need to replace 'lpadmin' with the name of the group your
    # admin users are members of.
    # Please note that you also need to set appropriate Unix permissions
    # to the drivers directory for these users to have write rights in it
    ; write list = root, @lpadmin
    # A sample share for sharing your CD-ROM with others.
    ;[cdrom]
    ; comment = Samba server's CD-ROM
    ; read only = yes
    ; locking = no
    ; path = /cdrom
    ; guest ok = yes
    # The next two parameters show how to auto-mount a CD-ROM when the
    # cdrom share is accesed. For this to work /etc/fstab must contain
    # an entry like this:
    # /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
    # The CD-ROM gets unmounted automatically after the connection to the
    # If you don't want to use auto-mounting/unmounting make sure the CD
    # is mounted on /cdrom
    ; preexec = /bin/mount /cdrom
    ; postexec = /bin/umount /cdrom
    [Downloads]
    path = /home/Duccio/Downloads
    available = yes
    browseable = yes
    guest ok = yes
    public = yes
    writable = yes
    Both have static ip
    The problem are 2:
    1- the pc cant see eachothers with nautilus under "network" but..
    2- if i type in nautilus in the address bar from the arch pc "smb://ubuntu_ip" i can see shared folders the shared folder in ubuntu pc /home/Duccio/Downloads is browseable but i cant mount folders, the message is "unable to mount location"
    Another pc with ubuntu wich have dhcp is visible under nautilus network
    Last edited by jacopastorius82 (2010-11-02 21:14:51)

    in laptop pc with arch i have installed somewhat in gnome under System-->administration called "shared folder". Maybe this sort of software override manual configuration in /etc/samba/smb.conf?
    Something like that is probably standing in ubuntu as well i suppose..
    Last edited by jacopastorius82 (2010-11-03 22:13:53)

  • [SOLVED] Share Multiple Directories With Samba On Arch Linux and XP

    Hello,
    I have had the worst luck so far with Samba, which is far more likely because of an error on my part than on Samba's.
    I can only seem to share one directory regardless of how I setup my smb.conf. And worse yet, if I mess with Samba, smb.conf, after the first time I set it up it doesn't work again until I reinstall my OS. Now I'm sure that reinstalling isn't the only option, but I haven't figured out how to make it work again any other way. I've tried uninstalling it, deleting it from the cache, deleting /etc/samba and so on, still can't connect to it from XP when I reinstall it.
    I'm running Arch64 and I want to share some directories with a laptop running Windows XP.
    I want to share my home folder, but have it accessible from XP only by me, share my mother's home folder, and have it accessible on XP only by her (well actually I guess it needs to be accessible by both, since i'm the admin), share my media-server (a collection of five hard drives where I store movies and such), and have it read/write by both of us. And finally share /srv so I can work on that from the XP computer as well. I think that's all. And I would like to share printers between the two computers. I would also like to access XP files from here.
    I've always been able to get the media-server to share, but that's it, nothing else. And it doesn't always work right. It doesn't seem to want to follow sym links, but like I say if I mess with it it will stop working all together. So I'm not sure what to do.
    A thought was to instead make a /media/samba-share directory and share that, and inside it have symlinks to my home, media-server, etc. However, that will only work if samba will follow symlinks for me.
    Here is the smb.conf I am planning to use at the moment:
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # For a step to step guide on installing, configuring and using samba,
    # read the Samba-HOWTO-Collection. This may be obtained from:
    # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
    # Many working examples of smb.conf files can be found in the
    # Samba-Guide which is generated daily and can be downloaded from:
    # http://www.samba.org/samba/docs/Samba-Guide.pdf
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = MEDIA-SERVER
    netbios name = Avalon
    encrypt passwords = true
    # server string is the equivalent of the NT Description field
    server string = Samba Server
    # Symlinks
    follow symlinks = yes
    wide symlinks = yes
    unix extensions = no
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = user
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ; hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    load printers = yes
    # you may wish to override the location of the printcap file
    ; printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ; printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ; printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ; guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *
    ; password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ; realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ; passdb backend = tdbsam
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting.
    # Note: Consider carefully the location in the configuration file of
    # this line. The included file is read at that point.
    ; include = /usr/local/samba/lib/smb.conf.%m
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ; interfaces = 192.168.12.2/24 192.168.13.2/24
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ; local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ; os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ; domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ; preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ; domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ; logon script = %m.bat
    # run a specific logon batch file per username
    ; logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    # %L substitutes for this servers netbios name, %U is username
    # You must uncomment the [Profiles] share below
    ; logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ; wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ; wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ; add user script = /usr/sbin/useradd %u
    ; add group script = /usr/sbin/groupadd %g
    ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ; delete user script = /usr/sbin/userdel %u
    ; delete user from group script = /usr/sbin/deluser %u %g
    ; delete group script = /usr/sbin/groupdel %g
    include = /etc/samba/usershare.conf
    #============================ Share Definitions ==============================
    [homes]
    comment = Home Directories
    browseable = yes
    writable = yes
    [media-server]
    comment = Media Server
    path = /media/media-server
    browseable = yes
    writable = yes
    printable = yes
    valid users = theavataroftime, christina
    follow symlinks = yes
    [theavataroftime]
    comment = The Avatar of Time's Home Directory
    path = /home/theavataroftime
    browseable = yes
    writable = yes
    printable = yes
    valid users = theavataroftime
    follow symlinks = yes
    [christina]
    comment = Christina's Home Directory
    path = /home/christina
    browseable = yes
    writable = yes
    printable = yes
    valid users = christina
    follow symlinks = yes
    [server]
    comment = Server
    path = /srv
    browseable = yes
    writable = yes
    printable = yes
    valid users = theavataroftime, christina
    follow symlinks = yes
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ; comment = Network Logon Service
    ; path = /usr/local/samba/lib/netlogon
    ; guest ok = yes
    ; writable = no
    ; share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;[Profiles]
    ; path = /usr/local/samba/profiles
    ; browseable = no
    ; guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = yes
    Set public = yes to allow user 'guest account' to print
    guest ok = yes
    writable = no
    printable = yes
    # This one is useful for people to share files
    ;[tmp]
    ; comment = Temporary file space
    ; path = /tmp
    ; read only = no
    ; public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = yes
    ; printable = no
    ; write list = @staff
    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;[fredsprn]
    ; comment = Fred's Printer
    ; valid users = fred
    ; path = /homes/fred
    ; printer = freds_printer
    ; public = no
    ; writable = no
    ; printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;[fredsdir]
    ; comment = Fred's Service
    ; path = /usr/somewhere/private
    ; valid users = fred
    ; public = no
    ; writable = yes
    ; printable = no
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ;[pchome]
    ; comment = PC Directories
    ; path = /usr/pc/%m
    ; public = no
    ; writable = yes
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    ;[public]
    ; path = /usr/somewhere/else/public
    ; public = yes
    ; only guest = yes
    ; writable = yes
    ; printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;[myshare]
    ; comment = Mary's and Fred's stuff
    ; path = /usr/somewhere/shared
    ; valid users = mary fred
    ; public = no
    ; writable = yes
    ; printable = no
    ; create mask = 0765
    Now I wouldn't think I would need to list my home and mom's home seperately, but since [homes] has never worked for me in the past i thought i would give it a try. Does this look like something that would do what I am wanting?
    Otherwise I would delete [homes], [media-server], [theavataroftime], [christina], and [server] and replace them with just [samba-share] with all those as symlinks inside that directory as before mentioned.
    Anyway, thanks for the help. Any good guide on this matter would be appreciated, I have looked at several, but more can't hurt . Networking isn't my thing so to speak, so please be specific in any explanations. Thanks again.
    Last edited by The Avatar of Time (2009-03-02 03:38:12)

    Well it seems that my trouble all started when I began using the 'printable = yes' option for shares. Since I removed that the troubles seem to have left me.
    Does anyone know why that is listed as on option in smb.conf here:
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = yes
    ; printable = no
    ; write list = @staff
    As well as in a few other examples if it doesn't work? I seen the example and assumed that option was needed to print from those shared directories.
    Also, it seems that the comma is not needed between the 'valid users' names.
    Also, I guess it wasn't Windows XP's fault either but rather my own ignorance. I like the idea of blaming Windows better though.....
    I hope this servers to help others to aviod my mistakes.

  • Map linux shared folders to Z drive in Windows Client. Unable to login through Samba Server

    Hi,
    I am trying to map my linux machine to a network drive Z in Windows 7 . I added user guid in smbusers and created a password for this user through smbpasswd . Started Samba server on linuc, but when trying to create a network drive, it is asking for the login. I used credentials as GUID/<CREATEDPWD> . Not able to login with these credentials. Am I missing something. My Domain is ORADEV. I attached related files smb.conf,lmhosts,smbusers  files. Please let me know if i am not configuring samba server correctly.
    Here is the sm.conf file Details :
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name
       workgroup = ORADEV
    # server string is the equivalent of the NT Description field
       server string = %L (ST Samba Host), RedHat AS %v
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ;   hosts allow = 192.168.1. 192.168.2. 127.
    # if you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    #   printcap name = /etc/printcap
    #   load printers = yes
    # It should not be necessary to spell out the print system type unless
    # yours is non-standard. Currently supported print systems include:
    # bsd, sysv, plp, lprng, aix, hpux, qnx
    #   printing = lprng
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
      guest account = adoddi
    # this tells Samba to use a separate log file for each machine
    # that connects
       log file = /var/log/samba/%m.log
    # Put a capping on the size of the log files (in Kb).
       max log size = 0
    # Security mode. Most people will want user level security. See
    # security_level.txt for details.
       security = server
    # Use password server option only with security = server
    # The argument list may include:
    #   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
       password server = *
       password server =Samba Server
    # Password Level allows matching of _n_ characters of the password for
    # all combinations of upper and lower case.
    ;  password level = 8
    ;  username level = 8
    # You may wish to use password encryption. Please read
    # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
    # Do not enable this option unless you have read those documents
       encrypt passwords = yes
       smb passwd file = /etc/samba/smbpasswd
    # The following is needed to keep smbclient from spouting spurious errors
    # when Samba is built with support for SSL.
    ;   ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
    # The following are needed to allow password changing from Windows to
    # update the Linux sytsem password also.
    # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
    # NOTE2: You do NOT need these to allow workstations to change only
    #        the encrypted SMB passwords. They allow the Unix password
    #        to be kept in sync with the SMB password.
    ;  unix password sync = Yes
    ;  passwd program = /usr/bin/passwd %u
    ;  passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
    # Unix users can map to different SMB User names
    ;  username map = /etc/samba/smbusers
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting
    ;   include = /etc/samba/smb.conf.%m
    # This parameter will control whether or not Samba should obey PAM's
    # account and session management directives. The default behavior is
    # to use PAM for clear text authentication only and to ignore any
    # account or session management. Note that Samba always ignores PAM
    # for authentication in the case of encrypt passwords = yes
    ;  obey pam restrictions = yes
    # Most people will find that this option gives better performance.
    # See speed.txt and the manual pages for details
       socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ;   interfaces = 192.168.12.2/24 192.168.13.2/24
    # Configure remote browse list synchronisation here
    #  request announcement to, or browse list sync from:
    # a specific host or from / to a whole subnet (see below)
    ;   remote browse sync = 192.168.3.25 192.168.5.255
    # Cause this host to announce itself to local subnets here
    ;   remote announce = 192.168.1.255 192.168.2.44
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
       local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ;   os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
       domain master = no
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
       preferred master = no
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ;   domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ;   logon script = %m.bat
    # run a specific logon batch file per username
    ;   logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    #        %L substitutes for this servers netbios name, %U is username
    #        You must uncomment the [Profiles] share below
    ;   logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ;   wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
       wins server = 130.35.62.34
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ;   wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The built-in default for versions 1.9.17 is yes,
    # this has been changed in version 1.9.18 to no.
       dns proxy = no
    # Case Preservation can be handy - system default is _no_
    # NOTE: These can be set on a per share basis
    ;  preserve case = no
    ;  short preserve case = no
    # Default case is normally upper case for all DOS files
    ;  default case = lower
    # Be very careful with case sensitivity - it can break things!
    ;  case sensitive = no
    #============================ Share Definitions ==============================
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    [ade]
      comment = ADE Directory
      path = /ade_global/
      public = no
      writable = yes
    [homes]
       comment = Home Directories (UNIX Home Dirs auto_home)
       browseable = no
       writable = yes
       valid users = %S
       create mode = 0664
       directory mode = 0775
    # If you want users samba doesn't recognize to be mapped to a guest user
    map to guest = bad user
    security = user
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ;   comment = Network Logon Service
    ;   path = /usr/local/samba/lib/netlogon
    ;   guest ok = yes
    ;   writable = no
    ;   share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;[Profiles]
    ;    path = /usr/local/samba/profiles
    ;    browseable = no
    ;    guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    #[printers]
    #   comment = All Printers
    #   path = /var/spool/samba
    #   browseable = no
    # Set public = yes to allow user 'guest account' to print
    #   guest ok = no
    #   writable = no
    #   printable = yes
    # This one is useful for people to share files
    [tmp]
       comment = Temporary file space on %L
       path = /tmp
       read only = no
       public = yes
    # This is for the /private dir
    [private]
       comment = /private file space on %L
       path = /private
       read only = no
       public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ;   comment = Public Stuff
    ;   path = /home/samba
    ;   public = yes
    ;   writable = yes
    ;   printable = no
    ;   write list = @staff
    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;[fredsprn]
    ;   comment = Fred's Printer
    ;   valid users = fred
    ;   path = /home/fred
    ;   printer = freds_printer
    ;   public = no
    ;   writable = no
    ;   printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;[fredsdir]
    ;   comment = Fred's Service
    ;   path = /usr/somewhere/private
    ;   valid users = fred
    ;   public = no
    ;   writable = yes
    ;   printable = no
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    [public]
       path =: /usr/somewhere/else/public
       public = yes
       only guest = yes
       writable = yes
       printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;[myshare]
    ;   comment = Mary's and Fred's stuff
    ;   path = /usr/somewhere/shared
    ;   valid users = mary fred
    ;   public = no
    ;   writable = yes
    ;   printable = no
    ;   create mask = 0765
    Here  is the smbusers file : adoddi is my GUID
    # Unix_name = SMB_name1 SMB_name2 ...
    root = administrator admin
    nobody = guest pcguest smbguest
    adoddi = adoddi
    lcmHosts File :
    127.0.0.1 localhost

    Hi,
    To clarify a couple of things:
    1- "reverse-route" does not have anything to do with this issue, the problem relies on the Windows 7 machine.
    2- Do you connect with an Admin account (Windows admin)?
    3- Do you run the VPN client as an administrator?
    4- Have you tried to disable any AV or software protection on the machine (just for testing).?
    Let me know.
    Portu.
    Please rate any helpul posts
    Message was edited by: Javier Portuguez

  • [SOLVED]Samba not working despite all my efforts

    Hi all, this be my first post ever.
    I am somewhat of a noob, jumped over to arch64 after ubuntu about a month ago, so please bear with me if I seem a little "behind".
    I've spent probably a total of 24 hours trying to get my Samba shares available to my other housemates.  They can see the shares, but cannot mount them (windows and linux).  All I want is for a public share to be writable, everything else read-only and the security to be "share" (I don't want unix accounts for each of my housemates, and this would be annoying for anyone else who drops in with their laptops).  I've trolled the internet for every how-to guide and nothing seems to work.  What is further annoying is that one of my housemates also runs arch and his (near) exact smb.conf doesn't work for me.
    Anyway, to business.  My smb.conf:
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # For a step to step guide on installing, configuring and using samba,
    # read the Samba-HOWTO-Collection. This may be obtained from:
    # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
    # Many working examples of smb.conf files can be found in the
    # Samba-Guide which is generated daily and can be downloaded from:
    # http://www.samba.org/samba/docs/Samba-Guide.pdf
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = HOUSEOTDAMNED
    # server string is the equivalent of the NT Description field
    server string = ***
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = share
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ; hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    load printers = yes
    # you may wish to override the location of the printcap file
    ; printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ; printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ; printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ; guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *
    ; password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ; realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ; passdb backend = tdbsam
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting.
    # Note: Consider carefully the location in the configuration file of
    # this line. The included file is read at that point.
    ; include = /usr/local/samba/lib/smb.conf.%m
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ; interfaces = 192.168.12.2/24 192.168.13.2/24
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ; local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ; os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ; domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ; preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ; domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ; logon script = %m.bat
    # run a specific logon batch file per username
    ; logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    # %L substitutes for this servers netbios name, %U is username
    # You must uncomment the [Profiles] share below
    ; logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ; wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ; wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ; add user script = /usr/sbin/useradd %u
    ; add group script = /usr/sbin/groupadd %g
    ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ; delete user script = /usr/sbin/userdel %u
    ; delete user from group script = /usr/sbin/deluser %u %g
    ; delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
    ;[homes]
    ; comment = Home Directories
    ; browseable = no
    ; writable = yes
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ; comment = Network Logon Service
    ; path = /usr/local/samba/lib/netlogon
    ; guest ok = yes
    ; writable = no
    ; share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;[Profiles]
    ; path = /usr/local/samba/profiles
    ; browseable = no
    ; guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = yes
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    # This one is useful for people to share files
    ;[tmp]
    ; comment = Temporary file space
    ; path = /tmp
    ; read only = no
    ; public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = yes
    ; printable = no
    ; write list = @staff
    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;[fredsprn]
    ; comment = Fred's Printer
    ; valid users = fred
    ; path = /homes/fred
    ; printer = freds_printer
    ; public = no
    ; writable = no
    ; printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;[fredsdir]
    ; comment = Fred's Service
    ; path = /usr/somewhere/private
    ; valid users = fred
    ; public = no
    ; writable = yes
    ; printable = no
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ;[pchome]
    ; comment = PC Directories
    ; path = /usr/pc/%m
    ; public = no
    ; writable = yes
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    [public]
    path = /home/***/Data/public/
    public = yes
    guest ok = yes
    only guest = yes
    guest account = nobody
    browsable = yes
    writable = yes
    printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;[myshare]
    ; comment = Mary's and Fred's stuff
    ; path = /usr/somewhere/shared
    ; valid users = mary fred
    ; public = no
    ; writable = yes
    ; printable = no
    ; create mask = 0765
    The group "nobody" does exist in /etc/group.  I have also made sure that "public" has 777 permissions.  The others shares aren't here as I kinda figured as one works, the others would follow suit when I add them.
    If it helps, my rc.conf daemons and modules:
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(vboxdrv usblp acpi_cpufreq cpufreq_ondemand cpufreq_powersave fuse)
    DAEMONS=(@syslog-ng @alsa @cpufreq hal fam gdm !network @crond @portmap @networkmanager @samba @netfs @cups @ntpd @xinetd)
    For what it's worth, I don't think my housemate uses networkmanager.
    Any help would be greatly appreciated, this is driving me insane.  Please let me know if any more info would help also.
    Thanks!
    Last edited by o1911 (2009-05-15 09:35:13)

    That did it- thank you very much!
    edit: not sure how to put [SOLVED] in the topic...
    Last edited by o1911 (2009-05-15 08:36:39)

  • Why can't I access my roommates' Windows computers through samba?

    I'm using KDEmod.  I can see our workgroup, MSHOME, by going through system -> remote places -> samba shares.  Sometimes, I can open the workgroup and see my roommates computers but if I try to access them, Konqueror will time out.  As of this very second, I can't even see them.  I'm pretty sure it isn't a problem with the network itself because they can all see each other and share files, and they can get my files as well, I just can't get theirs.  Here is my samba configuration file.  Any idea what the problem could be?  There is a good chance I have it configured wrong, I'm fairly new to Linux.  I followed the directions on the samba wiki entry.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = MSHOME
    # server string is the equivalent of the NT Description field
    server string = Samba Server
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = user
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ; hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    ; load printers = yes
    # you may wish to override the location of the printcap file
    ; printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ; printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ; printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ; guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *
    ; password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ; realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ; passdb backend = tdbsam
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting.
    # Note: Consider carefully the location in the configuration file of
    # this line. The included file is read at that point.
    ; include = /usr/local/samba/lib/smb.conf.%m
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ; interfaces = 192.168.12.2/24 192.168.13.2/24
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ; local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ; os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ; domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ; preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ; domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ; logon script = %m.bat
    # run a specific logon batch file per username
    ; logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    # %L substitutes for this servers netbios name, %U is username
    # You must uncomment the [Profiles] share below
    ; logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ; wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ; wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ; add user script = /usr/sbin/useradd %u
    ; add group script = /usr/sbin/groupadd %g
    ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ; delete user script = /usr/sbin/userdel %u
    ; delete user from group script = /usr/sbin/deluser %u %g
    ; delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
    #[homes]
    # comment = Home Directories
    # browseable = no
    # writable = no
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ; comment = Network Logon Service
    ; path = /usr/local/samba/lib/netlogon
    ; guest ok = yes
    ; writable = no
    ; share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;[Profiles]
    ; path = /usr/local/samba/profiles
    ; browseable = no
    ; guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    #[printers]
    # comment = All Printers
    # path = /var/spool/samba
    # browseable = no
    # Set public = yes to allow user 'guest account' to print
    # guest ok = no
    # writable = no
    # printable = yes
    # This one is useful for people to share files
    ;[tmp]
    ; comment = Temporary file space
    ; path = /tmp
    ; read only = no
    ; public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = yes
    ; printable = no
    ; write list = @staff
    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;[fredsprn]
    ; comment = Fred's Printer
    ; valid users = fred
    ; path = /homes/fred
    ; printer = freds_printer
    ; public = no
    ; writable = no
    ; printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;[fredsdir]
    ; comment = Fred's Service
    ; path = /usr/somewhere/private
    ; valid users = fred
    ; public = no
    ; writable = yes
    ; printable = no
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ;[pchome]
    ; comment = PC Directories
    ; path = /usr/pc/%m
    ; public = no
    ; writable = yes
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    ;[public]
    ; path = /usr/somewhere/else/public
    ; public = yes
    ; only guest = yes
    ; writable = yes
    ; printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;[myshare]
    ; comment = Mary's and Fred's stuff
    ; path = /usr/somewhere/shared
    ; valid users = mary fred
    ; public = no
    ; writable = yes
    ; printable = no
    ; create mask = 0765
    #This is my music
    [Music]
    path = /media/SEA_DISC/Music
    browseable = yes
    read only = yes
    valid users = nelson
    #This is my videos
    [Videos]
    path = /media/SEA_DISC/Videos
    browseable = yes
    read only = yes
    valid users = nelson

    I don't know much about samba, but I have had very similar problems with netbios in windows, I find it to be very unreliable and I think you would be better off with ftp, but that's just my opinion. Apart from that, are you sure you have the necessary ports opened, and so do they? And you might need a line in /etc/hosts.allow
    Last edited by calef13 (2008-04-21 10:28:45)

  • Printer shares not working since upgrade to samba 3.5.0 - SOLVED-ish

    I share my printer with my wife's XP laptop and another linux box.  This has been the position for the past 2 years or so, without any problems at all.  Yesterday I did my first reboot for a couple of weeks, and the first, therefore, since samba / smbclient upgraded to 3.5.0.  I can no longer print from the XP or other linux boxes.  Samba logs the error as :
    laptop (10.0.0.5) connect to service Oki initially as user visitor (uid=1001, gid=1001) (pid 12634)
    [2010/03/13 18:31:51.509666,  0] printing/print_cups.c:108(cups_connect)
      Unable to connect to CUPS server /var/run/cups/cups.sock:631 - Interrupted system call
    Setting cups logging to debug, the closest entries to the above attempt is as follows :
    D [13/Mar/2010:18:31:21 +0000] cupsdAcceptClient: 13 from localhost (Domain)
    D [13/Mar/2010:18:31:21 +0000] Report: clients=1
    D [13/Mar/2010:18:31:21 +0000] Report: jobs=500
    D [13/Mar/2010:18:31:21 +0000] Report: jobs-active=0
    D [13/Mar/2010:18:31:21 +0000] Report: printers=1
    D [13/Mar/2010:18:31:21 +0000] Report: printers-implicit=0
    D [13/Mar/2010:18:31:21 +0000] Report: stringpool-string-count=1334
    D [13/Mar/2010:18:31:21 +0000] Report: stringpool-alloc-bytes=6496
    D [13/Mar/2010:18:31:21 +0000] Report: stringpool-total-bytes=18208
    D [13/Mar/2010:18:31:21 +0000] cupsdReadClient: 13 WAITING Closing on EOF
    D [13/Mar/2010:18:31:21 +0000] cupsdCloseClient: 13
    D [13/Mar/2010:18:31:21 +0000] cupsdAcceptClient: 13 from localhost (Domain)
    I [13/Mar/2010:18:31:21 +0000] Generating SSL server key...
    E [13/Mar/2010:18:32:12 +0000] Unable to create SSL server key file "/etc/cups/ssl/server.key" - No such file or directory
    D [13/Mar/2010:18:32:12 +0000] cupsdCloseClient: 13
    I am guessing tht the "WAITING Closing on EOF" part may be important.
    Other aspects of samba do not appear to be affected. I can mount shares on the remote computers, use smbclient etc.
    Googling is not getting me anywhere.
    Any help will be greatly appreciated.
    Last edited by perseus (2010-03-14 18:54:41)

    I have had similar issues at my office.......I had a hylafax server (also sharing a couple printers via samba) running on debian 5 (samba 3.2) and upgraded it to debian 6 (samba 3.5). and it was samba printer sharing hell after that. What would happen is I would get samba logs full of the same jibberish
    [2011/02/25 15:11:20.201234,  0] lib/util_sock.c:1432(get_peer_addr_internal)
      getpeername failed. Error was Transport endpoint is not connected
      write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
    [2011/02/25 15:11:20.201249,  0] smbd/process.c:79(srv_send_smb)
      Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
    [2011/02/25 15:43:20.134201,  0] lib/util_sock.c:675(write_data)
    [2011/02/25 15:43:20.134220,  0] lib/util_sock.c:1432(get_peer_addr_internal)
      getpeername failed. Error was Transport endpoint is not connected
      write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
    [2011/02/25 15:43:20.134234,  0] smbd/process.c:79(srv_send_smb)
      Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
    I only post this here since I think it was more of a samba problem than a debian problem and we seem to be the only ppl out there talking about it......... the getpeername seemed to be the problem (to me anyway) and what would happen on our 25 or so XP home clients is that you would print but it wouldnt go ANYWHERE. Cups was not even recieving the jobs since samba was not passing the jobs to cups.
    It seems to me that the XP machines were not finding the server by its hostname so I messed around with changing the clients to map the printer by ip address instead of by hostname and it helped "some" but it still had big time glitchyness.
    the only conclusion I could come to in my mind is that this reminded me of back in the day when we had a win98se computer sharing a printer and the windows XP systems would hang for up to 2 min while trying to access the printer. The problem back then amounted to win XP not wanting to downstep to the older way of windows98's password encryption. So I started changing my smb.conf to allow guest on the printer, changed the mask to 777 and I even wrote up a whole new smb.conf from scratch to work on security = share no authentication, allow from everyone 777 etc etc.............STILL had problems.
    So I ended up throwing together a new server from a spare machine and installing debian 5.0.3 (with samba 3.2.5) and swapping it out yesterday........now EVERYTHING works fine.
    my educated guess here is that the new samba is probobly geared more towards vista & win7 than it is XP (since XP is a pretty old dog these days). I would loved to have worked this issue out but we just could not have the downtime any longer......so it looks like I am not going to be updating for a long time (which I now is not really the best policy) but it has to work.
    I hope this helps.....trust me you are not the only ones having this problem.

  • SMB Newbie: Accessing Linux Share

    I have my /etc/samba/smb.conf set up like so:
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # For a step to step guide on installing, configuring and using samba,
    # read the Samba HOWTO Collection.
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
    workgroup = WORKGROUP
    # server string is the equivalent of the NT Description field
    server string = Samba Server
    encrypt passwords = yes
    smb passwd file = /etc/samba/smbpasswd
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the HOWTO Collection for details.
    security = user
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ; hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    load printers = yes
    # you may wish to override the location of the printcap file
    ; printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ; printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ; printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ; guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/log.%m
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *
    password server = *
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ; realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ; passdb backend = tdbsam
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting.
    # Note: Consider carefully the location in the configuration file of
    # this line. The included file is read at that point.
    ; include = /usr/local/samba/lib/smb.conf.%m
    # Most people will find that this option gives better performance.
    # See the chapter 'Samba performance issues' in the Samba HOWTO Collection
    # and the manual pages for details.
    # You may want to add the following on a Linux system:
    # SO_RCVBUF=8192 SO_SNDBUF=8192
    socket options = TCP_NODELAY
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ; interfaces = 192.168.12.2/24 192.168.13.2/24
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ; local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ; os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ; domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ; preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ; domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ; logon script = %m.bat
    # run a specific logon batch file per username
    ; logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    # %L substitutes for this servers netbios name, %U is username
    # You must uncomment the [Profiles] share below
    ; logon path = \%LProfiles%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ; wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ; wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ; add user script = /usr/sbin/useradd %u
    ; add group script = /usr/sbin/groupadd %g
    ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ; delete user script = /usr/sbin/userdel %u
    ; delete user from group script = /usr/sbin/deluser %u %g
    ; delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
    [public]
    comment = Public Stuff
    path = /home/samba
    public = yes
    writable = yes
    printable = no
    Whenever I try to login from a windows XP machine, access is always denies.  How can I set up permissions for anyone to access the share?

    Ok, did you look at that page I recommended?  It gives you the steps.
    You don't have to create the file, just do, if the windows user is john, and has a password on the MS box of 1234
    smbpasswd -a john
    It'll ask for his  password, type in 1234, it'll ask for confirmation and type it in again.
    On the MS box, user john might have to log off and logon.
    However, again, I recommend taking a look at that page, trying the nbtstat and such.  Actually, I hadn't realized how dated that page is, I have to redo it, but the tips there should still be useful.

  • Unable to mount samba share file for xbox 360

    I want to be able to stream music from a directory in my arch linux computer (xfce4) to my xbox using samba on a local network using ethernet cables and a router not connected to the internet. I've been able to get samba to startup and I see the folder "share" in my network tab in thunar, but I am currentlly unable to mount that folder. I haven't been able to get the xbox to recognize my arch computer or visa versa.
    Here is the configuration I am running as of now:
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = XBOX
    # server string is the equivalent of the NT Description field
    server string = "Samba Server"
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = user
    [share]
    comment = music for xbox
    path = /home/ricky/Music
    browsable = yes
    guest ok = yes
    read only = yes
    create mask = 0777
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    I did a chmod -r 777 on the ~/Music directory already and I still haven't been able to mount it. I have read in the wiki that creating a /mnt/xboxshare directory, for example, would actually mount the share directory and allow the xbox to share. However, I would rather just use the directory I specified instead of creating another directory. Has anyone else experienced this problem or have any advice for me?
    Here is some additional information:
    I do have to input a password when I issue this command
    $ smbclient -L \\RG_ARCH
    Enter password:
    Domain=[XBOX] OS=[Unix] Server=[Samba 3.6.8]
    Sharename Type Comment
    share Disk music for xbox
    IPC$ IPC IPC Service ("Samba Server")
    rg Disk Home Directories
    Domain=[XBOX] OS=[Unix] Server=[Samba 3.6.8]
    Server Comment
    RG_ARCH Samba Server
    Workgroup Master
    XBOX RG_ARCH

    I was wondering whether it had anything to do with the network I was using. The router I am using can't access the internet and I am using the basic 192.168.1.X setup with 255.255.255.0 as the mask.
    My computer has an ip of 192.168.1.2 and the xbox has an ip of 192.168.1.3. However, I am still unable to ping the xbox or even see it show up in the network. I did notice that whenever I am using another router that is connected to the internet, I can see other windows based computers in the network tab in thunar under "windows network"
    Also, I do have a username and password associated with the samba setup.. so I assume maybe that has something do with it. I checked the permissions of the share folder and it was root:root with read and write permissions. I know samba is working fairly well.. but for whatever reason I can't get the xbox to connect even while it is on the same local network.

Maybe you are looking for

  • My iTunes 7.7 will not open, and no errors are showing up!

    I am running a Dell Inspirion 9400, with Windows XP SP3. I was using iTunes one day and all was well, I came back the next day to find my computer was restarted in lue of windows forcing updates on me, ( I have automatic updates turned off ) I am not

  • Unable to access ipod in windows 7 and itunes.

    My ipod has been sitting in a charging dock for a few months now.  Yesterday i removed it from the doc to add some new music.  When I tried to attach the ipod to my computer through the USB cable I noticed the ipod was not recognised in itunes or in

  • Windows 8.1 will not recognise my buffalo removable hard drive

    the hard drive worked until I had my laptop camera fixed & they have removed the driver & now it wont recognise it at all

  • Integrate HR org structure and CUA?

    We are considering a new design for our authorization management on our production ECC 6.0 system. There will be 2 productive ECC 6.0 systems; which system you use will depend on your global location.  We currently utilize the HR org structure to ass

  • GTX 8800 OC Continuous beep

    Hi all. My drama's this time seems to be a problem with my primary Card.  At random times, and often the PC freezes, screen goes blank but not necessarily black and card emits a continuous beep till I reset.  It also happens at startup time as window