search for: whiskey

...ously 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 > describing: It is ignoring the main DNS server. Here, check this out: > > jonathan.fisher at freeradius:~$ nslookup whiskey.windows.corp.XXX.com > <http://whiskey.windows.corp.XXX.com> > *Server:192.168.127.131* > Address:192.168.127.131#53 > > Name:whiskey.windows.corp.XXX.com <http://whiskey.windows.corp.XXX.com> > Address: 192.168.127.131 > > > Look, I will say it again, a bit...

...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 wine..windows.corp.XXX.com wine /etc/krb5.conf [libdefaults] default_realm = WINDOWS.CORP.XXX.COM krb4_config = /etc/krb.conf krb4_realms = /etc/krb.realms kdc_timesync = 1 ccache_type = 4 forwardable = true proxiable = true v4_instance_resolve = false...

On 03/12/15 20:45, Jonathan S. Fisher wrote: > Ok, I really do think that line is significant, I checked in AD and my > sitename is "Default-First-Site-Name" > Words fail me, unless you explicitly set your site name when you provision, your site name will be "Default-First-Site-Name" Rowland

...29 > search windows.corp.XXX.com <http://windows.corp.XXX.com> I take it 192.168.127.129 is your AD DC. > > /etc/hosts > > 127.0.0.1 localhost > 127.0.1.1 freeradius.windows.corp.XXX.com > <http://freeradius.windows.corp.XXX.com> freeradius > 192.168.127.131 whiskey.windows.corp.XXX.com > <http://whiskey.windows.corp.XXX.com> whiskey > 192.168.112.4 wine..windows.corp.XXX.com <http://windows.corp.XXX.com> > wine Hmm, I think you are using Network Manager, which uses dnsmasq as a cache, I would suggest you stop this ( open the network-m...

> 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 has SRV recor...

...oud and clear. If you could point out below what is the problem, because the client seems to be configured correctly as you have asked: root at freeradius:~# nslookup 192.168.127.131 Server: 192.168.127.131 Address: 192.168.127.131#53 Non-authoritative answer: 131.127.168.192.in-addr.arpa name = whiskey.windows.corp.XXX.com. Authoritative answers can be found from: root at freeradius:~# nslookup 192.168.112.4 Server: 192.168.127.131 Address: 192.168.127.131#53 Non-authoritative answer: 4.112.168.192.in-addr.arpa name = wine.windows.corp.XXX.com. Authoritative answers can be found from: root a...

.../windows.corp.XXX.com> >> > > I take it 192.168.127.129 is your AD DC. > > >> /etc/hosts >> >> 127.0.0.1 localhost >> 127.0.1.1 freeradius.windows.corp.XXX.com < >> http://freeradius.windows.corp.XXX.com> freeradius >> 192.168.127.131 whiskey.windows.corp.XXX.com < >> http://whiskey.windows.corp.XXX.com> whiskey >> 192.168.112.4 wine..windows.corp.XXX.com <http://windows.corp.XXX.com> >> wine >> > > Hmm, I think you are using Network Manager, which uses dnsmasq as a cache, > I would suggest y...

...samba.org> wrote: > On 03/12/15 16:06, Jonathan S. Fisher wrote: > >> > host -t SRV _ldap._tcp.windows.corp.XXX.com < >> http://tcp.windows.corp.XXX.com> >> _ldap._tcp.windows.corp.XXX.com <http://tcp.windows.corp.XXX.com> has >> SRV record 0 100 389 whiskey.windows.corp.XXX.com < >> http://whiskey.windows.corp.XXX.com>. >> _ldap._tcp.windows.corp.XXX.com <http://tcp.windows.corp.XXX.com> has >> SRV record 0 100 389 wine.windows.corp.XXX.com < >> http://wine.windows.corp.XXX.com>. >> >> > host -t...

On 03/12/15 16:06, Jonathan S. Fisher wrote: > > host -t SRV _ldap._tcp.windows.corp.XXX.com > <http://tcp.windows.corp.XXX.com> > _ldap._tcp.windows.corp.XXX.com <http://tcp.windows.corp.XXX.com> has > SRV record 0 100 389 whiskey.windows.corp.XXX.com > <http://whiskey.windows.corp.XXX.com>. > _ldap._tcp.windows.corp.XXX.com <http://tcp.windows.corp.XXX.com> has > SRV record 0 100 389 wine.windows.corp.XXX.com > <http://wine.windows.corp.XXX.com>. > > > host -t SRV _kerberos._udp.win...

...permail/asterisk-users/2003-June/013483.html Well, I just called Ovislink/dgtimes and was quoted $90 & $100 and the person said there was no price change. Anyone on this list actually bought them at the $75 & $85 rate ??? Regards...Martin -- Too much is just enough. -- Mark Twain, on whiskey

...gt;> On 03/12/15 16:06, Jonathan S. Fisher wrote: >> >>>> host -t SRV _ldap._tcp.windows.corp.XXX.com < >>> http://tcp.windows.corp.XXX.com> >>> _ldap._tcp.windows.corp.XXX.com <http://tcp.windows.corp.XXX.com> has >>> SRV record 0 100 389 whiskey.windows.corp.XXX.com < >>> http://whiskey.windows.corp.XXX.com>. >>> _ldap._tcp.windows.corp.XXX.com <http://tcp.windows.corp.XXX.com> has >>> SRV record 0 100 389 wine.windows.corp.XXX.com < >>> http://wine.windows.corp.XXX.com>. >>> &...

