I will try to keep this simple. New Exchange 2010 (Server 2008r2) deployment, old Exchange 2007 (Server 2008 SP1) still online. Old Exchange (2007) has two IP's xxx.xxx.xxx.237 & xxx.xxx.xxx.243. The .237 is for an internal device (receive connector already set) and the .243 is the primary address (set up through firewall and spam filter). After adding the secondary IP of .237 for the internal device (IPv4 network properties) on the new Exchange 2010 (xxx.xxx.xxx.202 w\rules set in firewall and spam filter) all outgoing mail stops and builds in the queue. Then after removing it from the new Exchange Server 2010 (.202), mail continues to go out as usual. After many hours of searching it is my understanding the lower IP becomes the"primary" IP. Therefore, the new primary IP for the new Exchange 2010 (.202) shouldn't have any problems, nor be overtaken by the higher IP of .237. So my question is:
Why would adding a higher secondary IP (i.e. xxx.xxx.xxx.237) seemingly overtake the send connector or primary IP of the server (xxx.xxx.xxx.202)?
I could open the .237 up on our firewall and spam filter but we do not want this particular device to have outside access (only internal). I've been to the end of the internet and back trying to figure this out. Any help would be greatly appreciated.
Thank You-
Daniel