similar to: net ads user add -F 'user flags'

Hello, I run the domain for the school here with qmail and vpopmail on FreeBSD with dovecot from the ports. I'm running dovecot 1.0.r26 and everything is working great. I been noticing that dovecot isn't updating when the user last logged in.. and I can't seem to figure out why. I also can't seem to find anything in the archives about it.. so am I the only one? name:

Ever since Columbus day things have been strange with my two dovecot servers, according to my Blackberry users. We do not have a BES just the standard BIS that comes with a personal account. Several people have told me that since that Monday that they get occasional duplicate copies of messages which only appear singularly in their Maildir inboxes. I myself even called VZW and got

>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. > you get a caching dnsmasq server as standard Not on ubuntu server... There is no dnsmasq package installed nor is it in ps -ef > If you have to have that

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 that still doesn't work, I think I can definitely narrow this down to a bug in Active Directory, our AD configuration, or a bug in

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.corp.XXX.com I deleted all the shared secrets, removed the computer from AD and rejoined... but of course, we're still getting the exact same

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? On Wed, Dec 2, 2015 at 10:07 AM, mathias dufresne <infractory at gmail.com> wrote: > OK, sorry, I haven't re-read the whole thread carefully enough. > From what I understand sometimes your DNS request are truncated,

All the DNS stuff checks out. The names resolve as they should (They pass all checks Mathias suggested). They all give the exact same answers. hostname -A is showing correctly. I nuked the boxed and reinstalled. Same problem. It simply won't request the ActiveDirectory SRV records from WINDOWS.CORP.XXX.COM, it requests them from WINDOWS and is disappointed when there isn't any DNS setup

On 04/12/15 09:21, Sven Schwedas wrote: > 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

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

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

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

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 Samba services you get the error

Hi, I'm experimenting with setting up winbind and so forth on a simple system joined to an existing AD domain and I've seem to run into some rather broken behavior with DNS updates. As everyone knows, Active Directory is heavily dependent on DNS and it's good to make sure that the DNS records for each system joined to the domain stay up-to-date. So I'm testing to make sure that

Hi, Trying the latest version again tonight 4.6.7 it has the same problem I've seen with the prior newer versions as well. The one I went back to was 4.4.15 which works. What is happening right now is there is a Win2K3 box that is the domain server, with thecompanydomain.com (NetBIOS domain name: COMPANY). That has the __MSBROWSE__ on it. I have a Linux Wheezy system on that is part of

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 >

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 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? --

List, Per someone's suggestion (thanks, whoever you were) from this list, I implemented dnsmasq to prevent the issue of resolving DNS when the net connection goes down. This morning the net connection was down, and our * server didn't miss a beat. I recommend looking into: http://thekelleys.org.uk/dnsmasq/doc.html And http://www.enterprisenetworkingplanet.com/netos/article.php/3377351

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