gateguard
asked on
Mail Server Dependent on Domain Controller?
On a small office domain, with two domain controllers, 1 & 2, both running server 2003. There is also a separate mail server, running server 2003 and exchange 2000.
I am new to this domain but I just noticed that when I reboot DC2 all outlook connections to the exchange server are frozen, for the entire time that DC2 is rebooting and even a bit longer.
DC2 does have IIS with a Virtual SMTP site, but I don't see that it's really configured to do anything.
And I don't see anything on the exchange server pointing explicitly to this domain controller.
Also, DC2 has terminal server installed, though no users are running any applications on this server and there are no applications other than windows installed.
Where can I start looking to see find our what connection there is between the exchange server, this dc2, and outlook clients on workstations throughout the network.
I am new to this domain but I just noticed that when I reboot DC2 all outlook connections to the exchange server are frozen, for the entire time that DC2 is rebooting and even a bit longer.
DC2 does have IIS with a Virtual SMTP site, but I don't see that it's really configured to do anything.
And I don't see anything on the exchange server pointing explicitly to this domain controller.
Also, DC2 has terminal server installed, though no users are running any applications on this server and there are no applications other than windows installed.
Where can I start looking to see find our what connection there is between the exchange server, this dc2, and outlook clients on workstations throughout the network.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The solution would be to make the other DC a GC, wait for the notation in the Active Directory event logs stating that the server is now a GC, and then reboot the DC. After that the gc should be able to respond to requests properly.
Cheers,
Bob
Cheers,
Bob
ASKER
Well, it's definitely true. DC2 has the Global Catalog box checked in its NTDS Settings Properties and DC1 doesn't.
Can I have two Global Catalog servers?
Can I have two Global Catalog servers?
ASKER
I see the answer to my question is "yes, but don't".
http://www.petri.co.il/configure_a_new_global_catalog.htm :
Configuring an excessive number of GCs in a domain wastes network bandwidth during replication. One GC server per domain in each physical location is sufficient. Windows NT sets servers as GCs as necessary, so you don’t need to configure additional GCs unless you notice slow query response times.
Anyway, Bob, thanks for the info. I'll be careful rebooting this machine in the future. Maybe enabling a 2nd GC first.
http://www.petri.co.il/configure_a_new_global_catalog.htm :
Configuring an excessive number of GCs in a domain wastes network bandwidth during replication. One GC server per domain in each physical location is sufficient. Windows NT sets servers as GCs as necessary, so you don’t need to configure additional GCs unless you notice slow query response times.
Anyway, Bob, thanks for the info. I'll be careful rebooting this machine in the future. Maybe enabling a 2nd GC first.
flyguybob, do you mind checking out this link I opened a while ago? I have a similar problem, but with more than one DC as a GC:
https://www.experts-exchange.com/questions/21329083/Exchange-2000-and-FSMO-GC-requirements.html
https://www.experts-exchange.com/questions/21329083/Exchange-2000-and-FSMO-GC-requirements.html
If you have two DCs and only one is a GC and it is a small site, the additional replication traffic should not be much of a concern.
ASKER
Ok. I'll try it. Thanks again.
Anytime.
Please see my post at https://www.experts-exchange.com/questions/21409700/How-to-make-RUS-fault-tolerant-in-a-single-Exchange-Server-2003-environment-and-dns.html
it not only references your redundancy regarding global catalogs, but also shows how to configure additional RUS (Recipient Update Servers) and additional DNS servers in the Exchange System Manager. see below:
Redundacy for Recipient Update Services in Exchange: How to Add a New Recipient Update Service
To add a new Recipient Update Service: 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the Recipients object, and then click the Recipient Update Services container.
3. Right-click Recipient Update Services, point to New, and then click Recipient Update Service.
4. Click Browse next to "Domain" to display a list of domains in your forest.
5. Click the domain that you want this Recipient Update Service to update, and then click OK.
6. Confirm that the domain that you selected is displayed in the New Object - Recipient Update Service dialog box, and then click Next.
7. Click Browse, click the Exchange server on which you want this instance of the Recipient Update Service to run, and then click OK.
8. Click Next.
9. Click Finish.
10. Right-click the new Recipient Update Service object that you created, click Properties, configure the Update interval setting, and then click OK.
Note When you are creating a Recipient Update Service, you cannot select the domain controller. You can only select the domain that you want the new Recipient Update Service to be associated with. After you have finished creating the Recipient Update Service, you can edit the properties of the Recipient Update Service and select the domain controller that you want.
Redundancy for DNS in Exchange 2003:
When I took down one of my DC's for maintenance the other day and my Exchange server stopped functioning correctly - couldn't resolve external DNS to send mail. I thought since the server NIC had two internal DNS servers listed (the one taken down plus another DC/DNS server) it would automatically forward all requests to the secondary DNS server listed in the NIC config.
I then found about the setting (in Exchange) that lets you tell Exchange directly) what DNS servers to use. See below
Directly setting DNS Servers in Exchange System Manager
1. Start Exchange System Manager.
2. Expand Your_Organization (where Your_Organization is the name of your Exchange organization).
3. Expand Servers, and then expand Your_Server (where Your_Server is the name of your server).
4. Expand Protocols, and then expand SMTP.
5. Right-click Your_SMTP_Virtual_Server (where Your_SMTP_Virtual_Server is the name of your SMTP virtual server), and then click Properties.
6. Click the Delivery tab, and then click Advanced.
7. Click Configure next to Configure external DNS Servers.
8. Click Add, type the IP address of your internal\external DNS servers, and then click OK
it not only references your redundancy regarding global catalogs, but also shows how to configure additional RUS (Recipient Update Servers) and additional DNS servers in the Exchange System Manager. see below:
Redundacy for Recipient Update Services in Exchange: How to Add a New Recipient Update Service
To add a new Recipient Update Service: 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the Recipients object, and then click the Recipient Update Services container.
3. Right-click Recipient Update Services, point to New, and then click Recipient Update Service.
4. Click Browse next to "Domain" to display a list of domains in your forest.
5. Click the domain that you want this Recipient Update Service to update, and then click OK.
6. Confirm that the domain that you selected is displayed in the New Object - Recipient Update Service dialog box, and then click Next.
7. Click Browse, click the Exchange server on which you want this instance of the Recipient Update Service to run, and then click OK.
8. Click Next.
9. Click Finish.
10. Right-click the new Recipient Update Service object that you created, click Properties, configure the Update interval setting, and then click OK.
Note When you are creating a Recipient Update Service, you cannot select the domain controller. You can only select the domain that you want the new Recipient Update Service to be associated with. After you have finished creating the Recipient Update Service, you can edit the properties of the Recipient Update Service and select the domain controller that you want.
Redundancy for DNS in Exchange 2003:
When I took down one of my DC's for maintenance the other day and my Exchange server stopped functioning correctly - couldn't resolve external DNS to send mail. I thought since the server NIC had two internal DNS servers listed (the one taken down plus another DC/DNS server) it would automatically forward all requests to the secondary DNS server listed in the NIC config.
I then found about the setting (in Exchange) that lets you tell Exchange directly) what DNS servers to use. See below
Directly setting DNS Servers in Exchange System Manager
1. Start Exchange System Manager.
2. Expand Your_Organization (where Your_Organization is the name of your Exchange organization).
3. Expand Servers, and then expand Your_Server (where Your_Server is the name of your server).
4. Expand Protocols, and then expand SMTP.
5. Right-click Your_SMTP_Virtual_Server (where Your_SMTP_Virtual_Server is the name of your SMTP virtual server), and then click Properties.
6. Click the Delivery tab, and then click Advanced.
7. Click Configure next to Configure external DNS Servers.
8. Click Add, type the IP address of your internal\external DNS servers, and then click OK
I forgot to take you to the following MS KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;875427
Global catalog server placement and ratios in an Exchange 2000 Server organization or in an Exchange Server 2003 organization.
“For scalability and for fault tolerance, we recommend that you configure at least two global catalog servers in each Active Directory site. If a site spans multiple domains, we recommend that you configure a global catalog for each domain where Exchange 2000 Server computers or Exchange Server 2003 computers and clients reside.”
http://support.microsoft.com/default.aspx?scid=kb;en-us;875427
Global catalog server placement and ratios in an Exchange 2000 Server organization or in an Exchange Server 2003 organization.
“For scalability and for fault tolerance, we recommend that you configure at least two global catalog servers in each Active Directory site. If a site spans multiple domains, we recommend that you configure a global catalog for each domain where Exchange 2000 Server computers or Exchange Server 2003 computers and clients reside.”
ASKER