similar to: "read error" when accessing a file on mounted samba share (Linux)

Hello, whenever I try to copy a new file from windowsXP (2K also) to a samba share which is NFS mounted on the samba server, I get an error on the client: "impossible to copy file.txt: the process cannot access the file because an other process has locked a part of it" (my english translation of the french message I have !) It worked fine before (3weeks ago) and I think that problem

I was trying to work through a PDC problem that I was having with 3.0.23a noted in bug 3964. I didn't know how to apply the offered patch and my distro, FC4, has not offered an update yet to 3.0.23b so I thought that I would revert to a previous version that is not affected by this bug. I forced an install of 3.0.23 samba, common, and client and now rpm reports that I have two versions of

I have a server roark (fedora core 5 with samba 3.0.23a-1.fc4.1) with a home directory awilliam. I'm trying to mount it on my linux workstation (fedora core 5, samba 3.0.23a-1.fc5.1). On my workstation I do: mount -t cifs "//roark/awilliam" /mnt/roark-awilliam/ -o username=awilliam,password=xxxxxx and when I cd to /mnt/roark-awilliam, ls works, but if I cat a file I get the

I made a post a few weeks ago regarding this but was unable to find a solution. This is the situation: + I'm attempting to upgrade from samba 3.0.23a (Fedora core package 3.0.23a-1.fc4.1) to the latest version compiled from Samba source. + When using the latest version (or 3.0.25b), Win clients can authenticate & access shares fine, but attempting to open any kind of MS Office doc (not

I'm not sure that the problem is with net ads join but I'm in desperate need of help either way. Using smb Version 3.0.23a-1.fc4.1 I do a net ads join I get the below error: [root@mustang tmp]# net ads join -U exservice@MACHINEVISIONPRODUCTS.COM exservice@MACHINEVISIONPRODUCTS.COM's password: Using short domain name -- MVP Failed to set servicePrincipalNames. Please ensure that the

Hi all, I wrote a small script (developed and testet on Solaris 8), which automates the generation and installation of the steps needed to put keys in place. I you are interested to take it, feel free to do it. -- *** Freundliche Gruesse **** Best regards *** Anton Burkhalter Dipl. El. Ing. HTL Mobile:+41(0)78 844-0290 mailto:anton.burkhalter at gmx.net

My samba shares aren't working with ACL access since the upgrade. Here is an example of the error from /var/log/messages Dec 14 12:44:17 gfm-atlas smbd[14365]: [2006/12/14 12:44:17, 0] smbd/service.c:make_connection_snum(911) Dec 14 12:44:17 gfm-atlas smbd[14365]: '/usr/GFM_Shares/Users/Receiving' does not exist or permission denied when connecting to [GF_Receiving] Error was

smbldap-tools in a working environment suddenly unable to add or modify users. smbldap-useradd kenh Use of uninitialized value in die at /usr/lib/perl5/vendor_perl/5.8.6/Convert/ASN1/_decode.pm line 111. Perl debug trace [root@steel ~]# perl -d /usr/sbin/smbldap-useradd jimh Loading DB routines from perl5db.pl version 1.28 Editor support available. Enter h or `h h' for help, or `man

samba SVN 17972, Linux 2.6.16-1.2096 That should be about the same as 2.0.23c getent passwd works to list domain accounts getent group works to list domain groups kinit works for domain accounts wbinfo -u lists domain user accounts wbinfo -g lists domain group accounts In order to access roaming profiles and any shares from 2000 & XP clients, I have to map DOMAIN\username to username in

On 1/2/20 1:00 AM, L.P.H. van Belle via samba wrote > Yes, you can use : > > install -d /var/lib/samba/bind-dns/ -o root -g bind -m 770 > And rerun it. > > Just dont forget to adjust the bind config files also. So after moving everything, fixing the bind config and restarting there is still an issue. While the forward zone myhome.nurdog.com is working fine,? the reverse zone

On 22/12/2019 18:20, Paul R. Ganci via samba wrote: > Hi All, > > A while ago I replaced a Samba AD on old hardware with a another AD on > newer hardware. Everything went smoothly including the demotion of the > old AD. However after I did some cleanup DNS records and turned off > the old hardware I noticed that there still was a NS record associated > with the old AD. So

On 1/1/20 3:49 PM, Paul R. Ganci via samba wrote: > I have been running this domain for quite a while and don't quite > understand why this problem would occur. What is somewhat strange is > the location of certain files. For example my dns.keytab is located here: > > > > ls /var/lib/samba/private/dns.keytab > /var/lib/samba/private/dns.keytab > > Does anyone

I'm trying to understand why my group mapping doesn't work in a consistent fashion. I've studied "Important Samba-3.0.23 Change Notes" & chapter 13 of TOSHARG but am still struggling. I'm on 3.0.23a-1.fc4.1 (Fedora Core 4) as a PDC, tdbsam backend. 'net groupmap list' gives this: Domain Power Users (S-1-5-21-1365060548-1276164359-2333037906-31037) ->

I'm running samba3.0.23 on a fedora core 4 box. I successfully joined the samba server into an AD and shared home directories on the fc4 box. (Actually, the home directories on that fc4 box are mounted from a NFS server) I can access the top level of my home directory without any problems because the permission is set as 755. But I can't access directores with permissions like 700. So I

Hi, I have working master & slave OpenLDAP servers the Samba PDC works correctly when using either as the passdb backend. However, when configuring for LDAP failover as per this doc: http://samba.org/samba/docs/man/Samba-Guide/2000users.html Samba doesn't work & the logs fill up with this: ldap_initialize: Bad parameter to an ldap routine Connection to LDAP server failed for the 1

On 09/11/2016 10:38 AM, Paul R. Ganci via samba wrote: > On 09/11/2016 01:23 AM, Rowland Penny via samba wrote: > Rowland, thanks for your reply. What you describe is pretty simple in > principle. It is the details about which I am confused. There are 3 > aspects of a Samba 4 AD that have to be properly setup for the AD to > function correctly. Namely the Samba configuration,

On Sun, 2 Oct 2016 22:01:32 -0600 "Paul R. Ganci via samba" <samba at lists.samba.org> wrote: > > > On 10/02/2016 07:57 PM, Paul R. Ganci via samba wrote: > > > > > > On 10/02/2016 06:15 PM, Paul R. Ganci via samba wrote: > >> On 09/11/2016 10:38 AM, Paul R. Ganci via samba wrote: > >> > >>> On 09/11/2016 01:23 AM, Rowland

On 10/02/2016 07:57 PM, Paul R. Ganci via samba wrote: > > > On 10/02/2016 06:15 PM, Paul R. Ganci via samba wrote: >> On 09/11/2016 10:38 AM, Paul R. Ganci via samba wrote: >> >>> On 09/11/2016 01:23 AM, Rowland Penny via samba wrote: >>> Rowland, thanks for your reply. What you describe is pretty simple >>> in principle. It is the details about

Hi All, A while ago I replaced a Samba AD on old hardware with a another AD on newer hardware. Everything went smoothly including the demotion of the old AD. However after I did some cleanup DNS records and turned off the old hardware I noticed that there still was a NS record associated with the old AD. So I went to the wiki page https://wiki.samba.org/index.php/DNS_Administration and

Hi. I''m back. Unfortunately I can''t get xrcise working. Here is the sample xrc file and the resulting error messages: =============== TestWxFb.xrc ========================================= <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <resource xmlns="http://www.wxwindows.org/wxxrc" version="2.3.0.1">