Taylor, Marc
2008-Oct-13 15:44 UTC
[Samba] Print server communications back to the client during printing
Hello All, I was wondering if anyone knows why a print server needs to talk back on the submitting client's ports 139 or 445? We are running Samba and we have pretty heavy firewall restrictions on our clients and we have noticed that interacting with the print server can seem to have lags in responses (job submission, print options, queue config, etc). Using the logging feature of the windows firewall we noticed the print server trying to talk back to the client's ports mentioned above. We also noticed that our Win2k3 server does the same thing and it isn't obvious as to why. Besides punching holes in the firewall is there a feature that can be turned off so that this doesn't happen, particularly in Samba (3.0.28)? Sorry to show my ignorance of this sort of thing but I am not sure how to phrase a Google query to get to the bottom of this. Many thanks. Marc Taylor
Gerald (Jerry) Carter
2008-Oct-13 15:57 UTC
[Samba] Print server communications back to the client during printing
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Taylor, Marc wrote:> Hello All, > > I was wondering if anyone knows why a print server needs to talk back on > the submitting client's ports 139 or 445?It's Microsoft's async print change notification protocol. Jeremy had talked about adding a separate timetou for the back channel connect, but I don't remember if this was ever done. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI82/4IR7qMdg1EfYRAg8tAKDI3xZ9+9ydqksP5kIJO6Te8TxnRwCdEiD2 3l/1K+Ebt95hBYZf0V6z7mk=XIcK -----END PGP SIGNATURE-----