Essay Help Services

ICTNWK505 | Assessment 4 Lab Network Services | IT

Home Recent Questions ICTNWK505 | Assessment 4 Lab Network Services | IT

1. IP address revision

For this initial part of the lab, no DHCP server should be active on your isolated network. 

• Make sure W99-SERVER1 is shut down. 

• Start the W99-CLIENT1 (restart the VM if it was previously running)

• Confirm that:

o The NetBIOS name of the Windows 10 machine is W99-CLIENT1. If required, rename the Windows 10 machine. 

o All IPv4 adapter settings on the W99-CLIENT1 are automatically allocated. 

o IPv6 is not active (unselected in the adapter properties)

• On W99-CLIENT1, open a PowerShell prompt and issue the command:  ipconfig /?

• Read through the listed options carefully because you will have to use some of them in this lab. 

• Issue the ipconfig command that will show the full configuration information for the network adapters on W99-CLIENT1. If required, expand the screen so that all settings are visible in the PowerShell window. 

a) Provide a screenshot of the PowerShell window showing all results listed. The screenshot must also show the VM title bar. Paste your screenshot below this line. 


2. DHCP

In this exercise, you will complete the DHCP configuration on W99-SERVER1.

• Start the VM W99-Win2016-Full-1-DE-Eval

• Sign in to W99-SERVER1 as w99-admin

• Open the DHCP management console and set the focus on the IPv4 ‘W99-Scope’

• Restart W99-SERVER1

• After the restart sign in as w99-admin and confirm that the DHCP scope is active, if not, activate the scope

Switch to W99-CLIENT1

• On W99-CLIENT1 open a PowerShell prompt with ‘Run as administrator’

• To ensure the updated scope settings are applied on W99-CLIENT1 without delay, issue the command that will renew the IPv4 address of the adapter (refer to section 1. for details).

• To confirm that W99-CLIENT1 was assigned an IPv4 address from the DHCP server, issue the command that will show full configuration information of the IP address configuration. If required, expand the screen to show all results of this command. 

d) Provide a screenshot of the PowerShell window demonstrating that W99-CLIENT1 was assigned the above DHCP scope settings (the screenshot must also show the VM title bar). Paste your screenshot below this line. 


3. DNS

The Domain Name System (DNS) is a hierarchical decentralised naming system for computers, services, or other resources connected to the Internet or a private network. Most prominently, it translates more readily memorized domain names to the numerical IP addresses needed for locating and identifying computer services and devices on the underlying network.

On W99-CLIENT1:

• Assign a static IP address to W99-CLIENT1 using the settings below:

IP address: 10.19.99.121

Subnet mask: 24-bit

Preferred DNS server: 10.19.99.1

Switch to W99-SERVER1:

• Open DHCP management and deactivate IPv4 the scope you previously created (scope ‘W99-Scope’). DHCP will not be used for this part of the lab. 

• On W99 SERVER1 add the ‘DNS Server’ role. 

• Once DNS is installed, open the DNS management console (found with the ‘Administrative Tools’ on the server).

• Create a new primary Forward Lookup Zone (FLZ). In the ‘New Zone Wizard’ use the following settings:

  o Zone name: W99.local

  o Keep all other default settings and complete the wizard.  

• Create a new primary Reverse Lookup Zone (RLZ). In the ‘New Zone Wizard’ use the following settings:

  o Select IPv4

  o Specify the first three octets of your subnet: 10.19.99. The wizard will then assign the zone name ‘99.18.10.in-addr.arpa.dns’ to the zone. 

  o Keep all remaining default settings and complete the wizard.  

• In the left pane select the Reverse Lookup Zone that you created previously, right-click the zone and select ‘Refresh’ 

• Check that the PTR records for W99 SERVER1 and W99 CLIENT1 were correctly created. If the PTR records are missing you have to create them manually. 


You are to familiarize yourself with using the nslookup command. nslookup is a command-line tool for querying the DNS to obtain the domain name, the IP address mapping or any other specific DNS record.

• On W99-CLIENT1 open a PowerShell prompt with ‘Run as administrator’ and run the command:  nslookup /?

• This will list the available command options. Leave this window open, as you will use it as a reference for looking up the command options for nslookup. 

• Open another PowerShell prompt on W99-CLIENT1 with ‘Run as administrator’ and run the command:  nslookup to enter the nslookup command line mode. 

• While in the nslookup command line mode, issue the commands listed in the table below and observe the output:

• If any of the above nslookup commands return an error, check that you typed the command correctly, check your DNS setup and check the DNS records that you have created. Retrace your steps, by following the above instructions carefully. Fix any issues as required. Then repeat the nslookup commands. 

• You are to copy the text output of the nslookup commands into this document. To do this, left-click the upper left corner of the PowerShell window, select ‘Edit’ and ‘Select All’ and then hit the ‘Enter’ key. This will copy the text from PowerShell window to the Clipboard. Assuming your VM is configured to share the Clipboard, you will be able to paste the data into a document on the host PC. Resolve any issues that may prevent you copying text from the VM window to the host. 


4. IIS – Web server

