Announcement

Collapse
No announcement yet.

XP Pro and Kubuntu are fighting -SOLVED!!!!-

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

    XP Pro and Kubuntu are fighting -SOLVED!!!!-

    Looks like that darn butterfly is jacking with my pengoo again.

    I am trying to share a folder in my nix box to my XP box. -Yeah, I've searched, researched, tried a ton of trix, and no joy.- This is something I've done with every nix I've used; even back when Lynx was the browser of choice, and I am kinda stumped here. I know when I present this the answer will either jump in my face, or one of you fine people will give me the answer.

    Scenario.
    Fresh install a couple of days back, Beryl, nVidia, games, shared printer, all aok. I use my nix box for multi media fetching, editing, and other authoring functions. I find nix utils to be more friendly than M$ ones. So.. I share the working folder with my XP box because it is the gaming beast and has the 5.1 surround sound speakers, remote, and -stuff-.

    At first I got a dialog asking for user name/pass. I tried my user, root, made a user, nobody, guest, tried all I knew. No joy. Made the share 'guest' friendly and then the dialog went away. YIPPIE!! Click on the folder it says 'permissions error, ask admin about it, you can't be here, go away' dialog.

    Real life situation.
    I scanned/edited a bunch of pix with Gimp, made a 'movie' with music and transitions and such to play at a wedding. I went to stream it and the above boggles were encountered. I ended up burning it and playing it via the drive, which is what I want to avoid. This simple 'share' saves me a ton in CD's and time waiting for them to burn.

    I've included my smb.conf. ANY help would be VERY welcomed. Thanks in advance.
    Ed

    Code:
    #
    # 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
    #
    # 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 commentary 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]
    
    ## Browsing/Identification ###
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
    workgroup = edsnet
    
    # 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 = 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/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 = 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(8) 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/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
    restrict anonymous = no
    domain master = no
    preferred master = no
    max protocol = NT
    acl compatibility = winnt
    ldap ssl = No
    server signing = Auto
    security = share
    
    # 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
    
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printable = 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
    
    [shows]
    case sensitive = no
    strict locking = no
    guest ok = yes
    msdfs proxy = no
    path = /home/ed/shows/
    read only = no
    admin users = ed,nobody
    invalid users = 
    valid users = ed,nobody
    Dell SC1425<br />1 Xeon 3GHZ CPU<br />1GB ECC-DDR2 RAM<br />Onboard ATI Radeon 7000-M&nbsp; w/ 16MB Fixed/unshared RAM<br />Dual 82541Gl Gigabit Nic&#39;s<br />DVD-ROM/CD-RW Combo<br />73GB SCSI Drive.<br />Never got Compiz to run properly on the ATI, but that is secondary of course.

    #2
    Re: XP Pro and Kubuntu are fighting

    You could change:
    "; security = user"
    to:
    " security = share"

    Comment


      #3
      Re: XP Pro and Kubuntu are fighting

      OK, you can give me a virtual obscene gesture for asking the obvious, but you did add yourself to the authorized samba users using smbpasswd didn't you?

      Comment


        #4
        Re: XP Pro and Kubuntu are fighting

        You can read my trail, tribulations and a solution here:
        http://kubuntuforums.net/forums/inde...opic=3081879.0

        I hope that is usefull
        HP Pavilion dv6 core i7 (Main)
        4 GB Ram
        Kubuntu 18.10

        Comment


          #5
          Re: XP Pro and Kubuntu are fighting

          Originally posted by Fintan
          You can read my trail, tribulations and a solution here:
          http://kubuntuforums.net/forums/inde...opic=3081879.0

          I hope that is usefull
          I'm afraid it was no help for me. No matter what I try, the Windows and Feisty box can't see shares. I had Samba client and server working on Edgy. I even used the exact same smb.conf file someone else did...They got it working, I can't make it work. I can ping my windows machine and The SMB workgroup info on both machines match. I've read through a number of Samba How-Tos. I need some help with this.

          Comment


            #6
            Re: XP Pro and Kubuntu are fighting

            Still having no luck with this. Has anyone successfully shared folders IN Kubuntu WITH XP Pro?

            Thanks
            Dell SC1425<br />1 Xeon 3GHZ CPU<br />1GB ECC-DDR2 RAM<br />Onboard ATI Radeon 7000-M&nbsp; w/ 16MB Fixed/unshared RAM<br />Dual 82541Gl Gigabit Nic&#39;s<br />DVD-ROM/CD-RW Combo<br />73GB SCSI Drive.<br />Never got Compiz to run properly on the ATI, but that is secondary of course.

            Comment


              #7
              Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

              Sorry for the delay. Lifeus-interuptus. heehee. Actually, I bought a new meat smoker and have been playing with it.

              Anyhoo, just thought I'd say. I GOT IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

              I followed the link UR gave; sorry btw UR I was just grumpy that day and was not targeting you personally just the problem at hand, and copied the smb.conf there.

              I setup the share via right click on folder-share-ect...... Also, I used 'expert mode' to setup 'nobody' as the default user.

              THEN after it rewrote the smb.conf I edited it again, and removed.

              msdfs proxy = no

              JOY JOY HAPPY HAPPY JOY JOY YIPPIE!!!!!!!

              Thanks a TON for everyones help, thoughts, prayers, and loss of hair.
              -cheers-

              Here is a copy of my ENTIRE smb.conf, please not how 'short' it is compared to the broken/bloated/system written one.

              [global]

              workgroup = EDSNET
              interfaces = eth0
              map to guest = bad user

              [myDesk]

              path = /home/ed/Desktop
              read only = no
              wide links = no
              username = ed
              create mask = 0644

              [Epson]

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

              [SHOWS]
              path = /home/ed/Shows
              guest ok = yes
              read only = no
              case sensitive = no
              strict locking = no
              Dell SC1425<br />1 Xeon 3GHZ CPU<br />1GB ECC-DDR2 RAM<br />Onboard ATI Radeon 7000-M&nbsp; w/ 16MB Fixed/unshared RAM<br />Dual 82541Gl Gigabit Nic&#39;s<br />DVD-ROM/CD-RW Combo<br />73GB SCSI Drive.<br />Never got Compiz to run properly on the ATI, but that is secondary of course.

              Comment


                #8
                Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

                Thanks for sharing it, Ted. Probably it will help 100 others who are suffering in silence......

                Comment


                  #9
                  Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

                  Was a long trek my friend. However, as always, worth every step. I don't mind tweaking crap to make it work, just frustrated when it's a known issue and not fixed. But hey, I am just the Guy In Back. ROFL!!

                  I am off today btw, enjoying a vodka and rootbeer on this fine Canadian day. I am at 14 degrees with a 10km/h wind off and sun shine.. 14 is about 58..
                  -cheers-

                  p.s. It's my thread, I can hijack it if I want to. 8)
                  Dell SC1425<br />1 Xeon 3GHZ CPU<br />1GB ECC-DDR2 RAM<br />Onboard ATI Radeon 7000-M&nbsp; w/ 16MB Fixed/unshared RAM<br />Dual 82541Gl Gigabit Nic&#39;s<br />DVD-ROM/CD-RW Combo<br />73GB SCSI Drive.<br />Never got Compiz to run properly on the ATI, but that is secondary of course.

                  Comment


                    #10
                    Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

                    Originally posted by TedNigma
                    Here is a copy of my ENTIRE smb.conf, please not how 'short' it is compared to the broken/bloated/system written one.
                    Which is one of the reasons why, to set-up Samba properly, I keep recommending to "start from scratch": in doing so, you'll get a clearly laid out configuration - and in addition, once this works, you may even know why ...

                    Comment


                      #11
                      Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

                      Yeah, true enough. Strange the GUI does not actually MODIFY the config file though. Oh well, mine is not the question why, just to make it work. 8)
                      Dell SC1425<br />1 Xeon 3GHZ CPU<br />1GB ECC-DDR2 RAM<br />Onboard ATI Radeon 7000-M&nbsp; w/ 16MB Fixed/unshared RAM<br />Dual 82541Gl Gigabit Nic&#39;s<br />DVD-ROM/CD-RW Combo<br />73GB SCSI Drive.<br />Never got Compiz to run properly on the ATI, but that is secondary of course.

                      Comment


                        #12
                        Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

                        I had the same problem. Solution worked great ....thx for figuring it out Ted.

                        Now....shouldn't this solution be in a sticky post till a patch is offered?
                        Would save alot of needless exasperation.
                        I'd call this a major issue.

                        Comment


                          #13
                          Re: XP Pro and Kubuntu are fighting -SOLVED!!!!-

                          Hi guys,

                          ... and here is another little annoyance with Samba sharing - and I've now had this with three completely separate installations of Feisty (one upgrade, two fresh installs). I am also aware that some will not have this problem, but hopefully this will help keep others' hair where it belongs!

                          When creating a special (separate) user for shares (adduser etc.) followed by smbpasswd to allow the SMB to connect has always reported "unable to find USER in passdb backend".

                          The cure for me (in each and every case) is to "deluser USER", and then to recreate the same user using "adduser" (with exactly the same options - nothing is changed). "smbpasswd" then finds the user and asks for the password (if not already inserted in the smbpasswd command).

                          Don't ask why, but it appears the "deluser" command shakes the user database into alignment.

                          M.

                          Comment

                          Working...
                          X