Cabbar Duzayak
2005-Sep-05 07:45 UTC
[Samba] Samba Printing Extremely Slow from Windows XP
Hi, I have setup samba server on my linux box (Fedora Core 4 with latest samba, just updated via RHN) and has configured file sharing via samba for this server and connecting to it from my windows xp box. So far, everything works fine and it is very fast. Then, I configured a printer, and shared it via samba. And, I can see+connect to it from Windows XP and can even print. But, everything related to printing is extreemeeely slow on Windows XP, i.e. open notepad -> File Menu->Print, and at that point notepad just freezes for couple of minutes, and then brings the printer dialog... Send a print out, it just freezes for a while, then prints out fine. Below is the log file I am getting from Samba, and for some reason it tries to connect to the samba server on Windows XP??? Have no idea what this means, and how I can fix this. Can you please provide any suggestions? Thanks a ton in advance... Log from samba: [2005/09/05 00:37:12, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:445 [2005/09/05 00:37:29, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:139 [2005/09/05 00:37:29, 1] libsmb/cliconnect.c:cli_connect(1330) Error connecting to 192.168.0.3 (Operation already in progress) [2005/09/05 00:37:29, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2 606) spoolss_connect_to_client: unable to connect to SMB server on machine MYMACHINENAME. Error was : SUCCESS - 0. [2005/09/05 00:37:47, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:445 [2005/09/05 00:38:04, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:139 [2005/09/05 00:38:04, 1] libsmb/cliconnect.c:cli_connect(1330) Error connecting to 192.168.0.3 (Operation already in progress) [2005/09/05 00:38:04, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2 606) spoolss_connect_to_client: unable to connect to SMB server on machine MYMACHINENAME. Error was : SUCCESS - 0. [2005/09/05 00:38:30, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:445 [2005/09/05 00:38:48, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:139 [2005/09/05 00:38:48, 1] libsmb/cliconnect.c:cli_connect(1330) Error connecting to 192.168.0.3 (Operation already in progress) [2005/09/05 00:38:48, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2606) spoolss_connect_to_client: unable to connect to SMB server on machine MYMACHINENAME. Error was : SUCCESS - 0. [2005/09/05 00:39:05, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:445 [2005/09/05 00:39:23, 1] lib/util_sock.c:open_socket_out(774) timeout connecting to 192.168.0.3:139 [2005/09/05 00:39:23, 1] libsmb/cliconnect.c:cli_connect(1330) Error connecting to 192.168.0.3 (Operation already in progress) [2005/09/05 00:39:23, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2606) spoolss_connect_to_client: unable to connect to SMB server on machine MYMACHINENAME. Error was : SUCCESS - 0.
Cabbar Duzayak
2005-Sep-05 08:44 UTC
[Samba] Re: Samba Printing Extremely Slow from Windows XP
One clarification for the log: 192.168.0.3 is the IP address of the Windows XP client that is trying to connect to the samba server on linux. And, MYMACHINENAME is the hostname of that same Windows XP machine. And, this log is from MYMACHINENAME.log file, which is in samba log dir. Once again, any help is appreciated. TIA... On 9/5/05, Cabbar Duzayak <cabbar@gmail.com> wrote:> Hi, > > I have setup samba server on my linux box (Fedora Core 4 with latest > samba, just updated via RHN) and has configured file sharing via samba > for this server and connecting to it from my windows xp box. So far, > everything works fine and it is very fast. > > Then, I configured a printer, and shared it via samba. And, I can > see+connect to it from Windows XP and can even print. But, everything > related to printing is extreemeeely slow on Windows XP, i.e. open > notepad -> File Menu->Print, and at that point notepad just freezes > for couple of minutes, and then brings the printer dialog... Send a > print out, it just freezes for a while, then prints out fine. > > Below is the log file I am getting from Samba, and for some reason it > tries to connect to the samba server on Windows XP??? Have no idea > what this means, and how I can fix this. Can you please provide any > suggestions? > > Thanks a ton in advance... > > Log from samba: > > [2005/09/05 00:37:12, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:445 > [2005/09/05 00:37:29, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:139 > [2005/09/05 00:37:29, 1] libsmb/cliconnect.c:cli_connect(1330) > Error connecting to 192.168.0.3 (Operation already in progress) > [2005/09/05 00:37:29, 0] > rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2 606) > spoolss_connect_to_client: unable to connect to SMB server on > machine MYMACHINENAME. Error was : SUCCESS - 0. > [2005/09/05 00:37:47, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:445 > [2005/09/05 00:38:04, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:139 > [2005/09/05 00:38:04, 1] libsmb/cliconnect.c:cli_connect(1330) > Error connecting to 192.168.0.3 (Operation already in progress) > [2005/09/05 00:38:04, 0] > rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2 606) > spoolss_connect_to_client: unable to connect to SMB server on > machine MYMACHINENAME. Error was : SUCCESS - 0. > [2005/09/05 00:38:30, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:445 > [2005/09/05 00:38:48, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:139 > [2005/09/05 00:38:48, 1] libsmb/cliconnect.c:cli_connect(1330) > Error connecting to 192.168.0.3 (Operation already in progress) > [2005/09/05 00:38:48, 0] > rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2606) > spoolss_connect_to_client: unable to connect to SMB server on > machine MYMACHINENAME. Error was : SUCCESS - 0. > [2005/09/05 00:39:05, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:445 > [2005/09/05 00:39:23, 1] lib/util_sock.c:open_socket_out(774) > timeout connecting to 192.168.0.3:139 > [2005/09/05 00:39:23, 1] libsmb/cliconnect.c:cli_connect(1330) > Error connecting to 192.168.0.3 (Operation already in progress) > [2005/09/05 00:39:23, 0] > rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2606) > spoolss_connect_to_client: unable to connect to SMB server on > machine MYMACHINENAME. Error was : SUCCESS - 0. >
Louis van Belle
2005-Sep-05 09:17 UTC
[Samba] Re: Samba Printing Extremely Slow from Windows XP
Hi, I also noticed this, i have this problem with some of the printers for example, i dont have this with the folowing printers. HP 4100 4200 4300 4350 9000 3380 i DO have this problem with HP 9065 MFP, Canon i865, HP 8050. mayby this help someone. btw, i use cups / Raw printen, i have a point en print setup. I use the windows printer driver supplied bij the provider and the updated versions. Louis>-----Oorspronkelijk bericht----- >Van: samba-bounces+louis=van-belle.nl@lists.samba.org >[mailto:samba-bounces+louis=van-belle.nl@lists.samba.org] >Namens Cabbar Duzayak >Verzonden: maandag 5 september 2005 10:45 >Aan: samba@lists.samba.org >Onderwerp: [Samba] Re: Samba Printing Extremely Slow from Windows XP > >One clarification for the log: > >192.168.0.3 is the IP address of the Windows XP client that is trying >to connect to the samba server on linux. And, MYMACHINENAME is the >hostname of that same Windows XP machine. And, this log is from >MYMACHINENAME.log file, which is in samba log dir. > >Once again, any help is appreciated. >TIA... > >On 9/5/05, Cabbar Duzayak <cabbar@gmail.com> wrote: >> Hi, >> >> I have setup samba server on my linux box (Fedora Core 4 with latest >> samba, just updated via RHN) and has configured file sharing >via samba >> for this server and connecting to it from my windows xp box. So far, >> everything works fine and it is very fast. >> >> Then, I configured a printer, and shared it via samba. And, I can >> see+connect to it from Windows XP and can even print. But, everything >> related to printing is extreemeeely slow on Windows XP, i.e. open >> notepad -> File Menu->Print, and at that point notepad just freezes >> for couple of minutes, and then brings the printer dialog... Send a >> print out, it just freezes for a while, then prints out fine. >> >> Below is the log file I am getting from Samba, and for some reason it >> tries to connect to the samba server on Windows XP??? Have no idea >> what this means, and how I can fix this. Can you please provide any >> suggestions? >> >> Thanks a ton in advance... >> >> Log from samba: >> >> [2005/09/05 00:37:12, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:445 >> [2005/09/05 00:37:29, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:139 >> [2005/09/05 00:37:29, 1] libsmb/cliconnect.c:cli_connect(1330) >> Error connecting to 192.168.0.3 (Operation already in progress) >> [2005/09/05 00:37:29, 0] >> rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2 606) >> spoolss_connect_to_client: unable to connect to SMB server on >> machine MYMACHINENAME. Error was : SUCCESS - 0. >> [2005/09/05 00:37:47, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:445 >> [2005/09/05 00:38:04, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:139 >> [2005/09/05 00:38:04, 1] libsmb/cliconnect.c:cli_connect(1330) >> Error connecting to 192.168.0.3 (Operation already in progress) >> [2005/09/05 00:38:04, 0] >> rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2 606) >> spoolss_connect_to_client: unable to connect to SMB server on >> machine MYMACHINENAME. Error was : SUCCESS - 0. >> [2005/09/05 00:38:30, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:445 >> [2005/09/05 00:38:48, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:139 >> [2005/09/05 00:38:48, 1] libsmb/cliconnect.c:cli_connect(1330) >> Error connecting to 192.168.0.3 (Operation already in progress) >> [2005/09/05 00:38:48, 0] >> rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2606) >> spoolss_connect_to_client: unable to connect to SMB server on >> machine MYMACHINENAME. Error was : SUCCESS - 0. >> [2005/09/05 00:39:05, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:445 >> [2005/09/05 00:39:23, 1] lib/util_sock.c:open_socket_out(774) >> timeout connecting to 192.168.0.3:139 >> [2005/09/05 00:39:23, 1] libsmb/cliconnect.c:cli_connect(1330) >> Error connecting to 192.168.0.3 (Operation already in progress) >> [2005/09/05 00:39:23, 0] >> rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client(2606) >> spoolss_connect_to_client: unable to connect to SMB server on >> machine MYMACHINENAME. Error was : SUCCESS - 0. >> >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba >
----- Original Message ----- From: "Cabbar Duzayak" <cabbar@gmail.com>> Hi, > > I have setup samba server on my linux box (Fedora Core 4 with latest > samba, just updated via RHN) and has configured file sharing via samba > for this server and connecting to it from my windows xp box. So far, > everything works fine and it is very fast. > > Then, I configured a printer, and shared it via samba. And, I can > see+connect to it from Windows XP and can even print. But, everything > related to printing is extreemeeely slow on Windows XP, i.e. open > notepad -> File Menu->Print, and at that point notepad just freezes > for couple of minutes, and then brings the printer dialog... Send a > print out, it just freezes for a while, then prints out fine. > > Below is the log file I am getting from Samba, and for some reason it > tries to connect to the samba server on Windows XP??? Have no idea > what this means, and how I can fix this. Can you please provide any > suggestions? >Cabbar, 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. That pretty much eliminates the problem being the latest xp patch since I connect with a laptop on both systems and I can print fine under 3.0.13, but I have major slowness with printing under 3.0.20. Ethereal shows some looping that seems to be caused by DCERPC error in the communicatons. Since Bartlett did his thesis on DCERPC, maybe he can shed some light on the issue. -- 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 --
On Tuesday 06 September 2005 11:16 am, david rankin wrote:> after moving to 3.0.20a. I have 3.0.20a running3.0.20a?
david rankin wrote:> ----- Original Message ----- From: "Cabbar Duzayak" <cabbar@gmail.com> > > >> Hi, >> >> I have setup samba server on my linux box (Fedora Core 4 with latest >> samba, just updated via RHN) and has configured file sharing via samba >> for this server and connecting to it from my windows xp box. So far, >> everything works fine and it is very fast. >> >> Then, I configured a printer, and shared it via samba. And, I can >> see+connect to it from Windows XP and can even print. But, everything >> related to printing is extreemeeely slow on Windows XP, i.e. open >> notepad -> File Menu->Print, and at that point notepad just freezes >> for couple of minutes, and then brings the printer dialog... Send a >> print out, it just freezes for a while, then prints out fine. >> >> Below is the log file I am getting from Samba, and for some reason it >> tries to connect to the samba server on Windows XP??? Have no idea >> what this means, and how I can fix this. Can you please provide any >> suggestions? >> > > Cabbar, > > 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 Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk@crc.dk Homepage: http://www.crc.dk
Gerald (Jerry) Carter
2005-Sep-07 16:15 UTC
[Samba] Samba Printing Extremely Slow from Windows XP
-----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" cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDHxIOIR7qMdg1EfYRAjKLAJ9vNAdUPcsp8lLdplgVtXFrr4BjFACcDK3R 9MvEF83/pnUvOyx1JE/OsfE=cuRc -----END PGP SIGNATURE-----
Jerry Carter wrote: "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." We use this workaround but it's pretty annoying as if you change the driver or add another printer (the latter happens often) you have to go into the reg and fix it. Is it known which XPSP2 patch caused this and whether a patch is due to resolve it? thanks Mark -- This E-mail contains legally privileged and confidential information intended only for the individual or entity named in the message. If the reader of this message is not the intended recipient, or the agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited. If this communication was received in error, please notify us by reply E-mail and delete the original message. --------------------------------------------------------------------
----- Original Message ----- From: "Gerald (Jerry) Carter" <jerry@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 --
On Tuesday 06 September 2005 17:16, david rankin wrote:> ----- Original Message ----- > From: "Cabbar Duzayak" <cabbar@gmail.com> >I also have a very similar, but perhaps not identical problem. The samba server is on SuSE 9.3 (but the same thing has happened on all SuSEes since 7.0). I have one printer, viz hp psc950 and four DOS boxes in the net. 1 Windows 98 2 Windows 2000 3 Windows XP (home) 4 Windows XP (professional) With the exception of 2, all boxes print almost immediately. But the Windows 2000 takes up to 30 min (minutes not seconds) to print ten pages of a simple Word document. Starting to print the first page can take up to 3 minutes. Needless to say, all boxes are configured in a very similar way. Malcoln Agnew> > Hi, > > > > I have setup samba server on my linux box (Fedora Core 4 with latest > > samba, just updated via RHN) and has configured file sharing via samba > > for this server and connecting to it from my windows xp box. So far, > > everything works fine and it is very fast. > > > > Then, I configured a printer, and shared it via samba. And, I can > > see+connect to it from Windows XP and can even print. But, everything > > related to printing is extreemeeely slow on Windows XP, i.e. open > > notepad -> File Menu->Print, and at that point notepad just freezes > > for couple of minutes, and then brings the printer dialog... Send a > > print out, it just freezes for a while, then prints out fine. > > > > Below is the log file I am getting from Samba, and for some reason it > > tries to connect to the samba server on Windows XP??? Have no idea > > what this means, and how I can fix this. Can you please provide any > > suggestions? > > Cabbar, > > 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. That pretty much eliminates the problem > being the latest xp patch since I connect with a laptop on both systems and > I can print fine under 3.0.13, but I have major slowness with printing > under 3.0.20. Ethereal shows some looping that seems to be caused by DCERPC > error in the communicatons. Since Bartlett did his thesis on DCERPC, maybe > he can shed some light on the issue. > > > -- > 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 > --