similar to: Windows client still tries to connect to old AD after replacement

Thanks again Rowland for getting back to me.  Here's my comments below: >> /etc/hosts: >> 127.0.0.1       localhost >> 192.168.0.17    ad.domain.intranet ad >> 192.168.0.21    domain-ad.domain.intranet     domain-ad > > Remove the line above, this is the old AD domain and shouldn't have > anything pointing to the new one. Have deleted this line. 

Hi all, I've decided to completely replace an old AD with a fresh, brand new one - the only thing linking the two is that I've transferred the user profiles & home folders over to the new one and I'm testing this configuration by disconnecting one of the Windows 10 computers from the old AD and then connecting it to the new AD. Old AD: Name - ad.domain.intranet IP -

Hi all, So we have a single AD-DC master, and I'm trying to join a fresh new DC (DOMAIN-ad.DOMAIN.intranet, 192.168.0.11) to the master (ad.DOMAIN.intranet, 192.168.0.17), and I'm using the HOWTO here: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory and I've hit a problem in the section "Built-in User & Group ID Mappings" - when

Ok, I setup a new smb.conf and rebooted. Winbind doesn't seem to pass on the domain users anymore and the DNS Update during domain join still fails. For some reason, although I have all samba 3.5.6. packages installed on this debian squeeze samba -V or samba-tool are unknown commands. Maybe this is why the dns update fails, some missing tools or commands? wbinfo -u and wbinfo -g return domain

I'm sorry it got confusing, changed the topic and I'll try to explain. I am using Jessie on the DC. Server13 is a linux file server and domain member, it is on squeeze. If possible, I do not want to upgrade it. The problem here is, that it does not seem to generate a DNS record when joining the domain and, after setting up the new smb.conf, the users aren't passed on from winbind to

Hello all, Have joined a new DC to an existing active directory consisting of a sole DC.  So, we now have two domain controllers, the original being ad.DOMAIN.intranet (192.168.0.17), and the new one being DOMAIN-ad.DOMAIN.intranet (192.168.0.11).  The old DC is also the file server - I'm aware this is strongly advised against.  I want the new DC to become the file server but can't

Thank you Louis for that answer! Actually I did get kinit and samba_dnsupdate working, though I am unsure how. I tried some changes to krb5.conf in the [realms] and [domain_realm] sections, als well as setting dns_lookup_realm = false to true, but reverted it all back to the initial file: [libdefaults] default_realm = INTRANET.MAYWEG.NET dns_lookup_realm = false dns_lookup_kdc = true After a

Good morning! First of all thanks Rowland for the fast answer yesterday! I realized that samba-technical might have been the wrong mailing list and switched it to the normal samba users list (hopefully it worked, as it does get a bit confusing with spamgourmets sendto addresses!). Unfortunately the problem with samba_dnsupdate remains after the changes. I did changed the smb.conf, krb5.conf, and

Hi guys, thanks again for the quick answers. First, the smb.conf on the linux fileserver. It is quite long, as I took the old file (working version from samba3 configuration) and only made adjustments, like adding the realm. /etc/samba/smb.conf: [global] ### Browsing/Identification ### workgroup = MAYWEG.NET realm = INTRANET.MAYWEG.NET netbios name = server13 smb ports = 139, 445

Hey Louis, thanks for the answer! That sounds like a viable route to go. Of course I'd prefer doing the classicupgrade and having the trust relationship still intact. It did work this way at some point during testing, that's why I find it hard to accept that I have to circumvent the problem like this. Did somebody else lose trust relationships after classicupgrade and found a way to

Hello all, Have joined a new DC to an existing active directory consisting of a sole DC.  So, we now have two domain controllers, the original being ad.DOMAIN.intranet (192.168.0.17), and the new one being DOMAIN-ad.DOMAIN.intranet (192.168.0.11).  I want the new DC to become the FSMO role owner, so I followed the instructions here -

Sigh, hopefully 3rd time lucky! Thank you Rowland and Louis, > > > > I do not use roaming profiles, but I seem to remember that > > they are are > > liberally plastered with SID-RID's. It is the SID that identifies the > > domain, so it is this that is probably causing your computers looking > > for the old DC. > > > > Rowland > >

Try change your resolv.conf from : >nameserver 127.0.0.1 >domain intranet.mayweg.net to nameserver 192.168.11.250 search intranet.mayweg.net >The only thing I was unsure about, was which hostname to enter >for Kerberos >Server and Kerberos admin server when asked during the >installation of the >packages.. Try these defealt settings for kerberos.. You didnt have to

On 20 March 2015 at 17:00, Rowland Penny <rowlandpenny at googlemail.com> wrote: > On 20/03/15 15:47, Timo Altun wrote: > >> I'm sorry it got confusing, changed the topic and I'll try to explain. I >> am using Jessie on the DC. Server13 is a linux file server and domain >> member, it is on squeeze. If possible, I do not want to upgrade it. The >>

Good morning! First of all thanks Rowland for the fast answer yesterday! I realized that samba-technical might have been the wrong mailing list and switched it to the normal samba users list (hopefully it worked, as it does get a bit confusing with spamgourmets addresses!). Unfortunately the problem with samba_dnsupdate remains after the changes. I did changed the smb.conf, krb5.conf, and hosts

can you run these commands and tell us the output. ( copy past it. ) SETFQDN=`hostname -f` SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SETSERVERIP=`hostname -i` echo "==========Test DNS Records ===============================" echo "Testing : dns entries" if [ -z "`host -t SRV _ldap._tcp.${SETDNSDOMAIN}. | grep 'not found'`" ]; then echo

Thank you for the answers Peter and Rowland and sorry to everybody for the spam...switched to another e-mail address and hope my messages will arrive only once from now on. As I wrote in my first mail, Kerberos does work. I can successfully request and list a ticket on the AC DC. kinit administrator at INTRANET.MAYWEG.NET Password for administrator at INTRANET.MAYWEG.NET: klist Ticket cache:

On 20/03/15 11:13, Timo Altun wrote: > Hi guys, > > thanks again for the quick answers. First, the smb.conf on the linux > fileserver. It is quite long, as I took the old file (working version from > samba3 configuration) and only made adjustments, like adding the realm. > > /etc/samba/smb.conf: > [global] > ### Browsing/Identification ### > > workgroup =

Ok, but you changed your hosts file :-p You removed 127.0.1.1 .. .. So now then, whats wrong here... >/etc/resolv.conf points to the dc as a nameserver > >search mydom.lan >nameserver IP.of.my.dc > >/etc/hosts >127.0.0.1 localhost >xxx.xxx.xxx.xxx fs.mydom.lan fs > ># The following lines are desirable for IPv6 capable hosts >::1 localhost ip6-localhost

Good point Daniel, thanks. Worth a try. I am using : interfaces = 192.168.0.21 127.0.0.1 bind interfaces only = yes Rowland, are u using these too? And you Harry? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mueller > Verzonden: woensdag 29 juni 2016 15:37 > Aan: samba at lists.samba.org >