similar to: setting up a new ADS infrastructure

On 13/06/2019 18:21, Stefan Froehlich via samba wrote: > I try to set up a small ADS infrastructure: 1 samba ADS-controller, > 1 samba file server, 2 Linux and 6 Windows clients. Starting with > controller and file server, quite a lot of things work, but not > everything. Here it starts getting complicate: looking for manuals, > googling for error messages leads to lots of different

On Thu, Jun 13, 2019 at 08:10:01PM +0100, Rowland penny via samba wrote: > On 13/06/2019 19:57, Stefan Froehlich via samba wrote: > >On Thu, Jun 13, 2019 at 07:02:27PM +0100, Rowland penny via samba wrote: > >>On 13/06/2019 18:21, Stefan Froehlich via samba wrote: > >>>File server and Linux clients shall use the AD-backend, so I read > >>>and followed

On Thu, Jun 13, 2019 at 07:02:27PM +0100, Rowland penny via samba wrote: > On 13/06/2019 18:21, Stefan Froehlich via samba wrote: > >File server and Linux clients shall use the AD-backend, so I read > >and followed <https://wiki.samba.org/index.php/Idmap_config_ad>. > >There it says: > > > >"Whichever setting you use, the group (or groups) set as the

On Sun, Jun 23, 2019 at 03:34:08PM +0200, Stefan Froehlich via samba wrote: > No need to be sorry - most likely I'll the whole setup from scratch. Did so (I am following a script by now, so it does not take too long), but I feel more and more lost - there must be always something different I do wrong: Now I configured DNS the other way round, pointing every host to the DC and using

On Sun, Jun 23, 2019 at 12:21:58PM +0100, Rowland penny via samba wrote: > You are coming from a PDC domain to an AD DC domain, easiest thing first, > you do not use 'wins' with an AD DC, you use 'dns'. I know the latter (had to delegate the zone in bind after all), but "wins support=yes" must have been created either by Debian or by "domain provision".

On Mon, Jun 24, 2019 at 09:12:00AM +0100, Rowland penny via samba wrote: > On 24/06/2019 08:39, Stefan Froehlich via samba wrote: > >On Sun, Jun 23, 2019 at 03:34:08PM +0200, Stefan Froehlich via > >samba wrote: (I am following a script by now, so it does not take > >too long) > > Can I see your script ? > > You may be doing something wrong. These are only

On 23/06/2019 13:34, Rowland penny via samba wrote: > On 23/06/2019 13:16, Stefan Froehlich via samba wrote: >> On Sun, Jun 23, 2019 at 12:21:58PM +0100, Rowland penny via samba wrote: >>> You are coming from a PDC domain to an AD DC domain, easiest thing >>> first, >>> you do not use 'wins' with an AD DC, you use 'dns'. >> I know the

On Fri, Jun 14, 2019 at 09:09:58AM +0100, Rowland penny via samba wrote: > On 14/06/2019 05:50, Stefan Froehlich via samba wrote: > >as I can do ssh logins with this account, even based on group > >membership, the unix side of the job seems to be quite settled. > >The windows side will have to wait a little bit as it requires my > >physical presence. > Windows should

Samba Machine 2 ethernet interfaces, 1 is DHCP via ISP and another is 10.10.0.1 VPN (POPTOP) is installed on the server (Server IP: 10.10.0.1, Client IPs: 10.10.0.2-255) Trying to connect to samba server (as \\10.10.0.1\NetRender) from windows xp client connected to the server via VPN and received ip of 10.10.0.2 Here is smb.conf [global] workgroup = InverseForge security = SHARE browseable

On 24/06/2019 12:41, Stefan Froehlich via samba wrote: > On Mon, Jun 24, 2019 at 10:22:41AM +0100, Rowland penny via samba wrote: >> On 24/06/2019 10:00, Stefan Froehlich via samba wrote: >>> On Mon, Jun 24, 2019 at 10:52:07AM +0200, Stefan Froehlich via samba wrote: >>>> <http://froehlich.priv.at/www/samba/> >>> Always try your own links before posting

