[Samba] Ref: Samba + Cups: don't succeed to print from Windows 2000station

[nadine . vandois]

Dragan, Andy


Thanks for your answsers.

Please find hereafter more information and my notes.


Nadine


-- Réacheminé par Nadine Vandois/FR/BULL sur 11/08/2003
10:56 ---


"Dragan Krnic" <[EMAIL PROTECTED]> sur 10/08/2003 09:47:05

Veuillez répondre à [EMAIL PROTECTED]

Pour : [EMAIL PROTECTED]
cc :   [EMAIL PROTECTED]
Objet : Re: Samba + Cups: don't succeed to print from Windows 2000
   station


| 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 ?  --> Yes

| 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.  --> I will try

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.


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)


(See attached file: smb.conf-ex.txt)(See attached
file: b1_423.PPD)

smb.conf  driver created with cupsaddsmb for samba




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



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cups addprinter fails dos error 0x00000013 (Samba 3b3)

[Chris Puttick]

Kurt Pfeifle wrote:

> Chris Puttick chris at centralmanclc.com wrote on Samba-Digest:
> 
>> Tue Aug 12 14:57:22 GMT 2003
>> 
>> 
>> Hi
>> 
>> As per subject line...
>> 

>> Running command: rpcclient localhost -N -U'root%**' -c 'adddriver
>> "Windows NT x86"
>> "coloura3:cupsdrvr.dll:coloura3.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"'
>> result was DOS code 0x0013
>> 
>> Attaching with rpcclient and running adddriver results in same error.
>> 
>> The print$ subdirectory "W32X86" is created, but not the expected "2"
>> one. The cups drivers are successfully copied into W32X86, as is the ppd.
>> 
>> Any thoughts? If further information is needed, let me know.
>> 
>> smb.conf below.
>> 
>> Regards
>> 
>> Chris Puttick
>> 
>> [global]
>> workgroup = TRINITY
>> netbios aliases = zulu2
>> server string =
>> security = SHARE
> 
> Try with setting
> 
> security = USER
> 
> 
> and repeat cupsaddsmb
> 
That did it! Vielen danke!

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba + Cups: don't succeed to print from Windows 2000station

[Dragan Krnic]

>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-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cups addprinter fails dos error 0x00000013 (Samba 3b3)

[Chris Puttick]

Hi

As per subject line...

Samba 3 beta 3 installed and functional (e.g. appears in browse lists on
windows, shares accessible etc.) on SuSE 8.2. 

CUPS 1.1.18 configured and functional, cups drivers installed.

Using cupsaddsmb results in failure with DOS code 0x0013:

Running command: rpcclient localhost -N -U'root%**' -c 'adddriver
"Windows NT x86"
"coloura3:cupsdrvr.dll:coloura3.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"'
result was DOS code 0x0013

Attaching with rpcclient and running adddriver results in same error.

The print$ subdirectory "W32X86" is created, but not the expected "2" one.
The cups drivers are successfully copied into W32X86, as is the ppd.

Any thoughts? If further information is needed, let me know.

smb.conf below.

Regards

Chris Puttick

