How to setup a lab with it's own internet access...

[wilddoktor]

Hi all; new to the forums and hope to gleen some info from the experts!

I've created a "test lab" consisting of an old linksys befsr11 router (wan port is not plugged in; lan port plugged into a small switch), a windows 2008 domain controller (w/DHCP and DNS, GC server for its own forest), a 2008 terminal server (Remote Desktop Server), and a few thin clients plugged into the switch, getting desktops from the RDS.

I intend to bring this entire "lab" to potential client sites to let them test drive it for a few weeks at a time.

The dilema I'm wrestling with is this: how do I hook this lab up to their current infrastructure so that the lab gets web access, but doesn't touch their current LAN or disrupt it in any way? What do I replace the linksys with? Where do I plug this router into the existing LAN?

Thoughts?

 

[thiggins]

It's mostly up to your client(s) to isolate you from their LAN(s). The router is primarily protecting their traffic from reaching your "lab".

The main thing you can do with the router is limit the outbound ports that clients can access.

 

[YeOldeStonecat]

You can set it up on a unique IP range on your befsr11 routers LAN port, one that you probably will never run across at another network, like 192.168.19.xxx
Set your DC to static, like 192.168.19.11, your other servers, etc. DHCP on your DC naturally, and DNS, etc, other infrastructure.
Leave the WAN port of the Linksys set to dhcp/obtain auto, it should pull a valid IP from your "hosts" network.

You're fairly well isolated from your hosts LAN...they cannot get to you well. Someone from inside your LAN can "find" your hosts network without too much effort.

Another option if you want total complete isolation, bring along a router that supports Evdo cards on the WAN interface..and use the cellular part for your WAN connection, this way you never have to touch your hosts network. Granted...reception is up to the building that you are visiting that day.