Hi,
I have been trying to access one VM from another VM both within a CS and within a VNET. Let me summarise all that I have done in the last couple of days.
I have VM1 and VM2 in the same CS and same VNET. I have disabled windows firewall in both the vms for testing purpose. VM1 internal IP Address is 10.0.0.4. VM2 internal IP Address is 10.0.0.5. Both VM1 and VM2 are pingable from each other.
VM1 runs my own virtual device network I created using one of our virtual device tools. The IP range of the virtual devices is 10.0.0.6 to 10.0.0.13 When I ping from VM1 itself all the .6 to .13 virtual devices are pingable. [Additionally, I installed asset
scanner in vm1 itself and was able to scan .6 to .13 successfully and ping successfully].
VM2 also runs a asset scan software. I open a cmd and route add as follows:
>route ADD 10.0.0.0 MASK 255.255.255.0 10.0.0.4
where 10.0.0.0 is the target network which would include 10.0.0.6 to 10.0.0.13. 10.0.0.4 is the gateway.
Now, I go to the asset scan [running in VM2 with internal ipaddress 10.0.0.5]. From its web client I initiate a asset scan giving the IP range as 10.0.0.6 to 10.0.0.13. the software is not able to detect/discover the virtual devices .6 to .13 [the virtual devices
running in vm1] Why?
From this vm2, I pinged 10.0.0.6, no response. I pinged 10.0.0.7 no response.... 10.0.0.13 no response.
HOWEVER, we created the above scenario using 2 physical servers in our LAN and it all worked fine.
Where/what am I missing?
K.Lakshmi Shankar