RISLA
asked on
ESXi 4.0 - vSphere Client/SSH issue.
I'm having an issue not being able to SSH to either of my ESXi hosts from workstations.
I also cannot download the vSphere client from http://xx.xx.xx.xx, although even the installation I already have is no longer connecting to either of the two hosts. (I've tried root and admin). I can ping both hosts, but cannot telnet to them.
The only access I have to the vSphere client is through vCenter...which can also SSH and Telnet into both hosts just fine.
I checked our *new* firewall, SSH is allowed and there has been no logs of the connections being rejected.
I also cannot download the vSphere client from http://xx.xx.xx.xx, although even the installation I already have is no longer connecting to either of the two hosts. (I've tried root and admin). I can ping both hosts, but cannot telnet to them.
The only access I have to the vSphere client is through vCenter...which can also SSH and Telnet into both hosts just fine.
I checked our *new* firewall, SSH is allowed and there has been no logs of the connections being rejected.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
xKincaidx I just configured my second interface to a 10 network and was able to get in (Thank you!)
I've configured a NAT policy for public web servers, but never for two internal subnets to communicate. Is it pretty straight forward?
I've configured a NAT policy for public web servers, but never for two internal subnets to communicate. Is it pretty straight forward?
e.g. telnet <ip address of host> 443
e.g. telnet <ip address of host> 80
test the above from vCenter Server and Workstations, what are the results?