similar to: RH6.0/Samba Oplock Problems (and fix) (PR#16952)

To any one who is using Red Hat Linux 6.0 (or, presumably, any glibc2.1 system) I recently installed a new RH 6.0 system on Intel. After installing my samba and my network application I noticed that I was experiencing oplock problems that were not present with the same version of Samba on my RH 5.2 systems and caused my application to not function. Since the problem seems to be with oplocks I

I hope that someone can help me with this because I'm at a loss. I have a Samba server running RH 5.2 w/all errata plus Samba 2.03 that is used, among other things, to serve a share for a Windows program called "Business Works" which is a network accounting package. This program uses the standard Windows range-locking to implement it's network capability. I have been using this

Hi, I'm trying to build samba 2.0.5a on Red Hat 5.2. It originally came with 1.9something, which seemed to have some bugs accessing large mounted directories. I downloaded Red Hat's updates package, but unfortunately it only comes with smbclient and smbd, and what I need is smbmount and smbumount. My binaries from my more recent systems (RH6 and OL2.2) won't run due to

Hi all, I have made a RedHat 6.0 i386 binary rpm of 2.0.4b with the glibc2.1 configuration fix available at : ftp:<samba.org mirror>/pub/samba/Binary_Packages/redhat/RPMS/6.0/samba-2.0.4b-19990527.i386.rpm This rpm is to be preferred over the one on the RedHat 6.0 cd as it contains an autoconf configuration test to work around the glibc2.1 bug w.r.t. 64 bit locking (the one that

Hello, people at SAMBA list. I'm going thru the same problem that Nicholas Williams has described in samba-list first (see references below), and I'm implementing the solution you've decribed in the list (SO_KEEPALIVE, etc). But I'm stuck with the script issue, as I run RedHat Linux 6.0 which doesn't use ksh but pdksh instead. The ksh script doesn't run in pdksh

I've used exactly that combination, and the domain join worked without a hitch. I had to go in as NT domain admin and create a server/workstation entry in Server Manager first, of course.

I just upgraded my server from RH5 to RH6. I am seeing two problems that may be related. 1. When I do an smbtar I get errors on some of the files: My command line: # smbtar -v -s schroon -x "D$" -d gt -p z -u backup -t /usr/tmp/a.tar The error message: Error reading file \gt\STk-dist\Demos\Html-Demos\Images\backward.gif. Got 0 bytes Didn't get entire file. size=714, nread=0

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, With SMB and NMB services stopped, I issue: smbpasswd -j DOMAIN -r PDC with these results: cli_net_auth2: Error NT_STATUS_NO_TRUST_SAM_ACCOUNT cli_nt_setup_creds: auth2 challenge failed modify_trust_password: unable to setup the PDC credentials to machine PDC. Error was: NT_STATUS_NO_TRUST_SAM_ACCOUNT. 1999/10/25 <timestamp>:

I have an application with is binary-only, does its job well, and is only available for either libc5 (!) or early early glibc2.0 (!!). It has been running on a Red Hat Linux 5.2 (NOT RHEL; RHL) server for a really long time, and it honestly does its job and it's not easily replaced by an open-source solution at the moment. So, I need to do one of the following things: 1.) Run Red Hat

We are having problems building R on Red Hat Linux 6.0/Sparc. R compiles with no problem but then it fails "make tests". Specifically, the line eigen(cbind(-1,c(1:2,0),0:2)) # complex values causes a segmentation fault. Previous versions of Red Hat Linux did not give this problem. The eigen() function is one of the rare cases in the base library where Fortran code is called via the

On 04/21/2017 12:11 PM, Lamar Owen wrote: > ... > The latest version of libc5 I know of that was shipped by Red Hat is > in RHL 6.2, libc-5.3.12. (There is a 5.4, but not sure of stability > or compatibility). > ... > I've successfully set up the bridging; a CentOS 7 VM on the same host > has full connectivity. So it's something about the rtl8139 and the >

Red Hat Software has been notified of a critical security problem (a buffer overrun) in /usr/bin/sperl*. As no official fix for this problem exists, we recommend turning off the setuid bit on /usr/bin/sperl*. As far as we know, this problem affects all platforms and all versions. As soon as a fix is available we will release a new version of the perl package and announce it here. If no fix seems

The Samba Team is pleased to announce Samba 2.0.5. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. Please read the "IMPORTANT NOTE" section of the release notes as this explains three security bugfixes which have been added in this release. It is vital that Samba admins understand these

The Samba Team is pleased to announce Samba 2.0.4. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. Samba 2.0.4 now supports the viewing and modification of UNIX security ownership and permissions from the standard Windows NT client security dialog. More details may be found in the NT_Security document

The Samba Team is pleased to announce Samba 2.0.6. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. It may be fetched via ftp from : ftp://ftp.samba.org/pub/samba/samba-2.0.6.tar.gz Or just follow the link on the main page of your nearest http://samba.org mirror. Binary packages for supported systems

The Samba Team is pleased to announce Samba 2.0.7. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. This version has been tested against Windows 2000 and has no *known* issues with that release of Windows. It may be fetched via ftp from : ftp://ftp.samba.org/pub/samba/samba-2.0.7.tar.gz Or just follow

fhsmith@logicsouth.com wrote: > > This is a follow up to an item placed on the comp.protocols.smb newsgroup. I have tried tweaking all of the settings until my face turns blue, so here goes: > > System is RedHat 6.0 - Linux Kernel 2.2.5-1. Samba 2.0.4b. > > Here is the gist of the problem (also posted on newsgroup). > > have a Samba server and about 10 Win95 machines

penso che ti/ci possainteressare, soprattuto il fatto che la versione html del libro sia disponibile con il prg GRATUITAMENTE Marco Frattola (???) - Cubecom S.p.A. Via de Marini,1 3 piano Torre WTC 16149 GENOVA tel. 010 6591184 > -----Messaggio originale----- > Da: samba@samba.org [mailto:samba@samba.org] > Inviato: Nessuna > Oggetto: > > > id

This is great news since I too have this problem. One question please. Could this be causing a problem where a win98 machine cannot write new files to the samba share (but can read and edit a file just fine)? Other win95 machines can write just fine to this share. Rehat 6.0 w/ stock samba (sorry don't know it and don't have access right now) thanks charles >Someone else has

mjt@tls.msk.ru wrote: > > I posted some messages about this, but there is still NO RESPONCE AT ALL!! > As I see, more and more users encountered this problem -- > oplocks code in 2.x (starting from all betas and now in 2.0) DOES NOT WORK!!! > > David! You can place "oplocks = no" into your [global] section and all > will be fine. But problem is opened! > There