[global]
workgroup = TRINITY
netbios aliases = zulu2
server string =
security = SHARE
map to guest = Bad User
log level = 1
syslog = 0
time server = Yes
unix extensions = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
printcap name = cups
os level = 2
wins support = Yes
idmap uid = 1-2
idmap gid = 1-2
printing = cups
veto files = /*.eml/*.nws/riched20.dll/*.{*}/


[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0640
directory mask = 0750
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printer admin = root
create mask = 0600
guest ok = Yes
printable = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = root
#   force group = ntadmin
create mask = 0666
guest ok = Yes

[clcrechp2100]
comment = HP2100
path = /var/spool/samba
printer admin = root
read only = No
create mask = 0600
guest ok = Yes
printable = Yes
printer name = clcrechp2100
oplocks = No
share modes = No

[coloura3]
comment = HP Colour Laserjet 8550DN
path = /var/spool/samba
printer admin = root
read only = No
create mask = 0600
guest ok = Yes
printable = Yes
printer name = coloura3
oplocks = No
share modes = No




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cups addprinter fails dos error 0x00000013 (Samba 3b3)

[Kurt Pfeifle]

Chris Puttick chris at centralmanclc.com wrote on Samba-Digest:

Tue Aug 12 14:57:22 GMT 2003

Hi

As per subject line...

Samba 3 beta 3 installed and functional (e.g. appears in browse lists on
windows, shares accessible etc.) on SuSE 8.2. 

CUPS 1.1.18 configured and functional, cups drivers installed.

Using cupsaddsmb results in failure with DOS code 0x0013:

Running command: rpcclient localhost -N -U'root%**' -c 'adddriver
"Windows NT x86"
"coloura3:cupsdrvr.dll:coloura3.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"'
result was DOS code 0x0013
Attaching with rpcclient and running adddriver results in same error.

The print$ subdirectory "W32X86" is created, but not the expected "2" one.
The cups drivers are successfully copied into W32X86, as is the ppd.
Any thoughts? If further information is needed, let me know.

smb.conf below.

Regards

Chris Puttick

[global]
workgroup = TRINITY
netbios aliases = zulu2
server string =
security = SHARE
Try with setting

	  security = USER

and repeat cupsaddsmb

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Ref: Samba + Cups: don't succeed to print from Windows2000 station

[Dragan Krnic]

> I took into account your answer.
>
> I installed and recompiled samba 2.2.8a.
>
> I didn't load glibc2 (which is not delivered with 
> the Suse distribution), but all seems to be OK.
>
> I then tried rpcclient with: enumdrivers, 
> getdriver.It works fine now.
>
>
> But I still have problems when asking to print from 
> a windows station. The window station find the 
> printer, but when I ask to print a document or the 
> test page,I get:
>
>
> Impossible to print: problem of configuration of 
> printer.
> Try ..
> and:
> Test page could not be printed. Do you want .
>
> On my Linux server, I can print from the samba guest 
> user: cups_samba_entry.
>
> Do you think it is a problem with cups or with 
> samba ? >What can I do or test ?

Hi Nadine,

I have edited your smb.conf to best match my own setup.
Lines beginning with "-" sign should be commented out.
By most of them there is a short comment why. Lines
beginning with "+" sign are new lines I added to make
it look more like my setup.

It should work at your side, but don't forget to first
create the default mode by accessing the printer as
root and performing the ritual I described in on of my
previous letters.

Good luck.



Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Ref: Samba + Cups: don't succeed to print from Windows2000 station

[Dragan Krnic]

The attachment. I didn't want to post it to all.





Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
# Samba config file 
# you can modify it
# via an editor
# or via swat

# Global parameters
[global]
workgroup = FREC
netbios name = LINUX01
server string = Samba Server
-   security = USER # it is default
encrypt passwords = Yes
passwd program = /usr/bin/passwd %u
-   passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd: 
all*authentication*tokens*updated*successfully*
username map = /etc/samba/user.map
unix password sync = Yes
+   lanman auth = No# if you don't have pre-WinNT clients
wins server = 129.183.1.3
log level = 9
+   debug timestamp = Yes
log file = /var/log/samba/%m.log
load printers = Yes
printcap name = cups
printing = cups
+   printer admin = ntadmin
+   show add printer wizard = Yes
+   character set = ISO8859-1   # helps see accented chars
+   domain admin group = root
-   guest account = cups_samba_entry
-   allow trusted domains = Yes # only valid for security != user
-   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
+   socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
-   obey pam restrictions = Yes # I wouldn't mess with pam yet
-   map to guest = Bad Password # not valid for security = user
-   null passwords = Yes# security loophole
-   public = yes# applies to a share
-   dns proxy = No  # leave the default yes
-   path = /tmp # must be an error
-   debug level = 1 # does not exist
-   comment = Temporary directory   # error
-   add user script = /usr/bin/smbadduser %u # but does it work?
-   pam password change = Yes   # no pam for a while
domain logons = Yes
logon script = logon.cmd# make it up and put it under netlogon
logon path = \\LINUX01\profiles\%U
logon drive = U:
logon home = \\LINUX01\$U

+[netlogon]
+   path = /some/existing/path
+   write list = ntadmin
+   browseable = No

+[profiles]
+   path = /some/existing/path
+   valid users = $U
+   read only = No
+   inherit permissions = No
+   security mask = 0777
+   directory security mask = 0777
+   browseable = No

[homes]
+   valid users = $U
+   read only = No
+   inherit permissions = No
+   security mask = 0777
+   directory security mask = 0777
+   browseable = No
-   create mask = 0664
-   directory mask = 0775
-   comment = Home Directories
-   valid users = %S

[print$]
comment = Printer Drivers
path = /etc/samba/drivers
browseable = Yes
+   guest ok = No
-   guest ok = Yes
read only = Yes
-   write list = root
+   write list = ntadmin

[printers]
comment = All Printers
path = /var/spool/samba
-   browseable = Yes
+   browseable = No
public = Yes
guest ok = Yes
-   writable = Yes
+   writable = No
printable = Yes
-   printer admin = root
+   printer admin = ntadmin-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba + Cups: don't succeed to print from Windows 2000station

[Dragan Krnic]

|> 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
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Ref: Samba + Cups: don't succeed to print from Windows 2000station

[nadine . vandois]

Dragan,

I took into account your answer.

I installed and recompiled samba 2.2.8a.

I didn't load glibc2 (which is not delivered with the Suse distribution),
but all seems to be OK.

I then tried rpcclient with: enumdrivers, getdriver.It works fine now.


But I still have problems when asking to print from a windows station.
The window station find the printer, but when I ask to print a document or
the test page,I get:


Impossible to print: problem of configuration of printer.
Try ..
and:
Test page could not be printed. Do you want .



On my Linux server, I can print from the samba guest user:
cups_samba_entry.



Do you think it is a problem with cups or with samba ?
What can I do or test ?



Please find hereafter:
smb.conf,


(See attached file: smb.conf)


Regards,
Nadine


-- Réacheminé par Nadine Vandois/FR/BULL sur 14/08/2003
14:40 ---


"Dragan Krnic" <[EMAIL PROTECTED]> sur 11/08/2003 20:45:43

Veuillez répondre à [EMAIL PROTECTED]

Pour : [EMAIL PROTECTED]
cc :   [EMAIL PROTECTED]
Objet : Re: Samba + Cups: don't succeed to print from Windows 2000
   station


>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







-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba + Cups: don't succeed to print from Windows 2000station

[Dragan Krnic]

| 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
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba + Cups: don't succeed to print from Windows 2000station

[nadine . vandois]

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









-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS via SMB with per-user credentials?

[Kurt Granroth]

I have a multi-user Linux box in a mostly Windows NT/2000 shop.  The office
printer is available only via SMB (hosted by a Win2000 box) and access is
restricted to valid users in the local NT domain.  There is no "global" or
"print" user/password.

Everything mostly works.  I have a 'DeviceURI
smb://MYUSERNAME:[EMAIL PROTECTED]/printer' in /etc/cups/printers.conf. 
This allows all of the users on this Linux box to be able to print.

However, this isn't ideal for several reasons:
1. It's horribly unsecure as people with 'root' access on the Linux box
aren't the same as the NT admins.  Too many people can see my username and
password
2. All print jobs show up on my queue.  This can be pretty irritating when
the WinPopup messages keep popping up on my screen from somebody else's
print job.
3. Everybody has their own NT login credentials, so why not use them?

Unfortunately, I can't figure out any way to do this.  Basically, CUPS needs
to get the login credentials from someplace else other than the
printers.conf file.  It doesn't seem to honor or recognize the
$HOME/.credentials file that we use for share mounting.

I am more than willing to RTFM is such a FM exists.  Just point me in the
right direction!

Is this possible or am I out of luck?

Thank you,
Kurt Granroth
kurt-samba at granroth.org

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] samba + cups print spooling

[Oleg Biteryakov]

Hello.
I have samba (2.2.8a) + cups(1.1.19 with postscript driver) setup.
Printing works just fine, both from linux client and windows client.
On linux server cups is configured to hold print jobs till release,
and that works if printing from server itself.

However, when printing from Win2k machines, print jobs don't get
delayed on the server, but print out right away.
What needs to be configured in order for Win2k print jobs to be
delayed on the server?

-- 
Best regards,
 Oleg Biteryakov
mailto:[EMAIL PROTECTED]


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups chopping off lines

[Shanti Katta]

Hi,

I have setup cups-1.1.19 and using samba-2.2.8a to serve windows
clients. The problem I am seeing is whenever printing through Unix, the
page is printed with top 2 lines chopped off in Landscape mode. Is there
any way that I can fix this? Searching google did not help much.

Shanti



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Cups or Samba?

[David Morel]

Le mar 01/07/2003 à 00:34, Kurt Pfeifle a écrit :

> > I think cupsd takes a little time to populate the printers list  at
> > startup, but i would tend to think smbd would reload the list on a
> > regular basis, is it not so ?
> > 
> 
> Oh yes -- that's the *theory*. As far as the *practical* side of
> things goes, unfortunately a bug in most recent versions of Samba
> prevents this from happening


ah! i knew it ! and they told me why do you keep HUPping processes, you
don't need to... ;-)
David
-- 
***
[EMAIL PROTECTED]
OpenPGP public key: http://www.amakuru.net/dmorel.asc
28192ef126bc871757cb7d97f4a44536




signature.asc
Description: Ceci est une partie de message=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups or Samba?

[Kurt Pfeifle]

David Morel david.morel at amakuru.net

Mon Jun 30 21:09:57 GMT 2003

Le lun 30/06/2003 à 21:07, Halászy-Kiss Ã?goston a écrit :

- after linux box boot it didn't print from any winXP, booting process
includes starting cupsd and smbd
- but if I reload samba it starts to print
- it seems to me samba didnt load printers at the boot process
I think cupsd takes a little time to populate the printers list  at
startup, but i would tend to think smbd would reload the list on a
regular basis, is it not so ?
Oh yes -- that's the *theory*. As far as the *practical* side of
things goes, unfortunately a bug in most recent versions of Samba
prevents this from happening
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Cups or Samba?

[David Morel]

Le lun 30/06/2003 à 23:13, Kurt Pfeifle a écrit :
> Halászy-Kiss Ágoston agoston at simeis.net
> 
> > Mon Jun 30 21:07:00 GMT 2003
> 
> []
> 
> > What I discovered:
> > 
> > - after linux box boot it didn't print from any winXP, booting process
> >   includes starting cupsd and smbd
> > - but if I reload samba it starts to print
> > - it seems to me samba didnt load printers at the boot process
> > 
> > Any ideas, solutions?
> > 
> 
> cupsd *must* be completely up and running for Samba to pick up the
> printer list.
> 
> * Make sure that cupsd is started well before smbd (and make sure
>that you get a return code of 0 for the "lpstat -r" before you
>try to start smbd
> 
> * Make sure that CUPS writes a "printcap" file by enabling the
>"Printcap /etc/printcap" directive in cupsd.conf.
> 
> > Please post me at : agoston at simeis.net
> > Thanks in advance
> > 
> 
> Cheers,
> Kurt

The issue with gentoo should be solved very soon if it is not already
done.

http://bugs.gentoo.org/show_bug.cgi?id=15492
-- 
***
[EMAIL PROTECTED]
OpenPGP public key: http://www.amakuru.net/dmorel.asc
28192ef126bc871757cb7d97f4a44536



signature.asc
Description: Ceci est une partie de message=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups or Samba?

[Kurt Pfeifle]

Halászy-Kiss Ágoston agoston at simeis.net

Mon Jun 30 21:07:00 GMT 2003
[]

What I discovered:

- after linux box boot it didn't print from any winXP, booting process
  includes starting cupsd and smbd
- but if I reload samba it starts to print
- it seems to me samba didnt load printers at the boot process
Any ideas, solutions?

cupsd *must* be completely up and running for Samba to pick up the
printer list.
* Make sure that cupsd is started well before smbd (and make sure
  that you get a return code of 0 for the "lpstat -r" before you
  try to start smbd
* Make sure that CUPS writes a "printcap" file by enabling the
  "Printcap /etc/printcap" directive in cupsd.conf.
Please post me at : agoston at simeis.net
Thanks in advance
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Cups or Samba?

[David Morel]

Le lun 30/06/2003 à 21:07, Halászy-Kiss Ágoston a écrit :

> - after linux box boot it didn't print from any winXP, booting process
> includes starting cupsd and smbd
> - but if I reload samba it starts to print
> - it seems to me samba didnt load printers at the boot process

I think cupsd takes a little time to populate the printers list  at
startup, but i would tend to think smbd would reload the list on a
regular basis, is it not so ?
-- 
***
[EMAIL PROTECTED]
OpenPGP public key: http://www.amakuru.net/dmorel.asc
28192ef126bc871757cb7d97f4a44536



signature.asc
Description: Ceci est une partie de message=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups or Samba?

[Halászy-Kiss Ágoston]

Hi all!

Please help me...

Scenario:
- linux box, turned on only for developing and printing purposes, printing
uses cups and samba
- 2 winXP box most of the time turned on

The following happened:

- installed the latest gentoo distro, updating all the time, prinitng worked
fine for couple weeks
- 2 days ago it started not to print

What I discovered:

- after linux box boot it didn't print from any winXP, booting process
includes starting cupsd and smbd
- but if I reload samba it starts to print
- it seems to me samba didnt load printers at the boot process

Any ideas, solutions?

Please post me at : [EMAIL PROTECTED]

Thanks in advance



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba/CUPS Printing from Windows

[Collins, Kevin]

I've got a Samba server that is acting as a member server in a Windows NT
Domain.  I enabled CUPS printing yesterday and have shared the 4 printers to
the domain.  I then added the printers onto a Windows 2000 client, and can
print just fine to any of them.

But I have two problems (read "annoyances"):

1).  When I look at any of the printers from Windows (i.e. Control
Panel/Printers) I can see the Samba supplied network printers, but when I
click on any of them I see a Status of "Access denied, unable to connect."
on the left hand side of the printers window.

2). Because of No. 1 (I think) when I double-click on a network printer, I
can't see any of the jobs in the queue for that printer as I should.

Anyone ran into these issues before?  I have included the smb.conf below for
inspection.

I'm running Red Hat 8.0, Samba 2.2.7, CUPS 1.1.17.


[global]
   workgroup = NESBITT_LEX
   netbios name = valykyrie
   server string = Linux Backup/Print Server
   log file = /var/log/samba/%m.log
   max log size = 50
   security = domain
   password server = file-server1 print-server
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   unix password sync = Yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *New*password* %n\n *Retype*new*password* %n\n \
*passwd:*all*authentication*tokens*updated*successfully*
   pam password change = yes
   obey pam restrictions = yes
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   local master = no
   os level = 0
   domain master = no
   preferred master = no
   domain logons = no
   wins server = 10.200.8.3
   dns proxy = no
   winbind separator = +
   winbind uid = 1-2
   winbind gid = 1-2
   winbind cache time = 10
   winbind enum users = yes
   winbind enum groups = yes
   winbind use default domain = yes
   template shell = /bin/bash
   template homedir = /home/%U
   printing = cups
   printcap name = cups
   load printers = yes
#=== Share Definitions =
[printers]
   comment = All Printers
   path = /var/spool/samba
   public = yes
   guest ok = yes
   writeable = no
   printable = yes

[homes]
   comment = Home Directories
   browseable = no
   writable = yes
   valid users = %S
   create mode = 0664
   directory mode = 0775

[backup]
  comment = Backup Files from Last Night
  path = /backup
  browsable = yes
  writeable = yes
  valid users = 
  create mode = 0777
  directory mode = 0777

[cdburn]
   comment = Files to be written to CD
   path = /cdburn
   browsable = yes
   writeable = yes

--
Kevin L. Collins, MCSE
Systems Manager
Nesbitt Engineering, Inc.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Help with printing on Samba, CUPS

[David F. Williams]

Hi All,

Having trouble printing to an HP710.  Can print from command line and over
Samba if I add the user to the admin users group as follows:

  admin users = administrator,user01,user02

When non-admin users attempt to print a test page the there is an error
"Test page failed to print...Would you like to try the troubleshooter?".  If
I try to print a file using Notepad I receive the error "A StarDocPrinter
Call was not issued."

I've seen the StarDocPrinter error posted numerous locations (both Windows
and Linux mailing lists) but haven't seen a solution.  Pretty sure the
problem is Samba related, I've tried making the permissions on the various
files/directories more liberal without any improvement.

I've attempted to place the Adobe postscript files in the
/usr/share/cps/drivers/ to allow seamlessly loading of drivers but haven't
been able to locate the NT/W2k/XP file sets (ADOBEPS5.DLL, ADOBEPSU.DLL,
ICONLIB.DLL).  I did locate the W95/W98 drivers and this feature does seem
to work properly for these clients.  Anyone know where to find these missing
files?  Hopeing that this will magically fix the problem.


Environment:

Samba server running Debian with 2.4.20, samba-2.2.8a (compiled from
source), Debian GhostScript 1.1.14 package.

Client:  Win2k SP3

Thanks in advance for any assistance you might be able to offer.

David Williams
Onbravo Communications, LLC


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba + CUPS = Two printers instead of one?

[Kurt Pfeifle]

Vizitiu, Ciprian  wrote on Samba-Digest:

Tue Jun 10 22:51:10 GMT 2003

Samba 2.2.8 + cups-1.1.17. 

load printers = yes
show add printer wizard = yes
printcap name = cups
printer admin = root
printing = cups
[print$]
   path = /home/printers
   guest ok = yes
   browseable = yes
   write list = root
[printers]
   comment = All Printers
   printable = yes
   path = /var/spool/samba
   browseable = no
   guest ok = yes
   public = yes
   read only = yes
   writable = no
[2 floor IBM BW]
   comment = IBM Infoprint 1222
   path = /var/spool/lpd/samba/2ndflbw
   printable = yes
   browseable = yes
   writable = no
   public = yes
   printer admin = root
Everything all right added drivers, set default all works like a charm just
it's just that... Why do I have two printers instead of one listed on the
server? 
Short answer: because you setup the smb.conf the way you did.

Long answer:

* the "load printers = yes" directive tells Samba to look for
  a printcap file and auto-create and use [printername] sections
  for each printername found in the printcap. These auto-created
  shares are not actually written to disk, but are visible
  in the Network neighbourhood and/or the server's "Printers and
  Faxes" folder. They use settings cloned from the [printers]
  section, (similar to how the [homes] section works...)
* the manually created share [2 floor IBM BW] duplicates your
  other effort. (BTW, don't forget to have the same "printername
  with spaces" {"2 floor IBM BW"} on the UNIX side, and don't
  forget to escape those spaces, should you want to use that
  printer in UNIX
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups / Samba Driver Download question

[James Sewell]

Hey all!!

Sorry about the crosspost but this invoves CUPS and Samba issues.

[Samba 2.2.8 / CUPS 1.1.8 / Redhat 7.2 std]

I have encountered a small problem (which is due to my own slipup more
than anything else).
I have "Windows 2000" versions of the Adobe postscript drivers installed
on many of my 2000 machines. Now I am wanting to use the CUPS drivers
which are "Windows 2000 or NT4" version stamped.
If a workstation has had a printer installed (Say it's called Bear)
before it will have the Bear W2K version drivers on it. The Bear printer
will be linked to this. If this printer is then removed and reinstalled
(just the printer not the drivers) then it will now install the Bear
NT4/2K drivers - thats fine. HOWEVER becasue these new drivers are lower
in the pecking hierachy than the old 2K version stamped ones they are
installed but not used. This is a problem.
I can see several solutions to this problem:

- Somehow get Samab to prompt a delete of all old drivers (the mappings
not the files obviously as printers can share files) with the same name
before an install form the client.
- Use a CUPS 2K only driver (which does not seem to be available as it
is not usually needed or wanted)
- Remove the old driver before installing the new printer. This however,
totally ruins the click to install metaphor that Samba and CUPS provide.
Does anyone have any suggestions or comments?

James.

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba + CUPS = Two printers instead of one?

[Vizitiu, Ciprian]

Samba 2.2.8 + cups-1.1.17. 

load printers = yes
show add printer wizard = yes
printcap name = cups
printer admin = root
printing = cups

[print$]
   path = /home/printers
   guest ok = yes
   browseable = yes
   write list = root

[printers]
   comment = All Printers
   printable = yes
   path = /var/spool/samba
   browseable = no
   guest ok = yes
   public = yes
   read only = yes
   writable = no

[2 floor IBM BW]
   comment = IBM Infoprint 1222
   path = /var/spool/lpd/samba/2ndflbw
   printable = yes
   browseable = yes
   writable = no
   public = yes
   printer admin = root


Everything all right added drivers, set default all works like a charm just
it's just that... Why do I have two printers instead of one listed on the
server? 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

re: [Samba] Cups printing works but status is always Access Denied

[Karl Banasky]

I use Cups here and the install has been with out fail.  Some oddities with XP but I 
figure that is cause I am not forking the doe out, no worries thou, it all works 
fabulously well.  I have Caldera 3.1.1  with CUPS 1.1.19.   Also with the smb 
My suggestion is to use these settings:

[global] 
printer admin = karl
printing = cups
printcap name = lpstat (this is the proper one per some cups document I read)
load printers = yes

[printers]
comment = All Printers
path = /var/spool/samba
guest ok = yes
browseable = no
public = yes
writable = no
printable = yes
printer admin = (user or @group name)

If you would like to add drivers put this in:

[print$]
comment = Printer Drivers
path = /etc/samba.d/drivers (path were driver will be located)
guest ok = no
write list = (user or @group name)
writable = no
browsable = yes

Review this for the right directories to setup and the cool cups utility to add 
drivers.  A little time is required and so smooth when done.
http://us2.samba.org/samba/docs/man/Samba-HOWTO-Collection.html#CUPS

Hope that assists you.  
Karl-


>>  I have a RedHat 9 installation running XFS.
 >>  Cups 1.1.17-13 is installed

 >>  I have compiled and installed Samba 2.2.8a and everything appears to be
 >>  working apart from a minor printing problem.
 >>  After I have installed a printer on my Win2K workstation I can print via
 >>  samba to the cups printer using the windows PCL print driver and it works
 >>  fine.
 >>  However the printer status is always 'Access denied, unable to connect'.

 >>  I get the following entries in the log file for my machine :-

 >>  [2003/06/10 12:28:24, 0] printing/print_cups.c:cups_printername_ok(388)
 >>  Unable to get printer status for
 >>  ::{2227a280-3aea-1069-a2de-08002b30309d} - client-error-not-found
 >>  [2003/06/10 12:28:24, 0] smbd/service.c:make_connection(252)
 >>  gb-desktop (192.168.1.250) couldn't find service
 >>  ::{2227a280-3aea-1069-a2de-08002b30309d}

 >>  My samba configuration :-

 >>  [global]
 >>  workgroup = ASCOT
 >>  netbios name = DIBBLER
 >>  server string = SAMBA-LDAP PDC Server
 >>  encrypt passwords = Yes
 >>  passwd program = /usr/local/sbin/smbldap-passwd.pl -o %u
 >>  passwd chat = *new*password* %n\n *new*password* %n\n *successfully*
 >>  unix password sync = Yes

 >>  log file = /var/log/samba/%m.log
 >>  log level = 5 ; remember to lower the log level in real life :-)
 >>  max log size = 0


 >>  socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

 >>  domain logons = Yes
 >>  os level = 80
 >>  preferred master = False
 >>  domain master = True
 >>  dns proxy = No
 >>  wins support = Yes

 >>  ; SAMBA-LDAP declarations
 >>  ldap suffix = dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
 >>  ldap admin dn = cn=Manager,dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
 >>  ldap port = 389
 >>  ldap server = 127.0.0.1
 >>  ldap ssl = No

 >>  load printers = yes
 >>  printing = cups
 >>  printcap name = cups

 >>  ; Deactivate opportunistic locks (wised)
 >>  ; opLocks = False
 >>  ; encoding to french
 >>  ; character set = iso8859-1

 >>  ; using smbldap-tools to add machines
 >>  add user script = /usr/local/sbin/smbldap-useradd.pl -w %u
 >>  ; users and groups allowed to be 'Domain Admins'
 >>  domain admin group = " @"Domain Admins" "

 >>  [homes]
 >>  comment = Home Directories
 >>  valid users = %S
 >>  read only = No
 >>  create mask = 0664
 >>  directory mask = 0775
 >>  browseable = No

 >>  [netlogon]
 >>  comment = Network Logon Service
 >>  path = /usr/local/samba/netlogon
 >>  guest ok = Yes

 >>  [profiles]
 >>  path = /data/profiles
 >>  writeable = yes
 >>  browseable = no
 >>  create mode = 0644
 >>  directory mode = 0755
 >>  guest ok = yes

 >>  [samba]
 >>  path=/data/samba
 >>  writable= yes
 >>  force create mode   = 660
 >>  force directory mode= 770
 >>  create mode = 660
 >>  directory mode  = 770
 >>  mangle case = yes
 >>  case sensitive  = no
 >>  default case= lower
 >>  preserve case   = yes
 >>  short preserve case = no
 >>  valid users = @users
 >>  force group = users

 >>  [printers]
 >>  comment = All Printers
 >>  path = /var/spool/samba
 >>  printable = Yes
 >>  browseable = No
 >>  public = yes
 >>  guest ok = yes
 >>  writable = no
 >>  printer admin = root


 >>  --
 >>  Gareth Blades
 >>  Webscreen Technology
 >>  Index House
 >>  St Georges Lane
 >>  Ascot, Berkshire
 >>  SL5 7EU, UK
 >>  Tel +44 (0) 1344 636339
 >>  http://www.webscreen-technology.com


 >>  -- 
 >>  To unsubscribe from this list go to the following URL and read the
 >>  instructions:  http://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

RE: [Samba] Cups printing works but status is always AccessDenied

[daniel . jarboe]

Sounds like you need the use client driver = yes hack in smb.conf, or
preferably, look into setting up print$ and automatic driver download.
man smb.conf for use client driver explains what appears to be your
problem in some detail.

Good luck,
~ Daniel



> After I have installed a printer on my Win2K workstation I 
> can print via
> samba to the cups printer using the windows PCL print driver 
> and it works fine.
> However the printer status is always 'Access denied, unable 
> to connect'.




---

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups printing works but status is always Access Denied

[Gareth Blades]

I have a RedHat 9 installation running XFS.
Cups 1.1.17-13 is installed

I have compiled and installed Samba 2.2.8a and everything appears to be
working apart from a minor printing problem.
After I have installed a printer on my Win2K workstation I can print via
samba to the cups printer using the windows PCL print driver and it works
fine.
However the printer status is always 'Access denied, unable to connect'.

I get the following entries in the log file for my machine :-

[2003/06/10 12:28:24, 0] printing/print_cups.c:cups_printername_ok(388)
  Unable to get printer status for
::{2227a280-3aea-1069-a2de-08002b30309d} - client-error-not-found
[2003/06/10 12:28:24, 0] smbd/service.c:make_connection(252)
  gb-desktop (192.168.1.250) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}

My samba configuration :-

[global]
workgroup = ASCOT
netbios name = DIBBLER
server string = SAMBA-LDAP PDC Server
encrypt passwords = Yes
passwd program = /usr/local/sbin/smbldap-passwd.pl -o %u
passwd chat = *new*password* %n\n *new*password* %n\n *successfully*
unix password sync = Yes

log file = /var/log/samba/%m.log
log level = 5 ; remember to lower the log level in real life :-)
max log size = 0


socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

domain logons = Yes
os level = 80
preferred master = False
domain master = True
dns proxy = No
wins support = Yes

; SAMBA-LDAP declarations
ldap suffix = dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
ldap admin dn = cn=Manager,dc=ASCOT.WEBSCREEN-TECHNOLOGY,dc=COM
ldap port = 389
ldap server = 127.0.0.1
ldap ssl = No

load printers = yes
printing = cups
printcap name = cups

; Deactivate opportunistic locks (wised)
; opLocks = False
; encoding to french
; character set = iso8859-1

; using smbldap-tools to add machines
add user script = /usr/local/sbin/smbldap-useradd.pl -w %u
; users and groups allowed to be 'Domain Admins'
domain admin group = " @"Domain Admins" "

[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0664
directory mask = 0775
browseable = No

[netlogon]
comment = Network Logon Service
path = /usr/local/samba/netlogon
guest ok = Yes

[profiles]
path = /data/profiles
writeable = yes
browseable = no
create mode = 0644
directory mode = 0755
guest ok = yes

[samba]
path=/data/samba
writable= yes
force create mode   = 660
force directory mode= 770
create mode = 660
directory mode  = 770
mangle case = yes
case sensitive  = no
default case= lower
preserve case   = yes
short preserve case = no
valid users = @users
force group = users

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
public = yes
guest ok = yes
writable = no
printer admin = root


--
Gareth Blades
Webscreen Technology
Index House
St Georges Lane
Ascot, Berkshire
SL5 7EU, UK
Tel +44 (0) 1344 636339
http://www.webscreen-technology.com


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba+CUPS+Drivers autodownload

[Dragan Krnic]

>> Your problem is trivial, Matt, but you're not doing
..
>:-)
>
>I eventually found the problem. Another admin had 
>helpfully changed the "share = " setting from user
>to share for some reason which I'm currently trying 
>to extract out of him. Changing it back to user and
>everything works okay with just your bugfixes (or 
>equivalent).

I guess you mean changed "security = user" to
"security = share". Duh! Short of peeking in
"smb.conf" you can infer that kind of error
only with server logs :-)

Glad you found the bugger, erm, the bug.




Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba+CUPS+Drivers autodownload

[Dragan Krnic]

>I'm still trying to set my Samba box up to allow the 
>Adobe PS drivers to be automatically downloaded.
>
>Thanks to a couple of replies, I've tried three 
>courses of action, none of which have been 
>successful. These are:

Your problem is trivial, Matt, but you're not doing
the right thing to find out how trivial it is. By
opting "-v" in your "cupsaddsmb" call in you are
seeing only the client's point of view on the problem. 
There is much more going on on the server side, which
rpcclient cannot show because its crystal ball is
as usual dusted over and it doesn't get much of
diagnostic from the rpc_server, just go/no-go.

Do yourself a favour and proceed as follows:

0. insert the option "debug timestamps = Yes" in your
   smb.conf and let it take effect. "smb restart" or

   psj smbd | \
   while read pid pid rest;
   do kill -HUP $pid; 
   done

   would do.

1. cd to the samba log dir and clean up your host's
   (WINS name for localhost) file, e.g.

   cd /var/log/samba
   > yourhost.log

2. increase debugging level liberally, e.g.

   smbcontrol smbd debug 

3. do your 
   cupsaddsmb -v -U root oki7200

4. reduce debugging level to normal

   smbcontrol smbd debug 1

5. try to make sense of so much static noise in
   "yourhost.log". If you need help, gzip and
   mail the file to someone (I volunteer).

Cheers
Dragan



Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba+CUPS+Drivers autodownload

[Matt Dainty]

Hi again,

I'm still trying to set my Samba box up to allow the Adobe PS drivers to
be automatically downloaded.

Thanks to a couple of replies, I've tried three courses of action, none
of which have been successful. These are:

1) Fix for source/lib/util_unistr.c (bugid #82)

2) Comment out the lines in source/rpc_server/srv_spoolss_nt.c enclosed
   between /* BEGIN_ADMIN_LOG */ and /* END_ADMIN_LOG */

3) Use the rpcclient binary from a 3.0 source build

Using the first two, I still get a NT_STATUS_UNSUCCESSFUL using the
"rpcclient adddriver". Using the rpcclient binary from a 3.0 source
build, (alpha24), I instead get a WERR_BADFILE for the same command.

Here's running "cupsaddsmb -v" with fixes 1) & 2):

# /usr/sbin/cupsaddsmb -v -U root oki7200
Password for root required to access localhost via SAMBA: 
Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put 
/var/spool/cups/tmp/3edb1698e3fc0 W32X86/oki7200.PPD;put 
/usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put 
/usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put 
/usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
added interface ip=192.168.50.129 bcast=192.168.50.255 nmask=255.255.255.128
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[XREFER] OS=[Unix] Server=[Samba 2.2.9pre1]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
putting file /var/spool/cups/tmp/3edb1698e3fc0 as \W32X86/oki7200.PPD (16523.1 kb/s) 
(average 16523.4 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (22343.6 
kb/s) (average 21179.7 kb/s)
putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (22083.0 
kb/s) (average 21354.6 kb/s)
putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (18016.8 
kb/s) (average 21250.3 kb/s)

Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86" 
"oki7200:ADOBEPS5.DLL:oki7200.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
cmd = adddriver "Windows NT x86" 
"oki7200:ADOBEPS5.DLL:oki7200.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"
result was NT_STATUS_UNSUCCESSFUL

Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put 
/var/spool/cups/tmp/3edb1698e3fc0 WIN40/oki7200.PPD;put 
/usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put 
/usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put 
/usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put 
/usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put 
/usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put 
/usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
added interface ip=192.168.50.129 bcast=192.168.50.255 nmask=255.255.255.128
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[XREFER] OS=[Unix] Server=[Samba 2.2.9pre1]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
putting file /var/spool/cups/tmp/3edb1698e3fc0 as \WIN40/oki7200.PPD (20653.8 kb/s) 
(average 20654.3 kb/s)
putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (22483.2 kb/s) 
(average 22231.0 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (23008.5 
kb/s) (average 22740.1 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (21317.0 
kb/s) (average 22602.4 kb/s)
putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (13174.5 
kb/s) (average 22502.1 kb/s)
putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (23071.4 kb/s) 
(average 22530.9 kb/s)
putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s) 
(average 22417.3 kb/s)

Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0" 
"oki7200:ADOBEPS4.DRV:oki7200.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,oki7200.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
cmd = adddriver "Windows 4.0" 
"oki7200:ADOBEPS4.DRV:oki7200.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,oki7200.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
result was NT_STATUS_UNSUCCESSFUL

Running command: rpcclient localhost -N -U'root%secret' -c 'setdriver oki7200 oki7200'
cmd = setdriver oki7200 oki7200
Succesfully set oki7200 to driver oki7200.

Here's running "cupsaddsmb -v" with fixes 1), 2), & 3) (the 3.0 rpcclient):

# /usr/sbin/cupsaddsmb -v -U root oki7200
Password for root required to access localhost via SAMBA: 
Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put 
/var/spool/cups/tmp/3edb1611677d2 W32X86/oki7200.PPD;put 
/usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put 
/usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put 
/usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
added interface ip=192.168.50.129 bcast=192.168.50.255 nmask=255.255.255.128
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[XREFER] OS=[Unix] Server=[Samba 

[Samba] CUPS and Samba 3.0 - printers no show

[Ken Sarkies]

Hi [Sambas]

I have RedHat 8.0, and have installed a compiled CUPS 1.1.19pre4 and
Samba 3.0 (latest this week from CVS). It all compiles and installs OK
with CUPS support in Samba, but no printers show up (according to
smbclient -L or from windoze). A reversion to Samba 2.2.8a works
perfectly with the identical setup, including configure options.
Installation and use of printers goes through OK. I assume others have
had success with Samba 3 and CUPS as I haven't seen any problem posts so
far. My ntadmins include administrator accounts for windoze although I
have had hassles with permissions that haven't yet been resolved.


Any ideas or suggestions?


smb.conf

# Global Settings
[global]

   netbios name = HTA41
   workgroup = TRINITY_NT
   server string = Samba Server 3.0 Experimental
   hosts allow = 192.168.1. 127.
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# PRINTERS

   load printers = yes
   printing = cups
   printcap name = cups
   printer admin = @ntadmins

# LOGGING

   log file = /var/log/samba/%m.log
   max log size = 0

# AUTHENTICATION now needs to be done here - setup as BDC

   security = user
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*passwd:*all*authentication*tokens*updated*successfully*
   pam password change = yes
   obey pam restrictions = no

# BROWSER CONTROL OPTIONS for BDC

   local master = yes
   os level = 20
   domain master = no
   preferred master = no
   domain logons = no
   logon path = \\%L\profiles\profiles\%U
   logon home = \\%L\profiles\%U

# MISCELLANEOUS

   map to guest = bad user

# Share Definitions

[printers]
   comment = All Printers
   path = /var/spool/samba
   writeable = no
   printable = yes
   browseable = no

[Data]
   comment = Space for Stuff
   path = /misc
   browseable = yes
   writeable = yes

[homes]
   comment = Home Directories
   browseable = no
   writeable = yes
   valid users = %S
   create mode = 0664
   directory mode = 0775

[print$]
 comment = Printer Drivers
   path = /etc/samba/drivers
   browseable = yes
   guest ok = yes
   read only = yes
   writelist = @ntadmins






-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups printer shared via samba require drives to be mapped

[Melinda Taylor]

Hello,

I am sharing my cups printers via samba (2.2.7) on a redhat 7.3 machine 
running a firewall configured with iptables.

I have included my smb.conf file below. My problem is that windows machines 
can setup the printer just fine, search for the
the server astro, the users enter their smb passwd and username and they 
can ste up the printer.

However I find everytime they reboot their machine, they can no longer 
print to the printer. It is still there but print jobs just sit there. If 
the user, accesses a shared drive such as /home or /data. They are able to 
print again after clearing the print queue. I have got around this problem 
temporarily by mapping a network drive from the server astro on the windows 
machines however sometimes, windows for some unknown loses this mapped 
drive (even though I have set reconnect at logon).

Does this seem like normal behaviour? Is there someway to get around having 
to map a network drive to get the printer to work?

Thanks,

melinda

[global]
   workgroup = ASTROPHYSICS
   server string = Astro
   hosts allow = 129.94.162. 129.94.163. 127.
   printcap name = /etc/printcap
   load printers = yes
   printing = cups
   printcap name = cups
   guest account = smb
   log file = /var/log/samba/%m.log
   max log size = 0
   security = user
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   unix password sync = Yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *New*password* %n\n *Retype*new*password* %n\n 
*passwd:*all*authentication*tokens*updated*successfully*
   pam password change = yes
   obey pam restrictions = yes
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   dns proxy = no
[homes]
   comment = Home Directories
   browseable = no
   writable = yes
   valid users = %S
   create mode = 0664
   directory mode = 0755
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   public = yes
   guest ok = Yes
   writable = no
   printable = yes
[print$]
comment = Printer Drivers
path = /etc/samba/drivers
browseable = yes
guest ok = no
read only = yes
write list = @cups
[Data]
   comment = %U Data Directory
   path = /data/%U
   valid users = %U
   public = no
   writable = yes
   printable = no

Thanks,

Melinda

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba+CUPS+Drivers autodownload

[Dragan Krnic]

>> Samba built with this change will not report
>> NT_STATUS_UNSUCCESSFUL when you execute "adddriver"
>> subcommand of rpcclient.
>
>I found reference to this in one of your posts and in 
>Samba's bugzilla database. I've tried commenting out 
>this code, rebuilding, installing, etc. but I still 
>get the error.

Unfortunately, many conditions can lead to the
same symptoms. Omitting a mandatory field in the
third parameter, mixing files from different levels,
versions and OS's, improper path permissions, etc.

You should increase the logging level drastically,
e.g. "smbcontrol smbd debug 999" execute the command,
reduce the logging level and pore over the logs. 

>> The other bug prevents rpcclient's "enumdrivers"
>> subcommands from completing and can be fixed by 
..
>This fix is in the CVS version I checked out. Their 
>fix is slightly different, but I can see it does the 
>same thing.

>> Another problem is building a fixed version of 
>> Samba. Somehow, the Linux vendors refrain from 
..
>I'm running on Slackware, so there's a Slackbuild 
>script in the source tree that explains how Samba was 
>built. At the moment I'm just doing a standard
>./configure build as I just want to see if this 
>printing will work smoothly.
>
>As of the current CVS checkout I made yesterday, and 
>trying your commenting-out fix, I still get the 
>errors.

Might it be, that your edits get somehow ignored
by the build script? Dumb question, perhaps.



Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba+CUPS+Drivers autodownload

[Dragan Krnic]

Hi Matt,

the problem you referred to is discussed in detail
as bug #82 in Samba's bug tracking tool. It consists
of 2 bugs. One prevents the registration of drivers
and is due to a NULL-pointer passed from that part
of code in rpc_server/srv_spoolss_nt.c which calls 
sys_adminlog function. It begins with the comment

   /* BEGIN_ADMIN_LOG */

and ends with the comment

   /* END_ADMIN_LOG */

The comments surround the code which should log
that a printer driver has been added, listing
driver's name, its OS, and admin's name. Since
this sys-admin-logging is non-essential for the 
operation of Samba and CUPS you may simply extend
the comment to include the whole code in between
the two comments by removing the first "*/" and
the second "/*" like this:

   /* BEGIN_ADMIN_LOG
. code here commented out 
  END_ADMIN_LOG */

Samba built with this change will not report
NT_STATUS_UNSUCCESSFUL when you execute "adddriver"
subcommand of rpcclient.

The other bug prevents rpcclient's "enumdrivers"
subcommands from completing and can be fixed by 
changing the line #943 in lib/util_unistr.c so
that it reads:

  src_len = ( src == NULL ? 0 :  strlen_w(src)*2+2 );

instead of just

  src_len = strlen_w(src)*2+2;

So that you may find that part easily, here are the
7 lines surrounding and including the offending line:

940dest_len=MAXUNI-3;
941
942if (flags & STR_TERMINATE) 
943   src_len = strlen_w(src)*2+2;
944 
945dest_len = MIN((src_len/2), (dest_len-1));
946unistr_to_ascii(dest, src, dest_len);

Another problem is building a fixed version of Samba.
Somehow, the Linux vendors refrain from disclosing
in full detail the files necessary for the build.

They all more or less build their packages with
"rpm -bb" which requires a ".spec" file. This is a 
kind of script listing all the dependencies, 
prerequisites, and steps to be taken in order to
build an RPM fully automatically. Some of these 
steps consist of patching different original Samba 
files to either fix defects discovered after a major
release came out or that are known to occur only in a 
specific distro, in other words to make it adhere to 
some specifics of a vendor's distro. The patch files
are the correct place to register such changes to
the source code as I mentioned above.

However, vendors just mirror the latest samba source 
and let YOU figure out what is needed to be done in 
order for the software to build and run. In my view 
this is in clear contravention of the GPL!!! The 
vendors are selling the work of others omitting the 
essential information which makes it tick on their 
particular distro. This is a SERIOUS PROBLEM which
has to be raised, unless of course it is just my
inability to locate those informations on the web.

In my case, SuSE 8.2, the vendor did a thorough job
of providing almost all of the pre-requisite files on 
their sites. The missing ones were a few documents and 
a couple of template Samba configuration files which 
were already in their original 2.2.8a offering. It 
wasn't difficult to just copy those files into 
the /usr/src/packages/SOURCES with the rest.

But try that with RedHat! I would really like to 
know which other vendors provide their customer with
such informations in full detail.

What is missing even in SuSE's documentation is a
list of all the devel packages which need to be
installed on a system in order to be able to build
samba. I mean, I ran myself into the problem that 
configure failed and stopped the build when it tried 
to verify if it can use the included popt lib. It 
couldn't compile the test case because I didn't have
"openldap2-deve-l2.1.12-44" installed. My guess is 
that you probably need the following:

   cups-devel-1.1.18-56
   libacl-devel-2.2.6-8
   libattr-devel-2.4.0-14
   libsmbclient-devel-2.2.8a-3
   openldap2-devel-2.1.12-44
   openssl-devel-0.9.6i-12
   pam-devel-0.77-38
   popt-devel-1.6.4-31

but I'm not sure because I've installed all devel 
packages (130 of them) just in case. I would be much
obliged if someone could correct this list, if
something is missing or superfluous.

Matt, I hope this information helps anyone confronted 
with this bug in 2.2.8a. If you happen to have SuSE
8.2 on your system, I might send you a tarball with
.spec and related files for the build. I guess that 
the same files would also work for RedHat and other 
distros but then again I might be wrong.

Cheers
Dragan



Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba+CUPS+Driver autodownload

[Kurt Pfeifle]

 Mathias Homann admin at eregion.de

Thu May 29 18:46:50 GMT 2003

Am Donnerstag, 29. Mai 2003 14:39 schrieb Kurt Pfeifle:

 http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/
Why on earth do people keep on insisting that imprints is useful and 
functional?
Hi, Mathias,

yours is the first comment I read about that section. In fact, this section
comes from the old HOWTO collection, and I felt it was only appropriate to
keep it in, if the warning about its unmaintained status is made more
prominent and the call for volunteers is repeated.
It's been dead since more than a year,
My draft says so and names a date: since December 2000.

has never worked for me, and anybody 
I've been mailing about imprints has not even had an active maintainer for 
more than a year.

I'm the first to say that the idea _behind_ it is temptingm
That's why I feel it should not be just abandoned.

but without anyone 
actively maintining it, and without a reliable, working version out there, it 
should not be mentioned as a _solution_.
OK -- this is open for discussion. If I hear more voices about it blowing
the same horn, it might go out...
bye,
MH
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba+CUPS+Driver autodownload

[Mathias Homann]

Am Donnerstag, 29. Mai 2003 14:39 schrieb Kurt Pfeifle:

>  http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/

Why on earth do people keep on insisting that imprints is useful and 
functional?

It's been dead since more than a year, has never worked for me, and anybody 
I've been mailing about imprints has not even had an active maintainer for 
more than a year.

I'm the first to say that the idea _behind_ it is temptingm but without anyone 
actively maintining it, and without a reliable, working version out there, it 
should not be mentioned as a _solution_.

bye,
MH

-- 
Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 
UWG und 823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede 
kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren 
Weitergabe an Dritte ist ausdrücklich untersagt!

gpg key fingerprint: 5F64 4C92 9B77 DE37 D184  C5F9 B013 44E7 27BD 763C

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Samba+CUPS+Driver autodownload

[Matt Dainty]

Hi,

The version of CUPS and cupsaddsmb is currently 1.1.18, (due to be
upgraded to 1.1.19 soon-ish).

Here's the output of running "cupsaddsmb -v ...":

# /usr/sbin/cupsaddsmb -v -U root oki7200
Password for root required to access localhost via SAMBA: 
Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put 
/var/spool/cups/tmp/3ed6034d677c4 W32X86/oki7200.PPD;put 
/usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put 
/usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put 
/usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
added interface ip=192.168.50.129 bcast=192.168.50.255 nmask=255.255.255.128
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[XREFER] OS=[Unix] Server=[Samba 2.2.9pre1]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
putting file /var/spool/cups/tmp/3ed6034d677c4 as \W32X86/oki7200.PPD (16523.1 kb/s) 
(average 16523.4 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (23519.6 
kb/s) (average 22062.2 kb/s)
putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (22083.0 
kb/s) (average 22066.4 kb/s)
putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (18016.8 
kb/s) (average 21935.8 kb/s)

Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86" 
"oki7200:ADOBEPS5.DLL:oki7200.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
cmd = adddriver "Windows NT x86" 
"oki7200:ADOBEPS5.DLL:oki7200.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"
result was NT_STATUS_UNSUCCESSFUL

Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put 
/var/spool/cups/tmp/3ed6034d677c4 WIN40/oki7200.PPD;put 
/usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put 
/usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put 
/usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put 
/usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put 
/usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put 
/usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
added interface ip=192.168.50.129 bcast=192.168.50.255 nmask=255.255.255.128
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[XREFER] OS=[Unix] Server=[Samba 2.2.9pre1]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
putting file /var/spool/cups/tmp/3ed6034d677c4 as \WIN40/oki7200.PPD (20653.8 kb/s) 
(average 20654.3 kb/s)
putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (23420.0 kb/s) 
(average 23025.0 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (23434.6 
kb/s) (average 23294.7 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (23981.6 
kb/s) (average 23355.8 kb/s)
putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (13174.5 
kb/s) (average 23244.0 kb/s)
putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (23071.4 kb/s) 
(average 23235.0 kb/s)
putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s) 
(average 23096.6 kb/s)

Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0" 
"oki7200:ADOBEPS4.DRV:oki7200.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,oki7200.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
cmd = adddriver "Windows 4.0" 
"oki7200:ADOBEPS4.DRV:oki7200.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,oki7200.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
result was NT_STATUS_UNSUCCESSFUL

Running command: rpcclient localhost -N -U'root%secret' -c 'setdriver oki7200 oki7200'
cmd = setdriver oki7200 oki7200
Succesfully set oki7200 to driver oki7200.

I've also tried running the enum{printers,drivers} commands.
"enumprinters [12]" both give output, but "enumprinters 3" gives me the
same NT_STATUS_UNSUCCESSFUL. "enumdrivers [123]" runs without an error
message, but displays nothing apart from the "cmd = ...".

Cheers

Matt
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba+CUPS+Driver autodownload

[Kurt Pfeifle]

Matt Dainty wrote on Samba-Digest


I'm trying to get Samba to offer the Adobe driver automatically for the
two printers I have set up with CUPS.
I have all of the necessary files plucked out of the Adobe Postscript
Windows driver package, but I'm hitting the problem when I come to run
"cupsaddsmb -v ..." that the "rpcclient adddrivers" command always fails
with NT_STATUS_UNSUCCESSFUL.
Which version of CUPS/cupsaddsmb are you running?

Have you seen the docu on

http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/

about this?

The drivers are being copied to the [print$]
directories correctly, just the driver registration fails.
Before looking at the level 100 Samba log, let's first see the "-v"
cupsaddsmb output on stderr
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba+CUPS+Driver autodownload

[Matt Dainty]

Hi,

I'm trying to get Samba to offer the Adobe driver automatically for the
two printers I have set up with CUPS.

I have all of the necessary files plucked out of the Adobe Postscript
Windows driver package, but I'm hitting the problem when I come to run
"cupsaddsmb -v ..." that the "rpcclient adddrivers" command always fails
with NT_STATUS_UNSUCCESSFUL. The drivers are being copied to the [print$]
directories correctly, just the driver registration fails.

I found the posts relating to this error in 2.2.8a, so I've actually
downloaded the current CVS SAMBA_2_2 branch as of yesterday, and I'm
still getting the same problem, which I assumed would be fixed in the
source now.

I have run "rpcclient -d 100 ..." but it's quite big so if anyone would
like to see that, please let me know.

Anyone have this fixed and working?

Cheers

Matt
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Redhat 8 Samba+CUPS

[Ulrich Kohlhase]

Baxter,

> Hi all.  In the interest of using a more mainstream business
> distribution, I changed my faithful file/printserver over to Redhat
> 8.0 from Debian Testing. Now, my shared directories are working fine
> but printing is not working.  I can browse to the printer using net
> view or Network Neighborhood in Windows or using smbclient -L in
> Linux but printing is not working. I've checked /var/log/samba/ and
> the only errors I found dealt w/ permissions on /var/spool/cups which
> I fixed w/ a chmod 1777.  Right now I suspect the printcap name =
> /etc/printca is my problem but I'm not sure.

You didn't include your printer share definitions, but we'll have a look at
the global part first:

> path = "/var/spool/cups"

Probably a better idea is to have another spool directory for Samba's print
files. This makes your configuration more flexible and avoids possible
permission problems with the cups spool dir. We use "path =
/var/spool/samba" and did a "chmod 777" on this dir. Cupsd is running as
user "lp" in group "lp" (see cupsd.conf) and a listing of "/var/spool/samba"
shows

drwx--   3 lp   lp   12288 Mär 23 11:22 cups
drwxrwxrwx   2 lp   lp  25 Mär 23 11:22 samba

If you omit the "-r" switch usually used with the lpr print command, the
(postcript) print files should stay in the Samba spool dir and not be
deleted. This may be useful for debugging purposes.

> printing = cups
> printcap name = /etc/printcap

In the thread "Clarifying CUPS Printing" Kurt Pfeifle gave a detailed
description regarding the "printing" and "printcap name" parameters, see
http://marc.theaimsgroup.com/?l=samba&m=103619611005286&w=2
Please check if Samba is compiled against the cups library with the
following command "ldd `which smbd` | grep libcups".

> valid users = bax morbo amy nobody planetexpress bender
> invalid users = root wins support = true

Not a printing related question, but why do have "valid users" in the global
part? Users without valid /etc/passwd and smbpasswd entries can't even
connect to shares unless "guest ok = yes" is set. A nice and easy option is
to disable users, see "man smbpasswd". What reason do you use "invalid users
= root" for and shouldn't the "wins support" param follow on the next line?


> default = printers

Why do have this parameter in your smb.conf? Is it still supported and what
does testparm say?

Does printing from linux work at all?

Another thing to watch for are PAM settings and restrictions if the Samba
and / or Cups packages are compiled with PAM support. You specified "obey
pam restrictions = Yes" in your smb.conf, which may be related to your
printing problems. See the files for cups and Samba in "/etc/pam.d".


HTH,
Uli



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Redhat 8 Samba+CUPS

[Baxter Shepperson]

  Hi all.  In the interest of using a more mainstream business distribution, I 
changed my faithful file/printserver over to Redhat 8.0 from Debian Testing.  
Now, my shared directories are working fine but printing is not working.  I 
can browse to the printer using net view or Network Neighborhood in Windows 
or using smbclient -L in Linux but printing is not working.  I've checked 
/var/log/samba/ and the only errors I found dealt w/ permissions on 
/var/spool/cups which I fixed w/ a chmod 1777.  Right now I suspect the 
printcap name = /etc/printca is my problem but I'm not sure.  If anybody has 
some input on this or even a working smb.conf using Redhat 8.0 w/ CUPS, I 
would appreciate it.  I am including a portion of my smb.conf in case someone 
can spot the error I'm missing :)
# Global parameters
[global]
path = /var/spool/cups
passwd program = /usr/bin/passwd %u
domain master = True
printing = cups
dns proxy = No
null passwords = Yes
encrypt passwords = Yes
valid users = bax morbo amy nobody planetexpress bender
invalid users = root
wins support = true
printcap name = /etc/printcap
max log size = 1000
hosts allow = 192.168.1.
obey pam restrictions = Yes
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n 
*Retype\snew\sUNIX\spassword:* %n\n .
username level = 8
map to guest = Bad User
security = user
message command = /bin/sh -c '/usr/bin/linpopup
server string = %h server (Samba %v)
workgroup = SHEP
syslog = 0
netbios name = PRINTSERVER
log file = /var/log/samba/log.%m
load printers = yes
os level = 35
default = printers


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS + Samba printing (newbie)

[Subba Rao]

Hi,

I am a newbie to CUPS printing system.  I have installed it on my Debian 3.0
(woody) system. Now I can print test pages thru the Browser.

How do I add it as the network printer to the Samba server?  I need to
print from a Windows client.

Thank you in advance for any help.

-- 
Subba Rao
[EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cups printing and user names from trusted domains

[Kurt Pfeifle]

Andrew Bartlett wrote on Samba-Digest:

[Samba] cups printing and user names from trusted domains
Andrew Bartlett abartlet at samba.org
Sat Mar 8 21:46:01 GMT 2003
On Sat, 2003-03-08 at 06:51, Andrew Bartlett wrote:
On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> 
> Im currently running some tests for a samba/CUPS based print server.
> The print server is a member of an NT domain and uses winbind to import
> NT domain users. Users accessing the print server will be not from the
> same domain but from trusted domains.
> Everything basically seems to work, once you use sufficiently new
> versions of cups and samba. (I'm on Debian woody, so I needed to get
> the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian
> unstable to get a version of cupsaddsmb that actually works.)
> 
> One remaining problem is that the print jobs show up in the CUPS queue as
> owned by "user" instead of "domain\user". Moreover, print jobs submitted by
> "domain1\user1" can be deleted by another user "domain2\user1" who has the same
> user name in a different trusted domain.
> 
> Am I doing something wrong? I remember vaguely, that during the first stage
> of my experiments (maybe with an older version of the cupsys packages), some
> printjobs showed up with a qualified name "domain\user".

I'll see what I can do to make them show up as the unix username used
for login.  This will be in HEAD, and will mean that they use the name
in the form 'domain\username' if you used winbind or 'username' if you
didn't.  (Effectively).
I've looked into this, and it looks like our CUPS printing is quite
broken in this respect.
The first thing I noticed is the lack of error handling we don't pass
the error back to the client when the printing fails.
However, when looking at the code in relation to your problem, I noticed
that we send completely the wrong username to CUPS.  For both the print
job's submission, and later attempts to cancel or pause a job, we send
the *original* 'smb_name'.  This is the unqualified username of the user
that originally sent the job, before any mapping.
The correct thing to send would be the unix name - possibly directly
from current_user, but I need to check on this.
Hmmm... I'm not so sure this is what most people would desire.

CUPS logs the names in question, for example in its "page_log" for
accounting purposes. If we serve Windows clients, and if we now and
then want to evaluated the page_log and create statistics and reports
from it -- is it the Unix name or the Windows user name we want to
appear there?
Jerry - can you put your eye to this?  From inside the print subsystem,
what is the correct way to get the current unix username?
Andrew Bartlett
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] cups printing and user names from trusted domains

[Andrew Bartlett]

On Sat, 2003-03-08 at 06:51, Andrew Bartlett wrote:
> On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > 
> > Im currently running some tests for a samba/CUPS based print server.
> > The print server is a member of an NT domain and uses winbind to import
> > NT domain users. Users accessing the print server will be not from the
> > same domain but from trusted domains.
> > Everything basically seems to work, once you use sufficiently new
> > versions of cups and samba. (I'm on Debian woody, so I needed to get
> > the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian
> > unstable to get a version of cupsaddsmb that actually works.)
> > 
> > One remaining problem is that the print jobs show up in the CUPS queue as
> > owned by "user" instead of "domain\user". Moreover, print jobs submitted by
> > "domain1\user1" can be deleted by another user "domain2\user1" who has the same
> > user name in a different trusted domain.
> > 
> > Am I doing something wrong? I remember vaguely, that during the first stage
> > of my experiments (maybe with an older version of the cupsys packages), some
> > printjobs showed up with a qualified name "domain\user".
> 
> I'll see what I can do to make them show up as the unix username used
> for login.  This will be in HEAD, and will mean that they use the name
> in the form 'domain\username' if you used winbind or 'username' if you
> didn't.  (Effectively).

I've looked into this, and it looks like our CUPS printing is quite
broken in this respect.

The first thing I noticed is the lack of error handling we don't pass
the error back to the client when the printing fails.

However, when looking at the code in relation to your problem, I noticed
that we send completely the wrong username to CUPS.  For both the print
job's submission, and later attempts to cancel or pause a job, we send
the *original* 'smb_name'.  This is the unqualified username of the user
that originally sent the job, before any mapping.

The correct thing to send would be the unix name - possibly directly
from current_user, but I need to check on this.

Jerry - can you put your eye to this?  From inside the print subsystem,
what is the correct way to get the current unix username?

Andrew Bartlett

-- 
Andrew Bartlett [EMAIL PROTECTED]
Manager, Authentication Subsystems, Samba Team  [EMAIL PROTECTED]
Student Network Administrator, Hawker College   [EMAIL PROTECTED]
http://samba.org http://build.samba.org http://hawkerc.net


signature.asc
Description: This is a digitally signed message part
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] cups printing and user names from trusted domains

[Andrew Bartlett]

On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> 
> Im currently running some tests for a samba/CUPS based print server.
> The print server is a member of an NT domain and uses winbind to import
> NT domain users. Users accessing the print server will be not from the
> same domain but from trusted domains.
> Everything basically seems to work, once you use sufficiently new
> versions of cups and samba. (I'm on Debian woody, so I needed to get
> the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian
> unstable to get a version of cupsaddsmb that actually works.)
> 
> One remaining problem is that the print jobs show up in the CUPS queue as
> owned by "user" instead of "domain\user". Moreover, print jobs submitted by
> "domain1\user1" can be deleted by another user "domain2\user1" who has the same
> user name in a different trusted domain.
> 
> Am I doing something wrong? I remember vaguely, that during the first stage
> of my experiments (maybe with an older version of the cupsys packages), some
> printjobs showed up with a qualified name "domain\user".

I'll see what I can do to make them show up as the unix username used
for login.  This will be in HEAD, and will mean that they use the name
in the form 'domain\username' if you used winbind or 'username' if you
didn't.  (Effectively).

Andrew Bartlett

-- 
Andrew Bartlett [EMAIL PROTECTED]
Manager, Authentication Subsystems, Samba Team  [EMAIL PROTECTED]
Student Network Administrator, Hawker College   [EMAIL PROTECTED]
http://samba.org http://build.samba.org http://hawkerc.net


signature.asc
Description: This is a digitally signed message part
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cups printing and user names from trusted domains

[Wolfgang Ratzka]

-BEGIN PGP SIGNED MESSAGE-

Im currently running some tests for a samba/CUPS based print server.
The print server is a member of an NT domain and uses winbind to import
NT domain users. Users accessing the print server will be not from the
same domain but from trusted domains.
Everything basically seems to work, once you use sufficiently new
versions of cups and samba. (I'm on Debian woody, so I needed to get
the 2.2.7a debs from samba.org, and cupsys-* 1.1.18-2 from Debian
unstable to get a version of cupsaddsmb that actually works.)
One remaining problem is that the print jobs show up in the CUPS queue as
owned by "user" instead of "domain\user". Moreover, print jobs submitted by
"domain1\user1" can be deleted by another user "domain2\user1" who has the same
user name in a different trusted domain.
Am I doing something wrong? I remember vaguely, that during the first stage
of my experiments (maybe with an older version of the cupsys packages), some
printjobs showed up with a qualified name "domain\user".
Kind regards,
Wolfgang Ratzka
- smb.conf---
[global]
~   workgroup = MYDOMAIN
~   server string = %h print server running samba %v
~   load printers = yes
~   printcap name = cups
~   printing = cups
~   printer admin = @MYDOMAIN\Druck-Admins
~   admin users = @MYDOMAIN\Druck-Admins
~   guest account = nobody
~   log file = /var/log/samba/log.%m
~   max log size = 1000
~   syslog = 0

~   security = domain
~   password server = *
~   encrypt passwords = true
~   socket options = TCP_NODELAY
~   wins server = 
~   dns proxy = no
~   passwd program = /usr/bin/passwd %u
~   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n .
~   obey pam restrictions = yes
~   winbind uid = 1-6
~   winbind gid = 1-6
~   character set = ISO8859-1
~   client code page = 850
[printers]
~   comment = All Printers
~   browseable = yes
~   path = /tmp
~   printable = yes
~   public = no
~   writable = no
~   create mode = 0700
~   printer admin = @MYDOMAIN\Druck-Admins
[print$]
~   comment = Printer Drivers
~   path = /var/lib/samba/drivers
~   browseable = yes
~   guest ok = no
~   read only = yes
~   write list = @MYDOMAIN\Druck-Admins
~   create mask = 0755
~   directory mask = 0755
- --
Wolfgang Ratzka  Phone: +49 6421 2823531  FAX: +49 6421 2826994
Uni Marburg,  HRZ, Hans-Meerwein-Str., D-35032 Marburg, Germany
~  http://www.uni-marburg.de/hrz/mitarbeiter/ratzka.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEVAwUBPmjTFRwiO5rz0xULAQHiZwf9HH6OcbQHGF9kUnveS+JEDIauoBYQeBb0
bMgOe60CnKzhKt0+aRHVdBaK2hzQ+x66NdtmW3nPmmSvChqCzeY/plMcFPnxFN02
PA8h1ycD9dfAjVoMLr/+XZkTvpEKz5tXlZFg5WuSreBMYfA+MNZ11VXvLk2W6Y9N
O9ReJFbZNJzvKrjOKNUODzsfMIljzBzvRGDgKotrnXZM5ytlIkofWKnfKmmYU58i
sdBZRrSBjn/x5CHDOdC2i8Tv/uRTFW1CDJCxb1ow6DKSue2rrrjTKhQZlyLqVBEO
yQD+X/LqAsrnXkC8GhWOBeHZb28f4CcgGMAmmf/N6lmbgMjRua3SSg==
=NLPa
-END PGP SIGNATURE-
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba, CUPs & Win2000 printing

[jason]

...done some more investigating on the Win2000 - Samba/CUPS print problem 
I posted earlier. As I said before, everything works fine using Samba as 
PDC with Win2000 client on a test network except for printing to this 
printer. I can print to this printer from the Linux machine through X ok.

If I try an

#echo "^MHello World^L" | smbclient "//sambaserver/printername"

...from a shell on the Linux/Samba machine I get:

tree connect failed: NT_STATUS_BAD_NETWORK_NAME

I have verified that I am using the correct case when when typing the 
share names as I've heard that smbclient is case sensitive. If I try from 
the DOS prompt on the Win2000 client (echo Hello^L > 
\\sambaserver\printername) I get "The network path was not found" but I 
can ping the Samba server using the machine name from the Win2000 client?

If I do an:

#smbclient -L //sambaserver -Uusername

The printer share name appears in the list?

I also tried adding the printer to the Win2000 client using 
"http://sambaserver:631/printers/printername"; but I then get  a message:

"Could not connect to printer. Access denied"

Are there any other tests I can do to narrow down where the problem could 
be? I've spent days trying to figure this out and havent really managed to 
get anywhere?

..I apologise once again for my basic Linux knowledge at the moment - I'm 
getting there.

Jase

"Bradley W. Langhorst" <[EMAIL PROTECTED]> wrote on 01/03/2003 01:27:56 
AM:

> On Thu, 2003-02-27 at 23:35, [EMAIL PROTECTED] wrote:
> > I'm very new to Linux and Samba so bear with me - I am migrating our 
> 
> > printcap name = cups
> ...
> > printing = cups
> i think this is all you need...
> 
> > 
> > [printers]
> > comment = All Printers
> > path = /var/spool/samba
> > printer admin = root
> > guest ok = Yes
> > printable = Yes
> > print command = lpr-cups -P %p -o raw %s
> > lpq command = lpstat -o %p
> > lprm command = cancel %p-%j
> > use client driver = Yes
> > browseable = No
> here's my printers share
> [printers]
> comment = All Printers
> path = /var/spool/samba
> printable = Yes
> browseable = No
> 
> I also use driver downloading with at print$ share 
> but worry about that after you get basic printing working...
> 
> best wishes!
> 
> brad
> > 
> > PS. anyone use HP Web Jetadmin software on Linux?
> i think there are some oss tools that can do some port 9100
> adminstration...
> -- 
> Bradley W. Langhorst <[EMAIL PROTECTED]>
> 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba, CUPs & Win2000 printing

[Bradley W. Langhorst]

On Thu, 2003-02-27 at 23:35, [EMAIL PROTECTED] wrote:
> I'm very new to Linux and Samba so bear with me - I am migrating our 

> printcap name = cups
...
> printing = cups
i think this is all you need...

> 
> [printers]
> comment = All Printers
> path = /var/spool/samba
> printer admin = root
> guest ok = Yes
> printable = Yes
> print command = lpr-cups -P %p -o raw %s
> lpq command = lpstat -o %p
> lprm command = cancel %p-%j
> use client driver = Yes
> browseable = No
here's my printers share
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

I also use driver downloading with at print$ share 
but worry about that after you get basic printing working...

best wishes!

brad
> 
> PS. anyone use HP Web Jetadmin software on Linux?
i think there are some oss tools that can do some port 9100
adminstration...
-- 
Bradley W. Langhorst <[EMAIL PROTECTED]>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba, CUPs & Win2000 printing

[jason]

I'm very new to Linux and Samba so bear with me - I am migrating our 
business to a Linux/Samba network from an NT network - using Samba as a 
PDC.

We are running RH7.3, Samba v2.2.7a, and CUPS v1.1.14

I have a test network set-up which includes the Linux/Samba PDC server, a 
Win2000 client and a HP Jetdirect network printer (Laserjet 4Si)

Domain logons and filesharing works fine, but I cannot get the Win2000 
client to print to the network printer through Samba. I am using CUPS for 
printing on the Linux machine - I have set-up the jetdirect printer using 
the "HP Laserjet 4V, 4Si, CUPS+GIMP-print v4.2.0" driver and can print 
test pages via CUPS admin page and can also print to the printer from 
Mozilla etc through X on the Linux machine.

Samba automatically lists the printer after its been set-up in CUPS.

On the Win2000 client I go to the add printer applet and can browse to the 
printer on the Samba server, select it - it gives the message saying the 
driver on the server is not correct, would I like to install a local 
driver. I install the native Win2000 HP 4Si driver, all goes well - I get 
the 'ready' status when the printer is selected in the printers folder but 
if I try to print a test page I immediately get:

 "Test page failed to print. Want to see the useless troubleshooter for 
assistance? Unable to create a print job."

If I try and print from a something like M$ Word I get: "Windows cannot 
print due to a problem with the current printer setup. Blah blah try 
printing a test page blah..."

Notepad returns: " A StartDocPrinter call was not issued"


Any help would be much appreciated - I cant kill the NT server until I 
have these jetdirect printers working through Samba!

Here is my smb.conf:

# Samba config file created using SWAT
# from 10.0.0.198 (10.0.0.198)
# Date: 2003/02/28 15:27:10

# Global parameters
[global]
workgroup = MACSERVICE
server string = Samba Server
encrypt passwords = Yes
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n 
*passwd:*all*authentication*tokens*updated*successfully*
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 0
announce version = 4
time server = Yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = cups
logon script = logonscript.bat '%G'
logon drive = g:
domain logons = Yes
os level = 99
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
winbind uid = 1-2
winbind gid = 1-2
template shell = /bin/bash
winbind separator = +
winbind cache time = 10
hosts allow = 10.0.0. 127.
printing = cups

[homes]
comment = Home Directories
read only = No
create mask = 0664
directory mask = 0775
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printer admin = root
guest ok = Yes
printable = Yes
print command = lpr-cups -P %p -o raw %s
lpq command = lpstat -o %p
lprm command = cancel %p-%j
use client driver = Yes
browseable = No

<-- irrelevent shares stuff removed -->

[netlogon]
comment = Netlogon share
path = /data/netlogon
write list = @admins
oplocks = No

[print$]
comment = Printer Drivers
path = /data/printer_drivers
write list = root

PS. anyone use HP Web Jetadmin software on Linux?
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS on RH 7.3

[Kevin Smith]

I installed this last night and so far it look promising. One thing. I cant
seem to access via MSIE. I've allowed port 631 on the firewall. but I still
get the DNS server error. I've tried using the IP address, and the actual
name, both seem to WANT to find it as they look for about 2 minutes, but
never does. 
I've looking the cupsd.conf, but am not sure what to change. The
/var/log/meessages doesn't show that it was dropped or refused. So isothere
another port that I need to open? The docs are good, but I couldn't find
anything addressing this problem. Which of course means , it right under my
nose. 

TIA 
Kev

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS or LPRng?

[Jon Niehof]

To be fair, I'm using Debian, so I used the .deb packages. They went in with
no hassle. You may have a hard time with it using a lesser distro. :-)


Ooooh, them's fighting words :)
I've been running Debian for about five years now but I do 
install everything from source. FWIW the main problem was in 
documentation--the CUPS documentation isn't exactly good 
about telling you when/how to install postscript filters.

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS or LPRng?

[Trey Nolen]

> As a counterexample I had a *hell* of a time getting CUPS
> going and the web interface still dies on me whenever I try
> to do anything from it. Now that it's configured though it's
>   been solid and reliable as long as I stick to command line.


To be fair, I'm using Debian, so I used the .deb packages. They went in with
no hassle. You may have a hard time with it using a lesser distro. :-)


Trey Noen


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS or LPRng?

[Jon Niehof]

Not only did it fix their issues, but it gives them a nice
web-based administration interface where they can delete jobs if one does
happen to get stuck.  Setup was much easier than I thought it would be and
definitely easier than LPRng if you haven't done work with lpd before.  We
were using HP Laserjet printers which were natively supported by CUPS.

As a counterexample I had a *hell* of a time getting CUPS 
going and the web interface still dies on me whenever I try 
to do anything from it. Now that it's configured though it's 
 been solid and reliable as long as I stick to command line.

CUPS really seems to be the wave of the future though and 
certainly a lot of the filter/driver support is centered on it.

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS or LPRng?

[Trey Nolen]

I've used LPRng for years, but recently we had one client that had printing
problems we just couldn't fix.  We switched them over to CUPS and I was very
impressed.  Not only did it fix their issues, but it gives them a nice
web-based administration interface where they can delete jobs if one does
happen to get stuck.  Setup was much easier than I thought it would be and
definitely easier than LPRng if you haven't done work with lpd before.  We
were using HP Laserjet printers which were natively supported by CUPS.  We
have decided to make CUPS our default printing system for future installs.

Trey Nolen



> Which is better to use on a large Samba print server only being used a
print server for Windows clients?
> Is one more stable then the other? Why is quicker?
>
> Thanks
> Jeff
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS or LPRng?

[Jeff Marcille]

Which is better to use on a large Samba print server only being used a print server 
for Windows clients?
Is one more stable then the other? Why is quicker?

Thanks
Jeff

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPs and Samba and XP

[hans]

Hi Jerry,

I have a log level 10 to look at, it's 6meg though, or 800k zipped for 24
seconds of trying to print and then cancel as per below..  I took a quick
peek through it, but I really don't know exactly what I'm looking at.  Can I
send this to you direct?

Thanks

Hans
- Original Message -
From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Samba" <[EMAIL PROTECTED]>
Sent: Wednesday, January 29, 2003 11:34 AM
Subject: Re: [Samba] CUPs and Samba and XP


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, 29 Jan 2003 [EMAIL PROTECTED] wrote:
>
> > Printing works, cancelling jobs via the web interface works after the
> > spooling is done.  What doesn't work.  Pausing jobs (though that's not
> > as important as the next trouble) and cancelling jobs from XP.  If I
> > cancel a job by hitting the cancel button on a windows print dialogue,
> > the program freezes until I manually restart the XP print spooler
> > service.  If I cancel a job by hitting cancel in the print spooler
> > window, the job does get cancelled (it disappears from the spooler
> > window), but the same problem, the program freezes until I manually
> > restart the spooler.  Anybody seen this before.  I didn't have this
> > trouble when I was using lpd, just recently with cups.  One other side
> > issue, i always have to manually refresh the spooler screen (F5) to see
> > current activity.  Is there a setting that I'm missing that will do that
> > for me.
>
> Check the Samba logs (level 10) and include timestamps to see where the
> hang is occurring.  The refreshing issue is a known isssue in Samba 2.2.
> The Print change notify code is a little iffy.  Much better in
> the SAMBA_3_0 cvs branch.
>
> I should mention that the print change notify stuff requires that the
> NT+ client being running the Server service (renamed to File & Print
> Shareing for MS Networks).
>
>
>
>
> cheers, jerry
>  --
>  Hewlett-Packard- http://www.hp.com
>  SAMBA Team -- http://www.samba.org
>  GnuPG Key   http://www.plainjoe.org/gpg_public.asc
>  "You can never go home again, Oatman, but I guess you can shop there."
> --John Cusack - "Grosse Point Blank" (1997)
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.0 (GNU/Linux)
> Comment: For info see http://quantumlab.net/pine_privacy_guard/
>
> iD8DBQE+OCzhIR7qMdg1EfYRAqPlAJ9FOlYUx3qgd/O9sV2O15AT/w3zJgCeNDaJ
> qgQHWITLgMI4pwFlClb0XWE=
> =8MgN
> -END PGP SIGNATURE-
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>
> ___
> All emails incoming and outgoing from SBS Forestry Inc.
> are scanned by Kaspersky Antivirus.


___
All emails incoming and outgoing from SBS Forestry Inc.
are scanned by Kaspersky Antivirus.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPs and Samba and XP

[Buchan Milne]

[EMAIL PROTECTED] wrote:
> Thanks for the reply.  The Samba server is setup as a PDC, and my computers
> and users authenticat to it properly.  I don't have the XP firewall running
> on any machine.  Printing is great, controlling printing is the problem for
> me.  I'll set my logging to 10 in a little while and post back to the group
> the log as Jerry suggested.
> 

Output of the following would also be useful:

$ grep print /etc/samba/smb.conf|egrep -v '[\;\#]'

Does this affect just XP users, or win2k/winnt also? Do you see the
right name in the print queue (the name of the document, vs the name of
the print file)?

Buchan

-- 
|--Another happy Mandrake Club member--|
Buchan MilneMechanical Engineer, Network Manager
Cellphone * Work+27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPs and Samba and XP

[hans]

Thanks for the reply.  The Samba server is setup as a PDC, and my computers
and users authenticat to it properly.  I don't have the XP firewall running
on any machine.  Printing is great, controlling printing is the problem for
me.  I'll set my logging to 10 in a little while and post back to the group
the log as Jerry suggested.

Thanks

Hans
- Original Message -
From: "Buchan Milne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 30, 2003 2:17 AM
Subject: Re: [Samba] CUPs and Samba and XP


> > Date: Wed, 29 Jan 2003 11:06:53 -0800
> > From: <[EMAIL PROTECTED]>
> > To: "Samba" <[EMAIL PROTECTED]>
> > Subject: [Samba] CUPs and Samba and XP
> > Message-ID: <007e01c2c7c9$959ddce0$ec00a8c0@tweety>
> > Content-Type: text/plain;
> > charset="iso-8859-1"
> > MIME-Version: 1.0
> > Content-Transfer-Encoding: 7bit
> > Precedence: list
> > Message: 2
> >
> > Hullo All.
> >
> > The preamble  Samba 2.2.7a compiled against CUPS, CUPs v 1.1.6
(version
> > that came with Mandrake 9.0), using client side drivers (raw printing)
on
> > XP.
> >
> > Printing works, cancelling jobs via the web interface works after the
> > spooling is done.  What doesn't work.  Pausing jobs (though that's not
as
> > important as the next trouble) and cancelling jobs from XP.
>
> Note that you can't really have user control of print jobs unless the
> user is authenticating to the server, and you haven't given any detail
> on how you are setup. Easiest way to tell on a default installation is
> if you see a share on the server with the username you are logged into
> windows with. If you don't, you're either going to have to add unix
> accounts (if they don't exist) which match the windows user names (or
> use a username map) and set their smbpasswd (smbpasswd -a ) or
> provide more info on how your authentication is setup.
>
> This works fine here, using the samba-2.2.7a-3mdk RPMs available at
> http://ranger.dnsalias.com/mandrake/samba on mandrake 8.0-9.0.
>
> > If I cancel a
> > job by hitting the cancel button on a windows print dialogue, the
program
> > freezes until I manually restart the XP print spooler service.  If I
cancel
> > a job by hitting cancel in the print spooler window, the job does get
> > cancelled (it disappears from the spooler window), but the same problem,
the
> > program freezes until I manually restart the spooler.  Anybody seen this
> > before.   I didn't have this trouble when I was using lpd, just recently
> > with cups.  One other side issue, i always have to manually refresh the
> > spooler screen (F5) to see current activity.  Is there a setting that
I'm
> > missing that will do that for me.
> >
>
> Printing to samba also doens't work that well if you have the XP
> firewall enabled, which be default firewalls off 137-139, preventing
> samba from being able to send a reply. This also affects printers on
> Windows NT servers.
>
> > Thanks for any and all help.
> >
> > Hans Rasmussen
> > Drafting/GIS Coordinator
>
> FYI, grass-5.0.0 is in Mandrake 9.0 contribs if that would interest you
...
>
> Buchan
>
> --
> |--Another happy Mandrake Club member--|
> Buchan MilneMechanical Engineer, Network Manager
> Cellphone * Work+27 82 472 2231 * +27 21 8828820x121
> Stellenbosch Automotive Engineering http://www.cae.co.za
> GPG Key   http://ranger.dnsalias.com/bgmilne.asc
> 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7


