Isolate local VLAN traffic from office network

I have just set up a Hyper-V VLAN on my office workstation for the purpose of testing network changes prior to implementation. The VLAN has a host server running Windows Server 2016 with DHCP, DNS, Windows Deployment Service and Active Directory. There are
also 2 clients running Windows 10. Currently the VLAN is on a Private switch, so there is no risk of my VLAN traffic bleeding into my office network. I’m at the point where I need to connect this VLAN to the internet, but in a way that there is no risk of
introducing any VLAN traffic, rogue DHCP servers, DNS explosions or any other assorted goodies onto my office’s production network. My workstation hosting this VLAN is a client on my office network which has a Windows 2012 R2 server also running DHCP, DNS
and AD, so there’s plenty to go wrong if don’t do this properly. I’ve set my VLAN on a different subnet, 192.168.10.# vs the office’s 192.168.20.#. I’m not sure if this is sufficient, or if there’s more that I’m missing. 

I know I’m not the first person to do this, but despite all my searching, I can’t seem to find anything that addresses my particular configuration. I’m still new to this, though, so maybe I’m not searching the right terms. Also, if someone knows a good tutorial
to point me toward, that would be great too.


Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 46 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995