search for: fdea

...ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.cyberdyne.local): view internal: query: _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.cyberdyne.local IN SRV + (10.0.1.6) ... [message repeated 16 times in total] or with IPv6 enabled: 04-Aug-2016 14:57:42.217 queries: info: client fdea:5b48:d4c1:1:68f2:fa7c:db26:ce22#53050 (_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.cyberdyne.local): view internal: query: _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.cyberdyne.local IN SRV + (fdea:5b48:d4c1:1:1::6) 04-Aug-2016 14:57:42.401 queries: info: client fdea:5b48...

...his zone is managing PTR entries for my local LAN eqipment with fixed IP addresses. It looks like when a machine is domain-joined the clients try to update those records and I see the following in my BIND logs (starts after domain join): 04-Aug-2016 17:09:52.381 update-security: error: client fdea:5b48:d4c1:1:2839:ba1e:ac57:aa6#56593: view internal: update '1.0.0.0.1.c.4.d.8.4.b.5.a.e.d.f.ip6.arpa/IN' denied 04-Aug-2016 17:09:52.382 update: info: client fdea:5b48:d4c1:1:2839:ba1e:ac57:aa6#54604/key cyb64w10-monste\$\@AD.CYBERDYNE.LOCAL: view internal: updating zone '1.0.0.0.1...

On Thu, 4 Aug 2016 12:02:18 +0200 rme at bluemail.ch wrote: > > Well, I am using IPv6 mainly for all services and don't want to > > disable it. Though I might try this temporary which will be quite a > > bunch of reconfiguration to disable IPv6 in all services. So I will > > come back with results on this later. > > I have completely disabled IPv6 on the server

...he PC, ( ipconfig /all ) looks good now.     Next.. your hosts files... > my /etc/hosts: > > # IPv4 and IPv6 localhost aliases > 127.0.0.1       localhost > ::1             localhost > > 10.0.1.6        skynet skynet.cyberdyne.local skynet.ad.cyberdyne.local > fdea:5b48:d4c1:1:1::6   skynet skynet.cyberdyne.local > skynet.ad.cyberdyne.local   Which looks ok but it isnt.   # look at this layout i made..  ( the localhost.localdomain is optional. ) 127.0.0.1            localhost localhost.localdomain # 10.0.1.6                skynet.ad.cyberdyne.loc...

  Can you run on a failing computer : - netdom verify yourpcname - nslookup yourpcname All ok? And is time in sync?   Did you install winbind after the update and also and did you change you server services line?   Like, i use bind9 dns My smb.conf contains only this :        server services = -dns   The full line is :  samba-tool testparm -vv | grep "server service"

...l from your client pc? And can it be you > also have addc servers in other non reachable subnets. Actually my trusted clients are in 10.0.1.0/24 subnet. Untrusted clients are in 10.0.2.0/24 subnet but this subnet does not contain ad-joined hosts. Samba listens on 3 IPs: - 10.0.1.6 - 10.0.1.6 - fdea:5b48:d4c1:1:1::6 DNS also resolves those hosts: >nslookup skynet Server: skynet.ad.cyberdyne.local Address: fdea:5b48:d4c1:1:1::6 Name: skynet.ad.cyberdyne.local Addresses: fdea:5b48:d4c1:1:1::6 10.0.2.6 10.0.0.6 10.0.1.6 Actually the routes and firewal...

...es the format is invalid. If I use the the FQDN of the AD domain it works fine. The DNS search is also including the AD domain as well as the primary DNS suffix is set to the AD domain (see below). > > C:\Temp>nslookup cyb64w10-monster > > Server: UnKnown > > Address: fdea:5b48:d4c1:1:1::6 > Also not good. It resolves fine. Just I missed the correct IPv6 PTR record from the DNS. I did quickly fix this now (with no change to the result in GPO sync): C:\Temp>nslookup cyb64w10-monster Server: skynet.cyberdyne.local Address: fdea:5b48:d4c1:1:1::6 Name: cyb...

...; > Hai, > > No, your output is not good. > > >C:\Temp>netdom verify cyb64w10-monster > >The format of the specified computer name is invalid. > > Thats not good. > > > C:\Temp>nslookup cyb64w10-monster > > Server: UnKnown > > Address: fdea:5b48:d4c1:1:1::6 > > Also not good. > > > If you resolving is setup correct both should work. > netdom verify cyb64w10-monster > and > netdom verify cyb64w10-monster.ad.cyberdyne.local > > Both work for me and my windows 10 gets this policies. > > open dos b...

