samba - Nov 2007 - Non-registry problem: Slow printing

Greetings,

I have a client running samba-3.0.24 with mostly Windows-XP clients.
They can print to some printers (those with drivers provided by Microsoft)
without problem.

They can also print to printers with vendor supplied printer drivers
but they end up waiting up to 30 seconds just to select the printer.
There is a similar wait when adding the printer to the list of printers
the XP client knows about.

This does not appear to be the much discussed registry problem, as
we have repeatedly removed these registry entries and, though they come
back, there is no performance improvement.  Also, when people have
described the registry problem they have not said that it was driver
dependent.  Furthermore, as I understand the registry problem, it occurs
when there are non-existant printers listed ... which there are not in
our case.

There is no firewall between the client and the server except that which
Microsoft provides, and we still have the problem with that completely
disabled.

Here is my smb.conf:

    [global]
	    workgroup = FUZZBALL
	    netbios name = fzb3
	    netbios aliases = fzb3
	    server string =  fzb3
	    bind interfaces only = true
	    interfaces = eth0
	    null passwords = Yes
	    security = SHARE
	    guest account = guest
	    lanman auth = No
	    client lanman auth = No
	    client plaintext auth = No
	    socket options = TCP_NODELAY IPTOS_LOWDELAY 
	    local master = yes
	    prefered master = yes
	    log level = 3
	    log file = /usr/local/samba/log.%m
	    name resolve order = wins bcast host 
	    deadtime = 1
	    printcap cache time = 750
	    printcap name = /etc/printcap
	    domain logons = No
	    #domain logons = yes
	    wins support = yes
	    local master = No
	    dns proxy = No
	    wins server = 10.1.1.1
	    ldap ssl = no
	    path = /var/tmp/samba%S
	    admin users = root, guest
	    printer admin = root, guest
	    guest ok = Yes
	    guest only = Yes
	    hosts allow = 10.1.0.0/10  127.0.0.1
	    hosts deny = 0.0.0.0/0 
	    printable = Yes
	    printing = lprng
	    print command = /usr/bin/lpr -Fl -r -P%p %s
	    lpq command = /bin/true
	    lprm command = /bin/true
	    lppause command = /bin/true
	    lpresume command = /bin/true
	    queuepause command = /bin/true
	    queueresume command = /bin/true
	    use client driver = Yes
	    show add printer wizard = no
	    disable spoolss = yes
	    max log size = 0

    [printers]

    [cr1000]
	    print command = lpr -Fl -r -P%p %s
	    comment = HPX,  Cole  0, C205
	    printer = cr1000
	    printable = yes
	    browseable = yes
	    guest ok = Yes
	    guest only = Yes
	    public = yes
	    writable = no
	    path = /var/spool/samba/cr1000

Does anybody have any ideas here?  The packet traces and samba log files
indicate that the PC is sending many transactions which are failing
but I am inexpert at decoding exactly what is wrong with them.  I can
include log files, but I am wondering if anyone knows of anything off the
top of their head?

All my web searches to date have revealed the registry issue but nothing
beyond that.

Thanks!  --Chris

Greetings,

I have commented out the "wins support" line, restarted samba and
added the printer with the slow driver.  No difference in performance.
I also tried moving "wins" to the end of the name resolve order, also
no difference.

I'd rather not bring the Internet to a halt by sending around the 987k
log file, but those wishing to see it can go to:

	http://www.brightsands.com/~chris/log.bz2

Anyone have any thoughts?  --Chris

