similar to: Samba Process stops while trying to print to a CUPS

Hi list, )2nd try bcs. of missing attachements). Following (very strange) problem: An ordinary windows user has mapped a drive F: on \\LUN1\Programme (running samba-3.0.20b-3 debian). The program "F:\Network\PMail V3\Pegasus Mail\winpm-32.exe" is being started, this works. But after about 10 minutes, the same program start fails with "invalid path or filename". When

In reviewing the recent printing-3-0-10_v2 patch, I think I have found an omitted 'release_print_db'. The following patch corrects this. Regards, Jerome Borsboom --- samba-3.0.10/source/printing/printing.c 2005-01-10 15:07:27.060999122 +0100 +++ samba-3.0.10.new/source/printing/printing.c 2005-01-10 15:07:36.784464292 +0100 @@ -1077,6 +1077,7 @@ if (

I currently have a 95% Novell Network network that continues to have constant printing issues. Enough Novell bashing, here lies the problem. I am trying to migrate all of our printers over to a samba print server, but in several of my tests I have come up with problems. I will attach my smb.conf at the end for those of you that wish to see it. I am using lprng as the printing backend because all

Hi, based on Bart Lagerweij's ( www.nu2.nu ) bootdisk, I've created a small DOS system that users can start by booting from network ( PXE ). The system is configured to map a network drive from a Suse 9.0 Pro / Samba server with various tools on it. The connection is anonymous. Until recently everything worked fine but suddenly there are strange errors: When I try to launch an EXE from

I have a Fedora 3 core system with cups and samba installed I have an HP deskjet 5740 on usb port 1 that prints just fine. the cups install and print test pages work and print. the installation of the printers on Windows XP goes just fine and I can print to the printer, however nothing ever prints on the printer here is the log from /var/log/samba/smbd.log [2005/02/07 10:27:15, 3]

Hello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings. I'm seeing an odd problem with 3.0.10 and 3.0.11 here. We have some pdf printers defined: [Accounting pdf printer] printer admin = "DOMAIN+Domain Users" browseable = yes path = /pdfdropbox/Accounting printable = yes writeable = no print command = /usr/bin/preprintpdf %s -r lpq command = lprm command =

Urs Rau wrote: >>I start to wonder what "dammage" it would do to set lpq to >>lpq command =/bin/true >>for my pdf printer? ;-) > > > > Well, wonder no more sir!!!!!! I set my lpq command = /bin/true and > ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you! That was all I did, I can't believe it worked......thank you!!!!!! >

I'm stumped! From within CUPS, I'm able to successfully print test pages. From the Windows machine, I'm able to: * Browse the Samba server's printers via SMB * Add the Samba server's printers * Write to the Samba server's print$ share If I pause the printers via CUPS's interface, then Samba successfully relays this information when I try printing a test page from the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i recently upgraded some of my servers from 3.0.2a to 3.0.4 after the upgrade my browselist shows duplicate entries for the domains. one domains is managed by a samba PDC(providing WINS too) and two samba BDC's. the other domains are managed by one samba PDC. 'smbclient -N -L <WINS_SERVER>' shows: - --- Workgroup

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded a new draft of the printing patch for 3.0.10 to http://www.samba.org/~jerry/patches/post-3.0.10/ The only change is a small fix to fix the register_message_flags() error messages in the logs. After some thought, I think this might address the 'jobs failing to be removed from the queue list' bug. If people could test and let