Re: Sites and services

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

anonymous_at_discussions.microsoft.com
Date: 09/20/04


Date: Mon, 20 Sep 2004 11:37:21 -0700


>-----Original Message-----
>"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in
message
>news:elLY92xnEHA.3396@tk2msftngp13.phx.gbl...
>> <anonymous@discussions.microsoft.com> wrote in message
>> news:21ab01c49f19$83fb74b0$a501280a@phx.gbl...
>> > THe clients get their dns settings through DHCP
which is
>> > on the same DC. the clients get assinged two DNS
servers,
>> > the primary is the same server as the dc and the
>> > secondary is the main dns server in a another site.
The
>> > client are allowed cached logons but would new users
or
>> > users with new passwords be able to log on? THank
you for
>> > your help
>> > >-----Original Message-----
>> > >"Jesse Hullihen" <Jesse.hullihen@kingharm.com>
wrote in
>> > message
>> > >news:473401c49f11$f67527f0$a601280a@phx.gbl...
>> > >> What happens when their is only one DC assinged
to a
>> > site
>> > >> and that DC goes down? Will clients still be able
to
>> > >> logon and work as normal through other DC's in
differnt
>> > >> sites?
>> > >
>> > >It depends on how the clients have their DNS
settings
>> > configured, and again
>> > >how your DNS servers themselves are configured, how
your
>> > AD Sites and
>> > >Services are configured, and whether you allow
cached
>> > logons or not. More
>> > >details on your question will allow us to provide a
>> > better answer.
>> > >
>> > >--
>> > >Todd J Heron, MCSE
>> > >Windows 2003/2000/NT
>>
>> Is the other site part of the same domain or not?
Assuming the other site
>> *is* part of the same domain, clients should be able
to find that second
>DNS
>> server and logon to the domain, albeit more slowly,
assuming that there is
>> in fact a DC for their domain in that other site, and
of course, bandwidth
>> conditions. If no DCs for the domain are available,
clients who have
>> previously logged on will be able to logon with cached
credentials. New
>> users or users with new passwords will not be able to
log on.
>>
>> --
>> Todd J Heron, MCSE
>> Windows 2003/2000/NT
>
>To add,
>
>No DNS = cannot find anything in AD (including DCs).
And no DCs = cannot
>logon to AD unless cached credentials can be utilized.
And a whole host of
>other stuff will happen in this scenario as well. This
is just from the
>client perspective.
>
>--
>Todd J Heron, MCSE
>Windows 2003/2000/NT
>
>
>Thanks alot. You have been very helpful.
>



Relevant Pages

  • Re: Start again on the newbies networking problem. Re: Need help (of course) setting up network
    ... As you are working on this, do download the latest ... > servers that will help you later. ... ; guest account = pcguest ... ; logon script = %m.bat ...
    (Fedora)
  • Re: WMI in ASP fails on 2003 (err 80041003); works fine on 2000
    ... > Strike the comment about the interactive logon. ... I still don't see the need for delegation. ... >>> tested it on two servers with no problems. ... >>> interactive logon - thus WMI to remote machine should be a single hop) ...
    (microsoft.public.win32.programmer.wmi)
  • Re: cant receive or send e-mail
    ... Does it show anything for Logon Information? ... Also, on the Servers tab, does the incoming server belong to the ... Do not enable the "Log on using Secure Password Authentication". ... Does it also do so before receiving? ...
    (microsoft.public.windows.vista.mail)
  • Re: Disapearing DC
    ... This computer was not able to set up a secure session with a domain ... There are currently no logon servers available to service the logon request. ... This may lead to authentication problems. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Created users cant immediately login
    ... In order for your clients to logon, ... > server that is in a remote location, with a different subnet. ... >> The other servers are for authentication in case the network fails. ...
    (microsoft.public.windows.server.active_directory)