[Samba] Unreliable Printing -- Samba To Win 2003 Printer

[Joseph Carri]

Hi,

I have installed Samba 2.2.6 on a SCO Openserver 5.0.7 System connected in a 
WAN.  The WAN has includes three networks (192.168.1.0, 192.68.11.0, & 
192.168.21.0) connected by ISDN leased lines and CISCO 805 routers.  I have no 
problem with the network, and all Windows users as well as (telnet) UNIX users 
have been using the setup for several months.

I need to print from the UNIX machine on 192.168.1.0 to a printer connected to 
a W2003 server on 192.168.11.0  I have set up Samba with smbprint.sysv and 
have none of the usual problems.  

The hassle I have run into is this.  When I give a print from the UNIX 
machine, some of the time it prints fine on the target printer.  Sometimes, 
however, nothing gets printed, and the target machines spooler does not even 
get the print file.
***************************************************************************
When a document prints correctly the arguments (passed by lp -d jumbo -ob 
filename) to smbrpint.sysv are:

Arguments = jumbo-37777 root  1  b /SPARE/APPLICATION/LOCATIONS/invt/mkt/x 

And the smbclient message (I have redirected output to a log file) is:

added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0
Domain=[DOMAIN] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2]
smb: \> CR/LF<->LF and print text translation now on
smb: \> putting file - as stdin-27268 (14.1 kb/s) (average 14.1 kb/s)
****************************************************************************

When a document fails to print, smbclient produces the arguments passed to 
smbprint.sysv are:

Arguments = jumbo-38110 root  1  
b /SPARE/APPLICATION/LOCATIONS/invt/mkt/1S20050213455463

Output from smbclient:

added interface ip=192.168.1.122 bcast=192.168.1.255 nmask=255.255.255.0
session setup failed: Call timed out: server did not respond after 20000 
milliseconds
*****************************************************************************
My reasoning so far is this:

1.	Since I can print half the time, there is nothing wrong with the 
networking or name resolution.

2.	Since I can print some of the time SMB printing is set up correctly.

What could cause the session setup to fail intermittently?  Can anyone suggest 
possible causes and remedies please?

Rgds,

Joseph Carri