Re: [Samba] windows 7 64 bit xerox print drivers
I would like to respond to my own question ... yes ... one year later :-)
My answer to this problem is * don't use Samba * to solve this type of
problem.
Instead I created a ".dat" file (using printui.dll) for each printer I
wanted to install, scripted the creation of an LPR port (
objWMIService.Get("Win32_TCPIPPrinterPort") and install print drivers using
printui.dll. I'm running LPD on the cups server.
Works like a charm. No hassles joining this server to the domain, no wonky
error messages, 500 desktops up and running at login, it just works.
I'm posting this here because I'm genuinely curious if there has been any
large scale success with Samba, Win 7 and Xerox (or other) 64 bit print
drivers.
Greg
On Mon, Aug 9, 2010 at 5:47 PM, Greg Saunders wrote:
> Samba 3.4.7
> Ubuntu 10.04
>
> Has anyone out there got Xerox 64 bit drivers working in a point and print
> samba set up? And if so, which Xerox drivers? And which method of driver
> installation?
>
> I'm at a complete loss. We currently have an environment with 500 +
> desktops and a couple dozen Xerox workgroup docucolor MFPs that are running
> fine now with XP clients and a Samba print server. We're moving to Win 7 64
> bit clients over the next couple of months and this is going to be a huge
> stumbling block.
>
> Several months ago I posted a problem I was having installing 64 bit Xerox
> drivers into a shared samba queue. 32 bit drivers seem to be fine but the 64
> bit are a world of pain. There didn't seem to be any resolution at that time
> and hoping things may have changed in the last few months.
>
> I've had success with 64 bit HP drivers ... just not Xerox.
>
> When adding the 64 bit driver as an "additional driver" under the sharing
> tab of the queue of the samba server, it complains, "The specified location
> does not contain the driver for the requested processor
> architecture." It clearly is a 64 version, it will install locally.
>
> As far as "cupsaddsmb" is concerned ... it just doesn't seem to work with
> 64 bit ... unless I'm doing something wrong ... which is completely likely
> :)
>
> If anyone could shed some light on this, it would be immensely appreciated.
>
> Thanking you all in advance.
> Greg
>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] windows 7 64 bit xerox print drivers
Samba 3.4.7 Ubuntu 10.04 Has anyone out there got Xerox 64 bit drivers working in a point and print samba set up? And if so, which Xerox drivers? And which method of driver installation? I'm at a complete loss. We currently have an environment with 500 + desktops and a couple dozen Xerox workgroup docucolor MFPs that are running fine now with XP clients and a Samba print server. We're moving to Win 7 64 bit clients over the next couple of months and this is going to be a huge stumbling block. Several months ago I posted a problem I was having installing 64 bit Xerox drivers into a shared samba queue. 32 bit drivers seem to be fine but the 64 bit are a world of pain. There didn't seem to be any resolution at that time and hoping things may have changed in the last few months. I've had success with 64 bit HP drivers ... just not Xerox. When adding the 64 bit driver as an "additional driver" under the sharing tab of the queue of the samba server, it complains, "The specified location does not contain the driver for the requested processor architecture." It clearly is a 64 version, it will install locally. As far as "cupsaddsmb" is concerned ... it just doesn't seem to work with 64 bit ... unless I'm doing something wrong ... which is completely likely :) If anyone could shed some light on this, it would be immensely appreciated. Thanking you all in advance. Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] windows 7 64 bit xerox print drivers
Samba 3.4.7 Ubuntu 10.04 Has anyone out there got Xerox 64 bit drivers working in a point and print samba set up? And if so, which Xerox drivers? And which method of driver installation? I'm at a complete loss. We currently have an environment with 500 + desktops and a couple dozen Xerox workgroup docucolor MFPs that are running fine now with XP clients and a Samba print server. We're moving to Win 7 64 bit clients over the next couple of months and this is going to be a huge stumbling block. Several months ago I posted a problem I was having installing 64 bit Xerox drivers into a shared samba queue. 32 bit drivers seem to be fine but the 64 bit are a world of pain. There didn't seem to be any resolution at that time and hoping things may have changed in the last few months. I've had success with 64 bit HP drivers ... just not Xerox. When adding the 64 bit driver as an "additional driver" under the sharing tab of the queue of the samba server, it complains, "The specified location does not contain the driver for the requested processor architecture." It clearly is a 64 version, it will install locally. As far as "cupsaddsmb" is concerned ... it just doesn't seem to work with 64 bit ... unless I'm doing something wrong ... which is completely likely :) If anyone could shed some light on this, it would be immensely appreciated. Thanking you all in advance. Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Windows 7 64-bit drivers
Hello All, I'm having trouble with 64 bit Xerox drivers on my Samba server. The below quote if from another thread which I have followed but on the client Win 7 64 bit machine, I get an error: "The specified location does not contain the driver for the Xerox WorkCentre 7675 rev2 PS for the requested processor architecture." Trying to add the driver from at 64 bit client first also fails with the same error. For sure the driver is x64, I can install the driver locally on the Win 7 64 client. I have HP 64 bit drivers installed, no problem ... any ideas? Thanks Greg We support 32bit and 64bit XP, Vista, and Windows7. We upload drivers from a windows client instead of using cupsaddsmb since we found this method solved alot of printing issues when we were using cupsaddsmb: http://samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id2627720 > With this method there are a few options to support both 32 and 64bit clients, based on how point and print works. > 1. Upload a driver from the Windows 32bit client's local driver store. When a 64bit client tries to connect, point and print does not find the appropriate driver on the samba server. Instead, it will attempt to find and install an appropriate driver with the correct filename from it's own local driver store or Windows Update. This is our preferred method since it's easier to manage. > 2. For cases where drivers for a specific printer model is not available in a clients local driver store then we upload both 32bit and 64bit drivers to the samba queue. First we upload 32bit then go into the driver properties, into the 'Sharing' tab, and click on 'Additional Drivers' to install 64bit drivers from a 64bit client. > Check out the Windows Point and Print Technical Overview for reference http://bit.ly/cGpqn8 > hope this helps, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] long delay accessing print properties on client
I've seen a proposed fix for this problem http://lists.samba.org/archive/samba/2005-September/110571.html and it has no influence on my installation. client workstations: XP Pro SP 2 number of clients: about 500 server O/S: ubuntu hardy 8.04 ha1 ~: uname -a Linux ha1 2.6.24-19-xen #1 SMP Wed Aug 20 21:08:51 UTC 2008 x86_64 GNU/Linux ha1 ~: dpkg -l samba* ||/ Name VersionDescription ii samba 3.0.28a-1ubunt a LanManager-like file and printer server fo ii samba-common 3.0.28a-1ubunt Samba common files used by both the server a I have some drivers that take 30 to 60 seconds to access the properties from the client; typically seem to be Xerox and a few HP Designjet drivers. I have other drivers, Ricoh as an example, that do not exhibit this behaviour and function properly. I have other installations with different server O/S (Open Suse 10.2) and older versions of Samba with the same problem. The samba process on the server ramps the CPU up to 90+% when the client operation is taking place. Help / suggestions is much appreciated. Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] print command is ignored after upgrade
I use to have a working custom "print command =" in my smb.conf until an upgrade to 3.0.28. OS: Suse 10.2 Samba: 3.0.28 Cups: 1.2.7 relevant smb.conf snippet [global] lpq command = lpstat -o%p ldap ssl = no name resolve order = host lmhosts bcast idmap gid = 15000-2 include = /etc/samba/dhcp.conf logon drive = P: map to guest = Bad User public = yes winbind use default domain = Yes realm = CANWEST.IBIGROUP.COM lprm command = cancel %p-%j printer admin = CANWEST\mvanderleest, mvanderleest, admin, administrator, root logon home = \\%L\%U\.9xprofile cups options = raw lpresume command = lp -i %p-%j -H resume print command = /usr/local/bin/printaccountserver.py '%f' '%p' '%m' '%I' '%U' '%u' '%s' '%J' '%z' '%a' & printing = sysv server string = SCA040002PS01 password server = 10.120.80.4 idmap uid = 15000-2 queuepause command = disable %p workgroup = CANWEST logon path = \\%L\profiles\.msprofile os level = 65 queueresume command = enable %p lppause command = lp -i %p-%j -H hold printcap name = cups security = ADS usershare allow guests = Yes winbind enum users = yes winbind enum groups = yes [printers] comment = All Printers path = /var/tmp create mask = 0600 printable = Yes browseable = No #browseable = Yes guest ok = Yes [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = CANWEST\mvanderleest, mvanderleest, admin, administrator, @ntadmin, root force group = ntadmin create mask = 0664 directory mask = 0775 now testparm reveals: SCA040002PS01:~ # testparm Load smb config files from /etc/samba/smb.conf Can't find include file /etc/samba/dhcp.conf WARNING: The "printer admin" option is deprecated Processing section "[profiles]" Processing section "[users]" Processing section "[groups]" Processing section "[printers]" Processing section "[print$]" Processing section "[printclient]" Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] workgroup = CANWEST realm = CANWEST.IBIGROUP.COM server string = SCA040002PS01 security = ADS map to guest = Bad User password server = 10.120.80.4 name resolve order = host lmhosts bcast printcap name = cups logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile os level = 65 ldap ssl = no usershare allow guests = Yes idmap uid = 15000-2 idmap gid = 15000-2 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes printer admin = CANWEST\mvanderleest, mvanderleest, admin, administrator, root guest ok = Yes printing = sysv cups options = raw print command = lp -c -d%p %s; rm %s lpq command = lpstat -o%p lprm command = cancel %p-%j lppause command = lp -i %p-%j -H hold lpresume command = lp -i %p-%j -H resume queuepause command = disable %p queueresume command = enable %p include = /etc/samba/dhcp.conf Restared samba, the works and still can't figure out why "print command = lp -c -d%p %s; rm %s" is showing up as my print command instead of the one specified in the smb.conf file. Any help would be appreciated. Thanks! Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] authentication problem
Hi all: I have a strange authentication problem. Samba box is running on a local network with about 300 Win2000 and WinXP clients as a domain member. No problems with local authentication to printer resources. On the WAN, all other locations with Win2000 and WinXP clients can access resources no problem. There are also Terminal Servers in each location (about a dozen different cities) and all Terminal Server clients can access Linux/Samba resources except one. This one asks for user/password authentication (which you are never able to successfully provide). If you browse to the IP address instead of the netbios name, you can at least see the printer/file resources but get an error message "unable to connect" when installing a printer. The same user login on different Terminal Servers works fine except this one. Thanks Greg Fedora Core 1 Samba 3.0.4 # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/07/23 14:29:18 # Global parameters [global] workgroup = GOLDER netbios name = CAL1-S-LRPRINT1 server string = security = DOMAIN log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = /etc/printcap dns proxy = No wins server = 157.208.71.2 ldap ssl = no idmap uid = 1-2 idmap gid = 1-2 printer admin = root, printadmin, GOLDER\KKroeker, GOLDER\RKroeker, GOLDER\RBudd, GOLDER\Ckruschel printing = lprng print command = /usr/local/bin/printaccountserver.py '%f' '%p' '%m' '%I' '%U' '%u' '%s' '%J' '%z' '%a' & lpq command = /bin/false lprm command = lprm -P'%p' %j lppause command = lpc hold '%p' %j lpresume command = lpc release '%p' %j queuepause command = lpc stop '%p' queueresume command = lpc start '%p' [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [printdrivers] path = /home/printdrivers read only = No guest ok = Yes [print$] path = /etc/samba/drivers write list = root, @Administrators, GOLDER\KKroeker, GOLDER\RKroeker guest ok = Yes browseable = No [bstinput] path = /home/bst write list = GOLDER\bstdba read only = No guest ok = Yes [pclient_golder] path = /home/printclient/golder read only = No [pclient_littlerock] path = /home/printclient/littlerock guest ok = Yes browseable = No [pclient] path = /home/printclient/golder read only = No [printqmonitor] path = /home/printqmonitor valid users = GOLDER\RKroeker, rkroeker read list = GOLDER\RKroeker, rkroeker write list = GOLDER\RKroeker, rkroeker read only = No -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] print spooling message never goes away
I have a Samba server that reports some print jobs "spooling" to the workstations on the network when clients browse it. There are no jobs spooling or printing and it never goes away unless I restart the Samba process. It does come back though and do the same thing. This happens on a few of the 50 queues it's serving. Any ideas? Thanks Greg Samba 3.0.4 Fedora Core 1 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cups/samba integration problems
Some notes first: Fedora Core 1 (2 node HA cluster, heartbeat & drbd) Cups 1.1.20 Samba 3.0.4 400 Windows 2000/XP clients 50 print queues HP Laserjets, Xerox colour multifunctionals, Ricoh mulitfunctionals, HP DesignJet plotters 2000+ print jobs/day 8000+ pages/day 5GB + print data/day I have a custom printer accounting application that is run by samba when a print job arrives at the server. This application supports PCL5, PCL6, postscript and HPGL2 blah blah blah. PROBLEM: Because samba and cups are now tightly integrated, samba does not offer the facility to issue a custom print command (print command =) when you tell samba the printing system is cups. Samba quietly ignores any custom print command, postexec, and preexec directives. The right thing to do would be to write a cups filter to invoke the printer accounting, however, the cups command line arguments to a filter program and the environment variables seem lacking some key pieces of information, namely, the remote host and remote ip address of the client. So, in my case, I must break the relationship between cups and samba and tell samba that the printing system is bsd or lprng in order to use my printer accounting application. This is where all hell breaks loose. There seems to be no valid lpq command that samba can hand off to cups that reports anything that samba understands. Worse, the default lpq command (lpq -P%p) invokes (I assume) cups lpstat program. Under the right (or wrong) conditions, this has brought my server to its knees. I don't know what's wrong with lpstat but it seems to be horribly inefficient, especially when 400 windows desktops query the samba server for print queue status (which it is unable to report anyway). In order to stop the samba/cups duo from crashing my server (doesn't really crash, it just can't do anything, like a self inflicted DOS attack) i have to map the samba lpq command to /bin/false. So here are my two questions: 1. Is it samba or cups that prevents samba from using a custom print command 2. What the heck is wrong with lpstat. Even a script that runs lpsat (multiple times) to collect different pieces of information seems to tax the system. Thanks Greg -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] print command, cups, lprng, bsd
Good day. I have a strange problem changing the "print command" from the smb.conf file with different print spooling subsystems specified in the conf file. samba 3.0.4 cups 1.1.20 fedora core 2 If the "printing" option is set to "cups" the "print command" is not executed. If the "printing" option is set to "lprng" or "bsd" the "print command" is executed. Also the "job name" (%J) changes Example: printing = cups Job name example: smbprn.0048 Remote Downlevel Document printing = lprng Job name example: smbprn.0047.6CpzDO on another print server (the only difference fedor core 1 instaed of 2) printing = cups Job name example: smbprn.0048 EIS mapping specs.xls Now, this "Remote Downlevel Document" has always driven me crazy and I don't understand why the job name comes across ok on the one server and not the other (EIS mapping specs.xls). Thanks Greg [global] workgroup = LNX server string = Samba Server username map = /etc/samba/smbusers log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 logon script = logon.cmd logon path = \\%N\profiles\%u logon home = \\homeserver\%u\winprofile os level = 33 dns proxy = No ldap ssl = no idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 printing = cups printcap name = cups [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [print$] path = /etc/samba/print read only = No guest ok = Yes [netlogon] path = /var/lib/samba/netlogon write list = ntadmin [profiles] path = /var/lib/samba/profiles read only = No create mask = 0600 directory mask = 0700 [cdrom] path = /mnt/cdrom [data] path = /home/data read only = No [ricoh3800] comment = Local Raw Printer path = /var/spool/samba print command = /usr/local/bin/printaccountserver.py '%f' '%p' '%m' '%I' '%U' '%u' '%s' '%J' '%z' '%a' & read only = No printable = Yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
