9 replies
by archeologistbb Accepted solution
by alex.beckwith Accepted solution
I recently had to do this for a current project for test purposes.
I promoted a second server box by specifying it was a peer joining an existing network.
Nothing else, nothing fancy. It knew it's place.
Switched off the primary domain controller and all the PC's on the network authenticated OK but squealed about roaming profiles (understandably because the accounts were hardcoded to look at the PDC particular computer name) but logged in with cached accounts fine.
Just checking if you've tried the basics first.
by p.j.hutchison Accepted solution
What is installed on the workstations? If using legacy OS such as NT4 or 98 then the DC running the PDC emulator role must be available.
If using Windows 2000 Pro or XP Pro, then it shouldn't matter.
It also helps if you allow cached credentials on your network, so if a user has logged in a PC at least once you can login again, even with no DCs present.
by archeologistbb Accepted solution
The 1st DC is the FSMO master for all roles + PDC emulator - but as you said, if all the clients are 2000+ it doesn't matter (which is true). For security's sake - we cannot allow cached logins. Both #1DC and #2DC are GC's (global catalog servers) and both are running DNS and update each other with changes - however, all the clients in the network point to a third DNS server that isn't part of AD - but we do regular zone transfers/copies to keep it up to date. I know it must seem backwards the way we are doing things - but its DoD, and they are itsec paranoid. Any other ideas?
**EDIT**
I just ran dcdiag /v /c /e on both DC's and they both come back clean as a whistle (except for #2DC complaining about not being able to forward dns requests - which is by design).
by julian.bennett Accepted solution
by p.j.hutchison Accepted solution
It could be a DNS issue. Run nslookup on all three dns servers.
Try the domain name, does it display all the ipaddresses of all your DCs (does it change when you re-enter it).
Check that all DNS servers have all the SRV resource records eg _ldap, _kerberos, _gc and CNAME records for the DC servers.
by archeologistbb Accepted solution
by archeologistbb Accepted solution
by jkatju2005 Accepted solution
1. Switch both the DCs in windows server 2003 native mode (both on domain-level as well as forest-level)... [in AD domains and trusts].
2. in TCP/IP properties of the local area connction, in DNS servers tab, insert the local ip as the primary DNS and the other DC's IP as secondary DNS
and check it out.
3. install support tools from the Windows server 2003 CD ((\support) folder).
4. on the GC (Global Catalog Server... First DC)... start >> run >> replmon >> press enter (follow instructions)
You will be up and running :-)
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending