Troubleshooting issues connecting to a VM via a public IP address or Skytap-managed DNS name
If you’re having trouble connecting to a VM over its public IP address or Skytap-managed DNS name, try the following steps:
Confirm that the VM is running.
You can’t use a public IP address or Skytap-managed DNS name to connect to a VM that is suspended or shut down.
If you recently created the Skytap-managed DNS name, wait a few minutes before trying to access the VM.
It may take several minutes for the name to propagate.
Confirm that the expected service is running on the VM.
For example, if you’re trying to connect to a web site hosted on the VM, access the VM using the another access method (for example, the SRA browser client) and use the command line or another application to check that the expected service (Apache, nginx, etc.) is running.
- Confirm that you’re trying to access the service over the correct port.
- Verify that the VM guest operating system or application firewall settings allow inbound access over the expected port.
Notes about connecting to the public IP address from:
Within the VM
Skytap routes traffic from the public IP address to the VM local IP address via Network Address Translation (NAT). Within the VM, the public IP isn’t visible to the guest OS or applications running on the VM. For example, if you’re logged into a firewall appliance VM that is attached to a public IP address, you’ll need to access the appliance’s web interface from the VM local IP address (example: 10.0.0.1).
Other VMs in the same environment
Generally, a VM can’t ping a public IP address that is attached to another VM in the same environment. VMs on the same network must communicate with one another using their private network IP addresses.
For more information, see Can I connect to a public IP address or published service from another VM in the same environment?