Re: Cupsaddsmb only running "setdriver"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Reader, If you have these same problems, I've got the answer from the CUPS people themselves. Here is the link for that posting: Later, Mark -BEGIN PGP SIGNATURE- Version: Gnu

Re: Cupsaddsmb only running "setdriver"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 M. Maas wrote: > > amsprint:/home/mark# cupsaddsmb -U root -v -a > Password for root required to access localhost via SAMBA: > Running command: rpcclient localhost -N -U'root%keepitsimple' -c > 'setdriver Test2 Test2' > Succesfully set Test2 to driv

Re: Cupsaddsmb only running "setdriver"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I do not have the foggiest as to why my email arrived twice... Sorry about that! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCpZglmHLz+zAEfmERAm+XAKCJyZho86

Cupsaddsmb only running "setdriver"

Hi All, I downloaded a fresh cd (Debian 3.1) to install a Printserver with. I've come to the bit that I can run cupsaddsmb, and expected it to run smbclient to add the drivers to the print$ share, and then rpcclient to do the "addriver" part and finaly the "setdriver" part. Unfortunatly, it is d

Cupsaddsmb only running "setdriver"

Hi All, I downloaded a fresh cd (Debian 3.1) to install a Printserver with. I've come to the bit that I can run cupsaddsmb, and expected it to run smbclient to add the drivers to the print$ share, and then rpcclient to do the "addriver" part and finaly the "setdriver" part. Unfortunatly, it is d