___
All emails incoming and outgoing from SBS Forestry Inc.
are scanned by Kaspersky Antivirus.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPs and Samba and XP

[Buchan Milne]

> Date: Wed, 29 Jan 2003 11:06:53 -0800
> From: <[EMAIL PROTECTED]>
> To: "Samba" <[EMAIL PROTECTED]>
> Subject: [Samba] CUPs and Samba and XP
> Message-ID: <007e01c2c7c9$959ddce0$ec00a8c0@tweety>
> Content-Type: text/plain;
>   charset="iso-8859-1"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Message: 2
> 
> Hullo All.
> 
> The preamble  Samba 2.2.7a compiled against CUPS, CUPs v 1.1.6 (version
> that came with Mandrake 9.0), using client side drivers (raw printing) on
> XP.
> 
> Printing works, cancelling jobs via the web interface works after the
> spooling is done.  What doesn't work.  Pausing jobs (though that's not as
> important as the next trouble) and cancelling jobs from XP.  

Note that you can't really have user control of print jobs unless the
user is authenticating to the server, and you haven't given any detail
on how you are setup. Easiest way to tell on a default installation is
if you see a share on the server with the username you are logged into
windows with. If you don't, you're either going to have to add unix
accounts (if they don't exist) which match the windows user names (or
use a username map) and set their smbpasswd (smbpasswd -a ) or
provide more info on how your authentication is setup.

