similar to: Windows XP Printing Woes..and a partial solution

I browsed through some posts about this issue which I've been struggling with for a long time now. Why is there no solution? I think this issue has been discussed so many times (with no final solution) that I don't need to rewrite the symptoms and logs. Printer HP LaserJet 1100 with latest HP drivers. Smb 3.0.7 (also tried 3.0.12pre with no difference in printing time). This is what I

Marcel, Did you ever solve the problem below? I am having the same trouble here. Thanks, Bill Szkotnicki On Mon, Oct 20, 2003 at 09:34:26AM +0100, Nick Maynard wrote: >/ > > > "A domain controller for the domain BEECHES could not be contacted. />/ > > > Ensure the domain name is typed correctly. />/ > > > If the name is correct, click Details for

Working with Windows XP and debian Samba 2.2.3a on a box as my PDC. Sign or seal patch was applied. The past few days when we have been adding new computers running windows XP to the domain we have had machines tell us they have joined the domain, but when we try to log onto them using a "domain" account we get the following error on the PC: "The system could not log you on to

Greetings, you kind and wonderful people. I've spent the past few hours or so (read: all day) attempting to get a basic PDC up and running, with no success. I've even gone to the extent of copying John Herpstra's config, which contains all sorts of weird and wonderful stuff, in the hope that he had something I missed. He didn't. I've got one box running debian testing, with

I checked through the archives and I didn't see this one. This has been driving me absolutely crazy for months now and I finally tumbled to what was going on. I get hesitations of up to 2 minutes from some of our XP machines when printing to a printer on the Samba server. My first suspicion was that it was some kind of name resolving issue. I tried using the domain name of the Samba

Doesn't really resolve the issue, but in my case the problem went away when using physical machines rather than virtual machines. The environments are identical - RH ES 3.0 with Windows XP sp1a client (no hotfixes or GPO settings applied). Thanks for everyone's help. On Fri, 2004-05-07 at 15:38, Michael Vermaes wrote: > On Fri, 2004-05-07 at 15:16, Clint Sharp wrote: > > >

Hi all, I'm running 3.0.6 on IRIX 6.5 (compiled from sources) Runs fine for almost all purposes. But I thought I'd have a look at the extra Samba-3 printing facilites today, and they've thrown up some real issues. 1st point. I still haven't managed to get to the bottom of this one, but I can't always add a printer drive to a Samba-served printer. I've been

Greetings, All, To start off, I think everyone has done a WONDERFUL job with Samba, and I'd enjoy my job much less with out it. A remarkable effort from everyone that has contributed to the effort. Now I will contribute my printing problems. I have Samba 2.2.3a running on top of Sun Solaris 8 and I have been seeing a number of printing related problems. From what I am seeing on the

Hi all, I've finally hit rsync limit. As someone already addressed the problem in this list the problem regards the impossibility for rsync to rename directories. The situation is as follow: every night I backup my samba dir with this command: rsync -ab --suffix=-`date +%F-%H%M` --filter="protect *-[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]-[0-9][0-9][0-9][0-9]" --delete

The most recent discussions I could find on the internet about how to tunnel Samba over ssh were on this list (http://lists.samba.org/archive/samba/2004-February/), but no complete answers were given. Here is a near complete answer, which works, pulled together from various sources on the web (which are referenced). Remaining questions are at the end. It is kind of PuTTY-centric, but as far as I

Hi Couple of printing issues that I can't get around. Probably relevant conf sections at bottom. Minor one first: In the Add Printer Wizard (the place most users look first), the Samba print server is not listed. Manually typing the \\server\printer works fine, but this is "difficult" for users adding printers on the fly. Adding the printer from \\server\printers works fine too,

Hi people!! i'm using samba with ADS authentication mode. when i try access the server samba, from windows, using hostname(\\serversamba) is showed a authentication screen, I enter my username and password, but isn't accepted. but when i try access via IP(\\192.168.1.1) all works. samba make the authentication with my username and password in AD(win2k box) . Why? sometimes this

List, Long and confusing message follows... I'm facing a frustrating problem. XP clients can use resoures on the samba server by IP-address, but not by name. So, "net view \\servername" gives "access denied" but "net view \\ipaddress" gives list of shared resources. Samba server (3.2.7 sernet rpm) is a member server in W2003 domain. I emphasise that with

Hi there, If the printer is connected to a W95 box the following information may help. 1) read the shell script '/usr/local/samba/smbprint', it provides info on how to setup the configuration files 2) install ghostscript, portable bitmap utils etc 3) install 'Magicfilter', it may need all of '2)' 4) modify the (last) lines in 'smbprint' to something like: (

We have a printing reliability problem with Samba printers/queues and we are trying to figure out how to troubleshoot it more methodically. Situation: We've been running Samba 3.x (always current/latest) for over a year with primarily Windows 2000 clients. This summer we are converting our 100 Win2K PCs to XP; this conversion is nearly complete. Our Samba printing is CUPS-based to HP

community, I submit to you my plain request as wether exchanging my video card would fix the fault. My concern issue looks like as follows: Not knowing wether anybody among you had noticed yet the phenomenon when ancient hardware and a relative new system clach ? I have a P III. PC desktop with FC4 running on it for a year or so.That configuration has been me working faultless till now. Recently

I've been banging my head against some printing problems that I've been having for quite a while. This weekend I am migrating an old server to new hardware and a new base OS, but the version of Samba and CUPS remain the same. Because of this I moved all the config files and the contents of /var/cache/samba from the old server to the new. (Foreshadowing: this was a mistake, but not a

I have set samba server as PDC and I can see the network in others computers but not in the server, any idea? thx for advance my smb.cnf: # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2007/03/09 22:38:36 [global] workgroup = DOMINI server string = %h Domain server (Samba, Ubuntu) obey pam restrictions = Yes passdb backend = tdbsam

The patch titled Subject: ocfs2: fix data corruption after failed write has been added to the -mm mm-hotfixes-unstable branch. Its filename is ocfs2-fix-data-corruption-after-failed-write.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/ocfs2-fix-data-corruption-after-failed-write.patch This patch will later

Hi Andrew, There is an updated version v2, which describe more clearly about the case: https://lore.kernel.org/ocfs2-devel/e9fc4b2f-1fcc-7c31-f346-59eccff50f9b at linux.alibaba.com/T/#u Thanks, Joseph On 5/26/23 4:55 AM, Andrew Morton wrote: > The patch titled > Subject: ocfs2: fix use-after-free when unmounting read-only filesystem > has been added to the -mm mm-hotfixes-unstable