Hi there, I have set-up cups with samba integrate everything working fine , all the printers are sharing in the network , mac clients works fine, Bonjour protocol is very fast im using ubuntu 12.04 64bit with samba 3.6.3-2ubuntu2.8 and cups 1.5.3-0ubuntu8 the only issue is for the any windows(xp/vista/7) clients, when I tried to search the printer from "panel control">"add a device" it will take 20-40 sec , Is there config to make more fast the print sharing ? Faster I mean when I search on windows machine it will come out in 1-5 sec . I don't care about sharing file and the printer are just sharing in local in different vlans. I have tried some optimization the config without any relevant result. From the default config smb.conf : I have change few things : socket options = IPTOS_LOWDELAY TCP_NODELAY name resolve order = bcast host that I'm not sure if this setting have need to be change : disable netbios = No and also I'm not running a wins server , do you think is better to run ? it will make faster the discovery device ? update: yes if I install on windows, "bonjour print services for windows " , it's working like on mac the printer come out immediately, but I want zero config from the windows client . thanks a lot
Thanks for the report Claudio. (In reply to comment #0) > Hi there, > I have set-up cups with samba integrate everything working fine , all the > printers are sharing in the network , > mac clients works fine, Bonjour protocol is very fast > > im using ubuntu 12.04 64bit with samba 3.6.3-2ubuntu2.8 and cups > 1.5.3-0ubuntu8 > > the only issue is for the any windows(xp/vista/7) clients, when I tried to > search the printer from "panel control">"add a device" it will take 20-40 sec , > > Is there config to make more fast the print sharing ? Faster I mean when I > search on windows machine it will come out in 1-5 sec . https://wiki.samba.org/index.php/Capture_Packets Please provide a network trace and debug logs, captured across the full "panel control">"add a device" delay. You can email the trace to me privately if you have privacy concerns. If your Samba server is joined to an Active Directory domain, then publishing the printer in AD (via net ads printer publish) should allow for clients to locate shared printers much quicker.
(In reply to comment #1) > Thanks for the report Claudio. > > (In reply to comment #0) > > Hi there, > > I have set-up cups with samba integrate everything working fine , all the > > printers are sharing in the network , > > mac clients works fine, Bonjour protocol is very fast > > > > im using ubuntu 12.04 64bit with samba 3.6.3-2ubuntu2.8 and cups > > 1.5.3-0ubuntu8 > > > > the only issue is for the any windows(xp/vista/7) clients, when I tried to > > search the printer from "panel control">"add a device" it will take 20-40 sec , > > > > Is there config to make more fast the print sharing ? Faster I mean when I > > search on windows machine it will come out in 1-5 sec . > > > https://wiki.samba.org/index.php/Capture_Packets > > Please provide a network trace and debug logs, captured across the full "panel > control">"add a device" delay. You can email the trace to me privately if you > have privacy concerns. > > If your Samba server is joined to an Active Directory domain, then publishing > the printer in AD (via net ads printer publish) should allow for clients to > locate shared printers much quicker. thanks David , I have sent you email with all info . let me know if you need more about my config.
(In reply to comment #2) .... > > thanks David , > I have sent you email with all info . > let me know if you need more about my config. Thanks for providing the requested details. Looking at the trace, there are couple of significant stalls in network traffic. The first occurs at the 5 second mark, after the client and server exchange login, anonymous authentication, then domain and server enumeration requests and responses. The stall lasts ~12 seconds, after which the client disconnects from the IPC$ pipe share and logs off. The second occurs at ~17 seconds, immediately following the log-off. There appears to be no activity for ~10 seconds, after which the client reconnects to IPC$ and issues a share enumeration request. More analysis required...
(In reply to comment #3) > (In reply to comment #2) > .... > > > > thanks David , > > I have sent you email with all info . > > let me know if you need more about my config. > > Thanks for providing the requested details. > Looking at the trace, there are couple of significant stalls in network > traffic. > > The first occurs at the 5 second mark, after the client and server exchange > login, anonymous authentication, then domain and server enumeration requests > and responses. The stall lasts ~12 seconds, after which the client disconnects > from the IPC$ pipe share and logs off. > > The second occurs at ~17 seconds, immediately following the log-off. There > appears to be no activity for ~10 seconds, after which the client reconnects to > IPC$ and issues a share enumeration request. > > More analysis required... thanks david for your answer, what I should check more ? do you need more info ? and what do you think I can improve ?
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > .... > > > > > > thanks David , > > > I have sent you email with all info . > > > let me know if you need more about my config. > > > > Thanks for providing the requested details. > > Looking at the trace, there are couple of significant stalls in network > > traffic. > > > > The first occurs at the 5 second mark, after the client and server exchange > > login, anonymous authentication, then domain and server enumeration requests > > and responses. The stall lasts ~12 seconds, after which the client disconnects > > from the IPC$ pipe share and logs off. > > > > The second occurs at ~17 seconds, immediately following the log-off. There > > appears to be no activity for ~10 seconds, after which the client reconnects to > > IPC$ and issues a share enumeration request. > > > > More analysis required... > > thanks david for your answer, > what I should check more ? > do you need more info ? > and what do you think I can improve ? Could you please provide the same trace captured against a Windows printer server. Then I can compare the wire traffic between the two.
Maybe spoolssd will help.
no progress here, I also don't see a significant delay, closing.