| Date: Wed, 14 Nov 2007 16:40:27 -0600
| From: Dale Schroeder <dale@BriannasSaladDressing.com>
| To: ccaldwell@suscom-maine.net
| Subject: Re: [Samba] Non-registry problem:  Slow printing
| 
| It may have nothing to do with your printing problem, but you should 
| never have both "wins support" and "wins server" in the
same smb.conf.
| If this system is the WINS server, then use "wins support".  If
another
| system is the WINS server, then use "wins server".  This might be 
| significant since wins is listed first in "name resolve order" and a
lot
| of network printers now come with WINS support.
| 
| I don't know a thing about lprng printing (CUPS exclusively), so I
can't
| help you there.  The logs may be necessary.
| 
| ccaldwell@suscom-maine.net wrote:
| > I have a client running samba-3.0.24 with mostly Windows-XP clients.
| > They can print to some printers (those with drivers provided by
Microsoft)
| > without problem.
| >
| > They can also print to printers with vendor supplied printer drivers
| > but they end up waiting up to 30 seconds just to select the printer.
| > There is a similar wait when adding the printer to the list of printers
| > the XP client knows about.
| >
| > This does not appear to be the much discussed registry problem, as
| > we have repeatedly removed these registry entries and, though they come
| > back, there is no performance improvement.  Also, when people have
| > described the registry problem they have not said that it was driver
| > dependent.  Furthermore, as I understand the registry problem, it occurs
| > when there are non-existant printers listed ... which there are not in
| > our case.
| >
| > There is no firewall between the client and the server except that which
| > Microsoft provides, and we still have the problem with that completely
| > disabled.
| >
| > Here is my smb.conf:
| >
| >     [global]
| > 	    workgroup = FUZZBALL
| > 	    netbios name = fzb3
| > 	    netbios aliases = fzb3
| > 	    server string =  fzb3
| > 	    bind interfaces only = true
| > 	    interfaces = eth0
| > 	    null passwords = Yes
| > 	    security = SHARE
| > 	    guest account = guest
| > 	    lanman auth = No
| > 	    client lanman auth = No
| > 	    client plaintext auth = No
| > 	    socket options = TCP_NODELAY IPTOS_LOWDELAY 
| > 	    local master = yes
| > 	    prefered master = yes
| > 	    log level = 3
| > 	    log file = /usr/local/samba/log.%m
| > 	    *name resolve order = wins bcast host* 
| > 	    deadtime = 1
| > 	    printcap cache time = 750
| > 	    printcap name = /etc/printcap
| > 	    domain logons = No
| > 	    #domain logons = yes
| > 	    *wins support = yes*
| > 	    local master = No
| > 	    dns proxy = No
| > 	    *wins server = 10.1.1.1*
| > 	    ldap ssl = no
| > 	    path = /var/tmp/samba%S
| > 	    admin users = root, guest
| > 	    printer admin = root, guest
| > 	    guest ok = Yes
| > 	    guest only = Yes
| > 	    hosts allow = 10.1.0.0/10  127.0.0.1
| > 	    hosts deny = 0.0.0.0/0 
| > 	    printable = Yes
| > 	    printing = lprng
| > 	    print command = /usr/bin/lpr -Fl -r -P%p %s
| > 	    lpq command = /bin/true
| > 	    lprm command = /bin/true
| > 	    lppause command = /bin/true
| > 	    lpresume command = /bin/true
| > 	    queuepause command = /bin/true
| > 	    queueresume command = /bin/true
| > 	    use client driver = Yes
| > 	    show add printer wizard = no
| > 	    disable spoolss = yes
| > 	    max log size = 0
| >
| >     [printers]
| >
| >     [cr1000]
| > 	    print command = lpr -Fl -r -P%p %s
| > 	    comment = HPX,  Cole  0, C205
| > 	    printer = cr1000
| > 	    printable = yes
| > 	    browseable = yes
| > 	    guest ok = Yes
| > 	    guest only = Yes
| > 	    public = yes
| > 	    writable = no
| > 	    path = /var/spool/samba/cr1000
| >
| > Does anybody have any ideas here?  The packet traces and samba log files
| > indicate that the PC is sending many transactions which are failing
| > but I am inexpert at decoding exactly what is wrong with them.  I can
| > include log files, but I am wondering if anyone knows of anything off the
| > top of their head?
| >
| > All my web searches to date have revealed the registry issue but nothing
| > beyond that.

>From your log:
check_sam_security: Couldn't find user 'guest' in passdb.
auth/auth.c:check_ntlm_password(273)
  check_ntlm_password: sam authentication for user [guest] FAILED with error
NT_STATUS_NO_SUCH_USER
auth/auth.c:check_ntlm_password(319)
  check_ntlm_password:  Authentication for user [guest] -> [guest] FAILED
with error NT_STATUS_NO_SUCH_USER
>From smb.conf
[global]
guest account = guest
guest only = yes

[cr1000]
guest only = Yes

It appears the user "guest" does not exist.  The clues would suggest
that you either need to add the user "guest", choose an existing user
for the guest account, or change the printer to something other than "guest
only".  Based on the logs, I'm guessing that all that extra time is
going toward trying to authenticate a forced user that doesn't exist.  Do
the printers that work have the same setup?
>From SWAT:
guest account (G)

    This is a username which will be used for access to services which are
specified as guest ok (see below). Whatever privileges this user has will be
available to any client connecting to the guest service. This user must exist in
the password file, but does not require a valid login. The user account
"ftp" is often a good choice for this parameter.

    On some systems the default guest account "nobody" may not be able
to print. Use another account in this case. You should test this by trying to
log in as your guest user (perhaps by using the su - command) and trying to
print using the system print command such as lpr(1) or lp(1).

    This parameter does not accept % macros, because many parts of the system
require this value to be constant for correct operation.

    Default: guest account = nobody # default can be changed at compile-time

    Example: guest account = ftp 

Hope this helps,
Dale



-----Original message-----
From: ccaldwell@suscom-maine.net
Date: Wed, 14 Nov 2007 19:14:40 -0600
To: samba@lists.samba.org
Subject: Re: [Samba] Non-registry problem:  Slow printing
> Greetings,
> 
> I have commented out the "wins support" line, restarted samba and
> added the printer with the slow driver.  No difference in performance.
> I also tried moving "wins" to the end of the name resolve order,
also
> no difference.
> 
> I'd rather not bring the Internet to a halt by sending around the 987k
> log file, but those wishing to see it can go to:
> 
> 	http://www.brightsands.com/~chris/log.bz2
> 
> Anyone have any thoughts?  --Chris
> 
> | Date: Wed, 14 Nov 2007 16:40:27 -0600
> | From: Dale Schroeder <dale@BriannasSaladDressing.com>
> | To: ccaldwell@suscom-maine.net
> | Subject: Re: [Samba] Non-registry problem:  Slow printing
> | 
> | It may have nothing to do with your printing problem, but you should 
> | never have both "wins support" and "wins server" in
the same smb.conf.
> | If this system is the WINS server, then use "wins support".  If
another
> | system is the WINS server, then use "wins server".  This might
be
> | significant since wins is listed first in "name resolve order"
and a lot
> | of network printers now come with WINS support.
> | 
> | I don't know a thing about lprng printing (CUPS exclusively), so I
can't
> | help you there.  The logs may be necessary.
> | 
> | ccaldwell@suscom-maine.net wrote:
> | > I have a client running samba-3.0.24 with mostly Windows-XP clients.
> | > They can print to some printers (those with drivers provided by
Microsoft)
> | > without problem.
> | >
> | > They can also print to printers with vendor supplied printer drivers
> | > but they end up waiting up to 30 seconds just to select the printer.
> | > There is a similar wait when adding the printer to the list of
printers
> | > the XP client knows about.
> | >
> | > This does not appear to be the much discussed registry problem, as
> | > we have repeatedly removed these registry entries and, though they
come
> | > back, there is no performance improvement.  Also, when people have
> | > described the registry problem they have not said that it was driver
> | > dependent.  Furthermore, as I understand the registry problem, it
occurs
> | > when there are non-existant printers listed ... which there are not
in
> | > our case.
> | >
> | > There is no firewall between the client and the server except that
which
> | > Microsoft provides, and we still have the problem with that
completely
> | > disabled.
> | >
> | > Here is my smb.conf:
> | >
> | >     [global]
> | > 	    workgroup = FUZZBALL
> | > 	    netbios name = fzb3
> | > 	    netbios aliases = fzb3
> | > 	    server string =  fzb3
> | > 	    bind interfaces only = true
> | > 	    interfaces = eth0
> | > 	    null passwords = Yes
> | > 	    security = SHARE
> | > 	    guest account = guest
> | > 	    lanman auth = No
> | > 	    client lanman auth = No
> | > 	    client plaintext auth = No
> | > 	    socket options = TCP_NODELAY IPTOS_LOWDELAY 
> | > 	    local master = yes
> | > 	    prefered master = yes
> | > 	    log level = 3
> | > 	    log file = /usr/local/samba/log.%m
> | > 	    *name resolve order = wins bcast host* 
> | > 	    deadtime = 1
> | > 	    printcap cache time = 750
> | > 	    printcap name = /etc/printcap
> | > 	    domain logons = No
> | > 	    #domain logons = yes
> | > 	    *wins support = yes*
> | > 	    local master = No
> | > 	    dns proxy = No
> | > 	    *wins server = 10.1.1.1*
> | > 	    ldap ssl = no
> | > 	    path = /var/tmp/samba%S
> | > 	    admin users = root, guest
> | > 	    printer admin = root, guest
> | > 	    guest ok = Yes
> | > 	    guest only = Yes
> | > 	    hosts allow = 10.1.0.0/10  127.0.0.1
> | > 	    hosts deny = 0.0.0.0/0 
> | > 	    printable = Yes
> | > 	    printing = lprng
> | > 	    print command = /usr/bin/lpr -Fl -r -P%p %s
> | > 	    lpq command = /bin/true
> | > 	    lprm command = /bin/true
> | > 	    lppause command = /bin/true
> | > 	    lpresume command = /bin/true
> | > 	    queuepause command = /bin/true
> | > 	    queueresume command = /bin/true
> | > 	    use client driver = Yes
> | > 	    show add printer wizard = no
> | > 	    disable spoolss = yes
> | > 	    max log size = 0
> | >
> | >     [printers]
> | >
> | >     [cr1000]
> | > 	    print command = lpr -Fl -r -P%p %s
> | > 	    comment = HPX,  Cole  0, C205
> | > 	    printer = cr1000
> | > 	    printable = yes
> | > 	    browseable = yes
> | > 	    guest ok = Yes
> | > 	    guest only = Yes
> | > 	    public = yes
> | > 	    writable = no
> | > 	    path = /var/spool/samba/cr1000
> | >
> | > Does anybody have any ideas here?  The packet traces and samba log
files
> | > indicate that the PC is sending many transactions which are failing
> | > but I am inexpert at decoding exactly what is wrong with them.  I
can
> | > include log files, but I am wondering if anyone knows of anything
off the
> | > top of their head?
> | >
> | > All my web searches to date have revealed the registry issue but
nothing
> | > beyond that.
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba

Update:
 
Each time we set up a new user on the system, passwords need changing on the AD
and the samba server. Is there a way to set permissions for the samba from the
AD so that we do not need to go through this rigmarole? (most problematic at the
start of a new school year).
 
>I completed this part of my task -
http://ubuntuforums.org/showthread.php?t=280702. It works perfectly for me. I am
amazed that I did not find it earlier.
 
My aim is to also have some linux (probably k/ubuntu) boxes that authenticate on
the network using standard AD credentials. I have tried in vain to find a way to
introduce a single point of authentication, I have looked at kerberos, winbind
and LDAP. I consider myself a good network technician, but the introduction of
linux into a domain has thrown me. Is there a an easy way to integrate a linux
fileserver with a windows controlled domain with both linux and windows clients?
 
> I am probably going to go with a kerberos and winbind mechanism to get this
working. Hold out guys - Anything is possible!
 
Ben
_________________________________________________________________
Feel like a local wherever you go.
http://www.backofmyhand.com

Greetings,

I created a guest user and the error message goes away but that doesn't
effect the performance of the printers.  That is, the printer drivers
that are slow are still slow and the ones that are fast have remained
fast.

I have updated the log in http://www.brightsands.com/~chris/log.bz2
if anyone has any ideas.  --Chris

:Cc: samba@lists.samba.org
:Subject: Re: [Samba] Non-registry problem:  Slow printing
:
:>From your log:
:
:check_sam_security: Couldn't find user 'guest' in passdb.
:auth/auth.c:check_ntlm_password(273)
:  check_ntlm_password: sam authentication for user [guest] FAILED with error
NT_STATUS_NO_SUCH_USER
:auth/auth.c:check_ntlm_password(319)
:  check_ntlm_password:  Authentication for user [guest] -> [guest] FAILED
with error NT_STATUS_NO_SUCH_USER
:
:>From smb.conf
:[global]
:guest account = guest
:guest only = yes
:
:[cr1000]
:guest only = Yes
:

