rour report is due in one time duration. It should include your answers, the r w
ID: 3605368 • Letter: R
Question
rour report is due in one time duration. It should include your answers, the r well as the supporting screenshot or printouts (before after) and explanation result of your test-implementatioans as Part A: t supports a large floor that can be split in 3 distinet rooms (7 ports per room), each rented or leased to customers (sometimes the whole room is lea sed to a single customer) 1) 2) Propose a solution to implement such network using only one switch Implement and test your solution. Requirements a) Give a description/presentation of this network device. b) Make sure that no one can make change to the network setup except for the administrator that will always connect on port 24 using the same machine (PC1). c) Make sure that the PCs can only be connected to the port that the administrator (you) originally connected them to. NO one but the administrator can manage the network. Would it be possible to make the 3 sections appear as one, in the case it is leased to one customer? Explain your answer and propose an implementation and test it on a simulator only, do not test it on the d) e) network. Make sure to specify the condition under which you did the test (ie use of console port or GUI to manage list the physical and logical addresses of each PC and the port number they are connected through) f)Explanation / Answer
Here is how I would attack the setup.
Set up the server to run Hyper-V or ESX.
Create a vm in a private virtual network (no connction to the physical LAN).
Give it a static IP in its own IP subnet. Run dcpromo and accept the offer to configure DNS for you.
Setup DHCP and authorise it in AD.
Create a second vm and install another instance of Windows Server or a client OS. Link it to the same virtual network as tha DC.
You should now have all you need to experiment with AD.
When you are happy that you understand how AD works you can connect this network to the physical network. The best way to do this is to configure a vm as a router between the two networks. You can use RRAS as a NAT router, or you can configure it as a LAN router so that you have full networking between the two networks. (This latter setup requires adding a static route to your D-Link). Or you could run a software firewall like ISA server.
The real problem is DNS. You will need to configure forwarders on your local DNS to resolve "foreign" URLs. Configuring forwarding to your D-Link should work for that. That is another reason to run AD in a separate network. AD is not compatible with the DHCP and DNS setup of a ADSL "router".
To run a web server, I would not put it in the private network. I would run it on the physical home network (rather like running it in a DMZ). If you put the web server in the private (AD) LAN it will be two hops from the Internet and you will need to jump through hoops to see it from outside your network. If you want to run the web server in a vm, it would need to link to the virtual network linked to the physical network. That is the network which is the "public" side of your router/firewall vm. In Hyper-V this is called an external private network (not sure what ESX calls it - maybe bridged).
Here is a simple diagram of my current setup with the virtual machines/networks running under Hyper-V on Server 2008 R2.
Internet
|
Netgear (static route 192.168.31.0 255.255.255.0 192.168.0.99)
192.168.0.1
|
LAN machines
192.168.0.x dg 192.168.0.1 (config from Netgear)
|
192.168.0.99 dg 192.168.0.1 --------------------------------
RRAS LAN router |
192.168.31.254 dg blank |
| |
Server 2008 DC virtual network
192.168.31.1 dg 192.168.31.254 |
| |
AD clients |
192.168.31.x (config from DHCP on DC) --------------------------
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.