Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

Can't manage ESXi 6.7 from different subnet

$
0
0

I had a standalone ESXi 6.7 host operating fine.  I needed to put it on a different subnet on the same physical switch.  The switch is layer 3 with multiple VLANs.  I changed the IP address and default gateway of the ESXi host and put it on the new VLAN, and now I cannot manage it with either the web interface or SSH.  I can ping it just fine, and I can manage it if I plug a computer into the same VLAN, but I cannot manage it from a different VLAN.

 

I remember running into this a few years ago, and it was a setting that blocked management from other VLANs by default, but after a few years I cannot remember what that setting was.  I tried everything I can think of, and I've rebooted the host, but still no luck.

 

EDIT:  I forgot to mention that when I try to connect over the web interface from the remote subnet, I don't get a timeout, instead I get a connection reset.  The ESXi host is sending a reset to my client.

 

Can anyone help with this?

 

Thanks

 

On a side note, I want to point out that it seems kind of dumb to me that ESXi won't allow you to change the default gateway first, then change the IP address.  It would only allow me to change the gateway after changing the IP address.  The problem with this is once I change the IP address, then the gateway is set for a different subnet and I can no longer reach the host remotely.  If I could change the gateway first, it wouldn't matter since it's originally on the same subnet, and then I could change the IP address afterwards, but VMware won't allow me to do it this way, which seems to me the much more sensible way.  I just wanted to mention how bad I feel that design is, in case someone from VMware reads this.


Viewing all articles
Browse latest Browse all 8132

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>