[Samba] print job name

Van Sickler, Jim vansickj-eodc at Kaman.com
Wed Sep 4 18:35:01 GMT 2002


For What It's Worth, from my setup:
 
Samba1 [Global] settings:
 
disable spoolss=yes
use client driver=yes
Win2k Port for Samba1's printers say \\Samba1\printername
<file://\\Samba1\printername> , Description=Lan Manager Printer Port
Document Name for listed print jobs:  "Remote Downlevel Document"
Job status refreshes automatically (Refreshing pops up next to printer name)
 
 
Samba2 [Global] settings:
 
disable spoolss = no
use client driver = yes or no, based on driver installibility
Win2k Port for Samba2's printers say Samba Printer Port, Description=Local
Port
Document Name for listed print jobs:  document name, related to application
Job status refreshes when printer icon is launched, must be refreshed
manually afterward
 
 
Results:  using Win2k spoolss support in samba will get you the document
names, but
you have to manually refresh the printer status to see how your jobs are
doing.
I'm using LPRng, raw printing to all printers (no ifhp, GhostScript, etc
filtering).  Win2k
clients mainly.  My Mita Ci1000 Fiery log shows this oddity:  win9x clients
provide both
the doc and sender info;  Win2k provides only the doc name...
the user is always Unknown.
 
Will this help you keep the samba print servers?  I don't know.
Load the latest 2.2.6pre snapshot and give it a go.  Try it with
a couple of clean Win2k workstations.  Clean as in NEVER had
printers installed on them.  Use one for the admin user,
and the other for the "normal" user.  Install the printer
drivers onto the samba box from the admin PC, then try
to install them on the "normal" PC.  Then try printing...
 
See what difference "use client driver=yes/no" makes.
"Yes" won't use the driver installed in samba's print$ share,
and "no" will.
 
I'm using the HP drivers (latest from HP, not the Win2k)
set up on the print$.  I don't have drivers for the Lexmark
Optra S 1250 installed in print$, but the Lexmark Universal
installer allows for installation to a remote printer.
 
Personally, if my Novell print servers were already paid for
and patched up to date, I'd keep them.  If the PC they're
on isn't up to the task, put them on a better system.  Like
the one(s) you're planning to use for samba....we had
file & print sharing for 200+ on a dual Pentium 90, and
they handled it just fine.  I can just imagine what the current
platforms are capable of...
 
I worked with NetWare up until 4.11, then "retired" from
the Air Force.  I've been working with NT4 servers since then,
and moved my printing over to samba (to replace a bunch of
standalone Win9x boxes this company was using for print
servers).  Bottom line?  I MISS NetWare!!!
 
Windows file sharing security management administration is
a PITA compared to NetWare's.  Novell print serving is still
the standard everyone else aspires to.
 
If your issue is with the NetWare client, I don't have any advice..
I don't know how the current client behaves.  I really liked
Client32, but that was long before Win2k...it was pretty,
stable, and had a LOT of functionality built in.  We don't have
anything like that for samba yet...
 
  Samba's done okay for me as a print server, but it is still evolving.
I'm far from happy with it in it's current state.  The fact that I "might"
have yet to configure it correctly is a very strong possibility.  The
issue is, there are a thousand ways to do samba right, and a million
ways to do it wrong...
 
The fact the Microsoft continues to "improve" their software
and networking subsystems makes the job of the samba
(and LPRng/CUPS) folks that much harder.  Which means
that it makes OUR job that much harder, too.
 
Enough rambling...
 
Jim
 
 

-----Original Message-----
From: Tony McGrew [mailto:tony at multicam.com]
Sent: Friday, August 30, 2002 2:56 PM
To: samba list
Subject: [Samba] print job name


I have not been able to find a fix for the print job name coming out as
remote downlevel document from W2k clients.  I know this is a microsoft
issue but it isn't going to be addressed by them.  Win98 clients work fine,
but I have 40 w2k clients.  The system is RH7.3 printing with cups.  samba
2.2.5 with cups support compiled in.  If I can't find a fix or patch or
other solution by next friday management will require me to move the print
servers back to Novell and I am unlikely to get another chance soon. So my
question is Should I dump cups and try to go back to lpr or wait another 6
months and try again.

Tony McGrew
www.multicam.com 

 

-------------- next part --------------
HTML attachment scrubbed and removed


More information about the samba mailing list