Forum Discussion
VMs on the same VNET can not talk to each other
Not sure what is exactly happening since it was always working before but VMs on different subnets within the same virtual network with no NSGs or firewalls between them can not talk to each other. Ping is failing as well as any other sort of communication. Firewalls are disabled on both sides. All machines have access to internet. Communication was tried using IP addresses and not names. Both ping as well as TCP based tests were used.
In that case i suggest you file a ticket so the network can be checked in the back end.
There are couple of things that could be at work here.
When you say 'talk to each other', what do you mean?
You mentioned the VMs have internet connection so i am assuming you are able to access them via RDP. Can you Port Query the RDP port from one VM to another? if so whats the result?
Mean I can not ping between them or can not open TCP connection between them. Yes internet and routing to proper Internet works fine, just communication between them is not. I'm using IP addresses for communication, firewalls on hosts are disabled.
PS C:\Windows\system32> Test-NetConnection 10.0.0.4 -port 3389 WARNING: Ping to 10.0.0.4 failed -- Status: TimedOut WARNING: TCP connect to 10.0.0.4:3389 failed ComputerName : 10.0.0.4 RemoteAddress : 10.0.0.4 RemotePort : 3389 InterfaceAlias : Ethernet 2 SourceAddress : 10.0.1.5 PingSucceeded : False PingReplyDetails (RTT) : 0 ms TcpTestSucceeded : False
The same test running against VM on local subnet works fine as expected
PS C:\Users\cloudadmin> test-netconnection 10.0.1.5 -port 3389 ComputerName : 10.0.1.5 RemoteAddress : 10.0.1.5 RemotePort : 3389 InterfaceAlias : Ethernet 7 SourceAddress : 10.0.1.6 PingSucceeded : True PingReplyDetails (RTT) : 3 ms TcpTestSucceeded : True
OK.
Let do a 'Route Print' and 'ipconfig /all' on 10.0.0.4 to confirm there is no custom route diverting traffic on the OS level.
