Trying out Server at home - want to leave router DHCP intact

[JustInspired]

So, I have decided to get my feet wet with a test server. Nothing fancy, just running on Server 2012 Essentials but I need to start somewhere!

I have set it up using all the default recommended settings and I have connected one workstation to its domain. That all works great.

I'd like to use this on the same network that I connect my customers' machines so it will need to also be able to share a folder for backups (and give out IP addresses?) to machines I put on the bench.

This is already a semi separate network in that all my customers machines connect to the internet via the Guest SSID on my WNDR3700 router. The router runs DHCP for everything but the IP range is the same for both main and guest networks - the guest machines can ping but not browse machines on the main network due to some sort of Wireless Isolation in the router.

The customer machines that plug into our LAN sockets (desktops etc) all get fed from a Gigabit switch that in turn gets Internet from a Wireless Bridge.

This way all of my customers' machines can get internet and access a central share without access to my main home network.

So, installing this server on the Guest network has caused a bit of an issue as (1) it cannot seem to get Internet access properly although I can access it from the workstation that I connected to it.
(2) By default I believe the server is trying to play a DHCP role as is the router.

So to test this properly in an isolated network while still getting Internet access via my home router; what do I need to do? Turn off DHCP on the router and stick static IPs on all my home machines? Not sure how my wireless bridge will handle this though as I don't know if it can be assigned a static IP. (it's a Buffalo Air Station)

N.B. I don't have much of a budget either!

I appreciate any pointers.

Many thanks,

Julian

 

[scandalist]

Decide which device you want to handle the DHCP. Its either going to be the router or the server - I'd go with the router personally.

Give your Server a static IP within the range of the local subnet and fill in the routers IP for the default gateway - this should get the server online.

Segmenting your network with only a single router can be tricky, some routers support DMZ which could do the trick but ideally you would need two routers.

Your "guest network" or whatever doesn't sound like its segmenting the network at all if you are able to ping your personal work systems. If you're the paranoid type this isn't something you would want to plug an infected machine into.

I personally jack client machines straight into my local network, never had a problem. I have a theory that viruses don't actually spread anymore like they used to.

 

[JustInspired]

Thanks. I think I might use my old spare router for now, just for the secondary network.
Just need to figure out how to set up one share on the server that will be accessible from any of my customers' machines without them needing to join the domain.