Connectivity issue with Classic VM

New Contributor

I have a classic VM instance running in Azure (CentOS 7). I have an endpoint rule that allows to connect through 22 port from my address. Firewalld is disabled, iptables are not installed at all. However, I can't access the VM through 22 port, even after explicitly adding my ip address (instead of whole subnet ip-address belongs) to a whitelist. I've tried to trace route of the packages and here's what I got:

  7         3 ms    TimeExceeded
  8        18 ms   TimeExceeded
  9        19 ms []        TimeExceeded
 10        61 ms []  TimeExceeded
 11       149 ms []   TimeExceeded
 12       143 ms []     TimeExceeded
 13       144 ms []    TimeExceeded
 14       144 ms []   TimeExceeded
 15       142 ms [] TimeExceeded
 16       143 ms []   TimeExceeded
 17       145 ms []     TimeExceeded
 18       142 ms [] TimeExceeded
 19      2002 ms        timed out
 19      2001 ms        timed out
 19      2001 ms        timed out
 20      2002 ms        timed out
 20      2002 ms        timed out
 20      2001 ms        timed out
 21      2001 ms        timed out

 Endpoint rules:


I can connect to that VM using another Azure VM which is whitelisted in "Endpoints". Is this some sort of network issue? I can easily telnet that port from another VM and can't do that from my working PC. Other Azure VMs are accessible without any problems.

3 Replies

Did you check the NSGs you have to allow the port 22 for inbound port from anywhere or specific IP

I don't have any NSG assigned to that VM. There are only endpoint rules.

1st rule covers a subnet my ip-address belongs to. The last rule includes only my ip-address.

I also have a rule for another server's address and from that server port is open but if I add my computer's ip, VM is not accessible through the same port. It really seems like firewall exceptions work only for some ip addresses.


Are you sure the your Public IP is a static. can you put instead and check the RDP is allowed