Any reason why the service console is not reachable outside its own VLAN
Posted on 2007-11-26
I have 2 recently built VMWare ESX3.x servers. All appeared to be fine on them when I set them up in our server room, i.e. I could access the service console for configuration and building of VM's etc.
I have now relocated to my office and desktop PC, which is on a different VLAN to the ESX servers and the servcie console is not reachable (via ping's of SSH connections). So ... In summary the service console can only be reached via machines on the same VLAN as the service console.
I have made an SSH session on to the service console and done a ping to my desktop (and several other devices across several VLANS) which responds fine, thus proving the networking and defualt gateway is set up fine. ALSO when I ping my desktop PC from the service console it appears to open up a hole in the firewall and enables me to access the service console from my desktop PC (shortly after I kill the ping my desktop PC loses the access to service console again).
There doesn't appear to be anything in our network set-up that would cause problems like this, is there something in ESX I need to configure, for example a firewall setting ?