similar to: Print Corruption - Vendor Driver, CUPS in RAW mode

Hey Samba team... I'll still buy you pizza! Anyway, trying to be good security folks, we had tossed in a global setting in smb.conf that root was an invalid user. No Windows client will ever have an account named that which they need to touch Samba with, and everyone knows it is bad bad bad to logon to your Linux box with root... but anyway, Samba sure seems to have an opinion about doing

I want to install a driver on a print server, i'm looking at this doc: http://us1.samba.org/samba/docs/man/howto/CUPS-printing.html#id2563056 i did: root#rpcclient3 -U'adm%passwd' NT-SERVER -c 'getdriver printer 3' [Windows NT x86] Printer Driver Info 3: Version: [3] Driver Name: [SHARP AR-M350U PCL5e] Architecture: [Windows NT x86] Driver Path:

I've a more 'normal' error, first error posted was due to a bad IP :/ now when i do: rpcclient3 -Uadm%passwd -c 'adddriver "Windows NT x86" \ "SHARP AR-M350U PCL5e:tiger5k.dll: \ tiger5k.dll:tiger5u.dll:tiger5.hlp: \ NULL:RAW:tiger5l.dll,tiger5p.dll, \ tiger5c.dll,tiger5j.dll,tiger5q.exe,\ tiger5x.dll,tiger5s.dll,tiger5wu.dll,\ tiger5wk.dll,tiger5z.exe"'

Hello everybody, I'm using CUPS 1.1.19 and Samba 2.2.8a on SuSE Linux 9.0 (I'm using SuSE's pre-built packages). Samba is running as a domain controller and the workstations are running Windows XP Professional. I manually installed cups-samba 1.1.19 Windows printer drivers because SuSE doesn't supply them. I've got three printers on the network which I would like to print on

Hello, I have few Windows2000 Pro samba domain members which logon to the domain without any obstacles. Recently I decided to upgrade all client workstations to WindowsXP SP2. Fresh copy of WindowsXP joined domain properly but when I tried to logon as usual it accepted password and shut down after a while (logs of samba confirm that workstation logged on). Windows claims that winlogon caused

I'm trying to adddriver using rpcclient but this error happens: ERROR: string overflow by 1 (1024 - 1023) in safe_strcpy [adddriver "Windows NT x86" "HP LaserJet 4250 PCL5e] The "server properties" add driver button is disable.... yes, I'm print operator: printserver:~ # net rpc rights list "DOMAIN\user" -Uroot -Wprintserver Password:

Recently, we added a Sharp AR-M550N copier to our network. This device functions as an MFC (scanner/printer/copier). When I attempt to install the drivers to the SAMBA server, I receive an error message which displays briefly and then I receive the following error message when trying to access the properties of the printer. Function address 0x3119c9f caused a protection fault. (exception code

Hello all! Samba works fine. GREATE WORK OF SAMBA TEAM!!! But when i try to upload more than one driver for printers samba writes to log: [2001/03/30 13:30:18, 0] printing/nt_printing.c:move_driver_to_download_area(1178) move_driver_to_download_area: Unable to rename [WIN40/hpblgbe.drv] to [WIN40/0/hpblgbe.drv] and then if i try to download driver to workstation, samba says that driver is not

Hi There. The next information was tested with more than 4month with a lot of client and with a nasty traffic. The only problem what with couldn't fix yet is some timesout coming from the wireless card some times but doesn't crash the traffic or the wireless card! the conclusion to make a good Access Point with freebsd is the next: We have a good and very nice hardware and software

This occurs with Samba downloaded drivers of an installed printer. When attempting to view the printer properties you receive the following error: ?Function address 0x2d04193 caused a protection fault. (exception code 0xc0000005) Some or all property page(s) may not be displayed.? Followed by: ?The ?<drivername>? printer driver is not installed on this computer. Some printer properties

> I have few Windows2000 Pro samba domain members which logon to the domain > without any obstacles. Recently I decided to upgrade all client workstations > to WindowsXP SP2. Fresh copy of WindowsXP joined domain properly but when I > tried to logon as usual it accepted password and shut down after a while > (logs of samba confirm that workstation logged on). Windows claims that

OK we do all the steps in my previous missive and everything looks fine, landscape, collating the whole works. This is on a Laserjet 4000 with the latest PCL6 driver. The firm still has a good number of Laserjet 4s so we dutifully load up the latest PCL5E driver for the 4 and connect to the 4 on a couple of workstations. Everything goes to hell. Landscpae, collating and all other problems

Greetings, This is an extenuation of "Non-registry problem: Slow printing" See: http://www.brightsands.com/~chris/quick.3.bz2 fast printer drivers loglvl=3 http://www.brightsands.com/~chris/slow.3.bz2 slow printer drivers loglvl=3 http://www.brightsands.com/~chris/quick.9.bz2 fast printer drivers loglvl=9 http://www.brightsands.com/~chris/slow.9.bz2 slow printer

Anastasios, I've done exactly what you want to do, only starting from SBS2008. Our office went down this road in 2014 when we investigated upgrading from SBS2008 only to find that MS replacement, Server Essentials, did not support Exchange. We currently have a "no cloud" policy, so going to Office 365, as you have done, was not an option (and btw, have you not considered Server

Maybe there's a trivial solution to this, but it's confused the hell out of me. I'm trying to upload the latest Windows XP PCL6 driver for our Laserjet 4250TN to my Samba 3.0.11 server. It works, and uploads the driver files, but then at the end it produces an error on the XP client "the operation could not be completed". The logs on the samba server state:

Greetings, I've now received private e-mail saying that others have seen this problem, sent e-mail to this list and received no answers. That ultimately, they ended up altering their Windows clients to use LPR instead of Samba. Is this really something that a genuine MS Windows server can handle and Samba cannot? Does anybody know when these other drivers stopped working well and what

Let's keep this on the samba list and not an interactive between you and me...Also, I prefer bottom posting so my reply will be at the bottom. On Fri, 2004-03-12 at 11:54, Lee Thao wrote: > Test page from cups using Postscript driver give printout saying printer is > not license for postsrcipt. Other drivers (Generic - PCL6) produces blank > sheet with a few chars in upper left,

Greetings, (Brief synopsis): | This is an extenuation of "Non-registry problem: Slow printing" | | See: | http://www.brightsands.com/~chris/quick.9.bz2 fast printer drivers loglvl=9 | http://www.brightsands.com/~chris/slow.9.bz2 slow printer drivers loglvl=9 | http://www.brightsands.com/~chris/smb.conf the smb.conf in use | | I have a sample Windows XP/SP2 client trying to

Hey Bjorn, Were you able to figure this out or is it still broken for you? Our scenario is a little bit different, but I have a theory as to what may be going wrong. What linker are you using when you compile your project with clang-cl? I am wondering whether the version of the linker and/or the libraries that you are using is too old in comparison to the one used for the clang compilation.

Hello, I've encountered a problem printing to a windows print share and am uncertain how to go about resolving my problem. From what I've been able to tell, the problem lies in samba. I've got a fedora 13 box with samba installed and running on it. My goal is to print to a windows print share. I am able to use smbclient to query the print server and get a list of shares and