On Wed, 2004-03-24 at 04:09, Paul Raines wrote: > Printing to a samba print share from a client that is firewalled/ > masqueraded is painfully slow. Seems the protocol requires the samba > server to make an initiating connection back to the SMB server on the > client which will of course fail on a firewalled/masqueraded client. > > The problem is that the a print job hangs till this operation times out > causing printing to take several minutes for users. Is there anyway to > decrease this timeout in samba? I have seen suggestions to use 'disable > spoolss' but this would cause more problems since that also disables > downloading of print drivers.
Welcome to the wonderful world of SPOOLSS printing. The issue is that a print server providing SPOOLSS is expected to make a *reverse* connection, from the print server, to the print client. This is not some part of the same TCP/IP socket, but a brand new, separate connection. No firewall knows that this particular connection is 'special', hence your results. More interestingly, MS is going to drop a default firewall on XP SP2. I wonder what it will do when it encounters this problem. Maybe MS has a more sane protocol now... Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
signature.asc
Description: This is a digitally signed message part
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
