similar to: After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command

Same results with that command. And the same DNS query occurred On Mon, Nov 30, 2015 at 2:20 PM, Rowland Penny <rowlandpenny241155 at gmail.com > wrote: > On 30/11/15 20:01, Jonathan S. Fisher wrote: > >> Hey guys, >> >> I've successfully joined the domain with "sudo net ads join -k". However, >> when I try to run this: "sudo net rpc

/etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.127.129 search windows.corp.XXX.com /etc/hosts 127.0.0.1 localhost 127.0.1.1 freeradius.windows.corp.XXX.com freeradius 192.168.127.131 whiskey.windows.corp.XXX.com whiskey 192.168.112.4

On 01/12/15 16:02, Jonathan S. Fisher wrote: > Well I got one step farther... > > hostname -d and hostname -f now work correctly if I add this line to > /etc/hosts > > /etc/hosts > 127.0.0.1 localhost > 127.0.1.1 freeradius.windows.corp.springventuregroup.com > <http://freeradius.windows.corp.springventuregroup.com> freeradius > > But same error on the

Thank you Rowland for the help so far. I followed the directions on that page very precisely. I was able to join the domain, but the RPC stuff still doesn't work and I'm still having the same problem. The actual root problem is that up to this point, winbind works for about a day or so then I start getting NT_STATUS_ACCESS_DENIED. Anyway, after the join, winbind works right now: sudo

On 30/11/15 20:30, Jonathan S. Fisher wrote: > Same results with that command. And the same DNS query occurred > > On Mon, Nov 30, 2015 at 2:20 PM, Rowland Penny > <rowlandpenny241155 at gmail.com <mailto:rowlandpenny241155 at gmail.com>> > wrote: > > On 30/11/15 20:01, Jonathan S. Fisher wrote: > > Hey guys, > > I've

On 30/11/15 20:01, Jonathan S. Fisher wrote: > Hey guys, > > I've successfully joined the domain with "sudo net ads join -k". However, > when I try to run this: "sudo net rpc info" I get this error: "Unable to > find a suitable server for domain WINDOWS" > > I dumped the DNS requests and it looks like the problem is that it's asking >

On 30/11/15 20:52, Jonathan S. Fisher wrote: > /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 192.168.127.129 > search windows.corp.XXX.com <http://windows.corp.XXX.com> I take it 192.168.127.129 is your AD DC. > > /etc/hosts >

> host -t SRV _ldap._tcp.windows.corp.XXX.com _ldap._tcp.windows.corp.XXX.com has SRV record 0 100 389 whiskey.windows.corp.XXX.com. _ldap._tcp.windows.corp.XXX.com has SRV record 0 100 389 wine.windows.corp.XXX.com. > host -t SRV _kerberos._udp.windows.corp.XXX.com _kerberos._udp.windows.corp.XXX.com has SRV record 0 100 88 whiskey.windows.corp.XXX.com. _kerberos._udp.windows.corp.XXX.com

OK, sorry, I haven't re-read the whole thread carefully enough. >From what I understand sometimes your DNS request are truncated, asking for machineName.windows rahter than machineName.windows.rest.of.your.domain.tld So you have to find what is cutting your DNS requests. If I'm wrong, don't read the rest :p First I would test my DNS resolution using dig, host or nslookup and check

Great things to investigate... thank you. Ok, so everything is pingable. I've checked to make sure I can send TCP and UDP traffic between the hosts with netcat. > Does your dhcp server deliver the required info? For DNS? Yes, it tells the client to use 192.168.127.129. I'd be in a world of hurt otherwise! > Does 'hostname -d' return the fully qualified domain name of the

Checked with the network guy... yes, the main DNS is indeed dnsmasq. He has a delegation though, so any query for WINDOWS.corp.XXX.com winds up going to to the correct place: domain=/windows.corp.XXX.com/192.168.127.141 domain=/windows.corp.XXX.com/192.168.112.4 The DC's (192.168.127.141, 192.168.112.4) are indeed running DNS (I can dig at them). Would it just be easier to make this host

On 02/12/15 16:27, Jonathan S. Fisher wrote: > Great thanks, I'll start digging into that. So your running theory is that > one of the DNS resolution attempts is returning .WINDOWS not . > WINDOWS.CORP.XXX.com? This is not your problem. Rowland > > On Wed, Dec 2, 2015 at 10:07 AM, mathias dufresne <infractory at gmail.com> > wrote: > >> OK, sorry, I

On 01/12/15 16:36, Jonathan S. Fisher wrote: > Checked with the network guy... yes, the main DNS is indeed dnsmasq. > He has a delegation though, so any query for WINDOWS.corp.XXX.com > <http://WINDOWS.corp.XXX.com> winds up going to to the correct place: Why, in your deity's name, why????? > > domain=/windows.corp.XXX.com/192.168.127.141 >

jonathan.fisher at freeradius:~$ sudo net ads join -Uadministrator Enter administrator's password: Using short domain name -- WINDOWS Joined 'FREERADIUS' to dns domain 'windows.corp.XXX.com' jonathan.fisher at freeradius:~$ hostname freeradius jonathan.fisher at freeradius:~$ hostname -d windows.corp.XXX.com jonathan.fisher at freeradius:~$ hostname -f

Well I got one step farther... hostname -d and hostname -f now work correctly if I add this line to /etc/hosts /etc/hosts 127.0.0.1 localhost 127.0.1.1 freeradius.windows.corp.springventuregroup.com freeradius But same error on the rpc command. It's still asking DNS for "_ldap._tcp.pdc._msdcs.WINDOWS" not "_ldap._tcp.pdc._msdcs.WINDOWS.CORP.XXX.COM" Can you do a

192.168.127.129 is the core DNS server. It forwards anything in the windows subdomain straight to the DCs, so it doesn't matter if this client is pointed at the DC or the main DNS server. Either way, it still does the wrong behavior, which is use the short .WINDOWS instead of . WINDOWS.CORP.XXX.COM I removed all .tdb files, purged /var/cache/samba, removed /etc/krb5.tdb, and deleted the

Can't you just disable dnsmasq service? You don't seem to be too much confident in that tool and you have DNS issue... dnsmasq has most certainly a good reason to exist. I just don't know it. In IT for work we generally don't need such tool as infrastructures of companies are meant to be stable. As the clients configuration. So I would start with dnsmasq removal, then I would

Here's a random question... would it matter if our domain has trust relationships setup? *Jonathan S. Fisher* *VP - Information Technology* *Spring Venture Group* On Wed, Dec 9, 2015 at 9:34 AM, mathias dufresne <infractory at gmail.com> wrote: > Hi Jonathan, > > You wrote: > domain windows.corp.springventuregroup.com > search windows.corp.*pringventuregroupcom* >

On 01/12/15 17:27, Jonathan S. Fisher wrote: >> It isn't running, one of the first things I do when setting up a new DC is > to remove nscd if it is installed. > Ah ok... well this isn't a DC, just a member... is NSCD ok to run as a > member? Otherwise I can remove it. I would remove it, everything dns wise should come from an AD DC > >> you get a caching dnsmasq

On 03/12/15 13:07, Rowland Penny wrote: > > > > > 2015-12-02 17:27 GMT+01:00 Jonathan S. Fisher < > jonathan at springventuregroup.com>: > > > Great thanks, I'll start digging into that. So your running theory is that > > one of the DNS resolution attempts is returning .WINDOWS not . > > WINDOWS.CORP.XXX.com? > > > > I'm not sure,