Pinging the namespace? Sorry, I'm not sure I understand how? Apparently
there's a larger gap in my knowledge base than I had previously discovered. :)
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Kennedy, Jim
Sent: Thursday, June 11, 2015 2:55 PM
To: [email protected]
Subject: [NTSysADM] RE: Slow access after DC replacement
Pinging the namespace from the DC is quick and correct?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Melvin Backus
Sent: Thursday, June 11, 2015 2:51 PM
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] RE: Slow access after DC replacement
That was actually the first thing I thought about too. I checked the client
setups. DNS is set via DHCP and the new server is pointing to itself as
expected. I did a spot check on client machines and they're all fine in that
respect.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Edward Berner
Sent: Thursday, June 11, 2015 2:35 PM
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] RE: Slow access after DC replacement
If the old DC was also a DNS server, maybe the clients are still pointing to it?
Edward
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Melvin Backus
Sent: Thursday, June 11, 2015 11:22 AM
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] Slow access after DC replacement
OK, I'm going around spinning my wheels on this one and the tread is getting
kinda thin. :)
I've got a remote office which has an RODC that we're replacing. Rather than
trying to do a direct replacement of the hardware we're moving from 2008r2 to
202r2 as well, so I stood up the new server, added it as a new RODC, etc. I've
migrated all the printers, DHCP, and since all the file shares were DFS I added
the new server as another node on all those.
I've marked all the DFS shares for the old server instances as disabled so no
one is accessing them, but what we're seeing is that as soon as the old server
is taken offline file access times slow to a crawl. When I brought the old
server back online (just powered back on) everything returns to normal.
The only thing that I've found that was different was the Password Replication
list between them, and I corrected that. This morning we simply unplugged the
network cable and access is back to a crawl again.
Obviously I've missed something in the picture but I'd appreciate some
suggestions of other things to check.
--------------------
Melvin Backus | Sr. Systems Engineer | Byers Engineering Company | 404.497.1565
Service Desk | 404-497-1599 | http://servicedesk.byers.com
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
