Page 1 of 38 12311 ... LastLast
Results 1 to 10 of 1059

Thread: HOWTO: Setup Samba peer-to-peer with Windows

Hybrid View

  1. #1
    Join Date
    Dec 2005
    Location
    Vienna, Austria
    Beans
    155
    Distro
    Ubuntu

    HOWTO: Setup Samba peer-to-peer with Windows

    HOWTO: Setup Samba peer-to-peer with Windows

    As many fellow Ubuntu users seem to have trouble setting up samba peer-to-peer with Windows I decided to write a small howto on this matter.

    NOTE: I am aware that there's a wiki-page as well as several other howto's around - but by looking at the constant "how do I setup samba" posts that are floating around in the forum I simply see the need for a more thourough guide on this matter.

    Feel free to contribute and suggest - it'll only help to make this howto a better guide.

    The goal of this howto is to have samba act like a Windows Workstation in the LAN. As a "value added bonus" we will use samba to do netbios name resolution so that you can use the names of the workstations for network drive mapping instead of their ip-addresses (i.e.: \MY_WINDOWS_BOX\SHARE) - but only for as long as your Linux box has an static ip-address and is up and running.

    This guide is based on Ubuntu 6.06 LTS and intended for all architectures (i386, AMD64, ...) - if you are still using Breezy it's safe to follow this guide as there should be no differencies.

    A second guide on how to setup samba as Primary Domain Controller along with several other services such as DHCP, DNS and NTP will follow later on as this topic will be a little more thourough.


    1. Prerequisites

    - Your Linux box should have an static ip-address.
    In case you're getting your ip from a router/server via DHCP make sure it's configured to provide a fixed dhcp-lease. If that's no valid option you cannot use WINS ... more on this way down.

    - You need to have samba installed.
    If you haven't done so already open a terminal and type:

    Code:
    sudo apt-get install samba
    Don't close the terminal upon installation - we still need the commandline to get several tasks done!


    2. Getting samba configured

    First, let us make sure samba isn't running:

    Code:
    sudo /etc/init.d/samba stop
    As a starting point I included an smb.conf below, and there are only a few simple things you may need to tweak.

    Since the installation of samba just installed a rather useless template file we're going to rename it - we keep the file just in case.

    Code:
    sudo mv /etc/samba/smb.conf /etc/samba/smb.conf.template
    Next we create a new empty file

    Code:
    sudo touch /etc/samba/smb.conf
    And finally we need to open the file inside an editor

    Code:
    sudo gedit /etc/samba/smb.conf
    NOTE: If you're on KDE replace "gedit" with "kate"

    Copy / Paste the contents of the code-section below into your editor and read on ...

    Code:
    [global]
        ; General server settings
        netbios name = YOUR_HOSTNAME
        server string =
        workgroup = YOUR_WORKGROUP
        announce version = 5.0
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192
    
        passdb backend = tdbsam
        security = user
        null passwords = true
        username map = /etc/samba/smbusers
        name resolve order = hosts wins bcast
    
        wins support = yes
    
        printing = CUPS
        printcap name = CUPS
    
        syslog = 1
        syslog only = yes
    
    ; NOTE: If you need access to the user home directories uncomment the
    ; lines below and adjust the settings to your hearts content.
    ;[homes]
        ;valid users = %S
        ;create mode = 0600
        ;directory mode = 0755
        ;browseable = no
        ;read only = no
        ;veto files = /*.{*}/.*/mail/bin/
    
    ; NOTE: Only needed if you run samba as a primary domain controller.
    ; Not needed as this config doesn't cover that matter.
    ;[netlogon]
        ;path = /var/lib/samba/netlogon
        ;admin users = Administrator
        ;valid users = %U
        ;read only = no
    
    ; NOTE: Again - only needed if you're running a primary domain controller.
    ;[Profiles]
        ;path = /var/lib/samba/profiles
        ;valid users = %U
        ;create mode = 0600
        ;directory mode = 0700
        ;writeable = yes
        ;browseable = no
    
    ; NOTE: Inside this place you may build a printer driver repository for
    ; Windows - I'll cover this topic in another HOWTO.
    [print$]
        path = /var/lib/samba/printers
        browseable = yes
        guest ok = yes
        read only = yes
        write list = root
        create mask = 0664
        directory mask = 0775
    
    [printers]
        path = /tmp
        printable = yes
        guest ok = yes
        browseable = no
    
    ; Uncomment if you need to share your CD-/DVD-ROM Drive
    ;[DVD-ROM Drive]
        ;path = /media/cdrom
        ;browseable = yes
        ;read only = yes
        ;guest ok = yes
    
    [MyFiles]
        path = /media/samba/
        browseable = yes
        read only = no
        guest ok = no
        create mask = 0644
        directory mask = 0755
        force user = YOUR_USERNAME
        force group = YOUR_USERGROUP
    Ok, I already mentioned that there are a few simple things you may need to tweak; so here they are:

    -> netbios name = YOUR_HOSTNAME

    Replace "YOUR_HOSTNAME" with your desired hostname (don't use spaces!). Best pratice would be to use the same name you configured upon installation.

    Example:

    netbios name = DAPPER

    -> workgroup = YOUR_WORKGROUP

    Replace "YOUR_WORKGROUP" with the name of your workgroup, but make sure you're using the same as configured in Windows.

    To find out the Workgroup name in Windows follow these steps:

    - Click "START"
    - Click "Control Panel"
    - Click "System"
    - Click the 2nd Tab entitled "Computername" and find the name of the Workgroup there.

    Example:

    workgroup = MSHOME

    -> wins support = yes

    If your box doesn't have a static ip-address, or you cannot configure your router/server to provide you with a fixed dhcp-lease, change this configuration parameter to "no".

    In this case you cannot use the benefits of WINS.

    -> [MyFiles]

    This is the name of the share. Leave it as it is or adjust it to whatever you prefer. Don't use more than 31 characters and try to avoid spaces!

    -> path = /media/samba/

    This suggests that you've mounted an hard drive or partition on /media/samba where all the shared files will be stored.

    In case you don't have an extra hard drive/partition you may also create folder.

    I assume you've been wise enough to put /home onto a separate partition having an reasonable amount of storage space.

    To create the folder type (inside a new terminal) ...

    Code:
    sudo mkdir /home/samba
    ... and adjust "path =" to read ...

    path = /home/samba/

    Remember that this is just an example - you are free to put things wherever you like.

    -> force user = YOUR_USERNAME
    -> force group = YOUR_USERNAME

    Well, this should say it all. Replace "YOUR_USERNAME" with the name you use for login (no spaces!).

    Example:

    force user = stormbringer
    force group = stormbringer

    Now we completed the part of editing smb.conf

    Save the file and close gedit.

    Since we are going to share the folder with other users we should now make sure that the permissions are set. Type:

    Code:
    sudo chmod 0777 /media/samba
    NOTE: Don't forget to correct the path to the location you chose above!

    That's it - now we need to start samba ...


    1.1 Starting samba and setting up user accounts

    Let us fire up samba for the first time. Type:

    Code:
    sudo /etc/init.d/samba start
    There shouldn't be any errors - if you are presented with an error message make sure everything is correct (search for typos and/or invalid paths).

    Time to add yourself as an samba user.

    NOTE: You will be asked for a password - make sure you use the same as you use for login!

    Code:
    sudo smbpasswd -L -a your_username
    sudo smbpasswd -L -e your_username
    In case you need other users to be able to access the share you need to add them to your system AND samba as well. Make sure you use the very same Windows usernames and passwords!

    NOTE: Windows XP doesn't set passwords for its useraccount per default. If you haven't set a password on your XP box just press enter when prompted to enter a password for the user account you're about to create!

    In the following example we will add an user called "mark" ...

    Example:

    Code:
    sudo useradd -s /bin/true mark
    sudo smbpasswd -L -a mark
    sudo smbpasswd -L -e mark
    The "-s /bin/true" in the first line prevents the users from being able to access the commandline of your linux box ("-s" stands for "shell"). I strongly advise you to follow this recommendation! Don't change that setting to a valid login-shell unless you really know what you are doing!

    Repeat this step until you configured all user accounts!

    Now that we configured samba and created the user accounts we are done with the Linux-part - there's one more thing to do in Windows.


    2. Changing network settings in Windows

    Now we should let Windows know that there's a WINS server active in the network.

    If you had to change "wins support" to "no" above skip this step!

    - Click "START"
    - Click "Control Panel"
    - Click "Network Connections"
    - Find your "LAN Connection"
    - Right-click the icon and select "Properties"
    - Select the "TCP/IP" Protocol and click the "Properties" button
    - Click "Advanced"
    - Select the third Tab entitled "WINS"
    - Click "Add"
    - Type in the ip-address of your Linux box
    - Click "Add"
    - Select "Use NetBIOS over TCP/IP"
    - Click "OK"
    - Click "OK"
    - Click "OK"
    - Reboot Windows

    Upon reboot you may now map the network drive within Windows.

    With WINS enabled:
    - Click "START"
    - Right-click "My Computer"
    - Select "Map network drive"
    - Choose the drive letter
    - Type \\DAPPER\MyFiles
    NOTE: Adjust this to the hostname and sharename you chose above!
    - Click "Finish"

    With WINS disabled:
    - Click "START"
    - Right-click "My Computer"
    - Select "Map network drive"
    - Choose the drive letter
    - Type \\<ip-address>\MyFiles
    NOTE: To find out the ip-address of your Linux box type "ifconfig" inside a terminal and find the ip for the correct interface (i.e. eth0). Don't forget to adjust the sharename to the name you chose above.
    - Click "Finish"

    That's it - samba is up and running now.


    3. Security consideration

    This is the right time to think about security right away.

    In case your computer has more than one network connection (i.e. wired and wireless ethernet) you may want to restrict access to samba.

    If not especially configured samba will bind its service to all available network interfaces.

    So, let us assume you only want your wired network to have access and that the network card is called eth0.

    Add the following lines to the [general] section of your smb.conf to achieve that goal:

    Code:
    interfaces = lo, eth0
    bind interfaces only = true
    If you did it correctly it should look similar to this:

    Code:
    [global]
        ; General server settings
        netbios name = YOUR_HOSTNAME
        server string =
        workgroup = YOUR_WORKGROUP
        announce version = 5.0
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192
        interfaces = lo, eth0
        bind interfaces only = true
    Now only the local loopback interface (dubbed "lo") and eth0 are able to access samba - there's no need to fear that someone might break into your system by wireless as the interface isn't bound to the service.


    4. Final words

    If you happen to have any questions feel free to ask - I'll try to help as soon as possible.

    If you find any mistakes in this howto please let me know so that I can fix them.

    Feel free to contribute and suggest - help to make this howto a better guide.


    5. Addendum: Useful links

    Here are some links you may find useful.

    The onsite links refer to other samba-guides and to ubuntu_daemon's "Important Links" thread.

    - Onsite
    Ubuntu Help: Windows Networkworking
    Ubuntu Documentation: Setting up Samba

    READ THIS FIRST prior to posting - IMPORTANT links (by ubuntu_daemon)


    The offsite links refer to the offical Samba homepage and to a selected choice of their official documentation; these links are useful if you like to dig yourself into the mysteries of samba's configuration and usage as well as troubleshooting problems.

    - Offsite
    Samba Homepage

    Practical Exercises in Successful Samba Deployment
    The Official Samba-3 HOWTO and Reference Guide
    Using Samba, 2nd Edition
    Last edited by Stormbringer; August 13th, 2006 at 03:26 PM.

  2. #2
    Join Date
    Mar 2006
    Beans
    2,358

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    stormbringer, wonderful guide you have created, I have a few questions though.

    you say that you will make this guide more thorough later to include DHCP with samba. is that going to happen any time soon or have you not planned it yet?

    also, please look at my attachment, it's a drawing of the way my network is physically setup. i just want to know if my network is safe. i use my windows desktop's shared folder as my backup folder, the folder where i backup all of my ubuntu stuff on it. my smb.conf is as generic as it can be, and i don't have a shared folder on my ubuntu desktop because i can browse, save, write to, and delete files on my windows desktop's shared folder. it never asks me for a password or anything on ubuntu. i just go to places, network servers, and go into my windows desktop's shared folder.

    is it me, or does that just not sound safe at all?!
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	setup.png 
Views:	5388 
Size:	25.4 KB 
ID:	11713  

  3. #3
    Join Date
    Jun 2006
    Beans
    Hidden!

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    Hello and thanks for your efforts in helping everybody.

    My problem is the following: I have a server (GATEWAY) that runs Ubuntu 6.06 and that, as it's name implies, is used as a gateway to a public network. Samba runs on this server and the firewall is configured to let Netbios and Samba ports traffic allowed from private interface. Also, I have setup all Windows workstation to use WINS over TCP using to the Gateway server IP address.

    My smbpasswd user list is synchonized with my Windows user names and password for all workstations and the smbpasswd users are enabled.

    I have 1 laptop that runs Win2K pro, 1 workstation that runs WinXp pro and 1 workstation that runs WinXP-home. Everything works fine from my win2K workstation. Using Windows explorer, I can navigate through the workgroup to the public share on the Gateway server. When using the WinXp ones, I simply cannot get to the shares. Here is what happens:

    I open Windows Explorer and navigate to my server. When I click on Gateway, I am asked by Wndows to enter a name and a password. I enter a valid name and password (ex: jacques and mysecret where they are both entered and enabled in the smbpasswd). The password screen is then redrawn asking for a name and password this time, the user field is populated with "GATEWAY\jacques". I enter again the password but no can do. The system remains in this loop forever.

    I tried the net test from the XP workstations and it worked OK (net use z: \\192.168.1.1\public mysecret /user:jacques /persistent:no and the drive is mapped correctly with the correct access rights) so it seems that it is at the password exchange level that ther is a problem.

    I also get that nasty password screen when I try to install a public printer on the XP workstation while I have no problen installing on the Win2K equipment.

    Here is my configuration:

    Code:
     
    [global]
    
        workgroup = HOMELEDX
        netbios name = GATEWAY
        server string = 
        interfaces = eth1 lo
        bind interfaces only = yes
    
        announce version = 5.0
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192
        passdb backend = tdbsam
        security = user
        null passwords = true
        username map = /etc/samba/usermap
        name resolve order = hosts wins bcast
        wins support = yes
    
        encrypt passwords = yes
       
        printing = cups
        printcap name = cups
    
    [public]
        path = /exports/samba/public
        read only = yes
        browseable = yes
        guest ok = no
        force user = ledxadmin
        force group = users
    
    [printers]
        comment = All printers
        path = /var/spool/samba
        guest ok = no
        printable = yes
        use client driver = yes
        browsable = no
    Thanks in advance for your help.

    ledj0

  4. #4
    Join Date
    Dec 2005
    Location
    Vienna, Austria
    Beans
    155
    Distro
    Ubuntu

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    Quote Originally Posted by ledj0 View Post
    I open Windows Explorer and navigate to my server. When I click on Gateway, I am asked by Wndows to enter a name and a password. I enter a valid name and password (ex: jacques and mysecret where they are both entered and enabled in the smbpasswd). The password screen is then redrawn asking for a name and password this time, the user field is populated with "GATEWAY\jacques". I enter again the password but no can do. The system remains in this loop forever.
    You're not the only one who reported this odd behaviour in this thread - and I tried hard to reproduce the problem inside a VMware environment (Ubuntu 6.06 Server with all patches applied, Windows XP Home Edition / Professional with SP2 and all hotfixes applied) but failed so far.

    To be honest ... I have no idea what the problem might be as I cannot reproduce the behaviour at all. It always works out for me (not only in the peer-to-peer setup but in a full PDC setup as well).

    Quote Originally Posted by ledj0 View Post
    I tried the net test from the XP workstations and it worked OK (net use z: \\192.168.1.1\public mysecret /user:jacques /persistent:no and the drive is mapped correctly with the correct access rights) so it seems that it is at the password exchange level that ther is a problem.
    That's what I think too ... something's different in the authentication; seems as Windows Explorer handles things slight different than "net" does.

    Quote Originally Posted by ledj0 View Post
    I also get that nasty password screen when I try to install a public printer on the XP workstation while I have no problen installing on the Win2K equipment.
    Ah ha ... so it's related to XP only ... well ... if that's the case then Server 2003 and/or XP x64 should have a similar problem as they share the same code-base (at least that's what M$ tells).

    Quote Originally Posted by ledj0 View Post
    Here is my configuration:
    <snip>
    Looks fine to me ... no typos and no misconfiguration.

    However, as you seem to run this setup on a multi-homed firewalling server ...

    Mind to post the firewall-rules of iptables you configured (just clean out any public IP with xxx.xxx.xxx.xxx)?

    Does the output of "smbclient -L localhost -U%" look fine or does it show any errors?

    -Storm

  5. #5
    Join Date
    Jun 2006
    Beans
    Hidden!

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    There might have been different problems: after I posted that message, I reviewed all parameters that might influence this setup in and out Samba. I realized that I did not have Wins registration (tcp-139) and SMB/CIFS udp-445 opened. Also, I have made a change in my [public] share's force user and force group. Finally, I removed the "username map" entry as the map file did not contain anything.

    I never used a Wins server in my network so this is why I overlooked the first one and the second is probably due to misreading or plain fatigue .

    I cannot tell exactly which of these change solved the problem. I will certainly try to isolate this some time but here's what I think:

    - I don't think the firewall ports have caused that specific problem since things were working fine in 2k. I tend to think that it might have influenced the browsing speed. Also, I doubt very very much that the password exchange routine varry that much at the interfacing level from 2k to XP but hey...we never know with Bill's baby.

    - As you made it clear in this thread, the "force user" and "force group" parameters have nothing to do with login but deals with file ownership. This means that this parameter should not have made difference in this situation.

    - This leaves the "username map" parameter. In my first post, I did not go into all details as did not want to write a novell. I said that my user configuration was checked, etc. Here are the details:

    - the login name from the 2k workstation was exactly reproduced in the linux box with the exact same case (ex: abc - abc). There was a direct match from win to samba password.

    -the login name from XP was the same name exept for the first character which was uppercase in win (ex Def - def). It is mentionned in some Samba books as well as in this thread that username case is converted to lowercase so I did not bother since this was exactly the case.

    However the match was not perfect and there is a "username map" parameter so (from this point, this is only speculation from my part as I did not go through Samba's sources ) Samba goes in resolution mode. It looks at "username map" parameter and if it does not find a map there, it simply returns as if you sent an invalid name. In my opinion, removing this parameter is the key as from there, Samba will follow it's standard internal resolution algorithm.

    In any case, things are (finally) working fine now. I will try to isolate exactly what fixed this and post back to this thread (after a short vacation8) ).

    Big thanks again for your time and efforts, you are a champ.

    ledj0

  6. #6
    Join Date
    Jun 2005
    Beans
    14

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    I agree with all the other folks who've praised what you did. Many thanks.

    Of course I'm here with a problem, one I couldn't find addressed in the many posts, although it may be.

    I followed the tutorial and have my windows machine seeing what I called "server1". I can start the mount process with XP, but when I get to the connect dialog box it doesn't accept my
    username and password. After it refuses plain "george" (username) It offers to try using the following "P390\george" as user name, where P390 is the machine name, but that doesn't work either.


    - I've checked that the user name (and password) are identical on both machines - including case.
    - I've restarted the windows machine

    I'm baffled what to do next to track down why it won't accept the login that is the same on both my XP and ubuntu (6.10) machine.

    Thanks for any help you can give

  7. #7
    Join Date
    Jun 2005
    Beans
    14

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    Oops.

    I restarted Ubuntu, closing a dialog box in the process and now it works as it should. I shot too soon.

    Thanks again anyway.

  8. #8
    Join Date
    May 2008
    Location
    Pampa, Texas
    Beans
    114
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    To add some light to my previous two posts, here is another thread that I found. Though my research STILL cannot find any answer to my problem, I have found that it is suddenly very common. It all seems to have started back in September:

    http://ubuntuforums.org/showthread.php?t=923922

    I urge everyone with knowledge of networking to read this thread. Something has changed, and no one with the necessary expertise seems to be helping. Was there a bad update, somewhere? Why the lack of response?
    Thanks.

    Ubuntu Studio 8.04, Pentium 4/2.4GHz, Asus P4S800D-X mobo, 4GB RAM, 160GB Western Digital HD, nVidia GeForce FX-6200 video card

  9. #9
    Join Date
    Feb 2007
    Location
    /home/paris
    Beans
    690
    Distro
    Lubuntu 12.10 Quantal Quetzal

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    Stormbringer,

    Just a note to see if you have any idea about a problem I am getting, I'm going to post a new thread also on the same thing, but I think you may have an idea as I get the feeling that it is samba related.

    so....

    The situation.

    I'm happily sitting in front of my pc and working on some programming stuff, when suddenly I get a major slow down of the pc (it won't even respond to keystroke inputs for about 15 mins).

    Eventually I pull the power - it seems to be the only solution! (bear with me here people I'm about to get to the point.... ).

    So after I've rebooted I look into my various system logs and I find these messages

    Jan 9 11:57:58 Anticlimax smbd[7533]: create_builtin_users: Failed to create Users
    Then a little later I see these in the log files

    Jan 9 12:44:29 Anticlimax nmbd[5571]: *****
    Jan 9 12:44:29 Anticlimax nmbd[5571]:
    Jan 9 12:44:29 Anticlimax nmbd[5571]: Samba name server ANTICLIMAX is now a local master browser for workgroup IRREDUTIBLES on subnet 134.157.195.129
    Jan 9 12:44:29 Anticlimax nmbd[5571]:
    Jan 9 12:44:29 Anticlimax nmbd[5571]: *****
    Jan 9 12:44:29 Anticlimax nmbd[5571]: [2009/01/09 12:44:29, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fa il(351)
    Jan 9 12:44:29 Anticlimax nmbd[5571]: find_domain_master_name_query_fail:
    Jan 9 12:44:29 Anticlimax nmbd[5571]: Unable to find the Domain Master Browser name IRREDUTIBLES<1b> for the workgroup IRREDUTIBLES.
    Jan 9 12:44:29 Anticlimax nmbd[5571]: Unable to sync browse lists in this workgroup
    so now I'm curious and try to see when all this started, I've noticed that the inability to find the workgroup is persistent, and don't know how to solve this, our local domain name is irredutibles (or at least that is what the boss has called it) is there anything I can do to confirm it's presence and that he isn't just "giving it a name" that doesn't really exist except for in the teams computers?

    Also on further investigation I find this

    Jan 9 10:22:12 Anticlimax nmbd[5609]: [2009/01/09 10:22:12, 0] nmbd/nmbd_incomingdgrams.crocess_local_master_announce(309)
    Jan 9 10:22:12 Anticlimax nmbd[5609]: process_local_master_announce: Server ASTERIX at IP 134.157.195.68 is announcing itself as a local master browser for workgroup IRREDUTIBLES and we think we are master. Forcing election.
    Jan 9 10:22:12 Anticlimax nmbd[5609]: [2009/01/09 10:22:12, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(14 9)
    Jan 9 10:22:12 Anticlimax nmbd[5609]: *****
    Jan 9 10:22:12 Anticlimax nmbd[5609]:
    Jan 9 10:22:12 Anticlimax nmbd[5609]: Samba name server ANTICLIMAX has stopped being a local master browser for workgroup IRREDUTIBLES on subnet 134.157.195.1
    Jan 9 10:22:12 Anticlimax nmbd[5609]:
    Jan 9 10:22:12 Anticlimax nmbd[5609]: *****
    Jan 9 10:22:25 Anticlimax nmbd[5609]: [2009/01/09 10:22:25, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
    Jan 9 10:22:25 Anticlimax nmbd[5609]: *****
    Jan 9 10:22:25 Anticlimax nmbd[5609]:
    Jan 9 10:22:25 Anticlimax nmbd[5609]: Samba name server ANTICLIMAX is now a local master browser for workgroup IRREDUTIBLES on subnet 134.157.195.1
    Jan 9 10:22:25 Anticlimax nmbd[5609]:
    Jan 9 10:22:25 Anticlimax nmbd[5609]: *****
    Jan 9 10:22:25 Anticlimax nmbd[5609]: [2009/01/09 10:22:25, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fa il(351)
    Jan 9 10:22:25 Anticlimax nmbd[5609]: find_domain_master_name_query_fail:
    Jan 9 10:22:25 Anticlimax nmbd[5609]: Unable to find the Domain Master Browser name IRREDUTIBLES<1b> for the workgroup IRREDUTIBLES. .
    which ties in perfectly with the time my system slow down started, for information ASTERIX is another pc with shared drives (it happens to be an XP machine

    I found some information on this here but I don't know what I need to change to set my pc as a "client" to stop it talking to the other system.

    Your help is much appreciated.

    David
    Eee pc via Wubi install.
    evertying works straight out of the box

    My Launchpad page

  10. #10
    Join Date
    Mar 2006
    Location
    Kitakyushu Japan
    Beans
    9,361
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: HOWTO: Setup Samba peer-to-peer with Windows

    Quote Originally Posted by theDaveTheRave View Post
    I found some information on this here but I don't know what I need to change to set my pc as a "client" to stop it talking to the other system.

    Your help is much appreciated.

    David
    I wasn't too sure how to interpret that post either, but after reading the "domain master" section of man smb.conf (several times) it became clear.

    Note that Windows NT Primary Domain Controllers expect to be able to claim this workgroup specific special NetBIOS name that identifies them as domain master browsers for that workgroup by default (i.e. there is no way to prevent a Windows NT PDC from attempting to do this). This means that if this parameter is set and nmbd claims the special name for a workgroup before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail.
    Add:
    Code:
    domain master = no
    to the [global] section of your smb.conf

Page 1 of 38 12311 ... LastLast

Bookmarks

Posting Permissions

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