...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> OK, earlier you posted this: 192.168.127.131 whiskey.windows.corp.XXX.com <http://whiskey.windows.corp.XXX.com> whiskey 192.168.112.4 wine..windows.corp.XXX.com <http://windows.corp.XXX.com> wine So what is '192.168.127.129' ? it certainly isn't one of your DCs, which is what it should be pointing at. I am sure I have said...

...39;m wrong, don't read the rest :p First I would test my DNS resolution using dig, host or nslookup and check with tcpdump if that resolution is working correctly. If request is not truncated your issue comes from something else than your DNS resolution configuration. ex: dig @192.168.127.129 whiskey.windows.corp.XXX.com dig @192.168.127.141 whiskey.windows.corp.XXX.com dig @192.168.112.4 whiskey.windows.corp.XXX.com If it works, I would continue with simple command, perhaps a kinit as that one should, I believe, also launch several DNS query (if your krb5.conf is still alsmot empty). Here...

...f ignominious defeats, gotten a general would could fight and win a battle, General Grant. A fussy old lady approached President Lincoln and complained loudly that Grant was a drunk. Lincoln blinked at the woman, then said, "Ma'am, if you'll be so kind as to find out what kind of whiskey Grant drinks, I'll send a case of it to all the other generals." Dovecot Works. That's all anyone needs to know. Plus it has a towering wizard of a developer and an avid, engaged and endlessly helpful community. -- ==== Once upon a time, the Internet was a friendly, neighbors-he...

...config *:backend = tdb > idmap config *:range = 2000-9999 > > You need these lines to get the builtin users & groups mapped. > > I think your problem is DNS related, you should be able to ping a DC via > ipaddress & hostname > > ping -c1 192.168.127.131 > ping -c1 whiskey.windows.corp.XXX.com > ping -c1 whiskey > ping -c1 192.168.112.4 > ping -c1 wine.windows.corp.XXX.com > ping -c1 wine > > The above commands should all return a reply. > > Does your dhcp server deliver the required info? > > Does 'hostname -d' return the fully...

...t 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 describing: It is ignoring the main DNS server. Here, check this out: jonathan.fisher at freeradius:~$ nslookup whiskey.windows.corp.XXX.com *Server: 192.168.127.131* Address: 192.168.127.131#53 Name: whiskey.windows.corp.XXX.com Address: 192.168.127.131 On Thu, Dec 3, 2015 at 2:49 PM, Rowland penny <rpenny at samba.org> wrote: > On 03/12/15 20:45, Jonathan S. Fisher wrote: > >> Ok, I really do...

...a ai completat inseamna ca esti in joc pentru a castiga cei 500 RON pusi in concurs in fiecare saptamana. Grabeste-te ai timp doar pana Marti. *********************************************** Astazi Linkutil va recomanda: http://cockeramerican.paginirosii.ro o pagina despre: Cocker american http://whiskey.paginirosii.ro o pagina despre: Whiskey http://scamator.paginirosii.ro o pagina despre: Scamator http://break.paginirosii.ro o pagina despre: Break *********************************************** www.simb.eu Acceseaza cel mai simplu motor de cautare www.simb.eu Acum peste 2 milion de acesari zi...

...I would test my DNS resolution using dig, host or nslookup and check >> with tcpdump if that resolution is working correctly. If request is not >> truncated your issue comes from something else than your DNS resolution >> configuration. >> ex: >> dig @192.168.127.129 whiskey.windows.corp.XXX.com >> dig @192.168.127.141 whiskey.windows.corp.XXX.com >> dig @192.168.112.4 whiskey.windows.corp.XXX.com >> >> >> If it works, I would continue with simple command, perhaps a kinit as that >> one should, I believe, also launch several DNS qu...

...low what is the problem, because the client seems to be > configured correctly as you have asked: > > > root at freeradius:~# nslookup 192.168.127.131 > Server:192.168.127.131 > Address:192.168.127.131#53 > > Non-authoritative answer: > 131.127.168.192.in-addr.arpaname = whiskey.windows.corp.XXX.com > <http://whiskey.windows.corp.XXX.com>. > > Authoritative answers can be found from: > > root at freeradius:~# nslookup 192.168.112.4 > Server:192.168.127.131 > Address:192.168.127.131#53 > > Non-authoritative answer: > 4.112.168.192.in-add...

...eed a bit more in your smb.conf: idmap config *:backend = tdb idmap config *:range = 2000-9999 You need these lines to get the builtin users & groups mapped. I think your problem is DNS related, you should be able to ping a DC via ipaddress & hostname ping -c1 192.168.127.131 ping -c1 whiskey.windows.corp.XXX.com ping -c1 whiskey ping -c1 192.168.112.4 ping -c1 wine.windows.corp.XXX.com ping -c1 wine The above commands should all return a reply. Does your dhcp server deliver the required info? Does 'hostname -d' return the fully qualified domain name of the client? Is there...