similar to: adding Windows client reverse dns entries

On 2016-11-05 07:46, Mike Lykov via samba wrote: > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > >> Once again, reading here and there and I am confused. >> >> I thought the W clients (both W7 and W10) reverse dns PTR records where >> added by the ADDC automatically. >> >> This mornings testing (nslookup of client IP addresses) is not

On 2016-11-05 08:21, Rowland Penny via samba wrote: > On Sat, 05 Nov 2016 08:07:18 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-11-05 07:46, Mike Lykov via samba wrote: > > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > > Once again, reading here and there and I am confused. > > I thought the W clients

>> I thought the W clients (both W7 and W10) reverse dns PTR records >> where added by the ADDC automatically. >> Yes, correct if your setup is correct then yes this works. With a default windows install and with a few GPO changes. > Early samba4 versions does not support (or have a buggy support) for auto->register PTR recors, as far i remember. I use windows to let

On 2016-11-07 03:06, Rowland Penny via samba wrote: > On Mon, 7 Nov 2016 09:51:50 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > I thought the W clients (both W7 and W10) reverse dns PTR records > where added by the ADDC automatically. Yes, correct if your setup is correct then yes this works. With a default windows install and with a

A few days ago I demoted my first DC (a v4.2.14, I think) and thought the demote had gone well. Now, when I run "samba-tool dnsupdate --verbose" I can see references to the first DC that remain. Unfortunately, that DC no longer exists so I simply cannot demote it again. Following the instructions on the "Demote a Samba AD DC" page "Verifying The Demotion" section, I

On 2016-11-14 08:39, L.P.H. van Belle via samba wrote: > Is this on a windows 7 or 10 client or both? > Are you useing \\FQ.DN\share or \\hostname\share > Try the FQ.DN, as Microsoft advices. > > And where are the TLS parameters in the below config. > Did you set this up? > > Greetz, > > Louis > >> -----Oorspronkelijk bericht----- >> Van:

On 09/20/2016 04:09 PM, Bob of Donelson Trophy via samba wrote: > On 2016-09-20 15:00, James Knott via samba wrote: > >> On 09/20/2016 03:54 PM, Bob of Donelson Trophy via samba wrote: >> >>> All of us are having trouble with the "Anniversary update" to W10 >>> Version 1607. If you can roll back to previous Version 15?? (sorry can't >>>

I just transfered fsmo roles from one DC to my newer DC and all went well. Thank you Samba team!! Great documentation, BTW. My domain (basically) consists of one ADDC, one member server and two W10 clients and one W7 client. While setting up the newer DC had been running some nslookup on the DC's and decided to run nslookup on my member server and do not know if I have discovered and

On 2016-12-01 10:00, Rowland Penny via samba wrote: > On Thu, 01 Dec 2016 09:20:15 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> From: Bob of Donelson Trophy via samba <samba at lists.samba.org> >> To: SAMBA MailList <samba at lists.samba.org> >> Subject: [Samba] member server resolv.conf question >> Date: Thu,

On Sat, 05 Nov 2016 08:43:05 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2016-11-05 08:21, Rowland Penny via samba wrote: > > > On Sat, 05 Nov 2016 08:07:18 -0500 > > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > > > On 2016-11-05 07:46, Mike Lykov via samba wrote: > > > >

On 2016-10-10 08:33, Marc Muehlfeld via samba wrote: > Hi Bob, > > Am 10.10.2016 um 13:18 schrieb Bob of Donelson Trophy via samba: > >> I noticed the "Joining a Samba DC to an Existing Active Directory" wiki >> page was updated yesterday (October 9, 2016.) > > yes, I'm currently doing a lot of major updates, rewrites, enhancements, > and so on.

On Sat, 05 Nov 2016 08:07:18 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2016-11-05 07:46, Mike Lykov via samba wrote: > > > 05.11.2016 16:09, Bob of Donelson Trophy via samba пишет: > > > >> Once again, reading here and there and I am confused. > >> > >> I thought the W clients (both W7 and W10) reverse dns

I have a member server running Ubuntu 16.10, Samba 4.4.5 that is serving files to W10 and W7 clients. Things appear fine and suddenly the server share disappears and the W clients "cannot see" the server. The client error message is: "The device or resource (member hostname) is nt setup to accept is not setup to accept connections on port "The file and print sharing

On 09/20/2016 03:54 PM, Bob of Donelson Trophy via samba wrote: > All of us are having trouble with the "Anniversary update" to W10 > Version 1607. If you can roll back to previous Version 15?? (sorry can't > remember) that MIGHT correct your issue. No promises. It's definitely that update that caused the problem.

I have been working towards retiring my first member server. (Sernet 4.2.14??) Moved all the user files, checked and double checked the ACL's and all seems good. My users redirect folders to my member servers with a GPO policy. I use roaming profiles (again via GPO) that have been confirmed as working properly against the newer member server (running Samba 4.5.3 from source.) Now, the

On 30/01/15 21:19, Bob of Donelson Trophy wrote: > > > Both DC1 and member server return nothing on 'getent passwd > Administrator' > > I have no other users other than 'root' and 'Administrator' on all three > (DC1, DC2 & member.) > > My plan was to get file permissions (aka profiles) working and add some > test users. > > How do

W7 client domain member? yes. Logged in as domainAdministrator? yes. "SeDiskOperatorPrivilege" set? yes Read "/Setup_and_configure_file_shares_with_Windows_ACLs"? yes. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [2] "Everyone deserves an award!!" On 2015-01-28 10:40, Marcel de Reuver wrote: >

I have been accessing Windows shares on Windows 7 and 10. However, the update last month seems to have killed samba access. The shares are accessible in Windows. Any idea why samba no longer works with W10 and what can be done about the problem? I'm running openSUSE 13.1. I have enabled the firewall rule as describe here, but it doesn't help, nor does turning off the firewall. tnx jk

I am setting up W7 profiles following the "Samba & Windows Profiles" on the Sambawiki. If it matters, I have two functional DC's and one member server. When I run '# chmod 1770 /srv/samba/profiles' (on the member server) the permissions changed to: root at mbr01:~# ls -alh /srv/samba/profiles total 12K drwxrwx--T+ 2 root root 4.0K Mar 1 10:21 . drwxr-xr-t 5 root

On 2016-09-19 14:08, Marcio Vogel Merlone dos Santos via samba wrote: > Em 09/09/2016 12:48, Luc Lalonde via samba escreveu: > >> We have some machines that have updated to the Windows 10 anniversary update (1607) that are having roaming profile sync problems. >> >> Before I search the event logs or provide details, has anyone experience profile sync wierdness? >>