similar to: Switching form NT PDC to AD

Hi guys, Thanks for those of you whole kept reading after seeing the subject line -- I know, it's like a flashback to about 2000 or so, but for mostly uninteresting reasons, I've got a situation that I wanted to run by the list just in case there's a work around. I have an NT 4 server that's the PDC that my new Samba box, running 3.4.0 w/ "security = domain" uses to

Am Mittwoch, 12. Oktober 2016 schrieben Sie: > Thanks to your help, earned. > > 1. I reinstalled ldap > > 2. remove all entries except sambaDomainName According to your logs, you have had three entries > 2. smbldap-populate > > 3. /usr/local/sbin/smbldap-passwd -s root > > 4. net rpc join -S 127.0.0.1 -U root%secret > > 5. restore from a backup of users,

Dear group, I know this is not the first post related to NT domain authentication with Samba. I actually did manage to set up NT domain authentication on a FreeBSD 5.4 using Samaba 3.0.12 based on infos I mostly found here. I'm stuck however to get the same thing working on a FreeBSD 4.11. The steps I've tried to follow are described in the Samba Howto. Configured/compiled Samaba 3.0.20b

Am Dienstag, 11. Oktober 2016 schrieben Sie: > On 11.10.2016 13:52, Harry Jede via samba wrote: > > On 10:43:49 wrote Gavrilov Aleksey via samba: > > Until now, you have destroyed your domain. > > Is the ldap directory on localhost in production or is this pc in a > > test lab? > > a copy of the old server ldap > > >> How do I introduce a new PDC in a

Hello everyone, i have been searching the whole day, trying ANY solution offered by the internet and before headbanging against the wall would like to try asking for your help. As many others, i am haveing problems loading the Rcmdr package with Macbook running Tiger 10.4.11. X11 version updated to the last one after having manually installed. I have also installed (obviously) the Rcmdr package

Hi all, I want to make a Samba Sever as amember of a Domain, using a Windows NT 4.0 as PDC. I have my smb.conf configured to do this, but users ca't connect on Samba useing the Windows NT account. Is it possible or I have to create them on a smbpasswd to make them login on it? I have a Samba Server 3.0.7 running under a Slackware Linux 10.0, with Kernel 2.6.8.1. I'm sending my smb.conf

We are in the process of upgading our windows 2003 pdc's to windows 2008Rr2. No problem there, but our samba/winbind clients are beginning to show some strange behaviour. In the beginning we saw a lot of messages appear in the logfiles. Example : -------------- pr 1 14:07:36 srvxxx winbindd[5148]: rpc_api_pipe: Remote machine pdc.company.net pipe \NETLOGON fnum 0x4003returned critical

Hi I am trying to get my linux box authenticate from an NT PDC. I am using samba 2.2.11. The linux box joins the pdc by the smbpasswd -j domain -r pdc -U admin command but it is not getting authenticated by the PDC . has anyone tried this and have some info/doc on this .. this is my system-auth file #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time

Hi all, I have got one query on QoS in bridging in Linux My question is, when we define IP QoS ( using a tc command ) queuing discplines and classses, will these be applicable to bridged frames also ? I mean the packets that take IP path will be sent out according to QoS we defined, but the bridged/ swithced packets will also be sent according to this defined IP QoS classses ? My doubt is

On 13/05/2020 18:52, David Lomax via samba wrote: > Hi all, > > I have a question about a multi-homed Samba file server and interoperability > with AD. It's a bit complicated, so please bear with me. Your problem is probably because your DC knows your Samba ADS client by its 192.168.42.0/24 Ipaddress. Also, why only use 10G on part of your network, surely the network speed

Hi Rowland, Thank you very much, you were spot on. I had changed the Windows 7 client to LM compatibility level, and now that I reverted it back to 5 (use NTLMv2) it works. It was this registry key that made it start working: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "LmCompatibilityLevel"=dword:00000005 I was ignoring the old LM options and the "NTLMv1" in

All, I have the following problem using Samba 3.0.28 on Solaris 8 in combination with Windows NT (no ADS): When I set permissions on shares (using "Computer Management from Windows"), Samba doesn't seem to act accordingly. If for example I have a share called HOME with the following permissions: Everyone (full control) My user account in the domain (full control) This way I can

HI, I am sorry I forgot to post the problem that I am having. It is the same issue who posted this e-mail originally. Please let me know what should I do to fix the problem that I am having. Edit /etc/samba/smb.conf [global] realm = KERBEROS.REALM security = ADS encrypt passwords = yes password server = kerberos.server Edit /etc/krb5.conf [libdefaults] default_realm = KERBEROS.REALM

Please help. I've been searching for days, trying nearly everything I can find that seems relevant, but I can't get this working. I am able to create users, login to Windows systems joined to the SAMBA domain as those users, but filesystem ACLs on Windows Domain Member Servers do not work which I suspect is due to my IDMAP OU is empty. wbinfo -u returns "Error looking up domain

On 11.10.2016 17:22, Harry Jede via samba wrote: > Am Dienstag, 11. Oktober 2016 schrieben Sie: >> On 11.10.2016 13:52, Harry Jede via samba wrote: >>> On 10:43:49 wrote Gavrilov Aleksey via samba: >>> Until now, you have destroyed your domain. >>> Is the ldap directory on localhost in production or is this pc in a >>> test lab? >> a copy of the

Hi all, I have a question about a multi-homed Samba file server and interoperability with AD. It's a bit complicated, so please bear with me. I've been running Samba 4.11.6 as an AD server (two DCs) for a while (in RFC2307 mode) in a mixed Windows/Linux environment. I have a server running Proxmox (Debian) with Samba 4.9.5 and it is sharing my huge ZFS volume via Samba to Windows

Hi folks, today I tried to switch from a samba 2.2.2 PDC to a samba 2.2.7 PDC. Everything semed to be working fine with smbclient. Windows user couldn't log on, but with following differences: * users belonging to the domain admin group could log on from Win2k boxes * normal users couldn't log on from win2k boxes, with the usual "check if you didn't mis-type

Hi, you should reboot your system one and getent passwd should the only show local users. su - DOMAIN+user should still work then... Mit freundlichem Gru?, Dirk Laurenz Systems Engineer Fujitsu Siemens Computers Sales Central Europe Deutschland Professional Service Organisation Nord / Ost Hildesheimer Strasse 25 30880 Laatzen Germany Telephone: +49 (511) 84 89 - 18 08 Telefax: +49 (511)

Hi list, I have samba-3.0.2-2 rpm installed on Redhat Enterprise Linux 3 AS kernel version. I've been using the Samba 3 How-To and messages on various mailing lists to join Samba to an AD domain and authenticate using winbind/pam. So far Samba has successfully become a member of the AD domain and can browse file servers using smbclient but I haven't been able to get winbind working -

I am investigating putting samba servers at our ISDN connected remote sites. We have an NT PDC as well as a large samba file server at our central site. This system would replace the existing remote NT BDC setup which requires many visits from the NT administrators. Are there any guidelines on what samba and NT settings work best in this environment? For example: - How should user's