Jump to content

Recommended Posts

Posted
If you set the DHCP server to assign a scope to a set of machines within Active Directory, that is what it will do, it wont work outside of those constraints

 

you can set the policies to pick the machines within an OU for machines. I learnt this in college, so if I am remembering badly, then fair enough I am happy to stand corrected.

 

As per the article you linked to this is a new feature available with 2012 so unless you've only just left college you're remembering something else entirely and even then the policies that the article talks about are setup in the DHCP mmc and are nothing to do with Active Directory policies.

 

Ben

Posted (edited)
you can set the policies to pick the machines within an OU for machines. I learnt this in college, so if I am remembering badly, then fair enough I am happy to stand corrected.

 

From that linked page, it looks like you're right but for the life of me I cannot find 'Policies' in DHCP on my 2012 DHCP server at all!

 

Edit: DERP! Looks like I'm an idiot. :) DHCP MMC on a Windows 7 machine is quite obviously not going to do it is it localzuk?! *slaps face*

 

However, that feature doesn't link to AD or OUs.

Edited by localzuk
  • Thanks 1
Posted
As per the article you linked to this is a new feature available with 2012 so unless you've only just left college you're remembering something else entirely and even then the policies that the article talks about are setup in the DHCP mmc and are nothing to do with Active Directory policies.

 

Ben

 

I did a night course last year in Server 2012. Didn't finish it due to personal circumstances.

Posted
did you not see my post?

 

yes - excluding DC I'm not understand what the other abrievations mean and also can't see where the firewall sits and you have a number of things off of one branch ( presumably cable )

 

Was hoping for something a bit more detailed / in depth so I can see where you would connect the firewall to and what the proxy connects ie

 

So Router from ISP --> firewall ( whether software or hardware ) --> proxy server --> VPN --> ?????

Posted (edited)
[ATTACH=CONFIG]23283[/ATTACH]

 

Don't know how much this will help, or confuse more, but this is a (very) rough layout of our current network topology.

 

That's more like it - just a few things

 

* Which physical server are the virtual servers running on ?

* SMB Folder shares is that a SAN or NAS or something to that effect ?

* VHD Access switch - what is this and what does it do / what is its purpose etc ? I thought VHD meant Virtual Hard Drive

* DMZ Switch - Is this an actual switch that is configured to place certain servers / items into the DMZ ?

* How come the smoothwall utm ( which deals with vpn / proxy / firewall etc ) has 2 connections into the DMZ Switch , they aggregated links or because said device deals with so many roles ie proxy / vpn / firewall etc so needs the extra connections ?

 

 

I presume the smoothwall UTM deals with all the different roles so proxy / firewall / vpn etc

Edited by mac_shinobi
Posted (edited)

* Which physical server are the virtual servers running on ?

Everything in the diagram is physical. So there are three individual physical host servers. The square brackets underneath give an indiciation of individual running virtual machines.

 

* SMB Folder shares is that a SAN or NAS or something to that effect ?

Technically I believe it qualifies as a NAS set up in a SAN-like configuration.

 

* VHD Access switch - what is this and what does it do / what is its purpose etc ? I thought VHD meant Virtual Hard Drive

This is the network route virtual machines hosted on the virtual servers take to access their virtual hard drives stored in a SMB share on the file server.

 

* DMZ Switch - Is this an actual switch that is configured to place certain servers / items into the DMZ ?

Physical switch on the "live internet" side of the firewall. Anything plugged into it has a live public IP address.

 

* How come the smoothwall utm ( which deals with vpn / proxy / firewall etc ) has 2 connections into the DMZ Switch , they aggregated links or because said device deals with so many roles ie proxy / vpn / firewall etc so needs the extra connections ?

 

2 routers, each with thier own 14 address subnet. One link to each subnet from the smoothwall. Allows the smoothwall to provide loadbalancing and failover between the two routers.

 

 

I presume the smoothwall UTM deals with all the different roles so proxy / firewall / vpn etc

Yes

Edited by tmcd35
Posted
Everything in the diagram is physical. So there are three individual physical host servers. The square brackets underneath give an indiciation of individual running virtual machines.

 

 

Technically I believe it qualifies as a NAS set up in a SAN-like configuration.

 

 

This is the network route virtual machines hosted on the virtual servers take to access their virtual hard drives stored in a SMB share on the file server.

 

 

Physical switch on the "live internet" side of the firewall. Anything plugged into it has a live public IP address.

 

 

 

2 routers, each with thier own 14 address subnet. One link to each subnet from the smoothwall. Allows the smoothwall to provide loadbalancing and failover between the two routers.

 

 

 

Yes

 

I would be interested in how the VHD Access Switch works to allow the different virtual machines / servers to access there relevant virtual hard drives stored on the SMB Share / File Server or is it just like vmware fusion etc where you have a profile for each virtual machine / server and in that profile it has the config ie which virtual hard drive said virtual machine uses and it points to the relevant VHD ??

Posted

(fake IP's)

 

Core Network addresses - 10.95.32.0-10.95.33.255

VHD Network addresses - 172.45.28.0-172.45.28.255

External IP addresses - 229.39.174.28-229.39.174.42

 

SMB File server has 2 IP addresses. One on core network (10.95.32.16) which users use to access shared folders (\\10.95.32.16\home$\%username%). The other on the VHD network (172.45.28.10) which virtual machines use to access their disk images (\\172.45.28.10\VHD$\PrintSvr\).

 

Both connections use 2x1Gbps bonded pairs and TOE (TCP/IP Off-load Engine, less CPU load) nics. The VHD network uses Jumbo frames for faster data transfer.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...