Hi,
not sure its an ESX topic or a network issue, but it only manifests on the esx boxes so...
I have two locations connected by a Sophos Red tunnel.
I moved an ESX box from one location to the other (different subnet) and want to add it to vcenter - this fails.
I then tried ssh-ing into the box - fails also. SSH setup has been working perfectly fine while the box was in the local location, so it should not be service/esx firewall related.
If I ssh into another box on the same subnet as the remote esx box (a freenas vm hosted on the esx) this works fine, so it should not be a firewall issue either (plus i could only see allowed packages, no drops in Sophos).
From that box i can ssh into the ESX box as well.
Ping, traceroute to the esx box are fine, from a windows box even telnet to the ssh port is working (showing challenge), but not ssh itself.
Locally I can connect my local ESX boxes also, but if I ssh to a remote box (freenas vm again) and then try to connect back to the local esx that fails as well.
So basically as soon as I try a remote ssh to an ESX box it fails. It work locally and it works for non ESX boxes.
Remote ESX has a single vmk, local have 2 vmks (vsan) but default route should be fine.
Any ideas what to look at?
p.s. vSphere Client is working fine as well
Edit: Fixed an issue with tracroute that was mentioned, problem was due to incorrect subnet setup of vsan interface. Does not change ssh problem:/
not sure its an ESX topic or a network issue, but it only manifests on the esx boxes so...
I have two locations connected by a Sophos Red tunnel.
I moved an ESX box from one location to the other (different subnet) and want to add it to vcenter - this fails.
I then tried ssh-ing into the box - fails also. SSH setup has been working perfectly fine while the box was in the local location, so it should not be service/esx firewall related.
If I ssh into another box on the same subnet as the remote esx box (a freenas vm hosted on the esx) this works fine, so it should not be a firewall issue either (plus i could only see allowed packages, no drops in Sophos).
From that box i can ssh into the ESX box as well.
Ping, traceroute to the esx box are fine, from a windows box even telnet to the ssh port is working (showing challenge), but not ssh itself.
Locally I can connect my local ESX boxes also, but if I ssh to a remote box (freenas vm again) and then try to connect back to the local esx that fails as well.
So basically as soon as I try a remote ssh to an ESX box it fails. It work locally and it works for non ESX boxes.
Remote ESX has a single vmk, local have 2 vmks (vsan) but default route should be fine.
Any ideas what to look at?
p.s. vSphere Client is working fine as well
Edit: Fixed an issue with tracroute that was mentioned, problem was due to incorrect subnet setup of vsan interface. Does not change ssh problem:/
Last edited: