Configuring Static Routes

Shadowjk said:

Remove the network bridge if you have already made one, my apologies Also change the IP address of the interfaces back to how they should if they changed. They should return to the original static configurations if the bridge is removed.

On the main server:

Go into Routing and Remote Access

Right click the server in the left hand pane and click on 'Configure and Enable Routing and Remote Access

Attachment 304137

Click Next to start the wizard. On the next page click on the 'Custom Configuration' radio button and then click next.

Attachment 304138

From here check the 'LAN Routing' tick box to enable the routing of traffic between each interface

Attachment 304139

Now click next and finish to end the configuration. You may be prompted about starting the service. Just start the service if asked.

Attachment 304140

Now, with the workstation client (192.168.1.116) the static routes should still be in place with the server as the gateway. Now try to initiate a connection. Remember that firewalls could block the communication so temporarily disable them if you have any enabled.

Test connectivity? Any quicker than without NAT?

If it is then you can keep that LAN routing config. To enable internet connection to the VMs simply add static routes on the linksys router that says something like:

Destination Address: 10.10.10.0
Mask: 255.255.255.0
Next Hop/Gateway: 192.168.1.136

Destination Address: 10.10.20.0
Mask: 255.255.255.0
Next Hop/Gateway: 192.168.1.136


Again, my apologies for creating the network bridge... I forgot this was a server that could do routing...

Josh :)

No problem about the network bridge. You've been so extremely helpful.

So, everything worked as you instructed. On the workstation, I removed the static routes, rebooted, and decided to enter it again. I entered route add 10.10.10.0 mask 255.255.255.0 192.168.1.136

From the workstation I can now ping and connect via RDP.

I tested some copying and pasting.

Test copy was done using a folder of 840 KB and 5 files inside it.

Copying from 10.10.10.4 to 192.168.1.136 was instant.

From workstation connected to \\10.10.10.4\c$ Copied folder to desktop of Workstation. Noticeable slowdown in speed. It worked, just took between 1-2 minutes.

Copying from 10.10.20.4 to 10.10.10.4 about 1 minute.

From 10.10.20.4 connected to \\192.168.1.136\c$ Copied folder instantly.

Internet connectivity via static route on the router now allows for systems to access the internet.

So I'm thinking I just have to live with the slower speeds? Other than that, everything works fantastic.

Shadowjk said:

Hmm... Is all of this running of one HDD? As in one HDD used for the server host and the two VMs? That might be a possible cause.

Another thing is the possibility for the physical NIC to be a bottleneck for traffic flowing through it. What is the bandwidth like on the NIC? Is it onboard or a PCI type one?

I'm taking wild guesses here since I have never personally deployed hyper-v. As a student I don't really have the money to get a machine that could run it half decently aha! I'll keep thinking about this throughout the day and post back suggestions that I may find

Josh :)

The server has 8 physical drives in it. 1 drive is setup for the OS. The 7 drives are setup to run the VM's with RAID-0. No redundancy and built as just a lab. The NIC is a Broadcom BCM5709C NetXtreme II GigE. The speed on the NIC is set to Auto. The NIC is PCI I'm about 99.9% sure.