[Samba] w2k and samba, printer properties hourglasses forver after driver upload + OK
daniel.jarboe at custserv.com
daniel.jarboe at custserv.com
Wed Aug 28 07:01:01 GMT 2002
Argh, rebuilt samba-2.2.5-1 with the following patches from
http://us4.samba.org/samba/ftp/patches/jerry/post-2.2.5/:
Makefile.in.patch 26-Jul-2002 08:18 1k
ldap_start_tls.patch 24-Jun-2002 16:11 1k
samba-2.2.5-printing..> 27-Aug-2002 21:17 30k
W2K printer properties still hangs forever after driver upload followed
by OK or Apply.
Very interesting open/close activity in the machine log below.
Here's what I do from w2k:
connect to share (as printer admin), Printers, right click printer name
and select properties
Device settings cannot be displayed... blah blah. [No] do not install
driver now.
Select Advanced Tab, Click "New Driver..." button
Have Disk, I select the manufacturer's OEMSETUP.INF, OK, Select correct
printer, Finish
Here I am prompted for '*.inf' from W2K CD-ROM. Add Drivers Wizard
doesn't like anything there, it will only proceed if I point back to
manufacturer's OEMSETUP.INF. Should I do something else for this to
work correctly?
I tell it to proceed from directory with OEMSETUP.INF. OK.
Digital Signiature not found, [Yes] install anyway.
Drivers are uploaded successfully, I see them on the server, the wizard
is done I'm back at properties. OK or APPLY causes hourglass forever.
I can browse to the share and see that the printer now has the Model
displayed.
I can't open a new properties window until I kill the old one. End
task, explorer.exe starts back up.
New properties sessions start up and close fine, but trying a "Test
Print" results in:
"Test page failed to print. Would you like to view the print trouble
shooter for assitance?
Operation could not be completed.
Adding the printer locally from the server seems to go without a hitch,
but test print results in same error.
Also, selecting the print driver from the dropdown menu for a different
print queue/share causes the same behavior on OK or APPLY.
While properties hourglasses, a tail -f shows that the machine log is
going through the roof with the windows client accessing the drivers like:
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcNtKrnl.dll read=Yes write=No (numopen=1)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcNtUI.dll read=Yes write=No (numopen=2)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KMKM5530.MDX read=Yes write=No (numopen=3)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KC3D0213.DAT read=Yes write=No (numopen=4)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KMAGFA1.FDF read=Yes write=No (numopen=5)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCPDLPS.DLL read=Yes write=No (numopen=6)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCPDL5E.DLL read=Yes write=No (numopen=7)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCPDLXL.DLL read=Yes write=No (numopen=8)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCMV3D.INI read=Yes write=No (numopen=9)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcProEpi.dll read=Yes write=No (numopen=10)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcMV3Da.dll read=Yes write=No (numopen=11)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcRes.dll read=Yes write=No (numopen=12)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcRdrGdi.dll read=Yes write=No (numopen=13)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcFSMain.dll read=Yes write=No (numopen=14)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcNtCore.dll read=Yes write=No (numopen=15)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcNtKrnl.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:38, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcNtKrnl.dll (numopen=15)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcNtUI.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:38, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcNtUI.dll (numopen=15)
[2002/08/28 11:45:38, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KMKM5530.MDX read=Yes write=No (numopen=16)
[2002/08/28 11:45:38, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KMKM5530.MDX (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KC3D0213.DAT read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KC3D0213.DAT (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KMAGFA1.FDF read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KMAGFA1.FDF (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCPDLPS.DLL read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCPDLPS.DLL (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCPDL5E.DLL read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCPDL5E.DLL (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCPDLXL.DLL read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCPDLXL.DLL (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KCMV3D.INI read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCMV3D.INI (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcProEpi.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcProEpi.dll (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcMV3Da.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcMV3Da.dll (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcRes.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcRes.dll (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcRdrGdi.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcRdrGdi.dll (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcFSMain.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcFSMain.dll (numopen=15)
[2002/08/28 11:45:39, 2] smbd/open.c:open_file(233)
jarboed opened file W32X86/2/KcNtCore.dll read=Yes write=No (numopen=16)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcNtCore.dll (numopen=15)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcNtKrnl.dll (numopen=14)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcNtUI.dll (numopen=13)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KMKM5530.MDX (numopen=12)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KC3D0213.DAT (numopen=11)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KMAGFA1.FDF (numopen=10)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCPDLPS.DLL (numopen=9)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCPDL5E.DLL (numopen=8)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCPDLXL.DLL (numopen=7)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KCMV3D.INI (numopen=6)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcProEpi.dll (numopen=5)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcMV3Da.dll (numopen=4)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcRes.dll (numopen=3)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcRdrGdi.dll (numopen=2)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcFSMain.dll (numopen=1)
[2002/08/28 11:45:39, 2] smbd/close.c:close_normal_file(213)
my_dom+jarboed closed file W32X86/2/KcNtCore.dll (numopen=0)
This is repeated over and over again, (open from 1 to 16, closing and
opening going from 15 to 16 open files, then finally closing down to 0)
Also notice that sometimes the files are openned as jarboed and
sometimes my_dom+jarboed. Could winbind be at fault here, or is this
normal?
Worked fine to w2k print server. Any ideas? What debug level of the
logs would be of more help?
Thanks very much, an incredible product, Samba team.
~ Daniel
RH 7.2, LPRng, winbind, security=domain, connecting to NT PDC and WINS
server
jerry at samba.org wrote:
>On Wed, 28 Aug 2002 daniel.jarboe at custserv.com wrote:
>
>>Any idea if uploading/downloading of print drivers from disk (not
>>generic windows print drivers) from w2k will be fixed with samba 3.0
>>release? The print drivers worked with uploading from w2k box to NT
>>print-server, but not w2k box to samba 2.2.5-1 rpm with patches. The
>>drivers upload successfully, but test print fails, etc. Maybe it had
>>something to do with no Microsoft digital signiature in the .inf file?
>>
>
>No. The signature wouldn't have affected this. Please try the recent
>patch I posted (last night) and try again. This would have had direct
>bearing on Win2k/XP clients.
>
>
>
>
>
>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--
>
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the samba
mailing list