?
Solved

IP Change, Can't Access ESXi VMs On Network

Posted on 2014-03-22
3
Medium Priority
?
1,230 Views
Last Modified: 2014-03-27
Hi Experts

We are having to change the ip range on our network, due to running out of ip addresses.

The IPs have been changed on the ESXi hosts and they can be accessed across the network, but when changing the IP on any VM on any host, they can't be accessed from the network, they also can't see each other.

We are not currently running any vLans, we are running ESXi 5.5, the VMs are Windows 2012 DC.

The subnet and gateway has been changed, and all physical devices can be accessed and are working, I have tried removing the virtual NIC and re-adding it with no luck.

The vm does report a strange IP address under the VMware summary page in vSphere client, and the range on each NIC within vSphere still shows the old network, but it's my understanding this can't be changed as it is non editable and updates itself.

Any help is greatly appreciated, as currently all my virtual servers are down

Thanks

Jon
0
Comment
Question by:Jon C
  • 2
3 Comments
 
LVL 12

Expert Comment

by:Vaseem Mohammed
ID: 39947860
Hi,
In case of domain controller, try a restart after changing the IP.
When you are changing the IP address on VM, have you tried pinging the gateway IP?
Also, try to register the new IP address in DNS (ipconfig /registerdns)
DCdiag /Fix will take care of re-registering service records in DNS.
No sure if changing the portgroup will help but can give a try by creating a new VM portgroup and move the VM with changed IP to newly created PortGroup.
If you have an extra NIC on Host, try to create a new vSwitch and move the VM to new vSwitch.
0
 

Accepted Solution

by:
Jon C earned 0 total points
ID: 39947998
Thanks for the reply, I had already tested your suggestions, after looking into the logs on the VMs, it said that there was an ip conflict for every ip, it also detailed the same MAC address on each error.
This was found to be an old Cisco switch on the network causing a conflict, once this was removed, everything started working
0
 

Author Closing Comment

by:Jon C
ID: 39958390
See post for resolution
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Understanding the various editions available is vital when you decide to purchase Windows Server 2012. You need to have a basic understanding of the features and limitations in each edition in order to make a well-informed decision that best suits …
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
Suggested Courses

615 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question