"hp_psc_1210:cupsdrv5.dll:hp_psc_1210.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"
result was NT_STATUS_UNSUCCESSFUL

This could mean some things, but I am not sure what the problem is. Most probably it's a misconfiguration in the smb.conf, but so far I didn't find anything wrong or missing in your config.

Maybe try that again with the /etc/samba/printer directory completely emtpy (it exists, doesn't it?)? Also, are Samba and CUPS running while you're doing this? And while we're at it: are the permissions on /etc/samba/printer set correctly?

That's all I can think of at the moment..._________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

how can I align my cardriges on an HP 916c? Under windows there is a tool for it, but under Linux ??????

I'm sorry, but I have no idea for that problem._________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

Yes, the directory exists, Yes I am doing it while samba and CUPS are running, and I am not sure about the permissions, but it's owned by root:root

hope this helps [you to help me]

Is it empty? The permissions should not matter though if you run cupsaddsmb as root.

I am running out of ideas here. In any case, your smb.conf is ok. I read somewhere that sometimes the .ppd file can cause problems, but I don't know if that applies here. If there is another .pdd you could use with your printer you may want to give it a try. BTW: which Samba version are you using? If it's 2.2.x maybe you could upgrade to 3.0 and try again.

Other than that I don't know at the moment. Error messages like NT_STATUS_OBJECT_NAME_COLLISION are a little too cryptic to get useful information out of...

I wonder: it worked the last time, why not now? Did you take the configuration over from the last setup?_________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

I wanted to post this in case there are others out there that have a similar problem. I followed all the instructions to a 'T'. I used the correct versions of cups, samba, etc. I went with the cups driver options (instead of Adobe's). The two problems I had where:

#1 I had to change the security=share to security=user and add a root user to samba to get the cupsaddsmb utility to work correctly. Once that was done, I changed the security setting back to share.

#2 The other problem I had was that my Windows XP machine would not download the drivers no matter what I did. I went through and double checked everything and ended up resetting up my cups/samba config with one apparent change. For all of my original settings I used [PhotoSmart] as the samba share for the printer and for the cups name of the printer (as instructed). When I set the configs up for the last time I chagned the name to [HPPhotoSmart1115] and matched that with the cups name. I also made sure the samba comment and the cups description matched. This seemed to solve my problem although I'm not completely convinced that it was the cause - maybe I changed something when I redid the config files. Who knows.

For completeness, here are my working configs. First my smb.conf file:

is for my setup on my FreeBSD machine. Adjust to what you have. Be sure to have the name (-p) right (the name you set above during the Samba configuration!) and to put in the correct usb:/dev/usb/blah, parallel:/dev/blah or whatever device you have the printer on.

If all worked you can access the printer now from the web interface. You should now be able to print a test page. If you aren't, you did something wrong or I forgot something Please correct me.

Thank you daff for writting this HOWTO. I'm just having a wee problem. Here's what I get when I type

Oh, I just looked at the previous post's date. I'm guessing this thread has gone stale. <mercy bump>_________________A wise man realizes that he too is a fool and then humbles himself to learn that which is greater than he.

Sorry it took me so long to get back to this topic, but I've been quite busy lately...

I'll try an help anyway, although I honestly have no real idea why you get that 'Connection refused' messages. The only thing that I can think of at the moment is that your network isn't configured in such a way that the localhost machine on 127.0.0.1 and the host with the IP address 192.168.1.n (also localhost, but with a 'real' IP address) are the same to CUPS (only allowing from 192.168.1.*, not from 127.0.0.1)...just a guess. Do you have a DNS running? If so then it is probably configured correctly, or else it wouldn't really run well, would it? (DNS always seemed a bit black-artish to me, before I figured it out.) If not, maybe check your /etc/hosts file so that entries like

Apart from that, try changing the Allow From rules in cupsd.conf to 127.0.0.* and see if it still doesn't want you to connect. If it lets you, then it really might be a network config problem. If it still wont let you then I don't know.

These are just guesses! From what you've posted I really can't make out what would cause the problems you're describing, sorry. The configurations seem just fine.

Good luck!_________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

Daff - your HOW TO is great! my HP PSC 950 works just fine ... but I'm not able to install the cups driver to use them with my Win2k clients . whenever I try to run cupsaddsmb I get the following error ...

the printer works fine - I can see it and print using the win drivers - but I can't get my Win2k clients to use the cups printers as I don't get them installed - any idea or feedback would be highly appreciated!

don't meant to seem pedantic but, just to clarify, are you doing what the error message suggests and then looking to see if you have renamed the ppd file and put it in the appropriate place?

snorre wrote:

the printer works fine - I can see it and print using the win drivers - but I can't get my Win2k clients to use the cups printers as I don't get them installed - any idea or feedback would be highly appreciated!

when you say you don't get them installed are you referring to the previous message of "no PPD file found..." or is it a client-side error like my

pubecon wrote:

The server on which the '<printername>' printer resides does not have the correct printer driver installed. If you want to install the driver on your local computer, click OK

This didn't work for me..... the first xxx times. Now, i'm duplicating the steps to write this post, and suddenly... it works... VERY strange, I didn't change anything

Now the files are in the /etc/samba/drivers/W32X86/2/ folder.

*Maybe* it has something to do with the 'security = user' setting in the samba config. I Had that set to share yesterday, and late yesterday evening i read somewhere that that could be a problem. I changed it to user, but I can't remember if I reloaded samba after that (well, it was very late, and I had to get up early in the morning....)

Maybe this will help someone else.

I am still not able to automatically download the driver from a windows XP workstation
I get the following error :

Quote:

The server for the printer does not have the correct driver installed. Blah blah blah....

gr,
Nossie

Last edited by Nossie on Sat Mar 20, 2004 2:31 pm; edited 1 time in total

I'm afraid, I too am experiencing much strangeness with this whole procedure (i.e I followed it all to the letter and it worked, then I went to add another printer and it's all come crashing down - none of the drivers upload to the windows clients now [fortunately I'd already added the essential ones)

since all my clients are win2k, my solution was to abandon this madness, duplicate all the printers as RAW in cups (see where this is going..)

then I, using win2ks built-in ipp support, added a 'network printer' with the address http://serveraddress.whatever.local:631/printers/printername and when the win2k clients noted that there was no driver associated with it I just pointed it to the .inf file I got off the manufacturers website (hp).

I'll come back to this samba magic if ever it is explained as less magic and more science (I managed to get a glimpse of a samba book and it appeared to explain this process in more detail. I'm half-tempted to buy one just to fix this problem and gain some more insight into it all)...

Everyone: I am very sorry but I really haven't had the time lately to support this thread, and I am quite sure I am not going to have much time in the future either. Hopefully some of you who have got it running could help out.

Just a quick hint for xcable: did you uncomment the following lines in /etc/cups/mime.types and /etc/cups/mime.convs?

Code:

mime.convs:
application/octet-stream application/vnd.cups-raw 0 -

mime.types:
application/octet-stream

As for the others, I may have some time the next two to three days to look into the reported problems as far as I can (I am no Samba or CUPS or IPP or whatever expert either ), if there's still need for this._________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

Thanks for the responce. I had already modified mime.convs and mime.types.

The major problem was that cups was not started up correctly, I fixed it be reverting to the example cupsd.conf, modifiing it and restarting cupsd. I also had to point my printer spool in smb.conf to "/var/spool/cups/tmp" not "/var/spool/cups".

I'm afraid, I too am experiencing much strangeness with this whole procedure (i.e I followed it all to the letter and it worked, then I went to add another printer and it's all come crashing down - none of the drivers upload to the windows clients now [fortunately I'd already added the essential ones)

since all my clients are win2k, my solution was to abandon this madness, duplicate all the printers as RAW in cups (see where this is going..)

It really can become a madness. Printing and print serving seem to be even more complicated and error- or misconfiguration-prone than mail servers and DNS.

pubecon wrote:

I'll come back to this samba magic if ever it is explained as less magic and more science (I managed to get a glimpse of a samba book and it appeared to explain this process in more detail. I'm half-tempted to buy one just to fix this problem and gain some more insight into it all.

True, true, the whole Samba stuff is WAY underdocumented if I may say so. The Samba website is quite worthless, and until recently it didn't even point to a main documentation project or manual or whatever.

It seems that this has changed, however: Here you'll find just about everything about Samba. See also Chapter 19, which explains everything I've written in my How-To, but had to gather from experience and trial & error: http://at.samba.org/samba/docs/man/

It still isn't as readable and good a manual as I'd like it to be.

One general word of advice: It seems like some of you are trying to install a a printer for the Windows clients without giving it the same name as the printer has in CUPS. Naming consistency seems to be really important when it comes to sharing printers across CUPS installations, Samba servers and Windows clients.

Also, the printer must be working within CUPS and Linux clients, before it can be shared with or exported to Windows clients!!! If you haven't got a working test page out of the CUPS administration Web interface, don't even bother with Samba and Windows.

I also can say that the How-To worked when I tested it recently when I set up a new server from scratch, so I don't think there are any major faults or mishaps inherent. But I sure might be wrong._________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

Thanks for the responce. I had already modified mime.convs and mime.types.

Ok. Whenever I ran across the error messages you posted it was very certain that someone forgot to edit these two lines, so that's the first thing that comes to mind

xcable wrote:

The major problem was that cups was not started up correctly, I fixed it be reverting to the example cupsd.conf, modifiing it and restarting cupsd. I also had to point my printer spool in smb.conf to "/var/spool/cups/tmp" not "/var/spool/cups".

I don't know about the spool directories you use (never heard about /var/spool/cups/tmp), but they shouldn't really matter I think, as long as the permissions are correct.

Very good that you seem to have it working now!_________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.

I added a section about Troubleshooting to the How-To. It is from Kurt Pfeifle's "Printing Support in Samba 3.0", the manual which covers everything about CUPS and Samba in way more detail and great length. Be sure to have a look at it and check the Troubleshooting section there! It contains many answers to many common problems.

I should have known about that from the beginning. Damn._________________Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.