search for: springventuregroup

...s and trying to solve my own problem. I appreciate your help so far, but if you don't have anything nice say, please just ignore this thread. So: jonathan.fisher at freeradius:~$ sudo hostname -y hostname: Local domain name not set jonathan.fisher at freeradius:~$ sudo hostname -d windows.corp.springventuregroup.com jonathan.fisher at freeradius:~$ sudo hostname -f freeradius.windows.corp.springventuregroup.com Unfortunately, since this box is an LXC container, I can't run the syctl command: jonathan.fisher at freeradius:~$ sysctl -w kernel.domainname=" windows.corp.XXX.com" sysctl: permissi...

...estion... 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* > nameserver 192.168.127.131 > nameserver 192.168.112.4 > > Is this a typo error when copying the content or is it a content error in > your resolv.conf? > > If you really have that "search" line in your resolv.conf...

Hi Jonathan, You wrote: domain windows.corp.springventuregroup.com search windows.corp.*pringventuregroupcom* nameserver 192.168.127.131 nameserver 192.168.112.4 Is this a typo error when copying the content or is it a content error in your resolv.conf? If you really have that "search" line in your resolv.conf it would be logical that rsetarting Sa...

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 rpc command. It's still asking DNS for > "_ldap._tcp.pdc._msdcs.WINDOWS" not > "_ldap._tcp.pdc._msdcs.WINDOWS.CORP.XXX.COM > <http://msdcs.WINDOWS.COR...

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

On 2015-12-04 10:11, Rowland penny wrote: > I still think it is his weird dns setup, were he has a dnsmasq server > replicating what the DCs know (or is supposed to). I think the sheer > fact that he didn't know what lmhosts is, says a lot. We're using such a setup in production without any problems. How about less wild blind guessing and user shaming, and more actual help? --

...int is to define where is the issue, removing points where doubt exists. DNS queries are DNS queries. Kerberos seems to be acting simply just for a kinit. Finally once dig and kinit are working, you could dig into Samba configuration. 2015-12-02 16:34 GMT+01:00 Jonathan S. Fisher < jonathan at springventuregroup.com>: > Dnsmasq is not running locally! Disabling it would do nothing but stop > DHCP and DNS forwarding for 2000+ soon to be irate people. > > What I am going to do however is bypass DHCP completely and assign a > static address with DNS pointed straight at active directory. If...

...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 rpc command. It's still asking DNS for >> "_ldap._tcp.pdc._msdcs.WINDOWS" not "_ldap._tcp.pdc._ >> msdcs.WINDOWS.CORP.XXX.COM <http://msdc...

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 tcpdump on yours and see what the desired behavior is? I used this command: "sudo tcpdump -vvv -s...

...s. >> DNS queries are DNS queries. Kerberos seems to be acting simply just for a >> kinit. >> >> Finally once dig and kinit are working, you could dig into Samba >> configuration. >> >> 2015-12-02 16:34 GMT+01:00 Jonathan S. Fisher < >> jonathan at springventuregroup.com>: >> >>> Dnsmasq is not running locally! Disabling it would do nothing but stop >>> DHCP and DNS forwarding for 2000+ soon to be irate people. >>> >>> What I am going to do however is bypass DHCP completely and assign a >>> static address wi...

...meant to be stable. As the clients configuration. So I would start with dnsmasq removal, then I would [learn how to] configure manually this client, then I would re-run test, starting with small tests (DNS with dig/nslookup, kinit...) 2015-12-01 21:40 GMT+01:00 Jonathan S. Fisher < jonathan at springventuregroup.com>: > So everything with the hostname with now resolving correctly, without the > 127.0.1.1 hack anymore. We just had to make sure DHCP was handing out the > correct domain, which it is now: > > $ hostname -d > windows.corp.XXX.com > $ hostname -f > freeradius.windows....

...ng points where doubt > exists. > DNS queries are DNS queries. Kerberos seems to be acting simply just for a > kinit. > > Finally once dig and kinit are working, you could dig into Samba > configuration. > > 2015-12-02 16:34 GMT+01:00 Jonathan S. Fisher < > jonathan at springventuregroup.com>: > > > Dnsmasq is not running locally! Disabling it would do nothing but stop > > DHCP and DNS forwarding for 2000+ soon to be irate people. > > > > What I am going to do however is bypass DHCP completely and assign a > > static address with DNS pointed stra...

...Kerberos seems to be acting simply just for >>> a >>> kinit. >>> >>> Finally once dig and kinit are working, you could dig into Samba >>> configuration. >>> >>> 2015-12-02 16:34 GMT+01:00 Jonathan S. Fisher < >>> jonathan at springventuregroup.com>: >>> >>> Dnsmasq is not running locally! Disabling it would do nothing but stop >>>> DHCP and DNS forwarding for 2000+ soon to be irate people. >>>> >>>> What I am going to do however is bypass DHCP completely and assign a >>>&g...

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, that's your issue, not mine, but you seemed to me...

...s configuration. > > So I would start with dnsmasq removal, then I would [learn how to] > configure manually this client, then I would re-run test, starting with > small tests (DNS with dig/nslookup, kinit...) > > 2015-12-01 21:40 GMT+01:00 Jonathan S. Fisher < > jonathan at springventuregroup.com>: > > > So everything with the hostname with now resolving correctly, without the > > 127.0.1.1 hack anymore. We just had to make sure DHCP was handing out the > > correct domain, which it is now: > > > > $ hostname -d > > windows.corp.XXX.com > >...

Ok, I really do think that line is significant, I checked in AD and my sitename is "Default-First-Site-Name" On Thu, Dec 3, 2015 at 2:29 PM, Jonathan S. Fisher < jonathan at springventuregroup.com> wrote: > 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 ....

...NDOWS" and it doesn't work of course... On Thu, Dec 3, 2015 at 7:15 AM, Rowland penny <rpenny at samba.org> wrote: > 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, that's your...

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

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

>unless you explicitly set your site name when you provision I guess we didn't. Is that an issue? I still wonder why that says "null" when, even if we used the default, our sitename is not null. > well it obviously isn't working your way To be sure, I took a packet capture. It shows the DNS is going straight to the DCs, so in reality it is working the way you are