Hai, No, your output is not good. >C:\Temp>netdom verify cyb64w10-monster >The format of the specified computer name is invalid. Thats not good. > C:\Temp>nslookup cyb64w10-monster > Server: UnKnown > Address: fdea:5b48:d4c1:1:1::6 Also not good. If you resolving is setup correct both should work. netdom verify cyb64w10-monster and netdom verify cyb64w10-monster.ad.cyberdyne.local Both work for me and my windows 10 gets this policies. open dos box and type ipconfig /all check you primary dns suffix A...

...m CYB64W10-MONSTER.AD.CYBERDYNE.LOCAL to the domain CYBERDYNE has been verified. The connection is with the machine \\SKYNET.AD.CYBERDYNE.LOCAL. The command completed successfully. > - nslookup yourpcname Seems to work fine: C:\Temp>nslookup cyb64w10-monster Server: UnKnown Address: fdea:5b48:d4c1:1:1::6 Name: cyb64w10-monster.ad.cyberdyne.local Addresses: fdea:5b48:d4c1:1:1::100 2a02:120b:2c38:2951:8d95:bd76:deaa:73db fdea:5b48:d4c1:1:8d95:bd76:deaa:73db 10.0.1.119 > All ok? To me this looks alright. Isn't it? > And is time in...

Hi Louis, > Ive tested the following, i use static and dhcp ip here. I am using DHCP only. > Everything on static ip works perfect on win7 and win10. > And at the domain join the a and ptr is created automaticly. > GPO works fine for both. Can't tell about static setup as it's impractical in my networks. > Dhcp ip. > Win 7 works fine, AD join A and PTR is created

On Thu, 4 Aug 2016 21:14:39 +0200 rme at bluemail.ch wrote: > Hello Rowland, > > > No its not, its fairly easy, once you get your head around it. I > > have been using something based on that webpage for nearly 4 years > > now and only had self inflicted problems. > > Thanks for the heads-up. Perhaps my wording wasn't very good on it. I > would actually

...for my local LAN eqipment with fixed IP addresses. > > It looks like when a machine is domain-joined the clients try to > update those records and I see the following in my BIND logs (starts > after domain join): > > 04-Aug-2016 17:09:52.381 update-security: error: client > fdea:5b48:d4c1:1:2839:ba1e:ac57:aa6#56593: view internal: update > '1.0.0.0.1.c.4.d.8.4.b.5.a.e.d.f.ip6.arpa/IN' denied > 04-Aug-2016 17:09:52.382 update: info: client > fdea:5b48:d4c1:1:2839:ba1e:ac57:aa6#54604/key > cyb64w10-monste\$\@AD.CYBERDYNE.LOCAL: view internal: updating...

...is interface. > > So I removed the entry manually: > samba-tool dns delete skynet.ad.cyberdyne.local ad.cyberdyne.local > skynet A 10.0.0.6 > > Now DNS looks alright, IPv4 only: >> nslookup skynet.ad.cyberdyne.local > Server: skynet.ad.cyberdyne.local > Address: fdea:5b48:d4c1:1:1::6 > > Name: skynet.ad.cyberdyne.local > Address: 10.0.1.6 I think the 10.0.06 entry was created during domain creation. I'd skim thru dns records from an windows machine if possible and delete all occurences of unwanted ip adresses. I assume the gpo's still ca...

...> > Also this was in lowercase which I changed with no effect. > > But I noticed another thing: > In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters > there > are a few important parameters: > Dhcpv6DNSServers: > Here I see correctly my server fdea:5b48:d4c1:1:1::6 listed. > > Dhcpv6DomainSearchList: > Here it looks only my suffix cyberdyne.local is listed and not > ad.cyberdyne.local. I have updated my DHCPv6 to include the search suffix > as well: > option dhcp6.domain-search "ad.cyberdyne.local", "cy...

...ere's my compiled parameters as printed by testparm: > > # Global parameters > [global] > workgroup = MYDOM > realm = ad.mydom.local > netbios aliases = SOFTWARE > server string = Server > interfaces = 127.0.0.1/8 10.0.1.6/24 fdea:5b48:d4c1:1:1::6/64 > bind interfaces only = Yes > server role = active directory domain controller > passdb backend = samba_dsdb > log file = /var/log/samba/smb.%M > max log size = 500 > time server = Yes > deadtim...

...NT_STATUS_CONNECTION_DISCONNECTED] Here's my compiled parameters as printed by testparm: # Global parameters [global] workgroup = MYDOM realm = ad.mydom.local netbios aliases = SOFTWARE server string = Server interfaces = 127.0.0.1/8 10.0.1.6/24 fdea:5b48:d4c1:1:1::6/64 bind interfaces only = Yes server role = active directory domain controller passdb backend = samba_dsdb log file = /var/log/samba/smb.%M max log size = 500 time server = Yes deadtime = 2 logon script = KIX32...