Greetings, We use a dedicated samba-3.3.12+cups-1.3.11 on debian lenny to serve printing (with point and print) to windows clients. We're getting complaints that some clients (win7, vista, XP) have to wait an awful long time from when they hit 'print' to when the job starts coming out of the printer. Other clients (win7, vista, XP) print right away. I can tail the cups log and see that as soon as it gets the job, it's printed immediately. The issue is cups does not log the job until a few minutes/hours after the problem clients hit print. I have a problem client to try and isolate the problem. The only difference I can see (for now) is that samba logs this when the problem client prints: [2010/11/15 16:23:34, 1] lib/util_sock.c:open_socket_out(1424) timeout connecting to 192.168.76.10:445 [2010/11/15 16:23:42, 1] lib/util_sock.c:open_socket_out(1424) timeout connecting to 192.168.76.10:139 [2010/11/15 16:23:42, 1] libsmb/cliconnect.c:cli_start_connection(1657) cli_start_connection: failed to connect to OA-C126-DGC<20> (192.168.76.10). Error NT_STATUS_ACCESS_DENIED [2010/11/15 16:23:51, 1] lib/util_sock.c:open_socket_out(1424) timeout connecting to 192.168.76.10:445 [2010/11/15 16:24:00, 1] lib/util_sock.c:open_socket_out(1424) timeout connecting to 192.168.76.10:139 [2010/11/15 16:24:00, 1] libsmb/cliconnect.c:cli_start_connection(1657) cli_start_connection: failed to connect to OA-C126-DGC<20> (192.168.76.10). Error NT_STATUS_ACCESS_DENIED [2010/11/15 16:24:09, 1] lib/util_sock.c:open_socket_out(1424) timeout connecting to 192.168.76.10:445 ... A client that prints right away does not get the error above. Why is samba trying to initiate a connection to this client? Could this be the cause of their delay? thanks and much appreciated, Ryan
Ok, it looks like this was the cause of the delay. As soon as I disable windows firewall on this client, the errors disappear and jobs start printing immediately. We have bring your own laptops (with their own image) here at the college. I suspect this is the same cause of their delays. Could someone please shed some light what samba uses this connection for? On 10-11-15 04:50 PM, Ryan Suarez wrote:> Greetings, > > We use a dedicated samba-3.3.12+cups-1.3.11 on debian lenny to serve > printing (with point and print) to windows clients. We're getting > complaints that some clients (win7, vista, XP) have to wait an awful > long time from when they hit 'print' to when the job starts coming out > of the printer. Other clients (win7, vista, XP) print right away. > > I can tail the cups log and see that as soon as it gets the job, it's > printed immediately. The issue is cups does not log the job until a > few minutes/hours after the problem clients hit print. I have a > problem client to try and isolate the problem. The only difference I > can see (for now) is that samba logs this when the problem client prints: > > [2010/11/15 16:23:34, 1] lib/util_sock.c:open_socket_out(1424) > timeout connecting to 192.168.76.10:445 > [2010/11/15 16:23:42, 1] lib/util_sock.c:open_socket_out(1424) > timeout connecting to 192.168.76.10:139 > [2010/11/15 16:23:42, 1] libsmb/cliconnect.c:cli_start_connection(1657) > cli_start_connection: failed to connect to OA-C126-DGC<20> > (192.168.76.10). Error NT_STATUS_ACCESS_DENIED > [2010/11/15 16:23:51, 1] lib/util_sock.c:open_socket_out(1424) > timeout connecting to 192.168.76.10:445 > [2010/11/15 16:24:00, 1] lib/util_sock.c:open_socket_out(1424) > timeout connecting to 192.168.76.10:139 > [2010/11/15 16:24:00, 1] libsmb/cliconnect.c:cli_start_connection(1657) > cli_start_connection: failed to connect to OA-C126-DGC<20> > (192.168.76.10). Error NT_STATUS_ACCESS_DENIED > [2010/11/15 16:24:09, 1] lib/util_sock.c:open_socket_out(1424) > timeout connecting to 192.168.76.10:445 > ... > > A client that prints right away does not get the error above. Why is > samba trying to initiate a connection to this client? Could this be > the cause of their delay? > > thanks and much appreciated, > Ryan >
On Tue, Nov 16, 2010 at 01:27:43PM -0500, Ryan Suarez wrote:> Ok, it looks like this was the cause of the delay. As soon as I > disable windows firewall on this client, the errors disappear and > jobs start printing immediately. We have bring your own laptops > (with their own image) here at the college. I suspect this is the > same cause of their delays. > > Could someone please shed some light what samba uses this connection for?This is the insane Windows print spooler design, where the server connects back to the client to do change notify. Samba tries to do the same - look at spoolss_connect_to_client() in rpc_server/srv_spoolss_nt.c - maybe we should have an option to disable this. Jeremy.
Hi, just a short question, which version of samba are you using ? I try to get 3.5.6 to run with windows 7 64 bit and this is a tidious task for me :( cheers christoph On Tue, 16 Nov 2010, Jeremy Allison wrote:> On Tue, Nov 16, 2010 at 01:27:43PM -0500, Ryan Suarez wrote: >> Ok, it looks like this was the cause of the delay. As soon as I >> disable windows firewall on this client, the errors disappear and >> jobs start printing immediately. We have bring your own laptops >> (with their own image) here at the college. I suspect this is the >> same cause of their delays. >> >> Could someone please shed some light what samba uses this connection for? > > This is the insane Windows print spooler design, where the server > connects back to the client to do change notify. > > Samba tries to do the same - look at spoolss_connect_to_client() > in rpc_server/srv_spoolss_nt.c - maybe we should have an option > to disable this. > > Jeremy. > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >best regards ~christoph -- /* Christoph Beyer | Office: Building 2b / 23 *\ * DESY | Phone: 040-8998-2317 * * - IT - | Fax: 040-8998-4060 * \* 22603 Hamburg | http://www.desy.de */