Sophos updating could not contact server

This tutorial will demonstrate the steps for deploying Exchange Server 2010 as a Client Access Server array using Windows NLB.

This is a demonstration only, and should not be taken as a recommendation to use Windows NLB for your load balancing.

Two or more Exchange Server 2010 Client Access Servers can be configured as a CAS array using NLB as long they are not also installed as Mailbox servers that are members of a Database Availability Group (DAG).

The reason is that DAG members utilize Windows Failover Clustering, which can't co-exist with NLB.

The Global Address Book (GAL) is a directory of available contact information for CUMC, NYPH and Columbia University faculty, staff and students.

It can be accessed when using a CUMC email (@cumc.columbia.edu) account with Outlook or when logged in to the Outlook Web App.

To demonstrate the setup of a CAS array the following servers have been provisioned.

Server #1 Note: In my lab the servers are also Hub Transport servers, and so I installed both sets of pre-requisites. Although the port rules can be made more specific, in this example the default rule is acceptable.

The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then A friend not on SF said: "That's normal, PTR is only updated by DHCP in Win2K ".

If you are not seeing correct contact information in the GAL for someone that has a valid email address (i.e.

someone who just received a CUMC email account, a new student, someone who recently changed their directory information) please use the steps below to synchronize your computer's locally cached version of the GAL.

A flag of "0" means the client updates the A record and requests that the server update the PTR record on its behalf. Also in the DHCP scope make sure == Click the DNS tab, click Properties, and then click to select the Dynamically update DNS A and PTR records only if requested by the DHCP clients check box == is set.

This would mean when the default flag of "0" comes in the server will then try to register the PTR record with the DNS server(s) it is configured to update.