This works fine here, using the samba-2.2.7a-3mdk RPMs available at
http://ranger.dnsalias.com/mandrake/samba on mandrake 8.0-9.0.

> If I cancel a
> job by hitting the cancel button on a windows print dialogue, the program
> freezes until I manually restart the XP print spooler service.  If I cancel
> a job by hitting cancel in the print spooler window, the job does get
> cancelled (it disappears from the spooler window), but the same problem, the
> program freezes until I manually restart the spooler.  Anybody seen this
> before.   I didn't have this trouble when I was using lpd, just recently
> with cups.  One other side issue, i always have to manually refresh the
> spooler screen (F5) to see current activity.  Is there a setting that I'm
> missing that will do that for me.
> 

Printing to samba also doens't work that well if you have the XP
firewall enabled, which be default firewalls off 137-139, preventing
samba from being able to send a reply. This also affects printers on
Windows NT servers.

> Thanks for any and all help.
> 
> Hans Rasmussen
> Drafting/GIS Coordinator

FYI, grass-5.0.0 is in Mandrake 9.0 contribs if that would interest you ...

Buchan

-- 
|--Another happy Mandrake Club member--|
Buchan MilneMechanical Engineer, Network Manager
Cellphone * Work+27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPs and Samba and XP

[Gerald (Jerry) Carter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 29 Jan 2003 [EMAIL PROTECTED] wrote:

> Printing works, cancelling jobs via the web interface works after the
> spooling is done.  What doesn't work.  Pausing jobs (though that's not
> as important as the next trouble) and cancelling jobs from XP.  If I
> cancel a job by hitting the cancel button on a windows print dialogue,
> the program freezes until I manually restart the XP print spooler
> service.  If I cancel a job by hitting cancel in the print spooler
> window, the job does get cancelled (it disappears from the spooler
> window), but the same problem, the program freezes until I manually
> restart the spooler.  Anybody seen this before.  I didn't have this
> trouble when I was using lpd, just recently with cups.  One other side
> issue, i always have to manually refresh the spooler screen (F5) to see
> current activity.  Is there a setting that I'm missing that will do that
> for me.

Check the Samba logs (level 10) and include timestamps to see where the 
hang is occurring.  The refreshing issue is a known isssue in Samba 2.2.
The Print change notify code is a little iffy.  Much better in 
the SAMBA_3_0 cvs branch.  

I should mention that the print change notify stuff requires that the 
NT+ client being running the Server service (renamed to File & Print 
Shareing for MS Networks).




cheers, jerry
 --
 Hewlett-Packard- http://www.hp.com
 SAMBA Team -- http://www.samba.org
 GnuPG Key   http://www.plainjoe.org/gpg_public.asc
 "You can never go home again, Oatman, but I guess you can shop there."  
--John Cusack - "Grosse Point Blank" (1997)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+OCzhIR7qMdg1EfYRAqPlAJ9FOlYUx3qgd/O9sV2O15AT/w3zJgCeNDaJ
qgQHWITLgMI4pwFlClb0XWE=
=8MgN
-END PGP SIGNATURE-

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPs and Samba and XP

[hans]

Hullo All.

The preamble  Samba 2.2.7a compiled against CUPS, CUPs v 1.1.6 (version
that came with Mandrake 9.0), using client side drivers (raw printing) on
XP.

Printing works, cancelling jobs via the web interface works after the
spooling is done.  What doesn't work.  Pausing jobs (though that's not as
important as the next trouble) and cancelling jobs from XP.  If I cancel a
job by hitting the cancel button on a windows print dialogue, the program
freezes until I manually restart the XP print spooler service.  If I cancel
a job by hitting cancel in the print spooler window, the job does get
cancelled (it disappears from the spooler window), but the same problem, the
program freezes until I manually restart the spooler.  Anybody seen this
before.   I didn't have this trouble when I was using lpd, just recently
with cups.  One other side issue, i always have to manually refresh the
spooler screen (F5) to see current activity.  Is there a setting that I'm
missing that will do that for me.

Thanks for any and all help.

Hans Rasmussen
Drafting/GIS Coordinator
SBS Forestry Inc.
250-561-1140


___
All emails incoming and outgoing from SBS Forestry Inc.
are scanned by Kaspersky Antivirus.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cups Printer Driver Donwload with Win9X (Adobe driver/cupsaddsmb) cups-1.1.18, samba-2.2.7

[Hansjoerg Maurer]

Hi,

printer driver download with W2000/Xp (samba-2.2.7 and cups-1.1.18)  and 
the Adobe PS Driver works fine for our location.
But when I try to download a driver with W9X the driver installation 
widzard starts.

Samba logs the following messages...
(Cant determine number of printer driver files...) (see second apandix)
The installation of the driver works with no error. (see first apendix)

Has anyone successfully installed the W9X Adobe Driver?

Thank you very much

Hansjörg



