Displaying 11 results from an estimated 11 matches for "caliphate".
Did you mean:
calibrate
2015 Dec 01
2
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...e nscd if you have it running and try again?)
>>
>>
>> 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.
>>
>>
>>> Why, in your deity's name, why?????
>> I'm starting my own caliphate. Seems to be all the rage these days.
>>
>> Dnsmasq isn't running locally... it's the main DNS server at
>> 192.168.127.129. At one time I guess we were running Bind, but he switched
>> to dnsmasq for simplicity. If there's a legit reason why Windows needs to
>...
2015 Dec 02
3
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...39;t running, one of the first things I do when setting up a new DC
> >>> is
> >>> to remove nscd if it is installed.
> >>>
> >>>
> >>> Why, in your deity's name, why?????
> >>>>
> >>> I'm starting my own caliphate. Seems to be all the rage these days.
> >>>
> >>> Dnsmasq isn't running locally... it's the main DNS server at
> >>> 192.168.127.129. At one time I guess we were running Bind, but he
> >>> switched
> >>> to dnsmasq for simplicity....
2015 Dec 01
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...ached?
> (Can you disable nscd if you have it running and try again?)
>
>
> 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.
>
>
> >Why, in your deity's name, why?????
>
> I'm starting my own caliphate. Seems to be all the rage these days.
>
> Dnsmasq isn't running locally... it's the main DNS server at
> 192.168.127.129. At one time I guess we were running Bind, but he switched
> to dnsmasq for simplicity. If there's a legit reason why Windows needs to
> handle 100% of...
2015 Dec 01
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...>>>
>>> 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.
>>>
>>>
>>> Why, in your deity's name, why?????
>>>>
>>> I'm starting my own caliphate. Seems to be all the rage these days.
>>>
>>> Dnsmasq isn't running locally... it's the main DNS server at
>>> 192.168.127.129. At one time I guess we were running Bind, but he
>>> switched
>>> to dnsmasq for simplicity. If there's a legit re...
2015 Dec 01
5
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
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
2015 Dec 01
1
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
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
>
2015 Dec 02
5
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...w DC
>> > >>> is
>> > >>> to remove nscd if it is installed.
>> > >>>
>> > >>>
>> > >>> Why, in your deity's name, why?????
>> > >>>>
>> > >>> I'm starting my own caliphate. Seems to be all the rage these days.
>> > >>>
>> > >>> Dnsmasq isn't running locally... it's the main DNS server at
>> > >>> 192.168.127.129. At one time I guess we were running Bind, but he
>> > >>> switched
>>...
2015 Dec 02
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...do when setting up a new
> DC
> > >>> is
> > >>> to remove nscd if it is installed.
> > >>>
> > >>>
> > >>> Why, in your deity's name, why?????
> > >>>>
> > >>> I'm starting my own caliphate. Seems to be all the rage these days.
> > >>>
> > >>> Dnsmasq isn't running locally... it's the main DNS server at
> > >>> 192.168.127.129. At one time I guess we were running Bind, but he
> > >>> switched
> > >>> to...
2015 Dec 02
2
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...>>>>>>>> is
>>>>>>>> to remove nscd if it is installed.
>>>>>>>>
>>>>>>>>
>>>>>>>> Why, in your deity's name, why?????
>>>>>>>> I'm starting my own caliphate. Seems to be all the rage these
>> days.
>>>>>>>> Dnsmasq isn't running locally... it's the main DNS server at
>>>>>>>> 192.168.127.129. At one time I guess we were running Bind, but he
>>>>>>>> switched
>>&...
2015 Dec 02
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...; is
> >> > >>> to remove nscd if it is installed.
> >> > >>>
> >> > >>>
> >> > >>> Why, in your deity's name, why?????
> >> > >>>>
> >> > >>> I'm starting my own caliphate. Seems to be all the rage these
> days.
> >> > >>>
> >> > >>> Dnsmasq isn't running locally... it's the main DNS server at
> >> > >>> 192.168.127.129. At one time I guess we were running Bind, but he
> >> > >&g...
2015 Dec 02
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
...>>> is
>>>>>>>>> to remove nscd if it is installed.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Why, in your deity's name, why?????
>>>>>>>>> I'm starting my own caliphate. Seems to be all the rage these
>>>>>>>>>
>>>>>>>> days.
>>>
>>>> Dnsmasq isn't running locally... it's the main DNS server at
>>>>>>>>> 192.168.127.129. At one time I guess we were running Bi...