Avatar of maximus81
maximus81
Flag for United States of America asked on

Exchange server keeps getting multiple preferred IP addresses

We have two Exchange Server 2010 that are both Virtual Machines. The issue we are seeing is for some reason one of them keeps getting multiple IP addresses and its causing issues with out users. That are experiencing disconnects. Where could this second IP address be coming from. I looked in DHCP and I don't see the second IP address assigned to this server.

Could this be an issue with VMware? Thanks
ExchangeEmail Servers

Avatar of undefined
Last Comment
jar3817

8/22/2022 - Mon
peelers

how many vNics do you have on the VM?  is the server set to static IP or DHCP?  where are you seeing the 2nd IP address.. in ipconfig?
maximus81

ASKER
There are 3 nics assigned to both Exchange servers. One is for the network and the other two are for communication to each other. The second IP address when you type in ipconfig /all is right below the current Preferred and its set as a static IP.
peelers

can you send a screenshot of the ipconfig/all pls?

also what is the reasoning in having 2 nics between the 2 exchange boxes?
Your help has saved me hundreds of hours of internet surfing.
fblack61
maximus81

ASKER
We rebooted the server and the IP address went away but once it comes back i will add a screenshot. The other two NICS are used for the Heartbeat and Administration. I didn't set them up so don't exactly what there used for.
maximus81

ASKER
The IP address is back, here is the screenshot.
maximus81

ASKER
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
peelers

ok so your exchange servers are clustered.  when clustered there are "virtual" services that get created so that your exchange service is highly available (hence the extra IPs).  the heartbeat network isn't really needed anymore in Win 2008 as you already have 2 networks that the cluster can use for cluster communications but you can ignore that for now.

given above, the issue is not your extra IP address, all that is supposed to be there.  you need to start checking the health of the cluster (see if it is constantly failing over on its own between the two hosts, use Failover Cluster Manager), and if thats fine, check your vmware infrastructure to make sure 1) your virtual cluster-in-a-box is configured correctly, and 2) you don't have issues with connectivity to the ESXi hosts themselves.  also do a ping -t to one of the VMs from a non-VM and make sure there are no strange drops..

more to do but start with this first
Sandy

Run DHCP client monitoring in the network there you will found the DHCP discover packets.

This will give you info of DHCP Server who is giving you the IP address.
ASKER CERTIFIED SOLUTION
jar3817

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.