Running command: smbclient //localhost/print\$ -N -U'root%XXX%' -c 
'mkdir W32X86;put /var/spool/cups/tmp/3e256bfa5c7d8 
W32X86/hp2250.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL 
W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL 
W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP 
W32X86/ADOBEPSU.HLP'
added interface ip=129.247.181.169 bcast=129.247.181.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[NTROBOTIC] OS=[Unix] Server=[Samba 2.2.7]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
putting file /var/spool/cups/tmp/3e256bfa5c7d8 as \W32X86/hp2250.PPD 
(787.4 kb/s) (average 787.4 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS5.DLL as 
\W32X86/ADOBEPS5.DLL (1732.1 kb/s) (average 1597.1 kb/s)
putting file /usr/share/cups/drivers/ADOBEPSU.DLL as 
\W32X86/ADOBEPSU.DLL (1965.0 kb/s) (average 1688.9 kb/s)
putting file /usr/share/cups/drivers/ADOBEPSU.HLP as 
\W32X86/ADOBEPSU.HLP (265.5 kb/s) (average 1467.1 kb/s)

Running command: rpcclient localhost -N -U'root%XXX%' -c 'adddriver 
"Windows NT x86" 
"hp2250:ADOBEPS5.DLL:hp2250.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
cmd = adddriver "Windows NT x86" 
"hp2250:ADOBEPS5.DLL:hp2250.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"
Printer Driver hp2250 successfully installed.

Running command: smbclient //localhost/print\$ -N -U'root%XXX%' -c 
'mkdir WIN40;put /var/spool/cups/tmp/3e256bfa5c7d8 WIN40/hp2250.PPD;put 
/usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put 
/usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put 
/usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put 
/usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put 
/usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put 
/usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
added interface ip=129.247.181.169 bcast=129.247.181.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Domain=[NTROBOTIC] OS=[Unix] Server=[Samba 2.2.7]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
putting file /var/spool/cups/tmp/3e256bfa5c7d8 as \WIN40/hp2250.PPD 
(691.0 kb/s) (average 691.0 kb/s)
putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM 
(1437.6 kb/s) (average 1354.4 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV 
(1449.5 kb/s) (average 1417.7 kb/s)
putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP 
(1199.4 kb/s) (average 1390.1 kb/s)
putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD 
(280.4 kb/s) (average 1356.5 kb/s)
putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL 
(1955.2 kb/s) (average 1378.4 kb/s)
putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL 
(602.1 kb/s) (average 1336.0 kb/s)

Running command: rpcclient localhost -N -U'root%XXX%' -c 'adddriver 
"Windows 4.0" 
"hp2250:ADOBEPS4.DRV:hp2250.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,hp2250.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
cmd = adddriver "Windows 4.0" 
"hp2250:ADOBEPS4.DRV:hp2250.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,hp2250.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
Printer Driver hp2250 successfully installed.



[2003/01/15 15:17:08, 3] smbd/lanman.c:api_DosPrintQGetInfo(884)
 api_DosPrintQGetInfo: uLevel=52 name=HP2250
[2003/01/15 15:17:08, 3] smbd/lanman.c:get_printerdrivernumber(836)
 Can't determine number of printer driver files
[2003/01/15 15:17:08, 3] smbd/lanman.c:api_DosPrintQGetInfo(918)
 api_DosPrintQGetInfo: Driver files count: 0
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(656)
 printerdriver:hp2250:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(657)
 Driver:ADOBEPS4.DRV:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(658)
 Data File:hp2250.PPD:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(659)
 Language Monitor:PSMON.DLL:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(661)
 lp_driverlocation:\\PRINTSERVER2\print$\WIN40\0:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(664)
 Data Type:RAW:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(665)
 Help File:ADOBEPS4.HLP:
[2003/01/15 15:17:08, 3] smbd/lanman.c:fill_printq_info_52(679)
 fill_printq_info on  gave 0 entries
[2003/01/15 15:17:09, 3] smbd/process.c:process_smb(878)
 Transaction 16 of length 39

root at wertach:/usr/local/samba/printers/WIN40# l

[Samba] Samba/CUPS printing again

[Kurt Pfeifle]

Darin Bawden wrote on Samba-Digest:


[Samba] Samba/CUPS printing again
Darin Bawden [EMAIL PROTECTED]
Fri Jan 10 00:42:19 2003


Hello...again...Y'all are getting sick of me, aren't ya?  ;)
Anyway, I am having quite the dilemna about printing.  I'm using samba
2.2.7a aong with cups-1.1.5.


First off: this is a very old CUPS. It was released in Autumn 2000.


I know this is an old version of cups, but
this is a production server and I don't want to fool with it yet.


But you do -- running such an old version of CUPS with the most recent
version of Samba ;-)


Anyway,
we have 2 printers: HP laser Jet 4 Plus and an Office Jet R80.  each are
running off a jet direct.  One is located in address x.x.x.32, the other in
x.x.x.38.  We can print to the laserjet without a problem.


Which driver do you use here? Is it locally installed on the clients?


However, we are
completely unable to print to the office jet. 

Which driver do you use? Which Win OS versions are the clients? Do they
use the HP driver? Is CUPS spooling the files as "raw"?

What does the CUPS "error_log" say? Did you set "LogLevel debug" in CUPS
and restart cupsd to get a more verbose output?


I can print a test page from
teh CUPS web GUI and from the bash prompt from the server box itself.


The testpage is PostScript and therefor is nearly guaranteed to get
rendered and printed OK.


However, when anything is sent from windows, it never prints.


What the Windows driver sends is "unknown". In CUPS-speak, it is of
MIME type "application/octet-stream". And this MIME type is disabled
by default.

See if you have in *both* files, /etc/cups/mime.types|convs, on the last
line the "#" removed. Then try again.

If the problem persists, see in the "error_log" for hints (not the page_log)


There's no
record of it ever reaching the que. 

Windows clients print into the receiving queue of Samba (probably
"/var/spool/samba/"). See if anything arrives here. If not, it is a pure
Samba problem at this stage. If yes, investigate why it doesn't get
passed to the CUPS queue (probably "/var/spool/cups/"), or why it doesn't
get processed there.


I'm not sure where to look for info.


There is a a lot of docu at "http://localhost:631/documentation.html";

"man -k cups" should also list all relevant man pages.

The Release Notes at http://www.linuxprinting.org/ contain 2 arguments on
every single line why you should upgrade (there might be half an argument
per section why you could stay were you are...  ;-)


it's acting like the windows machine are not sending the print files to the
Cups que. 

Verify this by looking in the Samba log first.

Also, did you know you can change the Samba debug level "on the fly" by
giving "smbcontrol smbd debuglevel " ?? (My
advice: try "3" first, or you'll be drowned in messages)

Also: which printing releted settings are you using in smb.conf?



It never hits the page_log as a job.  When I look at the
properties of the printer, the samba printer port is not checked.  When I
check it and hit apply, it tells "Printer settings could not be saved.
Access denied"  My network username is part of the root group, and I've set
the printer admin and domain admin to include it, so I should have the
rights to do whatever I want.


Yes you should

But have you verified that this is what Samba sees you as?

Try "smbstatus" to see which credentials XP really presents to Samba.




	Does anyone have any ideas how I can fix this?

	as a side not, does anyone happen to have an enumports script that I can
use? 
I'm not a script writer, so I would have any idea where to start.

Thanks in advance...again  ;)

 Darin Bawden, Technical Support
Spectrum Software, Inc
(615) 333-1900




--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba/CUPS printing again

[Darin Bawden]

Hello...again...Y'all are getting sick of me, aren't ya?  ;)
Anyway, I am having quite the dilemna about printing.  I'm using samba
2.2.7a aong with cups-1.1.5.  I know this is an old version of cups, but
this is a production server and I don't want to fool with it yet.  Anyway,
we have 2 printers: HP laser Jet 4 Plus and an Office Jet R80.  each are
running off a jet direct.  One is located in address x.x.x.32, the other in
x.x.x.38.  We can print to the laserjet without a problem.  However, we are
completely unable to print to the office jet.  I can print a test page from
teh CUPS web GUI and from the bash prompt from the server box itself.
However, when anything is sent from windows, it never prints.  There's no
record of it ever reaching the que.  I'm not sure where to look for info.
it's acting like the windows machine are not sending the print files to the
Cups que.  It never hits the page_log as a job.  When I look at the
properties of the printer, the samba printer port is not checked.  When I
check it and hit apply, it tells "Printer settings could not be saved.
Access denied"  My network username is part of the root group, and I've set
the printer admin and domain admin to include it, so I should have the
rights to do whatever I want.

Does anyone have any ideas how I can fix this?

as a side not, does anyone happen to have an enumports script that I can
use?  I'm not a script writer, so I would have any idea where to start.

Thanks in advance...again  ;)

 Darin Bawden, Technical Support
Spectrum Software, Inc
(615) 333-1900


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS permissions issues

[Kurt Pfeifle]

Tom Hallewell <[EMAIL PROTECTED]> wrote on Samba-digest


Fri Dec 27 16:04:00 2002

Hello-
I am running Debian Woody, Samba 2.2.7, and Cups 1.1.14-3.
I can print as any local Linux client, but there is a permissions issue when
I try to print from Windows 2000.
My spool directory is /var/spool/cups,


I hope you didn't set the *Samba* spool directory the same as
the *CUPS* spool directory??


the permissions are set 700 to user
lp and group sys.  If I chmod the directory to 777, printing works fine, but
when I restart cupsd, the permissions revert back to 700.
I am running Domain-level security, as well as ACLs and winbindd, not sure
if this matters.
It seems like I am missing something really simple, so am giving a simple
description now, but I can supply much more detail if needed.

Here is the relevant stuff from smb.conf:
 load printers = yes
 printcap name = cups
 printing = cups

[printers]
   comment = All Printers
   path = /var/spool/cups


Ah, yes, it seems you did.

You need to understand: Samba spooling and CUPS (or any other "real"
print subsystem in Unix) spooling are two different kinds of birds
and need to be kept separate. When you print to Samba from a Windows
client, the printfile goes to the Samba (spool) path specified in your
smb.conf first, and is under control of smbd. Then, smbd, hands this
file to the print daemon (here: "cupsd"), and the file moves  to the
spool directory of that print daemon (as determined in cupsd.conf;
most likely it is also "/var/spool/cups/").

Change your [printers] entry to "path = /var/spool/samba" (and make
sure this exists) and your problem will be gone.

The permissions change back when cupsd is re-started, because cupsd
claims an exclusive right to "its" spool directory.


   writable = no
   printable = yes
   create mode = 0777
   use client driver = yes

Any help would be much appreciated.
Tom Hallewell




--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS permissions issues

[Tom Hallewell]

Hello-
I am running Debian Woody, Samba 2.2.7, and Cups 1.1.14-3.
I can print as any local Linux client, but there is a permissions issue when
I try to print from Windows 2000.
My spool directory is /var/spool/cups, the permissions are set 700 to user
lp and group sys.  If I chmod the directory to 777, printing works fine, but
when I restart cupsd, the permissions revert back to 700.
I am running Domain-level security, as well as ACLs and winbindd, not sure
if this matters.
It seems like I am missing something really simple, so am giving a simple
description now, but I can supply much more detail if needed.

Here is the relevant stuff from smb.conf:
 load printers = yes
 printcap name = cups
 printing = cups

[printers]
   comment = All Printers
   path = /var/spool/cups
   writable = no
   printable = yes
   create mode = 0777
   use client driver = yes

Any help would be much appreciated.
Tom Hallewell

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Printproblem WinXP / Samba / Cups

[Phil]

I'm using Samba 2.2.3 (Debian-testing) and CUPS 1.1.15 with a HP-Deskjet950c

Printing from all Linux-Clients works fine. 
I also can print any document from the Windows-Boxes ( XP & 2k ).

The Problem is : If I want to make more copys than one I still get one paper printed 
out!
This problem only appears when printing from Windows to the Samba-Share.

I also tested lpr/lpd printer spooling system -> same result:
With Windows I could only make one copy of the document.
With Linux all works fine.


my smb.conf :

[global]
   workgroup = IMMORTUX
   netbios name = blub
   guest account = blub
   server string = %h server (Samba %v)
   load printers = yes
   printcap name = /etc/printcap.cups
   printing = bsd   
# I also testet with option 'cups' and without option 'print command' > same result..

   invalid users = root
   log file = /var/log/samba/log.%m
   max log size = 1000
   syslog = 0
   security = share
   encrypt passwords = false
   dns proxy = no
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* 
%n\n .
   obey pam restrictions = yes

[printers]
   comment = All Printers
   browseable = yes
   path = /tmp
   printable = yes
   public = yes
   print command = /usr/bin/lpr -o raw -P%p -r %s
   create mode = 0700
   guest ok = yes

I read the docu without getting new ideas so the mailinglist is my last hope *g*
thx4reading

Phil

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba/CUPS new printer not showing up, must restart

[Bradley W. Langhorst]

On Thu, 2002-12-12 at 14:01, Jason Jeremias wrote:
> Someone please say it isn't so.  I'm running Samba 2.2.7 on Linux, 
> compiled from source.  I use CUPS for my printing needs and I have samba 
> setup to load printers.  
> 
> I'm having 2 problems:
> 
> 1) if I add a new printer to CUPS (which in turn adds it to 
> /etc/printcap) it doesn't show up in Samba.  I've tried to -HUP the smbd 
> process to get the printer to show up and that didn't work.
> 
> Here are my relevent settings in smb.conf
> 
> printcap name = lpstat
try
printcap name = /etc/printcap.cups

instead
> 
> 2) Even thought I have samba setup to print using this command:
> 
> print command = /usr/bin/lpr -P %p -o raw %s -J'%J' -r
> 
> It doesn't seem to be removing the jobs out of my /var/spool/samba 
> directory when they are complete, any Ideas why?
If i remember correctly, when you use cups the print command is ignored
- instead the files are sent to cups directly.

you might try setting printing to bsd if you want to use lpr to submit
jobs.

brad

> 
> Bradley W. Langhorst <[EMAIL PROTECTED]>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba/CUPS new printer not showing up, must restart

[Jason Jeremias]

Someone please say it isn't so.  I'm running Samba 2.2.7 on Linux, 
compiled from source.  I use CUPS for my printing needs and I have samba 
setup to load printers.  

I'm having 2 problems:

1) if I add a new printer to CUPS (which in turn adds it to 
/etc/printcap) it doesn't show up in Samba.  I've tried to -HUP the smbd 
process to get the printer to show up and that didn't work.

Here are my relevent settings in smb.conf

   printcap name = lpstat
   load printers = yes
   printing = cups


The only think I've found that works is restarting samba, this is a 
terrible solution for me because if I restart Samba, which is acting as 
my PDC.  My Windows 2K Server, running SQL Server can no longer 
authenticate users and I have to restart that box to get it to work again.

Is there another solution PLEASE!!!  Having to restart samba to see a 
new printer just seems plain silly to me.


2) Even thought I have samba setup to print using this command:

print command = /usr/bin/lpr -P %p -o raw %s -J'%J' -r

It doesn't seem to be removing the jobs out of my /var/spool/samba 
directory when they are complete, any Ideas why?


Comments, Suggestions, all help appreciated.



--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups..works on LM8.1, LM8.2 but not LM9

[Ken Walker]

I've been trying every combination possible to get CUPS on LM9 to print to a
shared printer on a windows machine.

On setting up the printer in printerdrake, On LM8.1 it worked first time. On
LM8.2 with the same settings it worked first time. On LM9 it just sits there
and laughs at me, with the same settings as LM8.1 and LM8.2.

And how do i remove a default printer it thinks it has but isn't there ?

The printer on the remote windoz machine i'm trying to print to is a HP1100.
The default printer it thinks it has is also a HP1100, but has it down as
its own ip address, and not the ip address of the machine that actually has
the printer.

Last night i tried setting up an Epson 1160, also connected to a windows
machine.

LM8.1 set it up, and out pops a test page.

LM8.2 set it up, and out pops a test page.

On LM9nothing, again just sits there, says the printer is
printing, says its ready. but prints bugger all.


LM9.. Aaarh nothing.

Anybody had this problem

many thanks


ps is it possible to set up a LM box so that students print from a
windows machine  to the samba box, and then the samba box sends it to
another windows machine to actually be printed. I need only selected
students to use the printer ( otherwise the little buggers sneak in and
empty all the cartridges, then sneak out again )

Many thanks

Mr Smiley

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS printing problem under Samba 2.2.7

[John H Terpstra]

Istvan,

You need to install the package cups-devel for your Linux distro.
Then you can build samba with cups support.

- John T.


On Sun, 1 Dec 2002, YYyyy XXxxx wrote:

> Hi,
>
> I've just downloaded and installed samba 2.2.7
> with these options;
>
> # rpm -qa|grep cups
> cups-1.1.15-10
> cups-libs-1.1.15-10
>
> # ldconfig -v|grep cups
> libcups.so.2 -> libcups.so.2
> libcupsimage.so.2 -> libcupsimage.so.
>
> But after make, and make install I don't
> see cups among the supported libraries
> in smbd;
>
> # ldd /usr/sbin/smbd
> libdl.so.2 => /lib/libdl.so.2 (0x4001f000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x40023000)
> libpam.so.0 => /lib/libpam.so.0 (0x40038000)
> libpopt.so.0 => /usr/lib/libpopt.so.0 (0x4004)
> libc.so.6 => /lib/i686/libc.so.6 (0x4200)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
>
> I don't know what should I do.
> I think this is the reason why I don't see the
> printers under samba server from our clients...
>
> Could you help me please, what am I missed?

- John T.
-- 
John H Terpstra
Email: [EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS printing problem under Samba 2.2.7

[YYyyy XXxxx]

Hi,

I've just downloaded and installed samba 2.2.7
with these options;

./configure \
--prefix=/usr \
--libdir=/etc \
--with-lockdir=/var/lock/samba \
--with-privatedir=/etc/samba \
--with-pam \
--with-winbind \
--with-swatdir=/usr/share/swat \
--with-pam \
--with-mmap \
--enable-cups \
--with-logfilebase=/var/log/samba \
--with-smbmount \
--sysconfdir=/etc/samba \
--with-piddir=/var/run/samba

As you can see, I turned on cups support in
samba configuration.
I have the cups libraries also;

# rpm -qa|grep cups
cups-1.1.15-10
cups-libs-1.1.15-10

# ldconfig -v|grep cups
libcups.so.2 -> libcups.so.2
libcupsimage.so.2 -> libcupsimage.so.

But after make, and make install I don't
see cups among the supported libraries
in smbd;

# ldd /usr/sbin/smbd
libdl.so.2 => /lib/libdl.so.2 (0x4001f000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40023000)
libpam.so.0 => /lib/libpam.so.0 (0x40038000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0x4004)
libc.so.6 => /lib/i686/libc.so.6 (0x4200)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)

I don't know what should I do.
I think this is the reason why I don't see the
printers under samba server from our clients...

Could you help me please, what am I missed?

Thank in advance!

Regards;

 Istvan

_
The new MSN 8: advanced junk mail protection and 2 months FREE* 
http://join.msn.com/?page=features/junkmail

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Cups

[John H Terpstra]

On Thu, 28 Nov 2002, Simon Chappell wrote:

> Can anyone advise how to get Cups to survive a reboot with samba.
> After Reboot both samba and cups are running but there are no samba preinters
> unless I restart Samba. I have set links to rc3.d so that cups starts before
> samba but still doesnt work.
>
> Any help would be greatly appreceiated

You must start samba after cups is running. Your boot order is the
problem.

In the rc3.d directory your will find a script called Sxxname for each
service. The xx for cupsd needs to be earlier than the one for smb (or
samba).

- John T.

-- 
John H Terpstra
Email: [EMAIL PROTECTED]

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS installation with SAMBA

[cantisan]

I installed samba via rpm and I want to install cups
using the source code, anyone knows what are the
procedure to that ?

ps- CUPS will works with samba..

RedHat 7.2 Samba 2.2.5


__
Venha para a VilaBOL!
O melhor lugar para você construir seu site. Fácil e grátis!
http://vila.bol.com.br


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Cups

[Bjoern Jacke]

On 2002-11-28 at 10:22 + Simon Chappell sent off:

Can anyone advise how to get Cups to survive a reboot with samba.
After Reboot both samba and cups are running but there are no samba preinters
unless I restart Samba. I have set links to rc3.d so that cups starts before
samba but still doesnt work.


you simply need to make sure that cupsd is being *fully* started (not 
just starting in background) before samba is being started. I don't 
know much about the RH init script internals, so I can't tell you what 
to do exactly. On SuSE Linux it works out of the box. On RH, try 
changing the order the scripts are executed and make sure the cupsd is 
fully up. A little sleep might help in the script, too.

Bjoern


msg09691/pgp0.pgp
Description: PGP signature

Re: [Samba] Cups

[Martin Zielinski]

Perhaps you are using an older version of cups (1.1.15 or earlier).
In this versions the daemon puts itself to background before having loaded all
printers (including ppds, filters...).
This leads to the situation, that samba may request the list of printers 
before cups is ready to serve it.
That's the reason, why samba gets the list after a restart.
Solution: 
wait a little time after cups has been started or (better) 
use a current release of cups (1.1.16 or cvs).

bye

On Thursday 28 November 2002 11:22, Simon Chappell wrote:
> Can anyone advise how to get Cups to survive a reboot with samba.
> After Reboot both samba and cups are running but there are no samba
> preinters unless I restart Samba. I have set links to rc3.d so that cups
> starts before samba but still doesnt work.
>
> Any help would be greatly appreceiated
>
>
>
> Regards
>
>
>
> Simon
>
>
> -
> This mail sent through IMP on Redhat 8.0 and Qmail with Ldap.

-- 
Martin Zielinski   [EMAIL PROTECTED]

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS cancel print problem

[Paul Mitchell]

Strange problem here, whenever a job is selected by the user to delete, it 
disappears from the print queue visible from Windows (after press F5), but 
still remains in the cups queue.

I've seen some mention of using disable spoolss, to fix problems like this, 
however, we have the printer drivers on the samba box.

The configuration below is from our sandbox server, sandbox.  The domain 
master is a Samba server.  The sandbox is runing SuSE 8.1, CUPS 1.1.15 and 
Samba 2.2.6

This also happens on our production server SuSE 7.3 CUPS 1.1.15 and Samba 2.26

Thanks,
Paul

[global]
workgroup = MODUS
netbios name = sandbox
server string = IT Test server
os level = 32
time server = yes
unix extensions = yes
encrypt passwords = yes
log level = 1
syslog = 0
printing = CUPS
printcap name = CUPS
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
wins support = no
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
map to guest = Bad User
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Re-enter*new*password* %n\n 
*Password*changed*
unix password sync = Yes
preferred master = no
domain master = no
security = domain
password server = *

[homes]
comment = Home Directories
valid users = %S
browseable = no
writeable = yes
create mask = 0640
directory mask = 0750
[printers]
comment = All Printers
path = /var/tmp
printable = yes
create mask = 0600
browseable = no
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Cups

[Simon Chappell]

Can anyone advise how to get Cups to survive a reboot with samba.
After Reboot both samba and cups are running but there are no samba preinters
unless I restart Samba. I have set links to rc3.d so that cups starts before
samba but still doesnt work.

Any help would be greatly appreceiated



Regards



Simon 


-
This mail sent through IMP on Redhat 8.0 and Qmail with Ldap.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS drivers and Samba

[David Morel]

Le mar 19/11/2002 à 19:41, Romeyn Prescott a écrit :
> I am TRYING to get driver distribution working with CUPS and Samba. 
> I'm stuck here:
> 
> http://us4.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN1050
> 
> I can NOT for the life of me find or figure out how to extract the 
> files listed:
> 
>  ADFONTS.MFM
>  ADOBEPS4.DRV
>  ADOBEPS4.HLP
>  ADOBEPS5.DLL
>  ADOBEPSU.DLL
>  ADOBEPSU.HLP
>  DEFPRTR2.PPD
>  ICONLIB.DLL
> 
> I've been to Adobe's website and downloaded their "Universal 
> Postscript Windows Driver Installer" but it seems to me to be Mostly 
> Useless when it comes to getting these files installed anywhere.
> 
> Please enlighten me, what am I missing?
> 

Actually, you have to start the install so the files are extracted in a
temporary location. Do not perform the full install but look for the
files on your win hd (tip:use the win95 and win nt drivers if i recall
correctly) while the install window is open. It was easier with the
previous version, but it's the way i found with the newer one. 

> Thanks,
> ...ROMeyn
> -- 
> http://www2.potsdam.edu/prescor/signat-url.htm
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS drivers and Samba

[Bradley W. Langhorst]

On Tue, 2002-11-19 at 13:41, Romeyn Prescott wrote:
> I am TRYING to get driver distribution working with CUPS and Samba. 
> I'm stuck here:
> 
> http://us4.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN1050
> 
> I can NOT for the life of me find or figure out how to extract the 
> files listed:
> 
>  ADFONTS.MFM
>  ADOBEPS4.DRV
>  ADOBEPS4.HLP
>  ADOBEPS5.DLL
>  ADOBEPSU.DLL
>  ADOBEPSU.HLP
>  DEFPRTR2.PPD
>  ICONLIB.DLL
> 
> I've been to Adobe's website and downloaded their "Universal 
> Postscript Windows Driver Installer" but it seems to me to be Mostly 
> Useless when it comes to getting these files installed anywhere.

You may get more responses if you don't reply to a message but post a
new one (yours will get threaded away in some mail clients).


To install a printer driver on samba you need to follow the directions
in the howto collection.

Essentially 
browse to the printer share on the server, get the properties, go to
sharing...
you should get a windows dialog asking for the location of the files you
downloaded (there should be an inf file in there)

samba will suck up the drivers and store them in its own format for
feeding to clients.

brad


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS drivers and Samba

[Romeyn Prescott]

I am TRYING to get driver distribution working with CUPS and Samba. 
I'm stuck here:

http://us4.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN1050

I can NOT for the life of me find or figure out how to extract the 
files listed:

ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
ADOBEPS5.DLL
ADOBEPSU.DLL
ADOBEPSU.HLP
DEFPRTR2.PPD
ICONLIB.DLL

I've been to Adobe's website and downloaded their "Universal 
Postscript Windows Driver Installer" but it seems to me to be Mostly 
Useless when it comes to getting these files installed anywhere.

Please enlighten me, what am I missing?

Thanks,
...ROMeyn
--
http://www2.potsdam.edu/prescor/signat-url.htm

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS printing

[Kurt Pfeifle]

Someone calling himself "linuxpower" adviced on this list:


Message: 2
Date: Thu, 14 Nov 2002 07:30:18 +0100 (CET)
From: =?iso-8859-1?q?linux=20power?= <[EMAIL PROTECTED]>
Subject: Re: [Samba] CUPS printing
To: [EMAIL PROTECTED]

--0-1567453496-1037255418=:2514
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


Replace -P %p in the print command line with the absolute path to the printer.

> Bug in samba.

Hi, "linuxpower",

I have read your repeated advice on this list to use "the absolute
path to the printer" inside the print command. On other occasions you
talked about an "absolute path to a printing device". I suppose, you
mean the same thing with both your variants of your wording.

Would you please be so kind to explain to me what you mean by these?
Would you please give an example for an "absolute path to the printer",
for an "absolute path to a printing device" plus an example for the
"print command", as you imagine does work in the cases you advice to
use it?

Sorry, I can't make my mind up about this one. (I wouldn't mind about
this -- but your advices leads to e-mails, directed to *my* mailbox, of
people asking what the *~#?$§& this means...)

Your talking in the context of CUPS about "path to a device", makes it
very likely to be mixed up with the clearly defined technical term
"device URI" which CUPS uses.

On one occasion, you have even given the specific advice

   >>>> Fix it by replacing -P %p with the
   >>>>absolute path to the printing device found in lpstat
   >>>>-v

and on another one (Fri Oct 4 06:55:24 2002) you wrote

   >>>> There is a bug in samba which cannot resolve -P %p
   >>>> in the print command.Replace -P %p with the absolute
   >>>> path to the printer.

Excuse me -- this advice is pure nonsense (while a bug in Samba might
be there). Here are the reasons:

"lpstat -v" on a CUPS based printing system gives something that is named
a "device URI" in all relevant documentation. If it is the "parallel:/dev/lp0"
device-URI, one *could* assume to take the "/dev/lp0" part as a "path", even
an "absolute" path. But what about device-URIs like

   "lpd://10.160.51.131/PORT1"
   "socket://hp-printer:9100"
   "ipp://kde-cups-server/printers/infotec4105"

?? Would you also call "//10.160.51.131/PORT1" or "//hp-printer:9100" or
"//kde-cups-server/printers/infotec4105" an absolute path?

CUPS does encode in the "device-URI" the protocol to be used for the
communication with the printer plus something you might call "absolute
path to the device".

You can't replace inside the Samba "print command" (in smbd.conf) the
"-P %p" part by one of the quoted device URIs...

Your creation and usage of the term of "absolute path" I found nowhere
clearly defined  -- it seems to only lead to utter confusion and urban
legends...

-

About your conceived "bug in Samba" -- please consider this:

There is also a hint in the smb.conf man page:

  ...*if* the setting is "printing = cups" and "printcap = cups" and
  ...*if* Samba is compiled against libcups,
  ...and *if* there is an entry in "cupsd.conf" to get CUPS to create a
 printcap file ["Printcap /etc/printcap"],

then *any* print command setting in smb.conf will be *ignored*, as samba is
then using a direct access to the CUPS API for printing

This means: if the two simple settings "printing = cups" and "printcap = cups"
don't work, you probably don't have a smbd which is compiled against
libcups. To check, simply run as root "ldd `which smbd`" (on Linux, dunno
about "ldd" on other Samba platforms).

-

Now for the original question


Mark Belfanti <[EMAIL PROTECTED]> wrote:

>
> For printing from windows with windopws driver using cups you may need

to reconfigure to have sups act as a raw print queue. See Chapter 7 of
Samaba-HowTo-Collection.

Regards,
Mark

On Thu, 2002-11-14 at 13:25, Darin Bawden wrote:


Good evening everyone,
Kist a quick-type question I hope. I've just switched my Linux server to
use Cups instead of LPRng. I can print all day to our HP LaserJet 4 Plus.


Hi, Mark,

CUPS ships a well-working Laserjet driver. Install it (as root) with

   "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd"

(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository
for not-yet-installed-PPDs, which CUPS keeps at "/usr/share/cups/model/". Alter-
natively, you may use "-P /absolute/

RE: [Samba] CUPS printing

[Darin Bawden]

I will try that.  On another note, is it better to share printers as "All
Printers" or to share the individual printers?  Does that give me more
control or config options?


Darin Bawden
TeamDME! Technical Support
Phone: (615)333-1900 x.19
[EMAIL PROTECTED]


-Original Message-
From: Mark Belfanti [mailto:mark@;belfanti.com]
Sent: Wednesday, November 13, 2002 8:36 PM
To: Darin Bawden
Cc: Samba List
Subject: Re: [Samba] CUPS printing


For printing from windows with windopws driver using cups you may need
to reconfigure to have sups act as a raw print queue. See Chapter 7 of
Samaba-HowTo-Collection.

Regards,
Mark

On Thu, 2002-11-14 at 13:25, Darin Bawden wrote:
> Good evening everyone,
> Kist a quick-type question I hope.  I've just switched my Linux server to
> use Cups instead of LPRng.  I can print all day to our HP LaserJet 4 Plus.
> However, I can only print a Cups test page, from the web interface.  when
I
> try to print a windows test page, it acts like the job was never sent.
>   The reason I am not initially posting the smb.conf and/or cupsd.conf is I
> am not sure this is a Samba issue or cups issue.  can anyone advise me
which
> way to go?  I'm using samba 2.2.5 and cups 1.1.5  FWIW, I'm using the
> Foomatic+hpijs printer driver.
>   I'm not sure where to go with this issue.  If this isn't a samba issue,
> please pardon the OT.
>
> Thanks in advance  :)
>
> Darin Bawden
[EMAIL PROTECTED]
--
Mark Belfanti <[EMAIL PROTECTED]>



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS printing

[FP]

I did it and know my smb.conf for the printer is :

[printers]
   comment = Imprimante Chou1800
   path = /var/spool/samba
   guest account =
   create mask = 0777
   guest ok = Yes
   hosts allow = 192.168.1.232
   printable = Yes
   print command = lpr-cups -P /dev/usb/lp0 -o raw %s -r
   browseable = No

[Chou1800_Imprimante]
   path = /var/spool/samba
   read only = No
   create mask = 0777
   guest ok = Yes
   hosts allow = 192.168.1.232
   printable = Yes
   print command = lpr-cups -P /dev/usb/lp0 -o raw %s -r
   printer name = epson760
   oplocks = No

And it doesn't work yet.. Another idea?

Thanks in advance !

Fred


linux power wrote:


Replace -P %p in the print command line with the absolute path to the 
printer.