On 24/06/2019 10:00, Stefan Froehlich via samba wrote: > On Mon, Jun 24, 2019 at 10:52:07AM +0200, Stefan Froehlich via samba wrote: >> <http://froehlich.priv.at/www/samba/> > Always try your own links before posting them... it must be > <http://froehlich.priv.at/samba/> of course, sorry. > No problem, I just refreshed the old page I had open ;-) You have this on the

Hi, I setup a new samba file server (in a priviledged Proxmox container using the Debian 12 template) and apparently it works fine. In log I see every 10 seconds: write_browse_list: Fatal error - cannot find my workgroup DMYDOM Google found one hint telling it should set "network = ip", but man page does not explain such an option. Another hint suggests it could be related to an

On Mon, Jun 24, 2019 at 12:56:28PM +0100, Rowland penny via samba wrote: > On 24/06/2019 12:41, Stefan Froehlich via samba wrote: > >| [2019/06/24 13:33:06.220212, 5] ../source3/auth/token_util.c:866(debug_unix_user_token) > >| UNIX token of user 0 > >| Primary group is 0 and contains 0 supplementary groups > >| [2019/06/24 13:33:06.220255, 5]

On 14/06/2019 05:50, Stefan Froehlich via samba wrote: > On Thu, Jun 13, 2019 at 08:10:01PM +0100, Rowland penny via samba wrote: >> On 13/06/2019 19:57, Stefan Froehlich via samba wrote: > >> It already might have ;-) >> >> wbinfo reads directly from AD, but doesn't mean that? the OS knows >> your users & groups, does 'getent passwd test'

On 23/06/2019 14:34, Stefan Froehlich via samba wrote: > No need to be sorry - most likely I'll the whole setup from scratch. > But just to be sure and to avoid new mistakes, after re-reading the > samba wiki: > > I understand that they use the same SAMDOM.EXAMPLE.COM as DNS *and* > Windows domain which is (for legacy reasons and for a smoother > transition) something

On Sat, 16 Mar 2024 15:19:54 +0100 Steffen Dettmer via samba <samba at lists.samba.org> wrote: > Hi, > > I setup a new samba file server (in a priviledged Proxmox container > using the Debian 12 template) and apparently it works fine. > > In log I see every 10 seconds: > > write_browse_list: Fatal error - cannot find my workgroup DMYDOM > > Google found

Hi, I have a Samba 3 PDC running with around 20 Windows XP/2K clients. The PDC and the clients are in different subnets. I recently decided to add a Samba 3 BDC in the same subnet as the clients, to give some failover and also to reduce across-switch traffic. After creating the BDC, I restarted one of the clients but don't see it establishing connection with the BDC, instead it connects as

On 24/06/2019 13:34, Stefan Froehlich via samba wrote: > Both of them, yes, and wbinfo(1) works as well: > > | sfroehli at herakles:~$ getent passwd test > | test:*:10001:10000:Max Mustermann:/home/test:/bin/bash > | sfroehli at herakles:~$ getent passwd SYNTHESIS\\test > | test:*:10001:10000:Max Mustermann:/home/test:/bin/bash > | sfroehli at herakles:~$ wbinfo

On Sun, Jun 23, 2019 at 01:53:43PM +0100, Rowland penny via samba wrote: > You have a DC in the 'synth.intern' dns domain, yet the Kerberos Realm is > 'SYNTHESIS.SYNTH.INTERN', it should be 'SYNTH.INTERN' > > The Unix domain member is in the 'synthesis.synth.intern' dns domain and its > Kerberos Realm is 'SYNTHESIS.SYNTH.INTERN' > > I

Hi, I am migrating a ubuntu server to a centos one. The ubuntu server is working and new server even tough it's running I can't join the domain from a new machine. The new server is not on production so the client (win xp) is connected via a crossover cable. The error message on the client is something like user/password invalid (I am using the root user/password of the server). The