search for: cyberdyne

...some additional observations... I quickly enabled DNS query logging: # rndc querylog Then run another gpupdate on the client. During the Update I see lots of queries: 04-Aug-2016 14:46:58.414 queries: info: client 10.0.1.186#59270 (_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) 04-Aug-2016 14:46:59.223 queries: info: client 10.0.1.186#50476 (_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.cyberdyne.local): view internal: query: _ldap._tcp.D...

...servations. I noticed when I join my machine to AD it prompts a second time for the credentials. It does not matter what I enter or even cancel the dialog it will always display an error: Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "ad.cyberdyne.local". Well, actualy this is what I want anyway. I found this Microsoft article about: <https://support.microsoft.com/en-us/kb/2018583> But also forcing NetBIOS over TCP did not help. I have the follwowing in my dhcpd.conf anyway: option netbios-name-servers 10.0.1.6; optio...

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

Am 09.08.2016 um 22:18 schrieb Achim Gottinger via samba: > > > Am 09.08.2016 um 21:48 schrieb Rainer Meier via samba: >>> 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 can not be >>>

...cords. ;-) so one thing fixed thats ok..     The 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...

...hed the query log during gpupdate and didn't find anything special there. On a Windows 7 Pro VM I installed (note, it's in the untrusted 10.0.2.0/24 network) I see the following BIND logs on connect: 09-Aug-2016 23:18:24.585 database: info: samba_dlz: committed transaction on zone ad.cyberdyne.local 09-Aug-2016 23:18:24.654 database: info: samba_dlz: starting transaction on zone ad.cyberdyne.local 09-Aug-2016 23:18:24.655 update-security: error: client 10.0.2.95#57343: view internal: update 'ad.cyberdyne.local/IN' denied 09-Aug-2016 23:18:24.655 database: info: samba_dlz: cance...

...gt; > > 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 AND dns search. > Normaly these are the same, can you check this? > > My guess, your missing the dns-search > > Are you usi...

Hi Achim, Thanks a lot for your reply. > I remember this error. In my case the pc tried to connect to the gpo > share not via the server name but via the domain name. In your case > ad.cyberdyne.local. Well, I am even able to browser the policies via the domain name: \\ad.cyberdyne.local\sysvol\ad.cyberdyne.local\Policies Or via hostname: \\skynet.ad.cyberdyne.local\sysvol\ad.cyberdyne.local\Policies It's all working just fine. > In my case the domain name sometimes resolved t...

...l ntacl sysvolcheck returns the same error as > indicated in the thread above: > > # samba-tool ntacl sysvolcheck > ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - > ProvisioningError: DB ACL on GPO directory > /var/lib/samba/sysvol/ad.cyberdyne.local/Policies/{31B2F340-016D-11D2- > 945F-00C04FB984F9} > O:LAG:DAD:P(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;EA)(A;OICIIO;0x001 > f01ff;;;CO)(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;SY)(A;OICI;0x00120 > 0a9;;;AU)(A;OICI;0x001200a9;;;ED) > does not match expected value...

...hy" the ptr is not updated on win10. Besides that it looks normal here. Rainer, I dont think there is an inssue with your install. But i would change the krb5.conf to but im no kerberos guru, i would think its something like below what you need. [libdefaults] default_realm = AD.CYBERDYNE.LOCAL dns_lookup_realm = false dns_lookup_kdc = false [realms] AD.CYBERDYNE.LOCAL = { default_domain = ad.cyberdne.local kdc = skynet.ad.cyberdyne.local admin_server = skynet.ad.cyberdyne.local } [domain_realm]...

...is buggy.. Source : https://support.microsoft.com/nl-nl/kb/2891966 It was worth a try.. https://support.microsoft.com/en-us/kb/2954031 for the status rapport error, one you can check also. I see still something incorrect here. > C:\Temp>nslookup cyb64w10-hpnb > Server: skynet.cyberdyne.local > Address: 10.0.1.6 > C:\Temp>nslookup cyb64w10-hpnb > Server: skynet.cyberdyne.local > Address: 10.0.1.6 > > Name: cyb64w10-hpnb.ad.cyberdyne.local > Address: 10.0.1.186 SKYNET.AD.CYBERDYNE.LOCAL is the correct AD DC location. Above still shows : skynet.cyb...

...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: cyb64w10-monster.ad.cyberdyne.local Addresses: 2a02:120b:2c38:2951:8d95:bd76:deaa:73db fdea:5b48:d4c1:1:1::100 fdea:5b48:d4c1:1:8d95:bd76:deaa:73db 10.0.1.119 > open dos box and type ipconfig /all > check y...

..., can you post you smb.conf again, but this time, obtain it via cat Sure. As it's bit larger and I don't want to process or omit anything which could be important here's a complete paste: <http://pastebin.com/mYa1d5KG> In short without comments: [global] workgroup = CYBERDYNE realm = ad.cyberdyne.local netbios name = SKYNET netbios aliases = SOFTWARE server string = SkyNet server role = active directory domain controller acl:search = no ldap server require strong auth = no server services = -dns...

> Can you run on a failing computer : > - netdom verify yourpcname It seems to work only with FQDN: C:\Temp>netdom verify cyb64w10-monster The format of the specified computer name is invalid. The command failed to complete successfully. C:\Temp>netdom verify cyb64w10-monster.ad.cyberdyne.local The secure channel from 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-monste...

Hai, > > Windows can update the forward zone, but, if I understand it correctly, > it doesn't update the reverse zone, Unix clients does neither > > Rowland > > -- Some more info on this. - Windows 7/Static ip's Here windows does update there forward and reverse zone, but only when u use static ip, so to avoid problems here, all my normal pcs have static ip.

...he 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 AND dns search. Normaly these are the same, can you check this? My guess, your missing the dns-search Are you using ipv6 in your lan? If not, try disable it. And try...

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

...m the modemananger service and another USB device getting recognized. Only then, upsd is loaded and fails: Jan 1 02:00:14 beagle upsd[2744]: listening on 127.0.0.1 port 3493 Jan 1 02:00:14 beagle upsd[2744]: listening on ::1 port 3493 Jan 1 02:00:14 beagle upsd[2744]: Can't connect to UPS [cyberdyne] (usbhid-ups-cyberdyne): No such file or directory Jan 1 02:00:14 beagle upsd[2754]: Startup successful Jan 1 02:00:14 beagle upsmon[2803]: Startup successful Jan 1 02:00:14 beagle upsd[2754]: User upsmaster at 127.0.0.1 logged into UPS [cyberdyne] Jan 1 02:00:14 beagle upsmon[2805]: Poll UPS...

...bugs.launchpad.net/ubuntu/+source/nut/+bug/1176548 > Only then, upsd is loaded and fails: > Jan 1 02:00:14 beagle upsd[2744]: listening on 127.0.0.1 port 3493 > Jan 1 02:00:14 beagle upsd[2744]: listening on ::1 port 3493 > Jan 1 02:00:14 beagle upsd[2744]: Can't connect to UPS [cyberdyne] (usbhid-ups-cyberdyne): No such file or directory > Jan 1 02:00:14 beagle upsd[2754]: Startup successful > Jan 1 02:00:14 beagle upsmon[2803]: Startup successful > Jan 1 02:00:14 beagle upsd[2754]: User upsmaster at 127.0.0.1 logged into UPS [cyberdyne] > Jan 1 02:00:14 beagle upsm...

...used on a dedicated physical network interface. But I don't want > Samba to listen on it and the interfaces line (see above) does not > list it. Netstat confirms Samba does not listen on this 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....