spoolss back connections to client

Tom Vandepoel tom.vandepoel at be.ubizen.com
Tue Jun 11 02:18:02 GMT 2002

Since we've switched to spoolss printing (samba 2.2.4) it seems that the
server is always trying to connect to the client. 

[2002/06/11 10:52:41, 3] lib/util_sock.c:open_socket_out(843)
  Connecting to at port 445
[2002/06/11 10:52:41, 2] lib/util_sock.c:open_socket_out(871)
  error connecting to (Connection refused)
[2002/06/11 10:52:41, 3] lib/util_sock.c:open_socket_out(843)
  Connecting to at port 139

I've traced this back in the source to the "spoolss_connect_to_client"
call in rpc_server/srv_spoolss_nt.c. It seems this is used to reply back
to the client with printing info.

However, in our environment, such connections typically fail, as we
disable the "Server" service on NT/W2K clients as much as possible. In
those cases, printing still works fine, so I'm starting to wonder if
these back connections are absolutely needed. They are especially
annoying when the back connection is made to a firewalled client; it
slows down response of the print server enormously (the server waits
until the back connection times out).

So, I was thinking; is there an smb.conf option (or could it be
implemented) to disable these back connections? What would the impact be
if I modified the src_spoolss_replyopenprinter() routine to always
return false? Would that break anything?



More information about the samba-technical mailing list