[Samba] Samba Printing Extremely Slow from Windows XP

david rankin drankin at cox-internet.com
Thu Sep 8 03:17:33 GMT 2005


----- Original Message ----- 
From: "Gerald (Jerry) Carter" <jerry at samba.org>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mogens Kjaer wrote:
>
> |>
> |>    I am seeing the exact same problem. It first started seeing the
> |> problem after moving to 3.0.20a. I have 3.0.20a running on SuSE 9.0
> |> and I have the exact printer problems you describe. I am also running
> |> 3.0.13 on Mdk 2005LE and I have *no* problems at all.
> |
> | Me Too:
> |
> | Server running:
> |
> | Redhat 9, samba-2.2.12-0.90.6.legacy:    Slow print from XP
> | Fedora 3, samba-3.0.10-1.fc3:        Fast print from XP
> | Fedora 4, samba-3.0.14a-2:        Slow print from XP
>
> This is an XP client bug.  It has been covered before in the
> Samba ml archives.  You need to clean out the cached devmodes
> from the HCU portion of the registry on the client machine.
> Also check network traffic and I expect that you will see
> a stream of GetPrinterData() requests coming from the client
> looking up the value for "ChangeID"
>

In English Jerry ... in English???? Is this what you are talking about??

Procedure:
1. Edit the registry observing usual caution.
2. Locate the key HKEY_CURRENT_USER\Printers\DevModePerUser
3. Remove all VALUES for Network printers of the form:
\<print_server_name ><printer_queue_name>
4. Locate the key HKEY_CURRENT_USER\Printers\DevModes2
5. Remove all VALUES for Network printers of the form:
\<print_server_name><printer_queue_name>

Also, the issues described in 
http://www.24help.info/t310486-samba-xp-bug-client-spooler-loop-ms-kb-329234.html 
seem to still me lurking around. As you put it,

"Some old bugs never die I guess.
cheers, jerry"

This one still has some life left in it... The KB article describes the 
following:

"When a client opens several network printers that are all on a *single* 
server and then selects printer properties and preferences on *all these 
printers at the same time*, the spooler on the client side may not respond 
as expected. Additionally, the CPU-utilization of the print server may 
increase and remain high. In this scenario, a network capture shows that the 
client repeatedly queries the print server for printer properties.

A network capture displays the following remote procedure call (RPC) request 
from the client:

MSRPC: c/o RPC Request: call 0x3845 opnum 0x8 context 0x0 hint 0x734"
In our case now, the new xp service packs have been installed that were 
designed to remedy this. I dunno, something is still nuts. I get thousands 
of packets generated trying to access the printers. It seems to be some kind 
of loop. Here are the ethereal summary packet lines for 50 packets. Notice 
the SMB-DCERPC-TCP-TCP-TCP loop:

No.     Time        Source                Destination           Protocol 
Info
      1 0.000000    192.168.6.14          192.168.6.93          NBSS 
NBSS Continuation Message
      2 0.000132    192.168.6.93          192.168.6.14          SMB 
Read AndX Request, FID: 0x713f, 4280 bytes at offset 0
      3 0.001936    192.168.6.14          192.168.6.93          SMB 
Read AndX Response, FID: 0x713f, 4280 bytes
      4 0.002445    192.168.6.14          192.168.6.93          TCP 
