Announcement

Collapse
No announcement yet.

How Do I Fix Samba?

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

    How Do I Fix Samba?

    I have several Windows XP machines that need to access the printer attached to my Feisty Fawn desktop. Samba is set up. In the "Printers" menu (Printer Server sub menu), "Share printers on local network" is checked.

    On the XP clients, my Kubuntu box shows up in Network Neighborhood. A file share I set up shows as well. There is a folder called "Printers and Faxes". When clicking on that, you only get a blank (empty) directory.

    How do I get this to work? Thanks in advance.

    Ernie Grossmann<br />Opening doors, closing Windows.......<br />AMD Athlon X2<br />Asus K8, 2 GB PC 3200 RAM<br />Using Kubutu 10.10

    #2
    Re: How Do I Fix Samba?

    To start "somewhere": did you check that the netmasks of all systems involved are matching up (- different from all other systems I know, Kubuntu defaults to 255.255.0.0 instead of 255.255.255.0 ...).

    Comment


      #3
      Re: How Do I Fix Samba?

      Originally posted by UnicornRider
      To start "somewhere": did you check that the netmasks of all systems involved are matching up (- different from all other systems I know, Kubuntu defaults to 255.255.0.0 instead of 255.255.255.0 ...).
      Yes, my IP/mask are correct. Plus (as mentioned above), Samba is partially working -- my shared directories are visible. I just can't add a printer on the Windows clients because they don't see one available.
      Ernie Grossmann<br />Opening doors, closing Windows.......<br />AMD Athlon X2<br />Asus K8, 2 GB PC 3200 RAM<br />Using Kubutu 10.10

      Comment


        #4
        Re: How Do I Fix Samba?

        In this case, you may want to check the sharing of the printers by issuing testparm on the server.

        --

        Further Reading: Troubleshooting (Samba)

        Comment


          #5
          Re: How Do I Fix Samba?

          Originally posted by UnicornRider
          In this case, you may want to check the sharing of the printers by issuing testparm on the server.

          --

          Further Reading: Troubleshooting (Samba)
          testparm says everything is okay. The link to samba.org was too confusing -- I didn't really understand using some of those tools.

          I just don't understand why the folders show up and the printer does not. I can post my smb.conf and cups.conf files if it's helpful.
          Ernie Grossmann<br />Opening doors, closing Windows.......<br />AMD Athlon X2<br />Asus K8, 2 GB PC 3200 RAM<br />Using Kubutu 10.10

          Comment


            #6
            Re: How Do I Fix Samba?

            [quote=ernieg92]
            The ]

            Lame excuses :P

            Originally posted by ernieg92
            I just don't understand why the folders show up and the printer does not.
            I dare say the "printer share" fails to share anything, let alone a printer ...

            Be that as it may - could you please post the dump offered by testparm?

            Comment


              #7
              Re: How Do I Fix Samba?

              Originally posted by UnicornRider
              I dare say the "printer share" fails to share anything, let alone a printer ...

              Be that as it may - could you please post the dump offered by testparm?
              Ok, here is the results of testparm, including the dump:
              Code:
              ernie@famlin-pc-01u:~$ sudo testparm
              Password:
              Load smb config files from /etc/samba/smb.conf
              Processing section "[printers]"
              Processing section "[print$]"
              Processing section "[APPS]"
              Loaded services file OK.
              Server role: ROLE_STANDALONE
              Press enter to see a dump of your service definitions
              
              [global]
                  workgroup = MYWRKGRP
                  server string = %h (Samba, Ubuntu)
                  security = SHARE
                  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 = winnt
                  server signing = auto
                  preferred master = No
                  domain master = No
                  dns proxy = No
                  ldap ssl = no
                  panic action = /usr/share/samba/panic-action %d
                  invalid users = root
              
              [printers]
                  comment = All Printers
                  path = /var/spool/samba
                  create mask = 0700
                  printable = Yes
                  browseable = No
              
              [print$]
                  comment = Printer Drivers
                  path = /var/lib/samba/printers/
                  guest ok = Yes
                  case sensitive = No
                  strict locking = No
                  msdfs proxy = no
              
              [APPS]
                  path = /home/ernie/apps/
                  guest ok = Yes
              ernie@famlin-pc-01u:~$
              Now here is the funny thing -- check out the "printers" section of smb.conf:
              Code:
              [printers]
              comment = All Printers
              browseable = yes
              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/
              guest ok = yes
              case sensitive = no
              strict locking = no
              msdfs proxy = no
              Where would testparm get the "browseable=no" from, since it is allowed in smb.conf? I can post the entire smb.conf, but I didn't modify anything other than the Workgroup name and the "browseable" under "Printers". (Note, the testparm was run immediately after a reboot; the smb.conf was modified yesterday to make browseable. I even stopped/restarted Samba to make sure; same results.)

              Hope that helps you help me!




              Ernie Grossmann<br />Opening doors, closing Windows.......<br />AMD Athlon X2<br />Asus K8, 2 GB PC 3200 RAM<br />Using Kubutu 10.10

              Comment


                #8
                Re: How Do I Fix Samba?

                Originally posted by ernieg92
                create mask = 0700
                msdfs proxy = no
                For starters, you may want to eliminate the two records quoted above, as the former creates a "root only" share (not very useful ...), and the latter is simply crap (introduced by the "Kubunties" ...).

                --

                The other half of this cross-posted, therefore broken-off thread:
                http://kubuntuforums.net/forums/inde...opic=3084153.0

                Comment


                  #9
                  Re: How Do I Fix Samba?

                  Originally posted by UnicornRider
                  Originally posted by ernieg92
                  create mask = 0700
                  msdfs proxy = no
                  For starters, you may want to eliminate the two records quoted above, as the former creates a "root only" share (not very useful ...), and the latter is simply crap (introduced by the "Kubunties" ...).

                  --

                  The other half of this cross-posted, therefore broken-off thread:
                  http://kubuntuforums.net/forums/inde...opic=3084153.0
                  Ok, I removed those entries and restarted samba. Still says "Browseable=No" even though smb.conf says Yes. Any more thoughts?
                  Ernie Grossmann<br />Opening doors, closing Windows.......<br />AMD Athlon X2<br />Asus K8, 2 GB PC 3200 RAM<br />Using Kubutu 10.10

                  Comment

                  Working...
                  X