similar to: PATCH: downloading drivers from Solaris [was Re: So SAMBA no longer ...]

Our computers in our office ceased being able to print to a shared cups printer today. Could not find the cause. Seems the smbd processes are dying. Below is the stack trace produced by gdb bt full. The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd). 0x40150a59 in wait4 () from /lib/libc.so.6 #0 0x40150a59 in

Hi, I've a problem, with a cpu load (>66% while running a separate virusscanner with another 30%) of one of my smbd processes. It only happens occasionally (approx. 2 times in the last 4 weeks). The backtrace is attached. It seems to me, that smbd is looking for colorlaser5quota. This printer isn't attached anymore to the server and neither cups nor samba configuration files include a

Running Kubuntu linux with wine 0.9.22. Printing via cups seems to work fine from linux ("lpr tiger.ps" works fine). But when I try to print from coverxp through wine I get the following error (and nothing is printed): trace:winspool:OpenPrinterW (L"EPSONStylusC86", 0x33f690, (nil)) trace:winspool:GetPrinterDataExA (0x2, "PrinterDriverData", "Paper Size"

I have discovered a difference between Samba and Windows which I think is of interest to the Samba team as it prevents printer driver from being uploaded correctly. I would appreciate some comment on this subject please. The difference is that following uploading of the dlls to the Windows 2000 server the driver is loaded on the Server itself and the driver recieves notification of the fact by a

Hello! Jerry you are right about script and permissions! I'm looking again to usrmgr.exe and has corrected most of the problems of which I spoke earlier This patch is corrected most problems, but i can't fixed, current moment, problems where "not root" create "global group" ... sorry :( This patch not create security holes and another holes ... :) I'm testing

Hello everyone, I've got a Xerox Work Centre 5735 that I'm printing to via Samba. When I install the drivers on a client (using the right-click-Connect method) from the samba shared printer then the install goes smoothly but I can't load the Printing Preferences dialogue for that printer, I get an "Operation could not be completed" error. This same error does not occur

Hello, I have a problem with point and print (I belive) problem. I have a HP DeskJet 3550 shared in Samba server (samba-3.0.14a-2/Fedora Core 4) as ImpPcpJt. Connect a printer from a WinXP Pro work fine, but when I try to see the "Properties" of there, the Explorer.exe generate an protection fault. I don't know if is a printer driver or Samba problem, but I found a strange

I'm trying to get Wine to print through it's PS driver, without success, on a HP DeskJet 694C, configured on Linux with the cdj670 driver. What I get to see on screen after I attempt to print are three windows with exclamation marks on a yellow triangle and garbled text. The first window is titled "Printer name", the second "Device name", the third "Output".

My user observable errors seem to now be gone but I am seeing some behavior that may need to be looked at. There are error messages in Ethereal and in the logs like "_spoolss_getprinterdataex: Invalid keyname [DsDriver]". First I'll give the brief history and then more details below. I started a new install on FreeBSD 5.1 using samba 2.2.8. I compiled with CUPS (1.1.19). Printer is

Heads up everyone, Source release will be on download mirrors shorly. This is provided as a non-production release of the future 3.0 Samba codebase for testing purposes only. Use at your own risk. Now that I've cleared by conscience... :-) -- enjoy, -- The Samba Team Changes in alpha20 - Rework the 'guest account gets RID 501' code again... - Change

It's exactly the same. Except that I use tdbsam instead of ldap and the error message therefore also is different in the log file. But the example and result is the same. Do you have any idea of workaround or fix? Cheers, Joel -----Ursprungligt meddelande----- Fr?n: Doug Campbell [mailto:doug@bpta.net] Skickat: den 11 maj 2005 10:49 Till: Joel Larsson, PF, Posten; samba@lists.samba.org

I try to use Win32API EnumPrinterDataEx to get registry key's values and data from Samba print server (of course I previously connect to the print queue and retrieve keys by EnumPrinterKey). During the function execution (EnumPrinterDataEx) I collect ethereal trace to verify correct data is sent on wire and that Ethereal can correctly represent that info. Some of the keys parsed correctly

Hello Followed the doc's to setup a postscriptprinter but get the following message when starting wine: err:psdrv:PSDRV_FindPrinterInfo Error 2 getting PPD file name for printer 'Epson_360_dpi_' fixme:winspool:AddPrinterW DocumentProperties fails err:psdrv:PSDRV_FindPrinterInfo Error 2 getting PPD file name for printer 'Epson_360_dpi_' err:winspool:AddPrinterW

On Wed, Feb 08, 2017 at 04:36:31PM -0500, Dawid Zamirski wrote: > There are some corrupted registry files that have invalid hbin cells > but are still readable. This patch makes the following changes: > > * hivex_open - do not abort with complete failure if we run across a > block with invalid size (unless it's the root block). Instead just > log the event, and move on.

Hi, maybe (probably ??) it's me, but it took me more than a week to get winbindd working on Redhat 9. It works now after changing a parameter in smb.conf, but I have NO idea why. Maybe some of you already had the same problem. If so, PLEASE clearify ! Thanks... PS as you will see later, getent group also does not work. This is an independent problem I think... can it have something to do

Hello, The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be

share in the samba box, from the PDC server itself. The log.winbindd and log.nmbd are empty. [2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(865) Domain=[EERDBR001] NativeOS=[Windows NT 1381] NativeLanMan=[] [2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(876) sesssetupX:name=[administrator] [2001/08/08 13:11:28, 3] libsmb/namequery.c:resolve_lmhosts(733)

There are some corrupted registry files that have invalid hbin cells but are still readable. This patch makes the following changes: * hivex_open - do not abort with complete failure if we run across a block with invalid size (unless it's the root block). Instead just log the event, and move on. This will allow open hives that have apparent invalid blocks but the ones of potential

Hi Jerry, It seems that the "samba-2.2.5-printing.patch" has only fixed the problem for PCL drivers. With PS drivers (Laserjet 4050 PS) are the duplex & tray settings still missing. Best regards, Khiem -----Urspr?ngliche Nachricht----- Von: Glen Gibb [mailto:grg@ridley.unimelb.edu.au] Gesendet: Mittwoch, 28. August 2002 07:41 An: Gerald Carter Cc: Samba Betreff: Re: [Samba]

The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at