[Continuation to #3] microsoft-ds > 1118 [ACK] Seq=2883 Ack=63 Win=10220 
Len=1460
      5 0.002460    192.168.6.93          192.168.6.14          TCP 
1118 > microsoft-ds [ACK] Seq=63 Ack=4343 Win=17520 Len=0
      6 0.003420    192.168.6.14          192.168.6.93          TCP 
[Continuation to #3] microsoft-ds > 1118 [PSH, ACK] Seq=4343 Ack=63 
Win=10220 Len=1423
      7 0.003509    192.168.6.93          192.168.6.14          SMB 
Read AndX Request, FID: 0x713f, 4280 bytes at offset 0
      8 0.005264    192.168.6.14          192.168.6.93          SMB 
Read AndX Response, FID: 0x713f, 2352 bytes
      9 0.005619    192.168.6.14          192.168.6.93          TCP 
[Continuation to #8] microsoft-ds > 1118 [PSH, ACK] Seq=7226 Ack=126 
Win=10220 Len=955
     10 0.005639    192.168.6.93          192.168.6.14          TCP 
1118 > microsoft-ds [ACK] Seq=126 Ack=8181 Win=17520 Len=0
     11 0.005973    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     12 0.006004    192.168.6.93          192.168.6.14          TCP 
[Continuation to #11] 1118 > microsoft-ds [ACK] Seq=1586 Ack=8181 Win=17520 
Len=1460
     13 0.006026    192.168.6.93          192.168.6.14          TCP 
[Continuation to #11] 1118 > microsoft-ds [PSH, ACK] Seq=3046 Ack=8181 
Win=17520 Len=1428
     14 0.008359    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8181 Ack=3046 Win=10220 Len=0
     15 0.008799    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     16 0.008900    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     17 0.008927    192.168.6.93          192.168.6.14          TCP 
[Continuation to #16] 1118 > microsoft-ds [ACK] Seq=5934 Ack=8232 Win=17469 
Len=1460
     18 0.008948    192.168.6.93          192.168.6.14          TCP 
[Continuation to #16] 1118 > microsoft-ds [PSH, ACK] Seq=7394 Ack=8232 
Win=17469 Len=1428
     19 0.011226    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8232 Ack=7394 Win=10220 Len=0
     20 0.011770    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     21 0.011891    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     22 0.011919    192.168.6.93          192.168.6.14          TCP 
[Continuation to #21] 1118 > microsoft-ds [ACK] Seq=10282 Ack=8283 Win=17418 
Len=1460
     23 0.011941    192.168.6.93          192.168.6.14          TCP 
[Continuation to #21] 1118 > microsoft-ds [PSH, ACK] Seq=11742 Ack=8283 
Win=17418 Len=1428
     24 0.014255    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8283 Ack=11742 Win=10220 Len=0
     25 0.014799    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     26 0.015047    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     27 0.015103    192.168.6.93          192.168.6.14          TCP 
[Continuation to #26] 1118 > microsoft-ds [ACK] Seq=14630 Ack=8334 Win=17367 
Len=1460
     28 0.015138    192.168.6.93          192.168.6.14          TCP 
[Continuation to #26] 1118 > microsoft-ds [PSH, ACK] Seq=16090 Ack=8334 
Win=17367 Len=1428
     29 0.017736    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8334 Ack=16090 Win=10220 Len=0
     30 0.018308    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     31 0.018514    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     32 0.018562    192.168.6.93          192.168.6.14          TCP 
[Continuation to #31] 1118 > microsoft-ds [ACK] Seq=18978 Ack=8385 Win=17316 
Len=1460
     33 0.018593    192.168.6.93          192.168.6.14          TCP 
[Continuation to #31] 1118 > microsoft-ds [PSH, ACK] Seq=20438 Ack=8385 
Win=17316 Len=1428
     34 0.020794    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8385 Ack=20438 Win=10220 Len=0
     35 0.021377    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     36 0.021552    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     37 0.021632    192.168.6.93          192.168.6.14          TCP 
[Continuation to #36] 1118 > microsoft-ds [ACK] Seq=23326 Ack=8436 Win=17265 
Len=1460
     38 0.021667    192.168.6.93          192.168.6.14          TCP 
[Continuation to #36] 1118 > microsoft-ds [PSH, ACK] Seq=24786 Ack=8436 
Win=17265 Len=1428
     39 0.023851    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8436 Ack=24786 Win=10220 Len=0
     40 0.024424    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     41 0.024684    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     42 0.024740    192.168.6.93          192.168.6.14          TCP 
[Continuation to #41] 1118 > microsoft-ds [ACK] Seq=27674 Ack=8487 Win=17214 
Len=1460
     43 0.024771    192.168.6.93          192.168.6.14          TCP 
[Continuation to #41] 1118 > microsoft-ds [PSH, ACK] Seq=29134 Ack=8487 
Win=17214 Len=1428
     44 0.027545    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8487 Ack=29134 Win=10220 Len=0
     45 0.028159    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes
     46 0.028980    192.168.6.93          192.168.6.14          DCERPC 
Request: call_id: 1742 opnum: 53 ctx_id: 0
     47 0.029041    192.168.6.93          192.168.6.14          TCP 
[Continuation to #46] 1118 > microsoft-ds [ACK] Seq=32022 Ack=8538 Win=17163 
Len=1460
     48 0.029072    192.168.6.93          192.168.6.14          TCP 
[Continuation to #46] 1118 > microsoft-ds [PSH, ACK] Seq=33482 Ack=8538 
Win=17163 Len=1428
     49 0.031447    192.168.6.14          192.168.6.93          TCP 
microsoft-ds > 1118 [ACK] Seq=8538 Ack=33482 Win=10220 Len=0
     50 0.032180    192.168.6.14          192.168.6.93          SMB 
Write AndX Response, FID: 0x713f, 4280 bytes

Something is still rotten in denmark............


--
David C. Rankin, J.D., P.E.
RANKIN LAW FIRM, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankinlawfirm.com
-- 



More information about the samba mailing list