transfering fsmo roles caused slow my network places if tranferer goes offline.dns looks funny.
- From: "James W. Long" <JamesLong@xxxxxxxxxx>
- Date: Sat, 11 Feb 2006 02:48:43 -0500
Hi all:
I added a win2k3 dc to my win2k (p)dc. I tranferred 6 roles to the new
win2k3 dc,
rid,pdc,infrastructure,domain naming,schema master and Global Catalog.
but when I transferred the GC, the OLD win2k dc was off.
these dc's had already been replicating many times before that.
I also set the time service as master on the new dc,
and the browser service as ISdomainmaster TRUE on the new DC.
Then I went into DNS and found the OLD DC under "gc"
so I changed its address, its ptr(automatically) and its name to point to
the new win2k3 dc. why did I have to do this?
for a while there, I had duplicate records after I refreshed the forward
zone
(the ones I had changed re-appeared as they originally were again!)
but now it seems to look ok, I think it is back to one.
but I am not sure for all those ldap entries. the dc entry is correct.
"browstat status" reveals the master browser switches around as machines
are turned off. (for instance, turning off the new win2k3 DC makes the
master browser become the OLD win2k DC. so that works correctly.)
all "seems" good and dcdiag and netdiag run fine except the following
problem which really annoys us.
1. If I turn off the OLD win2k DC, my clients and even the win2k3 server
have to wait 30 seconds in My Network Places before they
get the list of the things in there. I thought this would all be in the GC?
or related to the master browser?
2. no client has a kerberos ticket in netdiag, is that normal?
I dont want to dcpromo to demote the win2k dc until "the network"
stops relying on it. what causes that huge delay in my network places?
I am running all 100mbs and My Network Places has zero problem
if both the new win2k3 dc AND and the old win2k dc are up,
but that is not what I need.
Thank you in advance,
James Long
.
- Prev by Date: Re: unable to resolve DNS
- Next by Date: Re: unable to resolve DNS
- Previous by thread: Re: unable to resolve DNS
- Next by thread: Re: TCP/IP DNS Settings
- Index(es):
Relevant Pages
|