samba - Aug 2003 - Samba + Cups: don't succeed to print from Windows 2000 station

Hello,



I have configured cups (1.1.18) on a Suse 8.2 Pro Linux server.
I have also configured samba (2.2.7a), and joined a domain.
I have created printers with cups and declared them to samba with
cupsaddsmb command.

All seems to be ok.


I can print from my Linux server.

But, when I want to print from ny windows2000 station:
- I can find my linux server
- I can find and connect printers which are declared
- I do not succeed to print (the test page or another document). The system
says it is not able to print.
I do not see the job on the cups web interface.


May someone help me ?
Is there a problem rather with cups or with samba configuration ? What is
the point of locking ?


I executed cupstestppd on cups-samba printers ppd files. All values are
'pass'.
I looked at log files, but didnt see anything that helped me.

So if someone has some idea to help me, the idea would be welcome.


Regards,
Nadine

| I have configured cups (1.1.18) on a Suse 8.2 Pro 
| Linux server. I have also configured samba (2.2.7a), 
| and joined a domain. I have created printers with 
| cups and declared them to samba with cupsaddsmb 
| command.

Has samba reported success at all stages ?

| All seems to be ok.
| I can print from my Linux server.
| But, when I want to print from ny windows2000 
| station:
| - I can find my linux server
| - I can find and connect printers which are declared
| - I do not succeed to print (the test page or 
| another document). The system says it is not able to 
| print. I do not see the job on the cups web 
| interface.

Assuming cupsaddsmb did indeed setup the printers
without any errors, the Windows expect a default mode
from a printer, which needs to be establiched by
connecting the printer as domain admin and setting it
up through the following suit of mouse clicks:

Select the printer, right-click and choose Properties.
Go to Advanced tab and click on Printing defaults. Do
any adjustment, even if only to revert it immediately
afterwards, so that the Apply button is not greyed out.
Clik on Apply. Done. 

However, it is essential that your samba server should
respond properly to rpcclient commands enumprinters
and enumdrivers. Lookit up in the manual.


May someone help me ?
Is there a problem rather with cups or with samba configuration ? What is
the point of locking ?


I executed cupstestppd on cups-samba printers ppd files. All values are
'pass'.
I looked at log files, but didnt see anything that helped me.



____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

|> Assuming cupsaddsmb did indeed setup the printers
|> without any errors, the Windows expect a default 
|> ......................................
|> However, it is essential that your samba server 
|> should respond properly to rpcclient commands 
|> enumprinters and enumdrivers. Lookit up in the 
|> manual.
>--> about enumprinters & enudrivers:
>enumprinters, getprinter --> OK
>
>enumdrivers:
>rpcclient -c "enumdrivers 1" -U root LINUX01   
>                   -->OK (Printer Driver ...)
>rpcclient -c "enumdrivers 2" -U root LINUX01   
>                   --> [Windows 4.0],
>Segmentation fault
>
>getdriver
>rpcclient -c "getdriver b1_423" -U root LINUX01 
>                   --> [Windows NT x86],
>Segmentation fault.
Now this is the typical symptom of bug #82, for which
there is a patch diff file as attachment #62 at

   https://bugzilla.samba.org/show_bug.cgi?id=82

You'll have to recompile your samba after applying the
patch and then the problem disappears.
>Since last friday, I have made somme progress:
>When people ask for printing through samba, they are 
>wecome as guest cups_samba_entry. There was a problem 
>because, samba could not read printers.conf. So, I 
>have now printers.conf readable by all. And, now I 
>get another error: 
>'problem of printer configuration'  
>(translation of french: 
>probleme de configuration d'imprimante)
After the patch for bug #82 is applied, then you also
need to configure the default settings as I described
in my previous posting.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

>My samba version (on Suse distribution) is 2.2.7a-58.
>Can and must I a also this patch on this version 
>and/or must I load samba 2.2.8 with the patch ?
SuSE 8.2, I presume. You should really get 2.2.8a 
sources compressed with bzip2. Look for the files
samba-2.2.8a.tar.bz2 and samba-vscan-0.3.2a.tar.bz2
at a samba mirror).

Enclosed is a small bzip2-compressed tarball with the 
other things that SuSE uses to build samba as an RPM, 
but including the patch for bugs #52, #82 and #102. 
All of them are checked in 3.0betas but not yet
consolidated in a new 2.x release (perhaps there will 
be no more 2.x releases).

You should put both samba sources in the directory
"/usr/src/packages/SOURCES" and unpack my tarball there
with "bzip2 -d < samba.deps.tbz2 | tar xvf -" and then 
execute:

   rpm -bb samba.spec 2>&1 | tee /tmp/228a.build

while still in that directory (the T-joint is so that
you may have a log of what happened in case anything
goes wrong so someone can have a look at it and tell
you what). The following suite of installable RPM 
packages will then be created in 
/usr/src/packages/RPMS/i386 directory, which you may 
use to install patched samba properly with the command
"rpm -Uhv libsmbclient* samba*":

libsmbclient-2.2.8a-4.i386.rpm
libsmbclient-devel-2.2.8a-4.i386.rpm
samba-2.2.8a-4.i386.rpm
samba-client-2.2.8a-4.i386.rpm
samba-doc-2.2.8a-4.i386.rpm
samba-vscan-0.3.2a-0.i386.rpm

Building samba means you need to have the gcc compiler
and various devel libraries installed on your computer 
(they can be found on your distro's media), but when 
all is in place you only need patience. It takes a 
while (20'25" on my PC).

The libraries needed:

ncurses-devel, readline-devel, security, libacl-devel, 
libattr-devel, popt-devel, cups-devel, openssl,
openssl-devel, pam-devel, openldap2-devel, gdbm, 
gdbm-devel, glibc-devel, glibc2-devel, glib-devel

This might look like an overkill and perhaps it is.
If someone knows better, please correct me. I haven't
seen a manifest of required libraries anywhere but
many people (including me) fail to build samba because
one or other library is missing and it's not very
obvious which one.

Good luck, Nadine.



____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005