Guys I could REALLY use some help setting up Home and Leb network

You need to login to view this posts content.

 

USE VLANS to solve your problem

I think what I would do in your situation is to use the two mobo nics to solve your problem: config one nic to use VLAN2 on10.0.1.2 and the other nic to use VLAN 10 for your lab. Now windows will only allow one nic to have a gateway so use your gate way to point at your WAN access. On the other nic use leased addresses because as part of DHCP leases you can set a gateway for each lease. Forget the second router it’s not needed config your switch to use VLAN 2 on the ports connected to you home gear and config VLAN 10 to all ports used for the lab and bobs your uncle

 

Your problem comes down to this: from the N300 router's point of view, everything that's on its WAN side is "external" and part of the Internet, including your 10.0.1.x subnet. Conceptually, just think of the N300 as a normal home router where the WAN port connects to the "Internet service provider" and the 10.0.2.x subnet is the home subnet. Think of what you would have to do if you were somewhere on the internet and were trying to connect to a computer on a home subnet.

Normally to ping a router from the WAN (external, Internet) side or connect to any services from outside to the inside, you'd have to configure the router's settings, open up ports and do port forwarding etc. For example for Remote Desktop, you would have to configure the N300 router to forward port 3389 to the appropriate 10.0.2.x address of your server. From a device on the 10.0.1.x network, you would have to remote desktop to the N300's WAN address, such as 10.0.1.100. With the setup you described, you will never be able to directly ping any 10.0.2.x address from 10.0.1.x.

You do not need VLANs to fix the problem as described above.

 

if this was your goal..why wouldn't you run directly from HP switch or Netgear "static" IP , allow server to take care of dhcp , routing , Vswitching for vm's ??

 

is the Dell server the only member of your "lab"? You will see once you start messing with the features how uncomplicated you can have your setup..especially if your lab will be contained within your server with vm's

 

I think rmilyard's approach is sound and I like it. He is keeping his Lab network completely isolated from the rest of his home network. This means he can screw things up on the Lab network as much as he wants.

@rmilyard: Keep doing what you are doing, keep 10.0.1.x and 10.0.2.x separate. You can do whatever the hell you want in your lab network (dhcp, dns etc.) and it won't mess up your home network.

As for remote desktop-ing into the VMs, you have two options:
1) As you yourself already suggested, remote desktop into the server, then from the server remote desktop into a VM. Such double-layered remote desktop-ing does work, I use it all the time. (If you are using Hyper-V as the hypervisor, then you can also use regular Hyper-V connection to a VM instead of the 2nd remote desktop.)
2) Open additional ports on the N300, one for each VM you want to remote desktop to. I don't recommend this solution, as the port configurations between the VMs will get messy.

 

his lab network involves one "1" server. no need for the n300 what-so-ever! He can set his vswitch to the 10.0.2.x for his vm's using his server's second lan port and keep his "lab network" isolated. once you open and foward ports from one lan to the other..not isolated anymore. if his procurve is a managed switch..well things just got a lil crazier didn't it. I didn't try to steer him one way or the other , he will find out through trial and error like we all have..but nothing is "sound" with his setup!

@rmilyard.. in time you will find less complicated ways to do your setup..if it works..so be it

 

You need to login to view this posts content.

 

took me a couple times for it to load..it's an online pdf

 

just an example..your setup works, don't sweat it. thats why your setting up a lab in the first place