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

    SAMBA with mixed network/workgroup... Nothing so far.

    I have been reading for the last several hours on many different forums, and cannot find anything directly applying to my problem.

    I am running FC2 on a mainly windowsXP LAN. I have installed samba as shown below;
    [root@host root]# rpm -qa | grep samba
    I CAN ping other machines on the network by their IP and their NETBIOS names. However, none of the windoze machines can see the linux box (network neighborhood) and the linux box cannot see the windows boxes (Network Servers app)

    If I disable the firewall, I start getting results both ways. ( I can see the workgroup but not access it from the linux box... I can see my shared folders on the linux box, but I cannot write to them) So, I followed the advice on one of the posts I found here to include 137-139TCP/UDP into the firewall permitted connections area. This was not the problem, since re-enabling the firewall with the new config still blocks the samba traffic.

    I went into SWAT to take a look around, but I cannot find anything wrong. Here is what swat has to say about the setup. (I'm sorry. But, I don't know what's important or not. So here's the whole file.)

    # Samba config file created using SWAT
    # from (
    # Date: 2004/07/17 20:19:58

    # Global parameters
    dos charset = CP850
    unix charset = UTF-8
    display charset = LOCALE
    workgroup = SANTORINI
    realm =
    netbios name = SANTORSERV
    netbios aliases =
    netbios scope =
    server string = Santorini Server
    interfaces =
    bind interfaces only = No
    security = USER
    auth methods =
    encrypt passwords = Yes
    update encrypted = No
    client schannel = Auto
    server schannel = Auto
    allow trusted domains = Yes
    hosts equiv =
    min passwd length = 5
    map to guest = Never
    null passwords = No
    obey pam restrictions = No
    password server = None
    smb passwd file = /etc/samba/smbpasswd
    private dir = /etc/samba
    passdb backend = smbpasswd
    algorithmic rid base = 1000
    root directory =
    guest account = nobody
    pam password change = No
    passwd program =
    passwd chat = *new*password* %n\n *new*password* %n\n *changed*
    passwd chat debug = No
    passwd chat timeout = 2
    username map = /etc/samba/smbusers
    password level = 0
    username level = 0
    unix password sync = No
    restrict anonymous = 0
    lanman auth = Yes
    ntlm auth = Yes
    client NTLMv2 auth = No
    client lanman auth = Yes
    client plaintext auth = Yes
    preload modules =
    log level = 0
    syslog = 1
    syslog only = No
    log file = /var/log/samba/%m.log
    max log size = 50
    timestamp logs = Yes
    debug hires timestamp = No
    debug pid = No
    debug uid = No
    smb ports = 445 139
    protocol = NT1
    large readwrite = Yes
    max protocol = NT1
    min protocol = CORE
    read bmpx = No
    read raw = Yes
    write raw = Yes
    disable netbios = No
    acl compatibility =
    nt pipe support = Yes
    nt status support = Yes
    announce version = 4.9
    announce as = NT
    max mux = 50
    max xmit = 16644
    name resolve order = lmhosts wins host bcast
    max ttl = 259200
    max wins ttl = 518400
    min wins ttl = 21600
    time server = No
    unix extensions = Yes
    use spnego = Yes
    client signing = auto
    server signing = No
    client use spnego = Yes
    change notify timeout = 60
    deadtime = 0
    getwd cache = Yes
    keepalive = 300
    kernel change notify = Yes
    lpq cache time = 10
    max smbd processes = 0
    paranoid server security = Yes
    max disk size = 0
    max open files = 10000
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    use mmap = Yes
    hostname lookups = No
    name cache timeout = 660
    load printers = Yes
    printcap name = /etc/printcap
    disable spoolss = No
    enumports command =
    addprinter command =
    deleteprinter command =
    show add printer wizard = Yes
    os2 driver map =
    mangling method = hash2
    mangle prefix = 1
    stat cache = Yes
    machine password timeout = 604800
    add user script =
    delete user script =
    add group script =
    delete group script =
    add user to group script =
    delete user from group script =
    set primary group script =
    add machine script =
    shutdown script =
    abort shutdown script =
    logon script =
    logon path = \\%N\%U\profile
    logon drive =
    logon home = \\%N\%U
    domain logons = No
    os level = 20
    lm announce = Auto
    lm interval = 60
    preferred master = Auto
    local master = Yes
    domain master = Auto
    browse list = Yes
    enhanced browsing = Yes
    dns proxy = No
    wins proxy = No
    wins server =
    wins support = No
    wins hook =
    wins partners =
    kernel oplocks = Yes
    lock spin count = 3
    lock spin time = 10
    oplock break wait time = 0
    ldap suffix =
    ldap machine suffix =
    ldap user suffix =
    ldap group suffix =
    ldap idmap suffix =
    ldap filter = (uid=%u)
    ldap admin dn =
    ldap ssl =
    ldap passwd sync = no
    ldap delete dn = No
    ldap replication sleep = 1000
    add share command =
    change share command =
    delete share command =
    config file =
    preload =
    lock directory = /var/cache/samba
    pid directory = /var/run
    utmp directory =
    wtmp directory =
    utmp = No
    default service =
    message command =
    dfree command =
    get quota command =
    set quota command =
    remote announce =
    remote browse sync =
    socket address =
    homedir map = auto.home
    afs username map =
    time offset = 0
    NIS homedir = No
    panic action =
    host msdfs = No
    enable rid algorithm = Yes
    idmap backend =
    idmap uid = 16777216-33554431
    idmap gid = 16777216-33554431
    template primary group = nobody
    template homedir = /home/%D/%U
    template shell = /bin/false
    winbind separator = \
    winbind cache time = 300
    winbind enable local accounts = Yes
    winbind enum users = Yes
    winbind enum groups = Yes
    winbind use default domain = No
    winbind trusted domains only = No
    winbind nested groups = No
    comment =
    path =
    username =
    invalid users =
    valid users =
    admin users =
    read list =
    write list =
    printer admin =
    force user =
    force group =
    read only = Yes
    create mask = 0744
    force create mode = 00
    security mask = 0777
    force security mode = 00
    directory mask = 0755
    force directory mode = 00
    directory security mask = 0777
    force directory security mode = 00
    inherit permissions = No
    inherit acls = No
    guest only = No
    guest ok = Yes
    only user = No
    hosts allow =
    hosts deny =
    ea support = No
    nt acl support = Yes
    profile acls = No
    map acl inherit = No
    afs share = No
    block size = 1024
    max connections = 0
    min print space = 0
    strict allocate = No
    strict sync = No
    sync always = No
    use sendfile = No
    write cache size = 0
    max reported print jobs = 0
    max print jobs = 1000
    printable = No
    printing = cups
    cups options =
    print command =
    lpq command =
    lprm command =
    lppause command =
    lpresume command =
    queuepause command =
    queueresume command =
    printer name =
    use client driver = No
    default devmode = No
    default case = lower
    case sensitive = No
    preserve case = Yes
    short preserve case = Yes
    mangle case = No
    mangling char = ~
    hide dot files = Yes
    hide special files = No
    hide unreadable = No
    hide unwriteable files = No
    delete veto files = No
    veto files =
    hide files =
    veto oplock files =
    map system = No
    map hidden = No
    map archive = Yes
    mangled names = Yes
    mangled map =
    store dos attributes = No
    browseable = Yes
    blocking locks = Yes
    csc policy = manual
    fake oplocks = No
    locking = Yes
    oplocks = Yes
    level2 oplocks = Yes
    oplock contention limit = 2
    posix locking = Yes
    strict locking = Yes
    share modes = Yes
    copy =
    include =
    exec =
    preexec close = No
    postexec =
    root preexec =
    root preexec close = No
    root postexec =
    available = Yes
    volume =
    fstype = NTFS
    set directory = No
    wide links = Yes
    follow symlinks = Yes
    dont descend =
    magic script =
    magic output =
    delete readonly = No
    dos filemode = No
    dos filetimes = No
    dos filetime resolution = No
    fake directory create times = No
    vfs objects =
    msdfs root = No
    msdfs proxy =

    comment = Home Directories
    read only = No
    browseable = No

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

    comment = Ken
    path = /home/kenneth
    read only = No

    comment = Web Folder
    path = /var/www
    read only = No

    Can anyone see what's going on here? Because I can't.

    Any help would be appreciated if not fairly compensated.

    SteedVLX [/quote]

  2. #2
    Just Joined!
    Join Date
    Jun 2004
    Leiria - Portugal

    All is important

    Once defined the whole file is important...

    One by one all strings are very important so take carefuly.

    test your file with testparm smb.conf and see the errors...

    On a Windows XP machine the most important is the war of wins master browsing....

    Set you server the master browser, you have to change some regitry strings also...

    Serach at gooogle, search at old posts here...

    Good info is everywhere, just have to know what to search....

    Sory my english

  3. #3

    Thank you for replying. I really do appreciate the attempt.

    However, I have been unable to determine what is meant by WINS. I've never used it. But, I will continue to look anyway.

    I apologize for my frustration. But, windows is looking easier and cheaper by the moment. I've spent a fortune on useless geek-ese books this past month. They may have the answer in there, but they always leave out important steps that they 'assume' you already know how to do.

    I will, however, do a search for WINS master browsing and see if anything useful turns up.

    Thanks in advance,

    EDIT: I have just came back from trying one of the partial solutions offered in another Samba thread. The instructions offered at www.yellobugcomputers/techdocs/sambadomain.html were somewhat helpful... I can now see and write to my linux shared directories from the windows XP systems. However, I am still unable to browse the workgroup from the linux box. I get an error alert "The Folder Contents Could Not Be Displayed: Couldn't display the contents of Windows Network: sardius".

    I have noted that the linux box repeatedly refers to the workgroup as "sardius", when in fact I have changed it many times to "SARDIUS". Isn't this a case-sensitive entry? Shouldn't it save it exactly as I enter it?

    That's all I know for now. Any additional help is appreciated.

    RH FC2 (2.6.xx core)

    Post edited for tone. Didn't like the way my original comments came off in writing.

  4. $spacer_open
  5. #4

    I have completed my 'research' on WINS. As it turns out, I don't need it. All of my systems are on the same subnet. Therefore WINS resolution would just a redundant service.

    I have set up all of my Samba machine accounts by IP address and Workstation name. So, unless I'm missing something important, there should be no need to supplement NetBios translations with WINS resolution service.


    As it stands now...

    I have completed the configuration of the XP boxes to logon to the Samba service. From XP--->Linux, it works fine including user-based permissions. However, Linux--->XP just ain't happening. My server cannot 'see' the rest of the workgroup from the Network interface even though terminal pings to the IP and Workstation name are good. Shouldn't I be able to see them?

    Am I misunderstanding the purpose of Samba? Does Samba provide linux to Windows file services? Or is it just so Windows machines can 'see' the Linux file system?


  6. #5
    Just Joined!
    Join Date
    Jun 2004
    Leiria - Portugal

    Not at all...

    Once activated samba provide file sharing betwen linux and windows systems, and in both directions...

    It just depends on the configurations of the program you're using to browse your network and the users/permisisons you're using to mount the shares.

    And about wins, yes it is a redundant microsoft only service, and yes it degenerate your nework performance if not well configured.

    See you...

  7. #6
    Well, thanks again for the reply.

    However, I have officially given up. I guess my brain is just too old for this stuff. I simply couldn't find the information I needed, and when I did find information on the subject at hand, it was just too far over my head to do me any good. And, most of the time it just led me to more things that I had to know before I could understand what I was reading.

    I got pretty far though for a newbie. The killer was when I tried to install the LAMP combination and everytime I thought I had something installed, it failed to initialize this or start that service because of this, that or the other thing.

    Until it becomes where you don't need a phD to configure your own server. I guess I'm just out of luck.

    Windows secure server configured and online in less than 5 hours. I guess that shows where my ten years of experience have been spent. The problem is, how long will it stay online this time? And, how many virus crisis will I have to endure.

    I wish I could figure this Linux bird out. It really does seem to be the best thing going.

    I'm keeping one box with RH installed. When I have time, I can experiment and learn it slowly.

    Thanks for those who have tried to help me on this and other forums.

    I'll be back!!


  8. #7
    Linux Guru kkubasik's Avatar
    Join Date
    Mar 2004
    Lat: 39:03:51N Lon: 77:14:37W
    You could just try a samba client suc has smb4k and then mount each computer via ip in a folder, then the browsing is irrelivent as the filesystem is mounted, just copy the file to your box, edit, and upload.
    Avoid the Gates of Hell. Use Linux
    A Penny for your Thoughts

    Formerly Known as qub333

  9. #8
    Just Joined!
    Join Date
    Sep 2004
    aurora, Illinois,U.S.A.

    folder contents could not be displayed

    steedvlx, I am having the same problem. My MS and Linux networking was working fine, and then I applied the XP release 2 fixes to the PCs. Now My PCs network OK and they see the files on the Linux machine, but I cannot access the PC files from the Linux box. I get the "The file contents could not be displayed" error message.

    I have had these kinds of problems before. Whenever I do an upgrade of either MS or Linux the first thing that seems to break is the networking. I have fixed it before, and will post the fix when I remember how to do it.

  10. #9
    This is hilarious indeed because I have the exact same situation and problem. I have linux box and an xp box connected via a router. I tried with samba and gnome but had little luck. I actually got much further with KDE using a LISa daemon and samba, but still didn't quite get it.

    I have been trying to do this for weeks. I have 3 750 page books in front of me but it seems no one would ever think you might want to connect a linux box to an windows box through a router. There is a lot of things I like about linux. and a lot of things I really dont care for.

  11. #10
    Hi. This sounds just like the problem that I'm having - and I'm starting to tear my hair out now....

    I have 3 PCs, one running Linux and the other 2 Win XP Pro. All are connected through a combined ADSL modem/switch/router. The router is also acting as the DHCP server (I don't always have my Linux PC running so this makes sense).

    What I have found is that if I use DHCP for ther Linux box to get an address, then all works fine. My Windows PC's can see the linux box both by IP and name. However, as soon as I switch the Linux box to use a static IP, the Windows PC's can now no longer reference the Linux box by name - only by IP...

    I want the static IP as I want to run a webserver from the box that is to be accessible through my internet connection. And this works fine. But, I also want to be able to use SAMBA to access the Linux PC's drives from my Windows PC...

    Anyone out there got any more thoughts on this please? It really shouldn't be this hard - and I bet it's something stupid that I've missed....

    Thanks in advance for any help

Posting Permissions

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