Find the answer to your Linux question:
Results 1 to 4 of 4
I have 3 PCs, a XP client, a Linux SAMBA client and a Linux SAMBA WINS server. The XP client registers with the WINS server fine and I can see ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2011
    Posts
    3

    Linux SAMBA client does not register with SAMBA WINS server


    I have 3 PCs, a XP client, a Linux SAMBA client and a Linux SAMBA WINS server. The XP client registers with the WINS server fine and I can see the shares, but the WINS server does not respond to requests from the SAMBA client. I have looked at this with Wireshark and I can see requests coming in from both the XP and SAMBA clients but the server just does not respond to the SAMBA client requests - should I expect it to? This is very frustrating as the requests from both machines look very similar

    Looking at the registration requests from the two clients the only real difference I could see was that the XP client described itself as a 'workstation' whereas the SAMBA client described itself as a 'server'. But I don't understand why one and not the other is ignored though?

    Here are my 2 SMB.CONF files and if anyone can offer any advice I'd be very grateful.

    SERVER SMB.CONF

    [global]
    workgroup = esl
    server string = Bastion
    netbios name = Bastion

    interfaces = lo eth1 192.168.0.0/24
    bind interfaces only = yes
    hosts allow = 127. 192.168.0.

    # --------------------------- Logging Options -----------------------------
    log file = /var/log/samba/log.%m
    max log size = 50
    log level = 2

    # ----------------------- Standalone Server Options ------------------------

    security = user
    ; passdb backend = tdbsam

    # ----------------------- Domain Members Options ------------------------
    ; realm = MY_REALM
    ; password server = <NT-Server-Name>

    # ----------------------- Domain Controller Options ------------------------
    domain master = yes
    ; domain logons = yes

    # ----------------------- Browser Control Options ----------------------------
    local master = yes
    os level = 65
    preferred master = yes

    #----------------------------- Name Resolution -------------------------------
    wins support = yes
    wins proxy = no

    hostname lookups = yes
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

    # --------------------------- File System Options ---------------------------
    encrypt passwords = yes
    guest ok = yes
    ; guest account = nobody
    guest account = john
    ; store dos attributes = yes

    browse list = yes

    [homes]
    comment = Home Directories
    browseable = yes
    writable = yes
    valid users = %S
    ; valid users = MYDOMAIN\%S

    [Public]
    path = /home/john/Public
    read only = no
    browseable = yes
    guest ok = yes

    CLIENT SMB.CONF

    [global]
    workgroup = ESL
    netbios name = xl1
    server string = xl1
    security = user

    interfaces = lo eth0 192.168.0.0/24
    bind interfaces only = yes

    ; hosts allow = 127. 192.168.0.

    # --------------------------- Logging Options -----------------------------
    log level = 2

    # ----------------------- Standalone Server Options ------------------------
    ; passdb backend = tdbsam

    # ----------------------- Domain Controller Options ------------------------
    domain master = no

    # ----------------------- Browser Control Options ----------------------------
    local master = no
    os level = 30
    preferred master = no

    #----------------------------- Name Resolution -------------------------------
    wins server = 192.168.0.1
    wins proxy = no

    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

    # --------------------------- File System Options ---------------------------
    encrypt passwords = yes

    [homes]
    browseable = yes
    read only = no
    valid users = %S

    [export]
    path = /export
    read only = no
    browseable = yes
    guest ok = yes

    Really all I want is the XP machine to be able to see shares on both the Linux machines. Because I had access problems with what is now the SAMBA client I thought it might help to have a WINS server - how wrong can you be

    Anyhow, thanks in advance to anyone who can offer any advice.
    Graham
    Last edited by tripletipple; 03-06-2011 at 12:38 PM. Reason: More detail

  2. #2
    Linux Engineer rcgreen's Avatar
    Join Date
    May 2006
    Location
    the hills
    Posts
    1,134
    Try putting a line in the configuration file like this

    Code:
    name resolve order = wins lmhosts bcast host
    By default, wins is not the first method used in name resolution.

    [Chapter 7] 7.3 Name Resolution with Samba

  3. #3
    Just Joined!
    Join Date
    Mar 2011
    Posts
    3
    I will add that line in and give it a go. I suspect it won't actually solve the issue in this case as both clients seem to know to use WINS but it is the WINS server that does not seem to be playing ball. Looking through some past posts it does seem as if there has been the odd issue between SAMBA WINS servers and SAMBA clients.
    In my case it is not essential that I have a WINS server, so will probably go back to a more basic SAMBA setup. It was just frustrating that the WINS server seemed to behave oddly.

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Mar 2011
    Posts
    3
    Just to finish this off, I found in the end that my problems were caused by Linux SE (and possibly firewall issues). My Samba configuration now works.

Posting Permissions

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