search for: ip_of_1st_dc

...you do you both servers listed as available DNS servers >>>> on your workstations? As well as your member server? >>> Yes, of course. For member servers, this is the content of >>> /etc/resolv.conf: >>> >>> search my.domain.tld >>> nameserver IP_of_1st_DC >>> nameserver IP_of_2nd_DC >>> >>> >>>> I made a small tweak but haven't fully tested is adding the following >>>> options to my resolv.conf. >>>> >>>> cat /etc/resolvconf/resolv.conf.d/tail >>>> options tim...

...up: [25392] 1452162640.959713: Getting initial credentials for administrator at my.domain.tld [25392] 1452162640.960294: Sending request (196 bytes) to my.domain.tld [25392] 1452162640.963005: Resolving hostname dc2.my.domain.tld. [25392] 1452162640.964554: Sending initial UDP request to dgram IP_of_1st_DC:88 [25392] 1452162640.972442: Received answer from dgram IP_of_1st_DC:88 [25392] 1452162640.973243: Response was not from master KDC [25392] 1452162640.973293: Received error from KDC: -1765328359/Additional pre-authentication required [25392] 1452162640.973381: Processing preauth types: 16, 15, 2...

...(following your suggestions, >>> Rowland, as everything else are defaults): >>> >>> [libdefaults] >>> default_realm = MY.DOMAIN.TLD >>> >>> And my /etc/resolv.conf is this: >>> >>> search my.domain.tld >>> nameserver IP_of_1st_DC >>> nameserver IP_of_2nd_DC >> >> Any idea why I still get this when trying to log on to a member >> server while the first DC is down? >> >> # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while >> getting initial credentials >&gt...

...tial credentials" > > > My /etc/krb5.conf looks like this (following your suggestions, > Rowland, as everything else are defaults): > > [libdefaults] > default_realm = MY.DOMAIN.TLD > > And my /etc/resolv.conf is this: > > search my.domain.tld > nameserver IP_of_1st_DC > nameserver IP_of_2nd_DC Any idea why I still get this when trying to log on to a member server while the first DC is down? # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while getting initial credentials Ole

...> > > > > Just to recap you do you both servers listed as available DNS servers > > on your workstations? As well as your member server? > > Yes, of course. For member servers, this is the content of > /etc/resolv.conf: > > search my.domain.tld > nameserver IP_of_1st_DC > nameserver IP_of_2nd_DC > > > > I made a small tweak but haven't fully tested is adding the following > > options to my resolv.conf. > > > > cat /etc/resolvconf/resolv.conf.d/tail > > options timeout:1 > > Great, this sounds exactly as what I ne...

Hi, I tested the AD (Samba4) domain log-in on Windows 7 clients and Linux member servers with my PDC being offline (plugged the cable). It is not working so well. On Windows it initially takes forever. It works again after rebooting the client, which seems to be the easiest solution (can be performed by the user). On Linux member servers, ssh log-in eventually times out. It works again,

...stated that bind9 will be the only solution. > > Just to recap you do you both servers listed as available DNS servers > on your workstations? As well as your member server? Yes, of course. For member servers, this is the content of /etc/resolv.conf: search my.domain.tld nameserver IP_of_1st_DC nameserver IP_of_2nd_DC > I made a small tweak but haven't fully tested is adding the following > options to my resolv.conf. > > cat /etc/resolvconf/resolv.conf.d/tail > options timeout:1 Great, this sounds exactly as what I need! However, I tried this: no effect. I created...

...tial credentials" > > > My /etc/krb5.conf looks like this (following your suggestions, > Rowland, as everything else are defaults): > > [libdefaults] > default_realm = MY.DOMAIN.TLD > > And my /etc/resolv.conf is this: > > search my.domain.tld > nameserver IP_of_1st_DC > nameserver IP_of_2nd_DC > > > So from a Windows client point of view, I am more or less fine (even > without restarting the machines). But it would be great if I could > log-in to the Linux member servers as well. > > Ole > > > I am getting nearer, I can now ad...

