similar to: Delayed Write Failed!

I?m running Debian Linux 3.0 r1 with Samba 2.2.8a and I have got printing problems: --- when I print something the job don't appear in the window printing status, so I have no way to check the actual status of the job, or to delete the job from window printer status in Win2K. here is configurations file of smb.conf: [global] workgroup = Gertian log level = 99 queuepause

Baxter, I could be wrong, but I thought /etc/printcap was the config for bsd style printing - not cups. Anyone? -- Christopher Barry Manager of Information Systems InfiniCon Systems http://www.infiniconsys.com -----Original Message----- From: Baxter Shepperson [mailto:baxshep@cox.net] Sent: Friday, March 21, 2003 5:24 PM To: samba@samba.org Subject: [Samba] Redhat 8 printcap I am trying to

Hi all, Yesterday, i changed from samba 2.2.3 to samba 3.0, and also i changed the machines which samba is running on. Samba worked and should work as a PDC. It runs on a Debian sid, the test client is a notebook with XP Professional. Yesterday, immediately after migrating, everything worked fine. Even after several reboots, i could logon as a domain user, and i could use the shares. Today, i

I have two Samba servers configure similarly. One shares fine across our entire network and the other only works within its own segment. I have poured over the smb.conf files and cannot see what it preventing the one from crossing segments. These both are Debian 2.2 boxes and I am just modifying the default smb.conf files. I am hoping a fresh pair of eyes will help. Any help would be greatly

Here is my printer config: printing = lprng load printers = yes use client driver = yes printer admin = @edutec, root printcap name = /etc/printcap print command = lpr -U%U@%M -r -P%p -J'%J' %s lpq command = lpq -P%p lprm command = lprm -U%U@%M -P%p %j lppause command = /usr/sbin/lpc -U%U@%M hold %p %j lpresume command =/usr/sbin/lpc -U%U@%M release

We have a lot of [2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355) Trying to delay for oplocks twice in the logs. Do they harm in general? And only in one single case I got this, don't know if I ever will get it reproduced, so maybe not related and happened by accident: Samba version 3.0.21a PID Username Group Machine

Greetings all, I'm still struggling with Samba 2.0.7-4 on a RedHat Linux 6.2 box and I'm wondering if there are any known issues when using samba on a box with multiple processors. I *seem* to recall reading something about this quite awhile ago, but I can't find it and don't remember enough about it to be useful. :-( Currently I'm using 1.9.18p10-52.4 on the box

Hi all, we've just recently switched to a new file server upgrading to samba 2.0.3. Unfortunately I've noticed that a couple of times a day a smbd process dies with 'oplock break failed' so I actually had to turn off oplocks thus degrading performance drastically. Does anybody have any idea why oplock breaks are failing so often now? Cheers, --- Martin Hoffesommer Soft

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Blanking someone is an incredibly powerful thing to do in civilized society. -- Bernard Black ============================================================== Release Announcement ==================== This is the latest

OK, then here's the weird part. I have another server, hosting other files, lets my Windows 10 system connect. The main server won't though. They are both running Debian Jessie 8.3, and Samba 4.1.17-debian. Below is the /etc/samba/smb.conf file *that works with Windows 7 and 10*: [global] workgroup = SD57 netbios name = SAMBA server string = sss interfaces

Version: 3.0.14a (debian stable: 3sarge1) I'm just about finished converting our company's network from NIS to LDAP. Part of that involved updating Samba to use that same directory so all the information is maintained in one place. Most everything is good, except that my roaming profiles won't work. My smb.conf file is attached. Upping the log level eventually showed messages

hi everybody we have been reading through the archives for quite some time now, and could not find a solution to our problem. please excuse if we overlooked something and our question was already answered elsewhere... we have Samba version 3.0.14a-Debian running on (you guessed it) debian with kernel 2.6.8-2-386. ever since our migration from samba 2.x we have speed issues with an ms

I'm currently having a problem with the new released Samba 2.2.5: I cannot print anymore on my shared printer. What is strange is that It worked fine with samba 2.2.4, but now I got an access denied whenever I try to access the printer... /var/spool/lpd/samba is chmod 777 and the username is in the group lp Here is part of my smb.conf: [global] workgroup = HOME netbios name =

Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget

I'm having some difficulties joining a Win2k workstation to a Samba domain. This particular workstation is my work laptop (DRUMMSW01) which normally operates as a member of a standard Win2k domain called BIZ. At windows startup/logon, BIZ is specified as the domain. At home, my Samba PDC's workgroup/domain is HOME.LAN When I try to browse shares on HOME.LAN with the Win2k laptop, I

I am experiencing a performance issue with MYOB accounting package being served from a Debian 2.4.18 based server running samba. Clients are Win2K/WinXP clients in a small workgroup environment, all maping drive to samba 'data' share. Network is pure TCP/IP, no other (MS or Samba) servers on LAN. I've experimented with Oplocks and veto oplocks but to no result the performance of

On 02/04/16 20:02, Luke Barone wrote: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE > > > On Sat, Apr 2, 2016 at 11:57 AM, Luke Barone

Hi all, After some config changes and reboots, I got the Samba server running properly for my client computers running Windows 7. My issue now is with Windows 10. I see threads relating to setting "max protocol = NT1", but this seems to break the Windows 7 clients (which are finally working again). Below is my smb.conf file (which works for Windows 7): [global] workgroup = JMC

Hello people, ok just a small problem I have with my samba settings. I have a RH 6.0 file/printer server that is connected to some Windoze 98 machines and a couple of Macs. The linux machine also has one printer on its local port lpt1. Ok...I have set up everything and currently I can print from the Windozes and the Mac to the printer that is localy connected on the Linux server. What I want

Hi, I have the problem, that from a Windows 2000 System (possibly from others to), a user can use a printershare with the guest account and I don't know why. Following my smb.conf: Samba config file created using SWAT # from 192.168.2.20 (192.168.2.20) # Date: 2004/11/20 14:26:14 # Global parameters [global] unix charset = ISO_8859-15 display charset = ISO_8859-15 workgroup = WG interfaces