Internet Information Services (IIS) is an extensible web server provided with Windows.  

In this part of the lab you will install IIS, setup websites and manage access to these sites via DNS. The website source files used in this assessment can be found on your host in folder C:Server-ResourcesWeb-Sites. 

On W99 SERVER1:

• Map C:Server-Resources as shared folder to access the required files

• Make sure that the File Explorer options on W99 SERVER1 are configured to show the file extension

• From the shared folder copy the folders Website1 and Website2 to C: and rename the two folders to show your ID (rename folders to C:W99-Website1 and C:W99-Website2)

• To turn W99 SERVER1 into a web server proceed as follows:

  o Add the ‘Web server (IIS)’ role. 

  o In the in the ‘Role Services’ window of the ‘Add Roles and Features Wizard’ add:

- HTTP Redirection

- Basic Authentication

• Open the ‘Internet Information Services (IIS) Manager’ (the IIS Manager can be found with the ‘Administrative Tools’ on the server).

• In the IIS Manager select ‘Sites’ and stop the ‘Default Web Site’

• Complete the following additional configuration for both websites:

  o Make the html file that is located in the corresponding website folder the default webpage for the web site:

- In IIS select the website (left pane)

- Double-click on ‘Default Document’ (in the right pane)

- Remove all listed documents

- Add the full name (including extension) of the html file that is located in the corresponding website folder (do not specify a path!)

  o Enable directory browsing (this makes troubleshooting easier but is normally not enabled on production websites):

- Select the website

- Double-click on ‘Directory Browsing’ 

- In the right pane select ‘Enable’


Switch to W99-CLIENT1

• You will use W99-CLIENT1 to test network access to the websites. In Windows 10, the Administrator account is not allowed to use the Edge browser. To complete this part, you therefore either have logon to W99-CLIENT1 as another local user, or use the Firefox browser that is preinstalled on W99-CLIENT1. 

• On W99-CLIENT1 start a browser and access the two websites via IP address (and port number if required)

Switch to W99-SERVER1

• In DNS, create a primary FLZ called website1.local (follow previous instruction for creating a primary zone) 

• In the FLZ website1.local create:

  o A host record called W99 and assign it the IPv4 address of W99 SERVER1

  o An alias record called www that references the FQDN for W99 in the FLZ website1.local

• On W99-SERVER1 in DNS create a primary zone called website2.local (follow previous instruction for creating a primary zone)

• In the FLZ website2.local create:

  o A host record called W99 and assign it the IPv4 address of W99 SERVER1

  o An alias record called www that references the FQDN for W99 in the FLZ website2.local

• On W99-SERVER1 in IIS set up http redirection whereby when someone connects to http://www.website1.local they are redirected to http://www.website2.local. 

• Open IIS, select W99-Website1, and in the right pane double-click on ‘HTTP Redirect’. 

• Select the ‘Redirect requests to this destination’ checkbox, in the URL field type http://www.website2.local and in the ‘Actions’ pane click on ‘Apply’

• On W99-SERVER1 open a PowerShell prompt using ‘Run as administrator’ 

• Issue the command:  

Get-DnsServerResourceRecord -ZoneName "website1.local"

• Followed by:

Get-DnsServerResourceRecord -ZoneName "website2.local"

• Expand the PowerShell window so that the output of both commands fits into the window. 

Switch to W99-CLIENT1:

• Make sure W99-CLIENT1 can successfully ping the FQDN’s www.website1.local and www.website2.local. Resolve any communication issues if required


5. Managing services using PowerShell

Services may be managed via the Graphical User Interface (GUI) and/or via the Command Line Interface (CLI). 

• Using the ‘Services’ GUI tool find the ‘Service name’ of the ‘World Wide Web Publishing Service’ and the ‘DHCP Server’ service. You will use these names to manage these services via PowerShell.

• Open a PowerShell prompt with ‘Run as administrator’

• To show a count of the services installed on W99-SERVER1 issue the command: (Get-Service).Count

• To show a count of the services currently running on W99-SERVER1 issue the command: (Get-Service | Where-Object Status -eq "Running").count

• Using the ‘Stop-Service’ PowerShell command stop the ‘World Wide Web Publishing Service’:

Stop-Service <name of WWW service>

• Using the ‘Get-Service’ PowerShell cmdlet check the status of the service

Get-Service <name of WWW service>

• Using the ‘Start-Service’ cmdlet starts the service again

Start-Service <name of WWW service>

• Using the ‘Get-Service’ PowerShell cmdlet confirm that the service is running

Get-Service <name of WWW service>

• Using the ‘Set-Service’ PowerShell cmdlet change the startup mode of the ‘DHCP Server’ service to manual startup (DHCP on W99-SERVER1 will not be used in the following assessments) 

Set-Service <name of DHCP service> -startup type Manual

• Using the ‘Get-Service’ PowerShell cmdlet confirm that the DHCP service is set to manual startup (make sure the following command is typed as a single line)

Get-Service <name of DHCP service> | Select Status,Name,DisplayName,StartType

Similar Posts

Order Now

Latest Reviews

Facebook

Payments And Security