similar to: NT Domain Integration

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

Greetings, I recently promoted a new DC in our existing domain. The existing domain consists of two domain controllers running Samba Version 4.2.0pre1-GIT-b505111 on Ubuntu 12.04 Server. The newly promoted DC is also running Ubuntu 12.04 server, but Samba Version 4.1.8. The promotion was successful and after a few tweaks to DNS, replication is working. It is however failing on some items and

Hello, I'm about to deploy Samba PDC and several BDCs. As far as I understand Samba and domain logons, this means that a user will be able to log onto any server, with his workstation choosing a domain controller that is probably the closest/fastest etc. one. As a consequence, this also means, that on each server there has to be a copy of a profile of a given user, right? If so, how can

Hello everyone, the time for me to use a OpenLDAP server is getting closer ( :( yikes..I'm still scared sorta) , I currently have a Samba PDC with tdbsam with 50 users goes fine, our company will grow (doing our best) in this year by a minimum of 25-30 computers, and I've stuided the TOSHARG , and it says that for every 50 computer a bdc is suggested. The questions : 1.how does

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

Hi All, I'm using samba 2.0 on Solaris 5.5.1 with the smb.conf that is included. I want to allow a user called admin_auto to connect to some shares to scan them for viruses from an nt workstation. I don't want any other user to be able to use the shares, and I've made them not browseable. My problem is that anyone can connect to the share without a password and use it. They just

Samba List - Like most people new to Samba, I'm having the most trouble setting up permissions. First of all, let me get this straight: if you use security = domain, you do not need to set up individual users on the Linux box (in an NT domain), correct? I want all users to be able to read the files in LSSNET, and only specific users allowed to write to it. If the folder is 775 and the

You can remember this. If you join a server, that make sure that that servers "hostname" gets an A and PTR record. The PTR is most important. Now if you creat a CNAME now, through PTR it knows its "original" hostname And kerberos works, this is how i do all my setups. As example. REALM : INTERNAL.EXAMPLE.COM FQDN : test-dc1.internal.example.com Hostname: test-dc1 SPN

> > > Adding pdc1 to the hosts file (c:\windows\system32\drivers\etc\hosts) > did > not make a difference. After adding pdc1 to lmhosts, "net use > \\pdc1" did > work. So in the case of pdc1 one, the name is being resolved as a > netbios > name (i.e. via lmhosts) not a tcp/ip type name (i.e. via dns or hosts) > > But then why does "net

I have a samba domain with a Samba 3.4.x PDC (compiled from source on Solaris 10) and two Samba 3.0.x BDC's (Sun-bundled Samba on Solaris 10.) XP clients use DHCP. When on the LAN, DHCP includes WINS server (the WINS server is one of the Samba 3.0.x machines.) We also have a VPN for remote client access for Windows XP machines. XP machines could include home PC's (not in the domain)

I have the following PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 PDC is configured to be the WINS server for everything, including XP Pro clients and other Samba machines. PDC# testparm -v | grep master Load smb config files from /etc/sfw/smb.conf ... Server role: ROLE_DOMAIN_PDC ... Press enter to see a dump of your service definitions preferred

update: - fixed smbd for win95-style profile-locating (it now works, thank you to everyone who sent in log files to get this fixed) - various modes tested and confirmed as working: * ROLE_STANDALONE security = user encrypt passwords = yes domain master = no domain logons = no * ROLE_DOMAIN_PDC security = user encrypt passwords = yes domain master = yes

Folks, Not even a peep. Did I ask the wrong question or am I on the wrong list? I don't mind pointers to more information.... I own both the recent books on Samba 3 and they are very good, but I seem to be missing something. Anyways... Thanks and hope to hear from you soon, Michael J Barber WPTZ/WNNE Computer Services Administrator p 518-561-5555 x563 m 518-572-6639 f 518-561-5940

smb.conf (relavent section) [global] workgroup = WPTZ security = DOMAIN map to guest = Bad User password server = WPTZSRV1, WPTZ-BDC username map = /etc/samba/smbusers log level = 2 syslog = 3 time server = Yes printcap cache time = 750 printcap name = cups logon path = \\%L\profiles\.msprofile logon

Hello list, I'd like to share with you my experience with Samba4 AD-DC and Mac OSX Mountain Lion 10.8.4 joining it to the domain and using kerberos implementation on OSX to authenticate users against the AD. Maybe it's useful to anyone here My scenario: My domain controller is on a remote location and I've got my router (Mikrotik) setup to create a PPTP tunnel to the w2k8 server

Hi all! I'm configuring Samba 3.0.1 on Solaris 9 (rel s9_58shwpl3) Sparc. Have successfully installed Ldap libs, Krb5 libs, and, finally - Samba. Trying to join W2KSP4 domain. net rpc join -S dc01 -U Administrator Gives bash-2.05# /usr/local/samba/bin/net rpc join -S dc01-tmn -U Administrator Password: Joined domain MYDOMAIN. Now i start winbindd. The smb.conf file is:

Hello, we are trying to upgrade from 2.0.5a to 2.0.6 (under Digital Unix and Windows 95 clients). After the upgrade we get a lot of errors like these: >>>>>>>>>>>>>>>>>> Log <<<<<<<<<<<<<<<<<<< Jan 4 16:18:35 fissio smbd[31799]: [2000/01/04 16:18:35, 0] smbd/service.c:make

Hi Brian, On Thu, 16 Feb 2017 01:20:46 -0800, brian lamb via samba wrote: > Configured as you mention, and prior with the other tweaks I had in the first place, Im getting the same results, which is "FSUTIL utility requires a Local NTFS Volume", and mapping it. Hmm, this works fine for me against a Samba 4.4.2 Btrfs backed Samba share. smb.conf: [global] ... store dos

On Thu, July 30, 2020 17:23, Robert Marcano wrote: > On 7/30/20 5:00 PM, James B. Byrne via samba wrote: >> FreeBSD-12.1p7 >> Samab-4.10.15 running in FreeBSD Jail >> >> >> I just wish to ensure that my conclusion respecting Samba, FreeBSD Jails, and >> NTP is correct. >> >> 1. Unless configured otherwise Windows domain clients will query and

Hello In 2 different subnets I have setup 2 identical samba servers (RH 6.5) as fileservers for windows clients. Each is a member of it's own AD Domain (Windows 2003 Servers). The problem: one of them only is accessible and sharing locally. On the windows-client, trying to mount a share gives this error: C:\Users\testuser>net use y: \\samba_server\topfolder /user:testuser System