Bug in samba.

 */Mark Belfanti <[EMAIL PROTECTED]>/* wrote:

For printing from windows with windopws driver using cups you may need
to reconfigure to have sups act as a raw print queue. See Chapter 7 of
Samaba-HowTo-Collection.

Regards,
Mark

On Thu, 2002-11-14 at 13:25, Darin Bawden wrote:
> Good evening everyone,
> Kist a quick-type question I hope. I've just switched my Linux
server to
> use Cups instead of LPRng. I can print all day to our HP
LaserJet 4 Plus.
> However, I can only print a Cups test page, from the web
interface. when I
> try to print a windows test page, it acts like the job was never
sent.
> The reason I am not initially posting the smb.conf and/or
cupsd.conf is I
> am not sure this is a Samba issue or cups issue. can anyone
advise me which
> way to go? I'm using samba 2.2.5 and cups 1.1.5 FWIW, I'm using the
> Foomatic+hpijs printer driver.
> I'm not sure where to go with this issue. If this isn't a samba
issue,
> please pardon the OT.
>
> Thanks in advance :)
>
> Darin Bawden
[EMAIL PROTECTED]
-- 
Mark Belfanti

-- 
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba



http://home.no.net/~knutove/knut_ove_hauge_kuren.htm

*Yahoo! Mail har fått nytt utseende* 

Nytt design, enklere å bruke, alltid tilgang til Adressebok, Kalender 
og Notisbok




--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS printing

[linux power]

Replace -P %p in the print command line with the absolute path to the printer.
Bug in samba.
 Mark Belfanti <[EMAIL PROTECTED]> wrote:
For printing from windows with windopws driver using cups you may needto reconfigure to have sups act as a raw print queue. See Chapter 7 ofSamaba-HowTo-Collection.Regards,MarkOn Thu, 2002-11-14 at 13:25, Darin Bawden wrote:> Good evening everyone,> Kist a quick-type question I hope. I've just switched my Linux server to> use Cups instead of LPRng. I can print all day to our HP LaserJet 4 Plus.> However, I can only print a Cups test page, from the web interface. when I> try to print a windows test page, it acts like the job was never sent.> The reason I am not initially posting the smb.conf and/or cupsd.conf is I> am not sure this is a Samba issue or cups issue. can anyone advise me which> way to go? I'm using samba 2.2.5 and cups 1.1.5 FWIW, I'm using the> Foomatic+hpijs printer driver.> I'm 
 not sure where to go with this issue. If this isn't a samba issue,> please pardon the OT.> > Thanks in advance :)> > Darin Bawden[EMAIL PROTECTED]-- Mark Belfanti <[EMAIL PROTECTED]>-- To unsubscribe from this list go to the following URL and read theinstructions: http://lists.samba.org/mailman/listinfo/sambahttp://home.no.net/~knutove/knut_ove_hauge_kuren.htmYahoo! Mail har fått nytt utseende 
Nytt design, enklere å bruke, alltid tilgang til Adressebok, Kalender og Notisbok

Re: [Samba] CUPS printing

[Mark Belfanti]

For printing from windows with windopws driver using cups you may need
to reconfigure to have sups act as a raw print queue. See Chapter 7 of
Samaba-HowTo-Collection.

Regards,
Mark

On Thu, 2002-11-14 at 13:25, Darin Bawden wrote:
> Good evening everyone,
> Kist a quick-type question I hope.  I've just switched my Linux server to
> use Cups instead of LPRng.  I can print all day to our HP LaserJet 4 Plus.
> However, I can only print a Cups test page, from the web interface.  when I
> try to print a windows test page, it acts like the job was never sent.
>   The reason I am not initially posting the smb.conf and/or cupsd.conf is I
> am not sure this is a Samba issue or cups issue.  can anyone advise me which
> way to go?  I'm using samba 2.2.5 and cups 1.1.5  FWIW, I'm using the
> Foomatic+hpijs printer driver.
>   I'm not sure where to go with this issue.  If this isn't a samba issue,
> please pardon the OT.
> 
> Thanks in advance  :)
> 
> Darin Bawden
[EMAIL PROTECTED]
-- 
Mark Belfanti <[EMAIL PROTECTED]>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS printing

[Darin Bawden]

Good evening everyone,
Kist a quick-type question I hope.  I've just switched my Linux server to
use Cups instead of LPRng.  I can print all day to our HP LaserJet 4 Plus.
However, I can only print a Cups test page, from the web interface.  when I
try to print a windows test page, it acts like the job was never sent.
The reason I am not initially posting the smb.conf and/or cupsd.conf is I
am not sure this is a Samba issue or cups issue.  can anyone advise me which
way to go?  I'm using samba 2.2.5 and cups 1.1.5  FWIW, I'm using the
Foomatic+hpijs printer driver.
I'm not sure where to go with this issue.  If this isn't a samba issue,
please pardon the OT.

Thanks in advance  :)

Darin Bawden
[EMAIL PROTECTED]


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

RE: [Samba] Samba, Cups, printer driver download problems

[Kalkoul Morad]

Sorry I did a mistake it wasn't for this mail.

-Message d'origine-
De : Kalkoul Morad [mailto:M-Kalkoul@;arte-tv.com]
Envoyé : mardi 29 octobre 2002 11:05
À : 'David Morel'; [EMAIL PROTECTED]
Objet : RE: [Samba] Samba, Cups, printer driver download problems


No

-Message d'origine-
De : David Morel [mailto:david.morel@;amakuru.net]
Envoyé : mardi 29 octobre 2002 10:30
À : [EMAIL PROTECTED]
Objet : Re: [Samba] Samba, Cups, printer driver download problems


Le lun 28/10/2002 à 20:40, Robert M. Martel a écrit :
> 
> I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running 
> Solaris 9.  Cups has replaced the stock system V lp spooler on this system

> (original packages removed.)
> 
> Cups working from UNIX command line is A-OK.
> 
> I have been working on setting up Samba to play nice with cups.  I have 
> followed the instructions from both the Cups and Samba websites to set up 
> downloading of the generic Adobe postscript drivers to MS Windows PCs and
use 
> CUPS as a RIP.
> 
> So far I have been unable to get the Windows 98 drivers to download to the

> client PC - when adding the printer the client ends up asking the user
what type 
> of printer is being added.  Driver downloads for W2K work OK.
> 

bug in cupsaddsmb (fixed in 1.1.16?) , some files are not copied right.

Problem : 
automatic downloading of adobe drivers added with cupsaddsmb fails with
message
"unable to open file adopeps4.drv" at the end of install on win98 client

Cause:
cupsaddsmb sends a 
rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0"
"printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
which forgets adobeps4.drv; 

Solution:
the proper command should read :
rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0"
"printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
ADOBEPS4.DRV:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

RE: [Samba] Samba, Cups, printer driver download problems

[Kalkoul Morad]

No

-Message d'origine-
De : David Morel [mailto:david.morel@;amakuru.net]
Envoyé : mardi 29 octobre 2002 10:30
À : [EMAIL PROTECTED]
Objet : Re: [Samba] Samba, Cups, printer driver download problems


Le lun 28/10/2002 à 20:40, Robert M. Martel a écrit :
> 
> I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running 
> Solaris 9.  Cups has replaced the stock system V lp spooler on this system

> (original packages removed.)
> 
> Cups working from UNIX command line is A-OK.
> 
> I have been working on setting up Samba to play nice with cups.  I have 
> followed the instructions from both the Cups and Samba websites to set up 
> downloading of the generic Adobe postscript drivers to MS Windows PCs and
use 
> CUPS as a RIP.
> 
> So far I have been unable to get the Windows 98 drivers to download to the

> client PC - when adding the printer the client ends up asking the user
what type 
> of printer is being added.  Driver downloads for W2K work OK.
> 

bug in cupsaddsmb (fixed in 1.1.16?) , some files are not copied right.

Problem : 
automatic downloading of adobe drivers added with cupsaddsmb fails with
message
"unable to open file adopeps4.drv" at the end of install on win98 client

Cause:
cupsaddsmb sends a 
rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0"
"printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
which forgets adobeps4.drv; 

Solution:
the proper command should read :
rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0"
"printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
ADOBEPS4.DRV:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba, Cups, printer driver download problems

[David Morel]

Le lun 28/10/2002 à 20:40, Robert M. Martel a écrit :
> 
> I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running 
> Solaris 9.  Cups has replaced the stock system V lp spooler on this system 
> (original packages removed.)
> 
> Cups working from UNIX command line is A-OK.
> 
> I have been working on setting up Samba to play nice with cups.  I have 
> followed the instructions from both the Cups and Samba websites to set up 
> downloading of the generic Adobe postscript drivers to MS Windows PCs and use 
> CUPS as a RIP.
> 
> So far I have been unable to get the Windows 98 drivers to download to the 
> client PC - when adding the printer the client ends up asking the user what type 
> of printer is being added.  Driver downloads for W2K work OK.
> 

bug in cupsaddsmb (fixed in 1.1.16?) , some files are not copied right.

Problem : 
automatic downloading of adobe drivers added with cupsaddsmb fails with
message
"unable to open file adopeps4.drv" at the end of install on win98 client

Cause:
cupsaddsmb sends a 
rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0"
"printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
which forgets adobeps4.drv; 

Solution:
the proper command should read :
rpcclient localhost -N -U'root%pass' -c 'adddriver "Windows 4.0"
"printer_name:ADOBEPS4.DRV:printer_name.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"



--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba, Cups, printer driver download problems

[Robert M. Martel]

I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running 
Solaris 9.  Cups has replaced the stock system V lp spooler on this system 
(original packages removed.)

Cups working from UNIX command line is A-OK.

I have been working on setting up Samba to play nice with cups.  I have 
followed the instructions from both the Cups and Samba websites to set up 
downloading of the generic Adobe postscript drivers to MS Windows PCs and use 
CUPS as a RIP.

So far I have been unable to get the Windows 98 drivers to download to the 
client PC - when adding the printer the client ends up asking the user what type 
of printer is being added.  Driver downloads for W2K work OK.

The relevant lines from a Samba log file seem to be:

-
[2002/10/28 14:17:46, 9] printing/nt_printing.c:get_a_printer_2(2702)
  Unpacked printer [ur10] name [\\techops\ur10] running driver [ur10]
[2002/10/28 14:17:46, 10] printing/nt_printing.c:get_a_printer(3302)
  get_a_printer: [ur10] level 2 returning WERR_OK
[2002/10/28 14:17:46, 10] 
printing/nt_printing.c:get_a_printer_driver_9x_compatible(1825)
  driver key: [DRIVERS/WIN40/0/ur10]
[2002/10/28 14:17:46, 8] printing/nt_printing.c:get_a_printer_driver_3(1758)
  get_a_printer_driver_3: [DRIVERS/WIN40/0/ur10]
  info3->name[ur10]
  info3->datafile[\print$\WIN40\0\ur10.PPD]
  info3->helpfile[\print$\WIN40\0\ADOBEPS4.HLP]
  info3->monitorname [PSMON.DLL]
  info3->defaultdatatype [RAW]
  info3->environment [Windows 4.0]
  info3->driverpath  [\print$\WIN40\0\ADOBEPS4.DRV]
  info3->configfile  []
[2002/10/28 14:17:46, 10] smbd/lanman.c:get_printerdrivernumber(799)
  9x compatable driver line for [ur10]: 
[ADOBEPS4.DRV:ur10.PPD:ADOBEPS4.HLP:PSMON.DLL:RAW:]
[2002/10/28 14:17:46, 3] smbd/lanman.c:get_printerdrivernumber(836)
  Can't determine number of printer driver files
[2002/10/28 14:17:46, 3] smbd/lanman.c:api_DosPrintQGetInfo(918)
  api_DosPrintQGetInfo: Driver files count: 0
[2002/10/28 14:17:46, 10] printing/nt_printing.c:get_a_printer(3277)
  get_a_printer: [ur10] level 2
[2002/10/28 14:17:46, 6] rpc_parse/parse_prs.c:prs_debug(60)
  00 sec_io_desc_buf nt_printing_getsec

---

Cupsaddsmb ran without errors and the WIN40 subdirectory is populated with 
files.


Can anyone offer any advice?

Thanks,
Bob Martel
**
 Speaking only for myself - CSU pays better people than me to speak for them.
 
 Bob Martel - System Administrator  | I met someone who looks 
 Maxine Goodman Levin College of Urban Affairs  |a lot like you
 Cleveland State University | She does the things you do
 (216) 687-2214 |But she is an IBM 
  
 [EMAIL PROTECTED]  |  -Jeff Lynne 
**


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba & CUPS...

[Brad]

I have an HP Laser connected to the parallel port on a Red hat 8.0 server and 
I have configured it to print with CUPS. It prints a test page OK, but I 
would now like to share the printer so that Windows clients can print to it.

According to the documentation, all I need to put in the smb.conf file is:

printing = cups
printcap name = cups

I have restarted samba and cups but the printer stil doesn't appear in Network 
Neighbourhood.

Does anyone have any ideas?
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] samba cups install

[PJourdan]

Gentlemen,
First, I want to thank all those who helped me figure out my problem.
Installation is FreeBSD 4.6.2;
A standard installation of cups, followed by an immediate upgrade refused 
to install properly. A direct install of the latest version from the ports 
collection (on 3rd clean install of OS) did finally work correctly. I 
suspect there is a problem in the upgrade mechanism since a straight 
install worked perfectly.
The samba end refused to show the printers and that turned out to be a 
timing problem. It looks like the problem was that both cups & samba were 
starting up in
parallel so that cups did not have time to initialize before samba was up 
and running. I just added "sleep 5" to the samba.sh startup script and 
everything is ok now.
Hope this helps someone.
Phil


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS / SAMBA / HP930C / WINDOWS CLIENTS!

[linux power]

Major bug in samba.Replace -P %p in the print command
with the absolute path to the printer.
Let me hear how it goes. 



--- Rodrigo Sirio Coelho <[EMAIL PROTECTED]> skrev:
> Server Samba 2.2.5! Printing = cups! Printing local
> all OK! 
> the printer is atached in a Print Server (PLANET) on
> IP 192.168.0.8. The cups is using LPD to print
> local! the another 2 printers atached on the print
> server and mapped on CUPS are all working good! the
> hp930c is only working local(on the linux), when
> printing from windows 98, the server gives a error
> message 
> 
> gis-01 (192.168.0.51) connect to service hp930c as
> user xico (uid=500, gid=104) (pid 19088)
> [2002/09/24 19:01:54, 0]
> printing/print_cups.c:cups_job_submit(655)
>   Unable to print file to hp930c -
> client-error-document-format-not-supported
> [2002/09/24 19:05:36, 1]
> smbd/service.c:close_cnum(681)
>   gis-01 (192.168.0.51) closed connection to service
> hp930c
> 
> 
> Anyone knows what is this??? ! :)
> 
> 
> Thank you

__
Se den nye Yahoo! Mail på http://no.yahoo.com/
Nytt design, enklere å bruke, alltid tilgang til Adressebok, Kalender og Notisbok
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS / SAMBA / HP930C / WINDOWS CLIENTS!

[Rodrigo Sirio Coelho]

Server Samba 2.2.5! Printing = cups! Printing local 
all OK! 
the printer is atached in a Print Server (PLANET) 
on IP 192.168.0.8. The cups is using LPD to print local! the another 2 printers 
atached on the print server and mapped on CUPS are all working good! the hp930c 
is only working local(on the linux), when printing from windows 98, the server 
gives a error message 
 
gis-01 (192.168.0.51) connect to service hp930c as 
user xico (uid=500, gid=104) (pid 19088)[2002/09/24 19:01:54, 0] 
printing/print_cups.c:cups_job_submit(655)  Unable to print file to 
hp930c - client-error-document-format-not-supported[2002/09/24 19:05:36, 1] 
smbd/service.c:close_cnum(681)  gis-01 (192.168.0.51) closed connection 
to service hp930c
 
Anyone knows what is this??? ! :)
 
 
Thank you

Re: [Samba] Re: samba & cups

[linux power]

Cupsd must be started before you start smbd at boot. 



--- Frank Matthieß <[EMAIL PROTECTED]> skrev:
> Freitag den 20.09.2002 um 18:35 CEST  +0200, schrieb
> P. Jourdan:
> > At 03:35 PM 9/20/2002 +0200, you wrote:
> > Gentlemen, and all others who have helped me:
> > 
> > Someohow, I think I understand the samba
> configuration enough to make it 
> > work.
> > OK. It works.
> > 
> > Now comes the stinger.
> > 
> > SAMBA WORKS FINE.
> 
> ok. first step.
> 
> > 
> > CUPS IS SICK. VERY SICK INDEED.  And I need help
> to fix it.
> >
> 
> If you have to start this correectly, you won't miss
> them. 
> But i must agree, the first time is hard to
> configure.
> 
> > After bootup, cups does not print. cupsd is
> running, so is smbd and nmbd.
> > 
> > IF I KILL CUPS AND THEN RESTART IT - ALL OF A
> SUDDEN EVERYTHING WORKS. I 
> > can print from command line, from Win2k, the web
> interface works.
> 
> The config seems to be ok.
> 
> > Now, the installation has been by the book. Done
> by good old make; make 
> > install.
> > cups startup is from rc.d.
> > 
> > Why do I have to restart cups to make it work when
> CUPS IS SUPPOSED TO WORK 
> > "OUT OF THE BOX"  -
> 
> It sounds like a dependency problem of services. Do
> you startup cups
> after the network setup?
> 
> Restarting manually is just only starting at last.
> 
> Just increase ther debug level of cups, reboot the
> machine and read the
> logs carefully. cupsd must complain some "missing
> parts".
> 
> Try to connect after the startup via browser to the
> webinterface. OK?
> 
> Frank.
> -- 
> Frank Matthieß   
> [EMAIL PROTECTED]
> 
> -- 
> To unsubscribe from this list go to the following
> URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

__
Se den nye Yahoo! Mail på http://no.yahoo.com/
Nytt design, enklere å bruke, alltid tilgang til Adressebok, Kalender og Notisbok
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: samba & cups

[Frank Matthieß]

Freitag den 20.09.2002 um 18:35 CEST  +0200, schrieb P. Jourdan:
> At 03:35 PM 9/20/2002 +0200, you wrote:
> Gentlemen, and all others who have helped me:
> 
> Someohow, I think I understand the samba configuration enough to make it 
> work.
> OK. It works.
> 
> Now comes the stinger.
> 
> SAMBA WORKS FINE.

ok. first step.

> 
> CUPS IS SICK. VERY SICK INDEED.  And I need help to fix it.
>

If you have to start this correectly, you won't miss them. 
But i must agree, the first time is hard to configure.

> After bootup, cups does not print. cupsd is running, so is smbd and nmbd.
> 
> IF I KILL CUPS AND THEN RESTART IT - ALL OF A SUDDEN EVERYTHING WORKS. I 
> can print from command line, from Win2k, the web interface works.

The config seems to be ok.

> Now, the installation has been by the book. Done by good old make; make 
> install.
> cups startup is from rc.d.
> 
> Why do I have to restart cups to make it work when CUPS IS SUPPOSED TO WORK 
> "OUT OF THE BOX"  -

It sounds like a dependency problem of services. Do you startup cups
after the network setup?

Restarting manually is just only starting at last.

Just increase ther debug level of cups, reboot the machine and read the
logs carefully. cupsd must complain some "missing parts".

Try to connect after the startup via browser to the webinterface. OK?

Frank.
-- 
Frank Matthieß[EMAIL PROTECTED]

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] CUPS & client driver download

[Gerald Carter]

On Sun, 9 Jun 2002, tony wrote:

> Hi everybody!
> 
> I've got a problem with downloading printerdrivers from my win2k box.
> Successfully added printer with cupsaddsmb-tool (as root, after
> failing as printer admin!!?!?!). The W32X86 and WIN40 directories
> have been created as they should and also did the PPD files.
> But if I connect to the printer from Win (as printer admin) I get the message that no
> driver could be found.
> 
> RPCclient CALL "enumprinters" gives me:
> 
> >INFO: Debug class all level = 2   (pid 6470 from pid 6470)
> >session setup ok
> >Domain=[VALIKTALS] OS=[Unix] Server=[Samba 2.2.3a]
> >cmd = enumprinters
> >enumprinters
> >flags:[0x80]
> >name:[\\localhost\HP690C]
> >description:[localhost\\localhost\HP690C,HP DeskJet 690C, Foomatic + 
>pcl3,localhost\HP690C]
> >comment:[localhost\HP690C]
> 
> but all the RPCclient CALL "enumdrivers" states is:
> 
> >INFO: Debug class all level = 2   (pid 6472 from pid 6472)
> >session setup ok
> >Domain=[VALIKTALS] OS=[Unix] Server=[Samba 2.2.3a]
> >cmd = enumdrivers
> >enumdrivers
> 
> shouldn't I be seing more info here?
> 
> here is how smb.conf looks like:
> 
> [global]
> ..
> ..
> security = SHARE

Make sure you use "security = user" for the point-n-print
feature ion Samba 2.2.x.


> ..
> load printers = yes
> printing = cups
> printcap name = cups
> printer admin = tony, root
> 
> [printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = no
> public = yes
> guest ok = yes
> writable = no
> printable = yes
> printer admin = tony, root 
> 
> [print$]
> comment = Printer Drivers
> path = /local/samba/printerdrivers 
> browseable = yes
> guest ok = yes
> read only = yes
> write list = tony, root
> 
> What am I missing? Has anybody got a clue?




cheers, jerry
 -
 Hewlett-Packard http://www.hp.com
 SAMBA Team   http://www.samba.org
 --http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.  ISBN 0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] CUPS & client driver download

[tony]

Hi everybody!

I've got a problem with downloading printerdrivers from my win2k box.
Successfully added printer with cupsaddsmb-tool (as root, after
failing as printer admin!!?!?!). The W32X86 and WIN40 directories
have been created as they should and also did the PPD files.
But if I connect to the printer from Win (as printer admin) I get the message that no
driver could be found.

RPCclient CALL "enumprinters" gives me:

>INFO: Debug class all level = 2   (pid 6470 from pid 6470)
>session setup ok
>Domain=[VALIKTALS] OS=[Unix] Server=[Samba 2.2.3a]
>cmd = enumprinters
>enumprinters
>flags:[0x80]
>name:[\\localhost\HP690C]
>description:[localhost\\localhost\HP690C,HP DeskJet 690C, Foomatic + 
>pcl3,localhost\HP690C]
>comment:[localhost\HP690C]

but all the RPCclient CALL "enumdrivers" states is:

>INFO: Debug class all level = 2   (pid 6472 from pid 6472)
>session setup ok
>Domain=[VALIKTALS] OS=[Unix] Server=[Samba 2.2.3a]
>cmd = enumdrivers
>enumdrivers

shouldn't I be seing more info here?

here is how smb.conf looks like:

[global]
..
..
security = SHARE
..
load printers = yes
printing = cups
printcap name = cups
printer admin = tony, root

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
printer admin = tony, root 

[print$]
comment = Printer Drivers
path = /local/samba/printerdrivers 
browseable = yes
guest ok = yes
read only = yes
write list = tony, root

What am I missing? Has anybody got a clue?

greets
tony.n


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba