Hi All,
Since updating a from 3.0.1-2 to 3.0.2-1 a few weeks back I've been
unable to print. I checked all the obvios settings, but as they had
been working perfectly for some time prior was not surprised to find the
configuration was correct.
The authentication is configured via winbind to a 2000 ADS PDC.
security = DOMAIN
I've since updated again to 3.0.2-2 and found the issue persists, even
admin users are unable to connect. The log seems to indicate some weird
processing of the user account in reference only to the printer shares
as all other shares are behaving well (inc printers.
It seems as though no matter which user connects, the backend attempts
to authenticate the user as root...
Case in point the following workstation log (level 10)...
checking name: \\ftwork\HP_4000
[2004/02/23 14:00:28, 10]
rpc_server/srv_spoolss_nt.c:open_printer_hnd(548)
open_printer_hnd: name [\\ftwork\HP_4000]
[2004/02/23 14:00:28, 4] rpc_server/srv_lsa_hnd.c:create_policy_hnd(142)
Opened policy hnd[2] [000] 00 00 00 00 27 00 00 00 00 00 00 00 CC 6C
39 40 ....'... .....l9@
[010] 12 42 00 00 .B..
[2004/02/23 14:00:28, 3]
rpc_server/srv_spoolss_nt.c:set_printer_hnd_printertype(447)
Setting printer type=\\ftwork\HP_4000
Printer is a printer
[2004/02/23 14:00:28, 4]
rpc_server/srv_spoolss_nt.c:set_printer_hnd_name(480)
Setting printer name=\\ftwork\HP_4000 (len=16)
searching for [HP_4000] (len=7)
share:printers
share:HP_4000
set_printer_hnd_name: Printer found: HP_4000 -> HP_4000
[2004/02/23 14:00:28, 5]
rpc_server/srv_spoolss_nt.c:open_printer_hnd(583)
2 printer handles active
[2004/02/23 14:00:28, 4]
rpc_server/srv_lsa_hnd.c:find_policy_by_hnd_internal(162)
Found policy hnd[0] [000] 00 00 00 00 27 00 00 00 00 00 00 00 CC 6C
39 40 ....'... .....l9@
[010] 12 42 00 00 .B..
[2004/02/23 14:00:28, 4]
rpc_server/srv_lsa_hnd.c:find_policy_by_hnd_internal(162)
Found policy hnd[0] [000] 00 00 00 00 27 00 00 00 00 00 00 00 CC 6C
39 40 ....'... .....l9@
[010] 12 42 00 00 .B..
[2004/02/23 14:00:28, 4]
rpc_server/srv_spoolss_nt.c:get_printer_snum(430)
short name:HP_4000
[2004/02/23 14:00:28, 10] lib/username.c:user_in_list(521)
user_in_list: checking user root in list
[2004/02/23 14:00:28, 10] lib/username.c:user_in_list(525)
user_in_list: checking user |root| against |FASTTRACK/Domain Users|
[2004/02/23 14:00:28, 10] lib/username.c:user_in_list(602)
user_in_list: checking if user |root| is in winbind group
|FASTTRACK/Domain Users|
[2004/02/23 14:00:28, 3]
rpc_server/srv_spoolss_nt.c:_spoolss_open_printer_ex(1764)
access DENIED for printer open
Another crazy thing is when altering the root password using passwd, I
get prompts for the pwd to be re-entered and then a prompt for the
password to be entered for root@FASTTRACK.NET.AU which then results in
passwd: Authentication failure
And for that matter the user root@FASTTRACK.NET.AU doesn't exist.
Of course the local root user account long exists in the tdbc courtesy
of smbpasswd.
Using smbclient as user root also fails with NT_STATUS_LOGON_FAILURE
Is the root@FASTTRACK.NET.AU passwd prompt a result of skewed automated
password sync?
nsswitch.conf ...
passwd: files winbind
shadow: files
group: files winbind
root is not listed as an invalid user in smb.conf
Can anyone can offer some suggestions here?
Thanks in advance!
Lewis Shobbrook
