Your smb.conf looks to have no errors. I see it was created with SWAT,
\nwhich usually sets things up without a hitch. Out of curiosity, why
\ndid you pick “security=SHARE”?
\nThere are a few lines I have in mine that I don’t see in yours (I
\nwill paste the relevant bits of mine at the end of the e-mail):
\n[global]
\n<\/p>\n
Your smb.conf looks to have no errors. I see it was created with SWAT,
\nwhich usually sets things up without a hitch. Out of curiosity, why
\ndid you pick “security=SHARE”?
\nThere are a few lines I have in mine that I don’t see in yours (I
\nwill paste the relevant bits of mine at the end of the e-mail):
\n[global]
\nprintcap name= lpstat
\nprintcap name = lpstat
\nprinting = cups (or BSD or whatever)<\/p>\n
[HP] (mine is called [printers] )
\npath = \/var\/spool\/samba (make sure this directory is chmod 1777)<\/p>\n
Question: You have your printer share named [HP] – is this the name of
\nyour print queue and has this changed between working \/ not working?
\nYou might add “read only = no” in there.<\/p>\n
The first thing I would suggest is to go to the Unofficial Samba Howto
\nhere: http:\/\/dennis_caparas.tripod.com\/samba_test.html
\n(There are other copies of it around the web, if you search for “Samba
\nHowto”) Follow all the tests in order, and see what you come up with.
\nThis will diagnose most Samba problems (and has worked well for me in
\nthe past).<\/p>\n
I forget if this is in the tests above, but make sure that the user on
\nthe Windows box has a valid samba user account and that the passwords
\nmatch.<\/p>\n
If these fail you, and they failed me last week, there are tests in a
\nbook called Samba Unleased published by SAMS, written by Steve Litt,
\net. al. I haven’t gotten through all of it yet, I just purchased it
\nyesterday. The chapter on troubleshooting printer problems is
\nexcellent. It approches things from a modular perspective to narrow
\ndown the cause of the problem & point of failure. I was able to
\ndiagnose & fix my printing problem in about an hour with this book,
\nwhere before I had tried the above link & Googled to no avail. My
\nproblem turned out to be samba not using the cups print system I had
\nsetup, and that the \/etc\/printcap file was missing ONE line. (blah,
\nRedhat 7.3 auto print configure borks the day). The Windows box
\nactually sent stuff to the printer (which started up like it was going
\nto print and then stop).<\/p>\n
Here are some tests to run that are quick if the Samba Howto doesn’t
\nwork out. They are taken from “Samba Unleased” and my own experience.<\/p>\n
– Run testparm on smb.conf and fix any errors
\n– Test connectivity between the two boxes by doing a ping from the
\nLinux box to the Windows box & vica versa
\n– Test DNS name resolution between the two boxes by pinging the name
\nof the Linux box from the Windows box & vica versa. Problems should be
\ncorrected by entries in the hosts file.
\n– Test to see if you can get share names from the Linux box with
\n smbclient -NL servername
\n Do this first from the Linux box on itself & then from the Windows
\nbox.
\n– From the windows client type
\n echo Hello^L > \\\\servername\\printqueuename
\n(I had to press the paper feed button on the printer for it to print
\nout) If this succeeds it rules out everything but the Windows printer
\ndefinition and application you are trying to print from. If this
\nsucceeds, try printing a test page from the properties of the printer
\nin Windows.
\n– Try printing a short text only file via smbclient with:
\n smbclient ‘\/\/servername\/printsharename’ -U userid, put dos.txt
\n This rules out samba if successful as the problem.If this succeeds
\nbut the Hello test above fails, a connectivity or name resolution
\nproblem is the most likely scenario. If this fails, the job is getting
\nlost in samba, do next test.
\n– From the Linux box (even tho it’s working) try:
\necho ^MHello^L | lpr -P printqueuename
\n(I had to press the paper feed button on the printer for it to print
\nout). If it fails, there is a print queue, print device or hardware
\nproblem.<\/p>\n
This ought to keep you busy for a while \ud83d\ude09 If this fails, let me know
\nwhat your test results were and we’ll see what we can do from there.
\n(BTW, it feels good to be able to give back support into the groups
\nthat have given a lot to me).<\/p>\n
—
\nI hope this is helpful \ud83d\ude42
\nTracey
\nLinux Counter #264789<\/p>\n
smb.conf
\n[global]
\n\tlog file = \/var\/log\/samba\/log.%m
\n\tload printers = yes
\n\tsmb passwd file = \/etc\/samba\/private\/smbpasswd
\n\tname resolve order = lmhosts bcast wins
\n\tsocket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
\n\tremote browse sync = 192.168.123.255
\n\thosts allow = 192.168.123.0\/24 127.
\n\tencrypt passwords = yes
\n\tpasswd program = \/usr\/bin\/passwd %u
\n\tdns proxy = no
\n\tnetbios name = localhost
\n\tnetbios aliases = localhost
\n\tprinting = cups
\n\tserver string = Selar Samba Server
\n\tdefault = fileshare
\n\tunix password sync = Yes
\n\tremote announce = 192.168.123.255\/mydomain.org
\n\tworkgroup = mydomain.org
\n\tlogon path = \\\\%L\\Profiles\\%U
\n\tos level = 20
\n\tadd user script = \/usr\/sbin\/useradd -s \/bin\/false %u
\n\tprintcap name = lpstat
\n\tsecurity = user
\n\tmax log size = 50
\n\tdomain admin group = root @wheel<\/p>\n
\n# Un-comment the following to provide a specific roving profile share
\n# the default is to use the user’s home directory
\n[Profiles]
\n path = \/var\/lib\/samba\/profiles
\n browseable = no
\n guest ok = yes<\/p>\n
# NOTE: If you have a CUPS print system there is no need to
\n# specifically define each individual printer.
\n# You must configure the samba printers with the appropriate Windows
\n# drivers on your Windows clients. On the Samba server no filtering is
\n# done. If you wish that the server provides the driver and the
\nclients# send PostScript (“Generic PostScript Printer” under Windows),
\nyou have# to swap the ‘print command’ line below with the commented
\none.
\n[printers]
\n comment = All Printers
\n path = \/var\/spool\/samba
\n browseable = yes
\n# to allow user ‘guest account’ to print.
\n guest ok = yes
\n writable = yes
\n printable = yes
\n create mode = 0700
\n# =====================================
\n# print command: see above for details.
\n# =====================================
\n; print command = lpr -P %p -o raw %s -r # using client side
\nprinter drivers. print command = lpr -P %p %s # using cups own
\ndrivers (use generic PostScript on clients).
\n# The following two commands are the samba defaults for printing=cups
\n#change them only if you need different options:
\n lpq command = lpq -P%p
\n lprm command = cancel %p-%j<\/p>\n
# This share is used for Windows NT-style point-and-print support. ————– next part ————– Your smb.conf looks to have no errors. I see it was created with SWAT, which usually sets things up without a hitch. Out of curiosity, why did you pick “security=SHARE”? There are a few lines I have in mine that … Read More »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-311","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/311","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=311"}],"version-history":[{"count":0,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/311\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=311"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=311"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=311"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n# To be able to install drivers, you need to be either root, or listed
\n# in the printer admin parameter above. Note that you also need write
\naccess# to the directory and share definition to be able to upload the
\ndrivers.# For more information on this, please see the Printing
\nSupport Section of
\n#\/usr\/share\/doc\/samba-
\n[print$]\twriteable = yes
\n\tpath = \/var\/lib\/samba\/printers
\n\twrite list = @adm, at root<\/p>\n
\nA non-text attachment was scrubbed…
\nName: not available
\nType: application\/pgp-signature
\nSize: 189 bytes
\nDesc: not available
\nUrl : http:\/\/linuxchix.org\/pipermail\/techtalk\/attachments\/20030318\/a99cd95e\/attachment.pgp<\/p>\n","protected":false},"excerpt":{"rendered":"