Re: Connect to a DC
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 21 Aug 2006 21:56:19 -0500
"Ian" <Ian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9DAFF921-97AB-4D22-8A5E-0FB839477277@xxxxxxxxxxxxxxxx
found app problem on a PC connecting to a DC that has a replication issue.
This is for troubleshoot reason.
After logon you can (at least in theory) use NLTest to alter the
DC which the client uses for its "secure channel".
This should (in theory) work for testing purposes -- that is a
major part of the reason d'etre for NLTest.
Warning: NLTest has one of the most annoyingly tedious
command lines around so your first step should be to dump
its help into a text file and bring that up in a note pad, since
you will be referring to it often.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"aa" wrote:
why? DC's replicate data between them so they are the same.
Do you mean in ADCU? then yes, right click the domain and select a
domain controller.
Or is your network for some reason using a remote DC instead of a local
one making it slow?
.
- References:
- Re: Connect to a DC
- From: aa
- Re: Connect to a DC
- Prev by Date: Can't have more than one "Run these programs at user logon" policy apply to a group of computers
- Next by Date: Re: Delegating local administrator password reset control
- Previous by thread: Re: Connect to a DC
- Next by thread: Re: Connect to a DC
- Index(es):
Relevant Pages
|