|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by KSComputing in Domain Name Service (DNS), Active Directory, Windows 2003 Server
I had a Windows 2003 Server running as the only DC for a domain ending with .com. It servered various capacities including DNS, DHCP, RAS, terminal server, terminal services licensing server, FTP, File & Print sharing and of course since it was the only DC it held all FSMO roles. We added another 2003 server to the domain and promoted it to DC. DNS, DHCP, FTP, RAS were added to it then all the FSMO roles were transferred to it. Everything was working well, replication was taking place as expected. The global catalog server role was transferred to the new DC as well. After hours of running well, replication issues developed. The replication issues were being caused by DNS issues. The local name of one of the DCs was being resolved to an internet IP address. Running the command ipconfig /flushdns resolved the issue but it returns over time especially when the servers are rebooted. The issue is not limited to one specific name and never happens to all local names at once. Our local domain is sc.fsm.com. There is an fsm.com register on the internet but we never experienced this issue until the addition of the second server. I'm thinking something went wrong when DNS was configured on the new DC. BTW, in an attempt to resolve an event log error I created a host record in GC under msdcs that pointed to the IP of the new server with the name (same as above). A similar record already existed pointing to the old DC's IP. Global catalog was removed from the old DC after adding it to the new. When the names were resolving properly neither DC gave any errors from DCDIAG or NETDIAG. WINs is not configured anywhere in the domain. Since then I have transferred all the FSMO roles and global catalog back to the old dc and demoted the new DC. its still running as a member server. Any ideas as to why this might have happened and what we can do to avoid it would be great. The plan is to move all the roles from the old DC to the new DC except for terminal services which will be on a seperate member server. Also I don't think it makes a difference but a C name was created referencing the new DC. It was going to be used by file/print clients so that in the event of failure the C name could be pointed to a backup server. Thanks in advance for all the help
20091111-EE-VQP-89 / EE_QW_2_20070628
