NSP P1

CompTIA Network+
Network Services and Protocols - Part 1
Introduction
Lab Topology
Exercise 1 - Preparing the lab
Exercise 2 - Troubleshooting ICMP Related Issues
Exercise 3 - Understand How ARP Works
Review
Introduction
Welcome to the Network Services and Protocols (Part 1) Practice Lab. In this module, you will be provided with the
instructions and devices needed to develop your hands-on skills.
ARP
IMCP
networking
Learning Outcomes
In this module, you will complete the following exercises:
Exercise 1 - Troubleshooting ICMP Related Issues (including Ping and Traceroute)

After completing this lab, you will be able to:
Access Windows Firewall

Troubleshoot ICMP Related Issues
Explain How ARP Works
Exam Objectives
The following exam objectives are covered in this lab:
N10-007 1.1: Explain the purposes and uses of ports and protocols (Protocol types, ICMP)
N10-007 1.3: Explain the concepts and characteristics of routing and switching (Properties of network traffic, Multicast)
N10-007 5.2: Given a scenario, use the appropriate tool (Software tools, Command line, ping)
N10-007 5.2: Given a scenario, use the appropriate tool (Software tools, Command line, tracert, traceroute)
N10-007 5.2: Given a scenario, use the appropriate tool (Software tools, Command line, ipconfig)
N10-007 5.2: Given a scenario, use the appropriate tool (Software tools, Command line, arp)
Note: Our main focus is to cover the practical, hands-on aspects of the exam objectives. We recommend referring to course
material or a search engine to research theoretical topics in more detail.
Lab Duration
It will take approximately 30 minutes to complete this lab.
Help and Support
For more information on using Practice Labs, please see our Help and Support page. You can also raise a technical support ticket
from this page.
Click Next to view the Lab topology used in this module.
Copyright © Practice Labs 2007 - 2018. All rights reserved.
Lab Topology
During your session, you will have access to the following lab configuration.
Figure 1 Lab Topology - The lab topology is composed of two subnets separated by an Ubuntu device called PLABRTR01
functioning as a router. The first subnet contains three computers. The first, called PLABDC01 is a Windows 2016 Server
with an IP address of 192.168.0.2/24 and functions as the Domain Controller. The second, called PLABSA01 is also a
Windows 2016 Server with an IP address of 192.168.0.3/24. The third, called PLABWIN10 is a Windows 10 device with an
IP address of 192.168.0.4/24. The PLABRTR01 device has an IP address of 192.168.0.1/24 on the interface that connects
to this subnet. The other interface connects to the second subnet with an IP address of 192.168.1.254/24. This second
subnet contains only one other device, the PLABWEB01 device which is also running Windows 2016 Server and has an IP
address of 192.168.1.1/24.
Connecting to your Lab

In this module, you will be working on the following equipment to carry out the steps defined in each exercise.
PLABDC01 (Domain Controller - Windows Server 2016)

PLABSA01 (Member Server - Windows Server 2016)
PLABWIN10 (Workstation - Windows 10)
PLABRTR01 (Router - Linux Ubuntu 17.10)
PLABWEB01 (Web Server - Windows Server 2016)
Click Next to proceed to the first exercise.
Exercise 1 - Preparing the Lab

In order for the lab to function correctly and to have the desired results, it is important for you to complete this prerequisite task
before beginning with Exercise 2.
Learning Outcomes
After completing this exercise, you will be able to:
Your Devices
You will be using the following devices in this lab. Please make sure these are powered on before proceeding.
Task 1 - Prerequisite task
Complete the following steps to prepare the lab.
Step 1
Connect to PLABSA01. Minimize Server Manager.
Right-click the network icon at the bottom right and choose Open Network and Sharing Center.
Figure 1.1 Screenshot of the PLABSA01 desktop: Context menu (that appears by right-clicking the network icon) > Open
Network and Sharing Center menu-options are displayed on the PLABSA01 Windows desktop.
Step 2
At the bottom left, choose Windows Firewall.
Figure 1.2 Screenshot of the PLABSA01 desktop: Network and Sharing Center window is displayed showing the Windows
Firewall link highlighted.
Step 3
Under the Update your Firewall settings section, click the Use recommended settings button.
Figure 1.3 Screenshot of the PLABSA01 desktop: Windows Firewall window is displayed showing the Use recommended
settings button available.
Step 4
Close the Windows Firewall window.
Figure 1.4 Screenshot of the PLABSA01 desktop: Windows Firewall window is displayed showing the firewall switched on
for all the listed login profiles and the Close icon available at the top-right corner.
Leave the device as it is and move on to Exercise 2.
Exercise 2 - Troubleshooting ICMP Related Issues

ICMP, short for Internet Control Message Protocol, is an essential part of an IP network. Various nodes on the network implement
ICMP to send out error messages about issues on the network. These issues include unavailability of a service on the network, or
inaccessibility of a node or a device. Some troubleshooting tools and applications, such as ping and traceroute, implement ICMP.
ICMP normally does not carry data on the network.
To get a better understanding of this technology, please also refer to your course material or use your preferred search engine to
research this topic in detail.
Learning Outcomes

Your Devices

PLABWEB01 (Web Server - Windows Server 2016)
Task 1 - Analyze an ICMP Related Issue
In this task, you will learn to analyze an ICMP related issue - a ping issue.
To analyze an ICMP related issue, perform the following steps:
Step 1
Ensure you have powered on the required devices defined in the introduction. Connect to PLABWIN10 device.
Step 2
Click Start and type cmd. As you begin to type, the search box appears.
Figure 2.1 Screenshot of the PLABWIN10 desktop: Command Prompt menu-option is highlighted on the Start menu.
Step 3
Press Enter. The Command Prompt window appears.
Figure 2.2 Screenshot of the PLABWIN10 desktop: Command Prompt window is displayed on the PLABWIN10 Windows
desktop.
Step 4
In this step you will send an ICMP echo request, that is, a ping to PLABSA01. On the command prompt, enter the command:
ping 192.168.0.3
Press Enter.
The result displays that the ping was unsuccessful.
Minimize command prompt window.

Figure 2.3 Screenshot of the PLABWIN10 desktop: Administrator Command Prompt window is displayed showing the
command typed-in to ping the required IP and system-response to the command.
Task 2 - Try to Resolve the ICMP Issue
In this task, you will learn to resolve the ICMP issue by reconfiguring the firewall settings of the PLABSA01.
To resolve the ICMP issue, perform the following steps:
Step 1
Connect to PLABSA01. Minimize Server Manager.
Right-click the network icon at the bottom right and choose Open Network and Sharing Center.
Figure 2.4 Screenshot of the PLABSA01 desktop: Context menu (that appears by right-clicking the network icon) > Open
Network and Sharing Center menu-options are displayed on the PLABSA01 Windows desktop.
Step 2
At the bottom left, choose Windows Firewall.
Figure 2.5 Screenshot of the PLABSA01 desktop: Network and Sharing Center window is displayed showing the Windows
Firewall link highlighted.
Step 3
Notice that the firewall is on for both private and public networks which are indicated by the green status.
Click on the Allow an app or feature through Windows Firewall at the top left.
Figure 2.6 Screenshot of the PLABSA01 desktop: Windows Firewall window is displayed showing the Allow an app or
feature through Windows Firewall link selected.
Step 4
From Allowed Programs window, scroll down the list and enable File and Printer Sharing check box. Verify that Public
check box is selected.
Click OK.
Note that the ICMP functionality is included within the apps and services that are categorized here as File and Printer
Sharing. Microsoft has chosen to group these together, so by enabling File and Printer Sharing, you should be enabling
ICMP or ping packets to traverse the firewall.
Figure 2.7 Screenshot of the PLABSA01 desktop: Allowed apps window is displayed showing the required selections
performed and the Ok button available.
Step 5
Close Windows Firewall window.
Figure 2.8 Screenshot of the PLABSA01 desktop: Windows Firewall window is displayed showing the Close button
available at the top-right corner.
Task 3 - Verify the ICMP Issue is Resolved
In this task, you will verify that the ICMP issue has been resolved by the reconfiguring of the firewall settings.
To verify the resolution of the ICMP issue, perform the following steps:
Step 1
From PLABWIN10, restore command prompt, again enter the command:
ping 192.168.0.3
Press Enter.
command typed-in to ping the required IP and system-response to the command.
Step 2
The ICMP echo request is successful. Notice the information that is sent back with every request. By default, four requests are sent.
The reply indicates:
IP address of the source of the reply

The size of the ping packet sent
The time the round-trip took
A Time to Live or TTL value of 128
Summarized statistics of the echo request
Minimize the command prompt window.
Task 4 - Learn to use Tracert
The Traceroute or Tracert utility is used to determine the path a packet will take to its destination. In this task, you will use
tracert to examine several paths to various destinations.
Note that the full name of the feature is Traceroute. However, the command from the Windows command prompt is
tracert. Other operating systems and CLI interfaces may use somewhat different syntax.
Step 1
From PLABWIN10, restore command prompt. If there is output from previous commands, you can remove this if you like by
issuing the command cls.
To examine the route packet will take to the PLABWEB01 device, enter the command:
tracert 192.168.1.1
Press Enter.
command typed-in to examine the route packet takes to the specified IP.
Note that this command may take several seconds to execute. Please be patient.
Step 2
The result is a list of two entries indicating the route taken to the destination.
Figure 2.11 Screenshot of the PLABWIN10 desktop: Administrator Command Prompt window is displayed showing
system-response to the command typed-in in the previous step.
Examine this output more closely:
Tracing route to 192.168.1.1 over a maximum of 30 hops

1 1 ms <1 ms <1 ms plabrtr01 [192.168.0.1]
2 1 ms <1 ms <1 ms 192.168.1.1
Trace complete.
The first entry indicates that the first device the packet traversed was 192.168.0.1. Looking at the lab diagram (and from the output
of the trace) you will see that this is the PLABRTR01 device. This is to be expected as this is the default gateway of the
PLABWIN10 device for destinations of 192.168.1.X.
The next entry is the destination device of 192.168.1.1.
So, the trace indicates that PLABWEB01 was reached via the PLABRTR01 device as is expected.
Step 3
In this step, you will initiate a similar trace to a location on the Internet. Specifically, you will ping 8.8.8.8 which is the DNS server
provided by Google.
In order to maintain security on the lab topology and on internal networks, Practice Labs does not allow ICMP packets to
traverse its firewall. For this reason, this tracert command will not work. It is recommended that this command is issued from
the command prompt of your local computer. If you are using a non-windows device, use your favorite search engine to
determine the corresponding commands.
To do this, issue the following command:
Note that the “-d” parameter indicates to the command not to provide DNS name resolution for each step. This will speed up
the process but won’t give domain names for IP addresses of each hop.
tracert -d 8.8.8.8
Press Enter.
The output you should get should be similar to the following:
Tracing route to 8.8.8.8 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.10.1
2 23 ms 22 ms 22 ms 80.107.125.7
3 28 ms 28 ms 27 ms 70.128.224.233
4 27 ms 27 ms 27 ms 61.75.3.153
5 76 ms 76 ms 77 ms 61.75.4.114
6 76 ms 75 ms 83 ms 73.14.196.66
7 * * * Request timed out.
8 75 ms 75 ms 75 ms 72.14.237.179
9 76 ms 76 ms 74 ms 8.8.8.8
Trace complete.
You may notice that one or more hops returns a Request timed out message. This is because the specific router on the path has
been configured not to respond to ICMP requests.
Keep all devices powered on in their current state and proceed to the next exercise.

ARP, short for Address Resolution Protocol, translates the IP address of a device to its physical address also known as an Ethernet
address/MAC address. It is one of the main components of the TCP/IP protocol suite. Misconfigured ARP can lead to random
connectivity issues across the network. You can analyze the ARP cache to troubleshoot and resolve issues including address conflict
or IP address duplication on a network.
To better understand this technology, also refer to your course material or use your preferred search engine to research this topic in
detail.
Learning Outcomes
Your Devices
PLABDC01 (Domain Controller - Windows Server 2016)

Task 1 - View ARP cache
In this task, you will learn to view the ARP caches of the various computers on the network and to identify the MAC or physical
addresses of the computers connected to each computer.
To view ARP cache, perform the following steps:
Step 1
Ensure you have powered on the required devices defined in the introduction. Connect to PLABDC01. Minimize the Server
Manager.
Click Start and type cmd. As you begin to type, the search box appears.
Figure 3.1 Screenshot of the PLABDC01 desktop: Command Prompt menu-option is highlighted on the Start menu.
Step 2
Press Enter. The Command Prompt window appears.
Figure 3.2 Screenshot of the PLABDC01 desktop: Administrator Command Prompt window is displayed.
Step 3
On the command prompt window, type the following command:
arp -a
Press Enter.
Figure 3.3 Screenshot of the PLABDC01 desktop: Administrator Command Prompt window is displayed showing the
command typed-in to display the arp cache on the local server.
Step 4
The ARP cache is displayed.
Figure 3.4 Screenshot of the PLABDC01 desktop: Administrator Command Prompt window is displayed showing system-
response to the command typed-in in the previous step.
Take a closer look at the following output:
Internet Address Physical Address Type

192.168.0.1 00-15-5d-09-77-d4 dynamic
192.168.0.3 00-15-5d-ea-07-f2 dynamic
192.168.0.4 00-15-5d-ea-07-f0 dynamic
192.168.0.250 5c-83-8f-9b-75-00 dynamic
192.168.0.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
The output that you will get from your lab may slightly differ from the table and screenshot provided in this step.
Step 5
The IP address 192.168.0.1 belongs to PLABRTR01, 192.168.0.2 to PLABCD01 and 192.168.0.4 to PLABWIN10.
relevant section highlighted on the listed arp cache.
Minimize the Command Prompt window.
Step 6
Connect to PLABSA01.
On the desktop, click Search and type:
cmd
Click the Command Prompt icon.

Figure 3.6 Screenshot of the PLABSA01 desktop: Command Prompt menu-option is highlighted on the Start menu.
Step 7
On the command prompt, type the following command:
Press Enter.
Figure 3.7 Screenshot of the PLABSA01 desktop: Administrator Command Prompt window is displayed showing the
command typed-in to display the arp cache on the local server and system-response to the command.
Note the following results:
Interface: 169.254.134.85 --- 0x4

224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
Interface: 192.168.0.3 --- 0x5
192.168.0.2 00-15-5d-ea-07-ed dynamic
192.168.0.4 00-15-5d-ea-07-f0 dynamic
192.168.0.250 5c-83-8f-9b-75-00 dynamic
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
Note once again that the values that you will get from your lab may slightly differ from the table and screen grab provided
in this step. Additionally, notice that the output includes the ARP cache of two interfaces. The first interface, which is not
connected to the network, includes only multicast addresses as well as an IPv4 link local address. For more information
about these types of addresses, refer to your course material or use your favorite search engine.
Step 8
You may notice in the output in the previous step, several of the IP addresses on the network may be missing. In the above example,
IP addresses 192.168.0.1 and 192.168.0.3 are missing. The IP addresses missing from your output may be different.
An ARP cache is not static but is dynamically updated whenever packets are exchanged.
From the PLABSA01 device command prompt, issue the following command:
Use an IP address that is missing from the output of your lab. For this example, the IP address of PLABRTR01 is used since it
was missing from the ARP cache of PLABSA01
ping 192.168.0.1
Press Enter.
command typed-in to ping an IP address and system-response to the command.
The ping is successful.
Step 9
Now issue the following command once again and press Enter:
arp -a
Notice that the ARP cache has been populated with the 192.168.0.1 IP address. This is because the PLABSA01 device sent an
ARP request for the specific IP and received its MAC address and populated the ARP cache accordingly.
command typed-in to display the arp cache on the local server and system-response to the command.
Task 2 - Verify MAC Addresses Individually
In this task, you will learn to establish the physical address (MAC) individually for each computer on the network.
To verify MAC addresses individually, perform the following steps:
Step 1
From PLABSA01, enter the following command at the command prompt:
You may want to maximize the command prompt window before initiating this command as the output can be somewhat
extensive.
ipconfig /all
Press Enter.
command typed-in to view IP configuration on the local server and system-response to the command.
Scroll through the output and find the following values:
Note that your values may be different than those displayed here.
Under the Windows IP Configuration section:
Host Name . . . . . . . . . . . . : PLABSA01
Under the Ethernet adapter Internal section:
Physical Address. . . . . . . . . : 00-15-5D-EA-07-F2

IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Make a note of these values to be used in the next few steps.

Step 2
Go to the PLABWIN10, restore the Command Prompt window.
Figure 3.11 Screenshot of the PLABWIN10 desktop: Administrator Command Prompt window is displayed on the
PLABWIN10 Windows desktop.
Step 3
On the command prompt, type the following command:
arp -a
Once again, you may notice two ARP caches.

command typed-in to display the arp cache on the system and system-response to the command.
Examine the ARP cache for the interface with IP address 192.168.0.4:

192.168.0.1 00-15-5d-09-77-d4 dynamic
192.168.0.2 00-15-5d-ea-07-ed dynamic
192.168.0.3 00-15-5d-ea-07-f2 dynamic
192.168.0.250 5c-83-8f-9b-75-00 dynamic
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
Find the entry for the IP address of 192.168.0.3, that is the PLABSA01 device, and compare this physical address with that noted
in Step 1. They should be the same.
If the IP address of 192.168.0.3 does not appear in your ARP cache, ping this IP address from the PLABWIN10 device and
then issue the arp -a command once again. The ARP cache should be populated with the appropriate IP and MAC addresses.
Task 3 - Configure a static ARP cache entry
Until now, all ARP entries of other devices on the network were dynamically learned and populated within the cache. In this task,
you will learn how to create a static ARP cache entry. You will enter an incorrect static physical address in the PLABDC01 device
that maps to the PLABWIN10 device then find out its effect on network connectivity.
Step 1
From PLABDC01, right-click on the network icon and choose Open Network and Sharing Center.
Figure 3.13 Screenshot of the PLABDC01 desktop: Context menu (that appears by right-clicking the network icon) > Open
Network and Sharing Center menu-options are displayed on the PLABDC01 Windows desktop.
Step 2
In Network and Sharing Center, under the View your active networks section, click Ethernet.
Figure 3.14 Screenshot of the PLABDC01 desktop: Ethernet link is selected on the Network and Sharing Center window.
Step 3
In Local Area Connection Status, click Properties.
Figure 3.15 Screenshot of the PLABDC01 desktop: Properties button is selected on the Ethernet Status dialog box.
Step 4
In Local Area Connection Properties, clear Internet Protocol Version 6 (TCP/IPv6) box. Click OK then Close.
Close from Network and Sharing Center window.
Note: You disabled IPv6 on PLABDC01’s interface to prevent it from using the protocol in making a secondary connection
to IPv6-aware devices like PLABWIN10.
Figure 3.16 Screenshot of the PLABDC01 desktop: Ethernet Properties dialog box is displayed showing the required
settings performed and the OK button available.
Step 5
Reopen the command prompt window, enter the following command:
netsh interface ipv4 add neighbors “Ethernet” 192.168.0.4 00-11-22-33-44-5e
Press Enter. The netsh command you entered will map a fictitious MAC address to a device with a numeric IP address of
192.168.0.2, that is, the PLABWIN10 device.
command to map a MAC address to an IP typed-in.
Step 6
To display the ARP cache once again, type:
arp -a
Press Enter.
Find the static ARP cache and the incorrect physical address mapped to 192.168.0.4.
Step 7
To test connectivity from PLABDC01 to PLABWIN10 type:
ping 192.168.0.4
Press Enter.
You will notice that the ping packets all timed out.
command typed-in to ping an IP address and system-response to the command.
Step 8
To clear the ARP cache on PLABDC01, type:
arp -d
Press Enter.
command typed-in to clear the arp cache on the system and system-response to the command.
Step 9
To view the ARP cache, enter the following command once again:
arp -a
Press Enter.
You will notice that there are fewer entries than before and the static entry has also been removed.
If you issue the two commands fast enough in succession, then you will find that the ARP cache is empty. Because packets
are being exchanged all the time on the network, these exchanges allow for the repopulating of the cache almost
immediately.
You may find that the correct physical address of PLABWIN10 may not have been restored. If this is the case, attempt to ping
192.168.0.4 once again.
Step 10
To verify that connectivity has been restored and to repopulate the ARP cache with the appropriate IP and MAC address
correspondence for PLABWIN10, type:
ping 192.168.0.4
Press Enter.
Ping packets are now being responded to by the PLABWIN10 device.

command to ping an IP address typed-in and system-response to the command.
Step 11
Check to see if the ARP cache has indeed been populated with the IP and MAC address of PLABWIN10. To do so, type:
arp -a
You will notice that the ARP cache has indeed been updated.
Leave the devices you have powered on in their current state and proceed to the next exercise.
Review
Well done, you have completed the Network Services and Protocols (Part 1) Practice Lab.
Summary
You completed the following exercises:
Exercise 1 - Troubleshooting ICMP Related Issues (including Ping and Traceroute)

You should now be able to:

Feedback
Shutdown all virtual machines used in this lab. Alternatively, you can log out of the lab platform.

NSP P1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NSP P1

Uploaded by

Copyright:

Available Formats

CompTIA Network+

Network Services and Protocols - Part 1

Exercise 1 - Troubleshooting ICMP Related Issues (including Ping and Traceroute)

After completing this lab, you will be able to:

Access Windows Firewall

Click Next to view the Lab topology used in this module.

Copyright © Practice Labs 2007 - 2018. All rights reserved.

Connecting to your Lab

PLABDC01 (Domain Controller - Windows Server 2016)

Click Next to proceed to the first exercise.

Exercise 1 - Preparing the Lab

Access Windows Firewall

PLABSA01 (Member Server - Windows Server 2016)

Task 1 - Prerequisite task

Complete the following steps to prepare the lab.

Leave the device as it is and move on to Exercise 2.

Exercise 2 - Troubleshooting ICMP Related Issues

Troubleshoot ICMP Related Issues

PLABSA01 (Member Server - Windows Server 2016)

Task 1 - Analyze an ICMP Related Issue

To analyze an ICMP related issue, perform the following steps:

The result displays that the ping was unsuccessful.

Minimize command prompt window.

Task 2 - Try to Resolve the ICMP Issue

To resolve the ICMP issue, perform the following steps:

Task 3 - Verify the ICMP Issue is Resolved

IP address of the source of the reply

Minimize the command prompt window.

Task 4 - Learn to use Tracert

Examine this output more closely:

Tracing route to 192.168.1.1 over a maximum of 30 hops

The next entry is the destination device of 192.168.1.1.

To do this, issue the following command:

The output you should get should be similar to the following:

Tracing route to 8.8.8.8 over a maximum of 30 hops

Exercise 3 - Understand How ARP Works

PLABDC01 (Domain Controller - Windows Server 2016)

Task 1 - View ARP cache

To view ARP cache, perform the following steps:

Take a closer look at the following output:

Internet Address Physical Address Type

Minimize the Command Prompt window.

On the desktop, click Search and type:

Click the Command Prompt icon.

Note the following results:

Interface: 169.254.134.85 --- 0x4

The ping is successful.

Task 2 - Verify MAC Addresses Individually

To verify MAC addresses individually, perform the following steps:

Scroll through the output and find the following values:

Under the Windows IP Configuration section:

Host Name . . . . . . . . . . . . : PLABSA01

Under the Ethernet adapter Internal section:

Physical Address. . . . . . . . . : 00-15-5D-EA-07-F2

Make a note of these values to be used in the next few steps.

Once again, you may notice two ARP caches.

Internet Address Physical Address Type

Close from Network and Sharing Center window.

netsh interface ipv4 add neighbors “Ethernet” 192.168.0.4 00-11-22-33-44-5e

Ping packets are now being responded to by the PLABWIN10 device.

Exercise 1 - Troubleshooting ICMP Related Issues (including Ping and Traceroute)

You should now be able to:

Access Windows Firewall