Announcement

Collapse
No announcement yet.

[Solved]Small (big) samba issue

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [Solved]Small (big) samba issue

    Okay I have winxp running under vmware WS/player and sharing files with samba perfectly under edgy.

    Now I thought okay, lets try this under feisty.
    So I copied the /etc/samba/smb.conf file from edgy to feisty, changed the user names approprietly, set up my shares and users exactly as in edgy, and changed the computername to the same one as edgy so I didn't have to fool around with changing to winxp network setup.
    I do a sudo /etc/init.d/samba restart then try and find my shares respect. open them in Konqueror / Networkfiles /sambashares and get this when clicking on a share:
    Die Datei oder der Ordner smb://fintanws2/DATA existiert nicht. Or in english:
    This file or directory smb://fintanws2/Data does not exsist or something to that extent.
    A reboot does not help either.

    I can see my workgroup, winxp sees it as well but I cannot access the files on the share.

    I have looked around here but to no avail.

    Am I missing something??

    EDIT: I just rebooted because I wanted to check my edgy settings again. After reboot I get this from konqueror/networkfiles/sambashares:
    Es ist keine Arbeitsgruppe im lokalen Netzwerk auffindbar. Dies könnte durch eine aktivierte Firewall verursacht werden. Meaning: no workgroup available. This could be due to an active firewall.

    Well I don't have a firewall and my workgroup showed up before reboot. Wad up??

    Here's my /etc/samba/smb.conf just for reference:
    #======================= Global Settings =======================

    [global]

    ## Browsing/Identification ###

    # Change this to the workgroup/NT-domain name your Samba server will part of
    workgroup = FINTANHOME



    # server string is the equivalent of the NT Description field


    # 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 = true



    #### Debugging/Accounting ####

    # 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 = 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/Samba-HOWTO-Collection/ServerType.html
    # in the samba-doc package for details.
    ; security = share

    # You may wish to use password encryption. See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
    encrypt passwords = no

    # 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

    ; guest account = nobody
    invalid users = root

    # 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 = no

    # For Unix password sync to work on a Debian GNU/Linux system, the following
    # parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
    # sending the correct chat script for the passwd program in Debian Sarge).
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\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 = no

    ########## 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
    ; 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

    ########## 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 manpage in the
    # cupsys-client package.
    ; printing = cups
    ; printcap name = cups

    # When using [print$], root is implicitly a 'printer admin', but you can
    # also give this right to other users to add drivers and set printer
    # properties
    ; printer admin = @lpadmin


    ############ 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/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
    printer name = HP880C
    restrict anonymous = no
    domain master = no
    preferred master = no
    max protocol = NT
    ldap ssl = No
    server signing = Auto
    acl compatibility = win2k

    # 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

    #======================= 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 directory as \\server\username
    ;[homes]
    ; comment = Home Directories
    ; browseable = no

    # 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
    ; valid users = %S

    # By default, the home directories are exported read-only. Change next
    # parameter to 'yes' if you want to be able to write to them.
    ; writable = no

    # File creation mask is set to 0600 for security reasons. If you want to
    # create files with group=rw permissions, set next parameter to 0664.
    ; create mask = 0600

    # 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

    # 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
    ; writable = no
    ; 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 = no
    ; create mask = 0600
    ; directory mask = 0700


    [Data]
    path = /Data/
    guest ok = yes
    read only = no
    valid users = fintan2,root
    write list = root
    admin users = fintan2
    force user = fintan2
    force group = fintan2
    case sensitive = no
    only user = yes
    msdfs proxy = no
    strict locking = yes
    msdfs root = no
    delete readonly = yes

    [HP880C]
    printing = cups
    path = /var/tmp
    printable = yes
    guest ok = yes
    guest only = yes

    [WINDOWS]
    path = /Windows/
    guest ok = yes
    read only = no
    admin users = root
    force user = fintan2
    force group = fintan2
    case sensitive = no
    msdfs proxy = no


    Some more reference:
    computername: xyzws2
    workgroup FINTANHOME
    Network connection: DHCP (have had no problems with that under edgy)

    Is samba for feisty not quite ready yet?

    Using sm4k is useless as well because after a search it will find the workgroup but then it asks me for a user and password. None have been defined and my user/sudo passwords don't work.

    EDIT: As I stated I can see the workgroup and the workstation (computername xyzws2) in kongueror by doing smb:/ but trying to open Data still gives file or directory smb://xyzws2/Data does not exsist.

    The only difference that I can see between my edgy and feisty smb is in the fstab where all hda's in edgy are replaced by sda's in feisty. Could this be the problem??

    I am at a loss. >

    Any sugestions are really greatly app.

    Cheers
    fintan
    HP Pavilion dv6 core i7 (Main)
    4 GB Ram
    Kubuntu 18.10

    #2
    Re: Small (maybe big) samba issue

    I am having exactly the same problem. > I am using edgy in a othrwise windows home network. I have everything set up to work with edgy and I have had no problems. So as a lazy person I copied my smb.conf over to feisty and set up my shares etc. exactly the same way. But I cannot connect to the other machines.

    As I would like to port my home smb settings into my office environememnt it would be a great help to get a few ideas on this here.
    I suppose I could still use edgy but feisty has proven better in identifying hardware and a few other issues.

    Anyone??

    Comment


      #3
      Re: Small (maybe big) samba issue

      Well I am glad I am not alone :P

      Well anyway my testparm looks like this:
      fintan2@fintanws2:~$ sudo testparm
      Load smb config files from /etc/samba/smb.conf
      Processing section "[Data]"
      WARNING: The "only user" option is deprecated
      Processing section "[HP880C]"
      Processing section "[WINDOWS]"
      Loaded services file OK.
      Server role: ROLE_STANDALONE
      Press enter to see a dump of your service definitions

      [global]
      workgroup = FINTANHOME
      encrypt passwords = No
      obey pam restrictions = Yes
      passdb backend = tdbsam
      passwd program = /usr/bin/passwd %u
      passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
      syslog = 0
      log file = /var/log/samba/log.%m
      max log size = 1000
      acl compatibility = win2k
      server signing = auto
      preferred master = No
      domain master = No
      dns proxy = No
      ldap ssl = no
      panic action = /usr/share/samba/panic-action %d
      printer name = HP880C

      [Data]
      path = /Data/
      valid users = fintan2, root

      and is identical to my edgy testparm

      I also looked at this:
      https://launchpad.net/ubuntu/+source/samba/+bugs

      and tried this:
      https://bugs.launchpad.net/ubuntu/+s...mba/+bug/32067
      good read

      and this:
      https://bugs.launchpad.net/ubuntu/+s...mba/+bug/19470

      but no great help in this situation

      smb://fintanws2/Data still tells me it doesen't exsist.

      Just for the hell of it I did this:
      fintan2@fintanws2:~$ sudo mkdir /Data
      Password:
      mkdir: kann Verzeichnis „/Data“ nicht anlegen: File exists
      fintan2@fintanws2:~$

      Same sh..., different day

      Getting upset >
      HP Pavilion dv6 core i7 (Main)
      4 GB Ram
      Kubuntu 18.10

      Comment


        #4
        Re: Small (maybe big) samba issue

        Okay I did a fresh install, I like the new partitioner
        Anyway after installing all the samba and smb stuff and editing my smb.config to equal the edgy one (which still works there). I do smb:/ in kongueror and can see my workgroup and my computer. It also shows the shares. But trying to open them gives me: smb://gandolf1/myfiles does not exsist.
        Here is a reduced copy thanks to the (penguine.ch) of my smb.conf:
        [global]

        workgroup = gandolfhome
        interfaces = eth0
        security = share
        map to guest = bad user

        [Myfiles]

        path = /myfiles
        read only = no
        wide links = no
        username = gandolf
        create mask = 0644
        guest ok = yes
        case sensitive = no
        strict locking = no
        msdfs proxy = no

        [HP995C]

        printing = cups
        path = /var/tmp
        printable = yes
        guest ok = yes
        guest only = yes

        bythw if I change :
        security = share to
        security = user

        I get a loginscreen whereby my logins don't work and after canceling I get: you are not authorized to open smb://gandolf1/myfiles or something to that effect. so what is it does it exsit or doesen't it. and why am I not authorized, I mean if it exsists?

        Of course it exsists, I use that directory (/dev/hda7 mounted as /myfiles) all the time after all it has all of my data on it.

        I am going nuts.

        Comment


          #5
          Re: Small (maybe big) samba issue

          I read this but it didn't help. http://kubuntuforums.net/forums/inde...082098.new#new

          I'll be doing a fresh feisty install tonight. I thought updating my beta was good enough. Maybe not. I am not upgrading my edgy, still need it until this sh....t gets sorted >
          HP Pavilion dv6 core i7 (Main)
          4 GB Ram
          Kubuntu 18.10

          Comment


            #6
            Small (maybe big) samba issue

            I trolled through a few googles and came up with this:

            https://bugs.launchpad.net/ubuntu/+s...mba/+bug/95460
            samba 3.0.24 on feisty is broken


            Wow: In your /etc/samba/smb.conf you have to comment out the line:
            msdfs proxy=no (or yes) to look like this:
            # msdfs proxy=no (or yes)
            It doesen't matter if it is yes or no, just comment it out.
            Do sudo /etc/init.d/samba restart
            and
            sudo testparm and the shares work again. way 8)

            I hope this helps the rest who are having a problem with samba and shares.

            HP Pavilion dv6 core i7 (Main)
            4 GB Ram
            Kubuntu 18.10

            Comment


              #7
              Re: [Solved]Small (big) samba issue

              Thanks Fintan, that helped but now eventhough I can see my shares in winxp(vmwarews) I only have read access. here ist my edited version of smb.conf:
              [global]

              workgroup = gandolfhome
              interfaces = eth0
              security = share
              map to guest = bad user

              [Myfiles]

              path = /myfiles
              read only = no
              wide links = no
              username = gandolf
              create mask = 0664
              directory mask = 0775
              guest ok = yes
              case sensitive = no
              strict locking = no
              msdfs proxy = no

              [HP995C]

              printing = cups
              path = /var/tmp
              printable = yes
              guest ok = yes
              guest only = yes

              Any ideas?

              Comment


                #8
                Re: [Solved]Small (big) samba issue

                Try this:
                unmount all shares, reboot, remount the shares, give them rw and reboot again.
                Should work, did with me

                Your smb.config looks ok though.
                HP Pavilion dv6 core i7 (Main)
                4 GB Ram
                Kubuntu 18.10

                Comment

                Working...
                X