[Samba] Java Application and Samba 3.0.1

[Jeffrey M. Hardy]

Hello all,

I am running Samba 3.0.1 and CUPS 1.1.19 on a production print server
and have a problem with a commercial java application.  This particular
app crashes immediately on a Windows client when opening the print
dialog if the default printer on that Windows client is a remote printer
on a Samba print server.  This problem exists for Windows XP, 2000, or
98 clients and has persisted at least back through Samba 2.2.8.  

However, the application will successfully bring up the dialog if the
default printer on the client is one of two things: 1) A local printer,
even if it is printing to a "custom" remote port which points to a queue
on the Samba server, or 2) Any queue on a Windows NT 4.0 print server. 
If the default is set to one of these two, the dialog will open and I
can even then select one of the "problem" printers on the Samba server
and print successfully.  The default can not be a Samba printer.

Here is what the application says for itself in a dump to a file on the
C drive:

##############################
##############################
[02/04/04 17:39:38 Eastern Standard Time]::Client Status [ConnId=0,
PID=856]
        >> ERROR: Abnormal termination, Error Code: C0000005
ACCESS_VIOLATION
                                                                                 
======================= STACK DUMP =======================
                                                                                 
Fault address:  672192C7 01:000582C7
Module: o:\orawin95\bin\UIW60.DLL
                                                                                 
System Information:
Operating System: Windows NT Version 5.1 Build 2600 Service Pack 1
Command line: o:\orawin95\bin\ifrun60  guainit
FORM/BLOCK/FIELD: GUAGMNU:KEY_BLOCK.NEXT_SELECTION
Last Trigger: KEY-PRINT - (Execution Suspended)
Msg: <NULL>
Last Builtin: PRINT - (Successfully Completed)
##############################
##############################


.... this is followed by a stack trace.  Nothing appears in a level 4
Samba log during this process.  In nearly all other areas, the print
server performs flawlessly.  These are standard drivers from the vendor,
in this case a range of HP models.  Has anyone seen behavior like this
with a java app or something similar?  If so, know of a good
workaround?  Is this a known bug/issue with Samba?



Thanks much.

-- 
Jeff Hardy
Systems Administrator
SUNY Potsdam
hardyjm at potsdam.edu