similar to: samba share an NFS import?

Hi. I am getting loads of errors "no backend defined for idmap config MYDOMAIN" after I upgraded from 3.5 -> 3.6 a couple of days ago. I read http://wiki.samba.org/index.php/Samba_3.6_Features_added/changed and did what man smb.conf suggested: idmap config MYDOMAIN : backend = tdb idmap config MYDOMAIN : range = 500-1999999 yet I still receive those errors. I used

Hi guys, I've joined CentOS 7 successfully to AD as member server, and set couple of shares. But, limiting access by listing groups, or forcing group write isn't working. Samba is clearly having issues with groups. This is example share not working at all (constantly asking for authentication): [tools] path = /data/tools/ comment = Web development

Hi, I'm running samba on a fully updated CentOS-6.3 box as a fileserver exporting to Win7 clients. samba-3.5.10-125.el6.x86_64 Anybody got an idea what is causing the following error message. It's filling up my logs. [2012/09/19 11:40:20.710031, 1] smbd/server.c:267(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/09/19 11:40:40.729746,

Hi, folks, Just ran into a problem: someone with a new laptop, running Win 10, version 1709, tried to map their home directory (served from a CentOS 6.9 box, and it fails, with Windows complaining that it no longer supports SMBv1, and if you go to their site, you can install support for that manually.... The server running samba can *not* be updated to 7 - we have a lot of stuff based off

After attempting to upgrade to version 3.6.23 I discovered that I was unable to authenticare against another Samba server running as a PDC and using winbind. Due to time constraints, I erased the samba setup and reinstalled version 3.6.9. Everything went back to normal. Is this a bug or did something on the configuration side change?

Really sorry to re-post but it looks like my thread has been buried and had no responses. I am using samba3.6 winbind to connect a RHEL5.8 linux box to a new Windows Server 2012 Active Directory which has Unix Identity Mapping installed. So I have all the uidNumber/gidNumber stuff in the windows schema. I am able to log in but I am not getting the right uid/gid. My AD uids start at around 800.

On 06/28/2018 07:30 AM, mark wrote: > Just ran into a problem: someone with a new laptop, running Win 10, > version 1709, tried to map their home directory (served from a CentOS > 6.9 box, and it fails, with Windows complaining that it no longer > supports SMBv1, and if you go to their site, you can install support > for that manually....

I'm exporting a directory, firewall's open on both machines (one CentOS 6.6, the other RHEL 6.6), it automounts on the exporting machine, but the other server, not so much. ls /mountpoint/directory eventually times out (directory being the NFS mount). mount -t nfs server:/location/being/exported /mnt works... but an immediate ls /mnt gives me stale file handle. The twist on this: the

I am using samba/winbind to connect a RHEL5.8 linux box to a new Windows Server box which has Unix Identity Mapping installed. So I have all the uidNumber/gidNumber stuff in the windows schema. I am able to login but I am not getting the right uid/gid. My AD uids start at around 800. FYI I am new to winbind. Apparently the ID mapping has changed again in samba 3.6 but I'm not really

I have a few C5 machines on an isolated LAN that connect to a RHEL5 server via NFS and NIS for authentication. I discovered that one of the C5 workstations worked fine for NFS exporting, but refused to collaborate with the EL5 server for NIS user authentication. I had successfully connected other systems to this server without issue, but this machine was finicky. I had initially enabled

m.roth at 5-cent.us wrote: > m.roth at 5-cent.us wrote: >> I'm exporting a directory, firewall's open on both machines (one CentOS >> 6.6, the other RHEL 6.6), it automounts on the exporting machine, but >> the >> other server, not so much. >> >> ls /mountpoint/directory eventually times out (directory being the NFS >> mount). mount -t nfs

So, we're doing a bad thing and re-exporting an NFS file system via Samba. For the most part it's always worked fairly well and we've been cognizant of the various locking scenarios that can come up. Recently, we've run into issues exposing NFS file systems sitting on RHEL6. Our Samba server runs Solaris 10 and the vendor provided Samba daemon (we're currently at 3.5.5 but

I'm running a piece of network backup software called 'bacula', on a minimal CentOS 6.4 install. I got everything working pretty well, but there's one piece giving me some problem-- a component which gives status info via a GUI. In the past, on previous installations, I could ssh to the bacula server with the -X option, and run the application (called 'bat'), and it would

What is the purpose of FSIDs? I am exporting 30 volumes via NFS. Do I need a FSID option? TIA

Hi, I''m happily aware of the way that there is no concept of unmanaging something and when this is in the context of a file ownership or whatever, then that makes sense. But when this is applied to things like nagios configuration data the principle seems to come unstuck. Or at least, it seems so to me. Say I have a nagios_service which uses another template nagios_service. I am about

Hi, I am trying to get the most out of my 40TB xfs file system and I have noticed that the inode64 mount option gives me a roughly 30% performance increase (besides the other useful things). The problem is that I have to export the filesystem via NFS and I cannot seem to get this working with the current version of nfs-utils (1.2.3). The export option fsid=uuid cannot be used (the standard

I had my samba printer shares working after many hours of struggling with the samba.conf file. I was happy. Now the printer shares have quit working. I checked the yum log to see if anything had been changed. Nothing applicable seems to have been changed. I've been surfing the net for the last couple of days trying to find a solution to the problem but I find many outdated and

Hi, thanks for all the feedback and topics. May be I can/should draw a better picture of my settings and question. We "still" use samba 3.6.9-167 from Red Hat with an openldap backend. I tried from an older posting somewhere: socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536 But there was no noticeable impact. The log level = 2. Thats all I changed

CentOS 6.2 [mlapier at mushroom ~]$ uname -a Linux mushroom.patch 2.6.32-220.4.1.el6.i686 #1 SMP Mon Jan 23 22:37:12 GMT 2012 i686 i686 i386 GNU/Linux [mlapier at mushroom ~]$ Applicable sections of smb.conf: [global] workgroup = MYGROUP server string = Samba Server Version %v log file = /var/log/samba/log.%m max log size = 50 security = user

I was able to do this by exporting and importing users (including passwords) with the pdbedit samba utility. Look at this: Http://serverfault.com/questions/675938/migrate-samba-users-to-new-server Maybe you need to change the passdb backend 2017-03-28 2:49 GMT-03:00 Mike Lykov via samba <samba at lists.samba.org>: > 27.03.2017 22:48, Santiago Londoño Mejía via samba пишет: >