...C for realm 'MY.DOMAIN.TLD' while getting initial credentials" My /etc/krb5.conf looks like this (following your suggestions, Rowland, as everything else are defaults): [libdefaults] default_realm = MY.DOMAIN.TLD And my /etc/resolv.conf is this: search my.domain.tld nameserver IP_of_1st_DC nameserver IP_of_2nd_DC So from a Windows client point of view, I am more or less fine (even without restarting the machines). But it would be great if I could log-in to the Linux member servers as well. Ole

...; My /etc/krb5.conf looks like this (following your suggestions, >> Rowland, as everything else are defaults): >> >> [libdefaults] >> default_realm = MY.DOMAIN.TLD >> >> And my /etc/resolv.conf is this: >> >> search my.domain.tld >> nameserver IP_of_1st_DC >> nameserver IP_of_2nd_DC > > Any idea why I still get this when trying to log on to a member server > while the first DC is down? > > # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while > getting initial credentials > > Ole > > > Ole,...

...t;>> Rowland, as everything else are defaults): >>>> >>>> [libdefaults] >>>> default_realm = MY.DOMAIN.TLD >>>> >>>> And my /etc/resolv.conf is this: >>>> >>>> search my.domain.tld >>>> nameserver IP_of_1st_DC >>>> nameserver IP_of_2nd_DC >>> >>> Any idea why I still get this when trying to log on to a member >>> server while the first DC is down? >>> >>> # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while >>> getting...

...t;>> Rowland, as everything else are defaults): >>>> >>>> [libdefaults] >>>> default_realm = MY.DOMAIN.TLD >>>> >>>> And my /etc/resolv.conf is this: >>>> >>>> search my.domain.tld >>>> nameserver IP_of_1st_DC >>>> nameserver IP_of_2nd_DC >>> >>> Any idea why I still get this when trying to log on to a member >>> server while the first DC is down? >>> >>> # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while >>> getting...

...;>> Just to recap you do you both servers listed as available DNS servers >>> on your workstations? As well as your member server? >> Yes, of course. For member servers, this is the content of >> /etc/resolv.conf: >> >> search my.domain.tld >> nameserver IP_of_1st_DC >> nameserver IP_of_2nd_DC >> >> >>> I made a small tweak but haven't fully tested is adding the following >>> options to my resolv.conf. >>> >>> cat /etc/resolvconf/resolv.conf.d/tail >>> options timeout:1 >> Great, this soun...

...servers >>>>>> on your workstations? As well as your member server? >>>>> Yes, of course. For member servers, this is the content of >>>>> /etc/resolv.conf: >>>>> >>>>> search my.domain.tld >>>>> nameserver IP_of_1st_DC >>>>> nameserver IP_of_2nd_DC >>>>> >>>>> >>>>>> I made a small tweak but haven't fully tested is adding the following >>>>>> options to my resolv.conf. >>>>>> >>>>>> cat /etc/re...

...as available DNS servers > >>>> on your workstations? As well as your member server? > >>> Yes, of course. For member servers, this is the content of > >>> /etc/resolv.conf: > >>> > >>> search my.domain.tld > >>> nameserver IP_of_1st_DC > >>> nameserver IP_of_2nd_DC > >>> > >>> > >>>> I made a small tweak but haven't fully tested is adding the following > >>>> options to my resolv.conf. > >>>> > >>>> cat /etc/resolvconf/resolv.conf....

...c/krb5.conf looks like this (following your suggestions, > > Rowland, as everything else are defaults): > > > > [libdefaults] > > default_realm = MY.DOMAIN.TLD > > > > And my /etc/resolv.conf is this: > > > > search my.domain.tld > > nameserver IP_of_1st_DC > > nameserver IP_of_2nd_DC > > Any idea why I still get this when trying to log on to a member server > while the first DC is down? > > # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while getting > initial credentials > > Ole > > > &...

Hi all, Wish you a happy new year altogether! Mathias, James, let me first say that I highly appreciate your help with all your testing and writing up your thoughts. Here are my responses: A. I have no different sites, no various subnets; so I don't really know what to do. B. I don't understand the purpose of setting my domain up with different sites with associated networks, if on