:It appears the user "guest" does not exist.  The clues would suggest
:that you either need to add the user "guest", choose an existing user
:for the guest account, or change the printer to something other than
:"guest only".  Based on the logs, I'm guessing that all that
extra time
:is going toward trying to authenticate a forced user that doesn't exist.
:Do the printers that work have the same setup?

(good information about SWAT deleted to try to keep this mail size down)

:Hope this helps, Dale
:
:
:
:-----Original message-----
:From: ccaldwell@suscom-maine.net
:To: samba@lists.samba.org
:Subject: Re: [Samba] Non-registry problem:  Slow printing
:
:> Greetings,
:> 
:> I have commented out the "wins support" line, restarted samba
and
:> added the printer with the slow driver.  No difference in performance.
:> I also tried moving "wins" to the end of the name resolve order,
also
:> no difference.
:> 
:> I'd rather not bring the Internet to a halt by sending around the 987k
:> log file, but those wishing to see it can go to:
:> 
:> 	http://www.brightsands.com/~chris/log.bz2
:> 
:> Anyone have any thoughts?  --Chris
:> 
:> | Date: Wed, 14 Nov 2007 16:40:27 -0600
:> | From: Dale Schroeder <dale@BriannasSaladDressing.com>
:> | To: ccaldwell@suscom-maine.net
:> | Subject: Re: [Samba] Non-registry problem:  Slow printing
:> | 
:> | It may have nothing to do with your printing problem, but you should 
:> | never have both "wins support" and "wins server" in
the same smb.conf.
:> | If this system is the WINS server, then use "wins support". 
If another
:> | system is the WINS server, then use "wins server".  This might
be
:> | significant since wins is listed first in "name resolve order"
and a lot
:> | of network printers now come with WINS support.
:> | 
:> | I don't know a thing about lprng printing (CUPS exclusively), so I
can't
:> | help you there.  The logs may be necessary.
:> | 
:> | ccaldwell@suscom-maine.net wrote:
:> | > I have a client running samba-3.0.24 with mostly Windows-XP
clients.
:> | > They can print to some printers (those with drivers provided by
Microsoft)
:> | > without problem.
:> | >
:> | > They can also print to printers with vendor supplied printer
drivers
:> | > but they end up waiting up to 30 seconds just to select the
printer.
:> | > There is a similar wait when adding the printer to the list of
printers
:> | > the XP client knows about.
:> | >
:> | > This does not appear to be the much discussed registry problem, as
:> | > we have repeatedly removed these registry entries and, though they
come
:> | > back, there is no performance improvement.  Also, when people have
:> | > described the registry problem they have not said that it was
driver
:> | > dependent.  Furthermore, as I understand the registry problem, it
occurs
:> | > when there are non-existant printers listed ... which there are not
in
:> | > our case.
:> | >
:> | > There is no firewall between the client and the server except that
which
:> | > Microsoft provides, and we still have the problem with that
completely
:> | > disabled.
:> | >
:> | > Here is my smb.conf:
:> | >
:> | >     [global]
:> | > 	    workgroup = FUZZBALL
:> | > 	    netbios name = fzb3
:> | > 	    netbios aliases = fzb3
:> | > 	    server string =  fzb3
:> | > 	    bind interfaces only = true
:> | > 	    interfaces = eth0
:> | > 	    null passwords = Yes
:> | > 	    security = SHARE
:> | > 	    guest account = guest
:> | > 	    lanman auth = No
:> | > 	    client lanman auth = No
:> | > 	    client plaintext auth = No
:> | > 	    socket options = TCP_NODELAY IPTOS_LOWDELAY 
:> | > 	    local master = yes
:> | > 	    prefered master = yes
:> | > 	    log level = 3
:> | > 	    log file = /usr/local/samba/log.%m
:> | > 	    *name resolve order = wins bcast host* 
:> | > 	    deadtime = 1
:> | > 	    printcap cache time = 750
:> | > 	    printcap name = /etc/printcap
:> | > 	    domain logons = No
:> | > 	    #domain logons = yes
:> | > 	    *wins support = yes*
:> | > 	    local master = No
:> | > 	    dns proxy = No
:> | > 	    *wins server = 10.1.1.1*
:> | > 	    ldap ssl = no
:> | > 	    path = /var/tmp/samba%S
:> | > 	    admin users = root, guest
:> | > 	    printer admin = root, guest
:> | > 	    guest ok = Yes
:> | > 	    guest only = Yes
:> | > 	    hosts allow = 10.1.0.0/10  127.0.0.1
:> | > 	    hosts deny = 0.0.0.0/0 
:> | > 	    printable = Yes
:> | > 	    printing = lprng
:> | > 	    print command = /usr/bin/lpr -Fl -r -P%p %s
:> | > 	    lpq command = /bin/true
:> | > 	    lprm command = /bin/true
:> | > 	    lppause command = /bin/true
:> | > 	    lpresume command = /bin/true
:> | > 	    queuepause command = /bin/true
:> | > 	    queueresume command = /bin/true
:> | > 	    use client driver = Yes
:> | > 	    show add printer wizard = no
:> | > 	    disable spoolss = yes
:> | > 	    max log size = 0
:> | >
:> | >     [printers]
:> | >
:> | >     [cr1000]
:> | > 	    print command = lpr -Fl -r -P%p %s
:> | > 	    comment = HPX,  Cole  0, C205
:> | > 	    printer = cr1000
:> | > 	    printable = yes
:> | > 	    browseable = yes
:> | > 	    guest ok = Yes
:> | > 	    guest only = Yes
:> | > 	    public = yes
:> | > 	    writable = no
:> | > 	    path = /var/spool/samba/cr1000
:> | >
:> | > Does anybody have any ideas here?  The packet traces and samba log
files
:> | > indicate that the PC is sending many transactions which are failing
:> | > but I am inexpert at decoding exactly what is wrong with them.  I
can
:> | > include log files, but I am wondering if anyone knows of anything
off the
:> | > top of their head?
:> | >
:> | > All my web searches to date have revealed the registry issue but
nothing
:> | > beyond that.
:> -- 
:> To unsubscribe from this list go to the following URL and read the
:> instructions:  https://lists.samba.org/mailman/listinfo/samba
:

Making an AD Domain Member Server is not difficult.  However, what is 
difficult, is getting it to work reliably.  It seems to work OK for a 
week or so at a time, which is not particularly robust...

Cheers,

H.

Ben Ladd wrote:
> Update:
>  
> Each time we set up a new user on the system, passwords need changing on
the AD and the samba server. Is there a way to set permissions for the samba
from the AD so that we do not need to go through this rigmarole? (most
problematic at the start of a new school year).
>  
>   
>> I completed this part of my task -
http://ubuntuforums.org/showthread.php?t=280702. It works perfectly for me. I am
amazed that I did not find it earlier.
>>     
>  
> My aim is to also have some linux (probably k/ubuntu) boxes that
authenticate on the network using standard AD credentials. I have tried in vain
to find a way to introduce a single point of authentication, I have looked at
kerberos, winbind and LDAP. I consider myself a good network technician, but the
introduction of linux into a domain has thrown me. Is there a an easy way to
integrate a linux fileserver with a windows controlled domain with both linux
and windows clients?
>  
>   
>> I am probably going to go with a kerberos and winbind mechanism to get
this working. Hold out guys - Anything is possible!
>>     
>  
> Ben
> _________________________________________________________________
> Feel like a local wherever you go.
> http://www.backofmyhand.com
>