Hello and thank you for taking the time to read this post. Here is my situation:
Physical server configured with one NIC card. IP address is: 192.168.1.136
Physical server is acting as the domain controller and running DNS services.
Physical server is running Windows Server 2012 and utilizing the Hyper-V Feature.
Hyper-V virtual switch has two virtual switches created. They're as follows:
10.10.10.2
10.10.20.2
I have numerous virtual machines working off of these two virtual switches without issue.
The physical server has Routing and Remote Access configured and working for NAT traffic for these virtual switches. All virtual guests are able to access the internet without a problem.
The problem comes in when I try to use my workstation PC. This is also a physical computer configured with one NIC as follows:
IP: 192.168.1.116
Subnet: 255.255.255.0
Gateway: 192.168.1.1 (This is the IP of the Linksys Router)
I'm trying to use this workstation PC to access my virtual guests running on 192.168.1.136. I understand that when I try to connect to something like 10.10.10.4, the Linksys router has no idea where this is. Therefore, I've configured a static route. Unfortunately, the static route is not working as I expected. Here is how I have the static route setup:
Destination LAN IP: 10.10.10.0
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.136
Destination LAN IP: 10.10.20.0
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.136
When I ping 10.10.10.4 from my 192.168.1.116 workstation, it's unable to reach it. I'm not sure what I could missing and any help would be appreciated. I can of course ping the physical server 192.168.1.136 without issue.
I did try changing the Destination LAN IP from 10.10.10.0 to 10.10.0.0 just to see if that would work. It did not. I also tried using the Linksys IP address for the gateway and that does not accept as a valid route.
Physical server configured with one NIC card. IP address is: 192.168.1.136
Physical server is acting as the domain controller and running DNS services.
Physical server is running Windows Server 2012 and utilizing the Hyper-V Feature.
Hyper-V virtual switch has two virtual switches created. They're as follows:
10.10.10.2
10.10.20.2
I have numerous virtual machines working off of these two virtual switches without issue.
The physical server has Routing and Remote Access configured and working for NAT traffic for these virtual switches. All virtual guests are able to access the internet without a problem.
The problem comes in when I try to use my workstation PC. This is also a physical computer configured with one NIC as follows:
IP: 192.168.1.116
Subnet: 255.255.255.0
Gateway: 192.168.1.1 (This is the IP of the Linksys Router)
I'm trying to use this workstation PC to access my virtual guests running on 192.168.1.136. I understand that when I try to connect to something like 10.10.10.4, the Linksys router has no idea where this is. Therefore, I've configured a static route. Unfortunately, the static route is not working as I expected. Here is how I have the static route setup:
Destination LAN IP: 10.10.10.0
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.136
Destination LAN IP: 10.10.20.0
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.136
When I ping 10.10.10.4 from my 192.168.1.116 workstation, it's unable to reach it. I'm not sure what I could missing and any help would be appreciated. I can of course ping the physical server 192.168.1.136 without issue.
I did try changing the Destination LAN IP from 10.10.10.0 to 10.10.0.0 just to see if that would work. It did not. I also tried using the Linksys IP address for the gateway and that does not accept as a valid route.