I have a Windows 2008R2 64bit server running Exchange 2010 utilizing two NICs. NIC1 is on the inside and NIC2 receives Mapi and OWA connections from the outside. I've had a terrible time with the server and clients preferring the outside NIC over the inside NIC.
When I first setup the server I was getting two internal DNS entries for my exchange server. My clients seemed to prefer connecting to the entry for NIC2 and because of a static route in my firewall would time out, and only then connect to NIC1. Which obviously slowed down access time and generated lots of calls.
Things I've tried:
-changed the Interface Metric to 10 on NIC2
-took the check out of "Register this connection's addresses in DNS"
NIC2 was still registering in DNS and my workstations were still preferring to use it.
Next I tried:
-disabling NIC2 and adding a second IP to NIC1
Same problem, My outside address was still registering and my workstation preferred to try it first.
So I removed the second address on NIC one, went back to NIC2 and ran:
-Netsh int ipv4 add address <Interface Name> <ip address> skipassource=true
Now this finally put a stop to NIC2 registering in DNS, and after I flushed everybody's cache and deleted NIC2 from all my DNS servers, all seemed fine.
However, now I seem to be having a new problem. My exchange server cannot ping several WAN DC servers unless I disable NIC2,(obviously because NIC2 does not have a DNS entry due to the Netsh command above) which is kicking up errors like the one below in Application Event viewer.
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1852). Exchange Active Directory Provider is unable to connect to the Domain Controller server.domain.com although its service location (SRV) resource record was found in the DNS
The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.com
The following domain controllers were identified by the query:
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running.
For information about correcting this problem, Type in the command line:
I can't ping them either.
If I disable NIC2 communications immediately function fine. I can't seem to figure out why at every turn NIC2, or its address seems to be preferred.
Any help would be great