[Samba] Print server communications back to the client during
novosirj at umdnj.edu
Mon Oct 13 17:39:30 GMT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Jeremy Allison wrote:
> On Mon, Oct 13, 2008 at 11:57:45AM -0400, Gerald (Jerry) Carter wrote:
>> -----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.
> Like the man said, it's Microsoft's doing :-). No, we don't have
> a separate timeout in spoolss_connect_to_client()
> (rpc_server/srv_spoolss_nt.c) but we could add one.
How does this actually work in the case of Samba? Does the Samba server
attempt to contact the NT machine, and is there a benefit to allowing
this to happen?
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II
|$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the samba