Which Two Actions Can Be Taken When Configuring Windows Firewall? (Choose Two.)

Connection Security Rule

Securing Network Access

Derrick Rountree , in Windows 2012 Server Network Security, 2013

IPSec Monitoring in Windows Firewall with Advanced Security

IPSec monitoring tin can exist washed in the Monitoring department of Windows Firewall with Advanced Security. There are two nodes that will provide you the information you need: Connection Security Rules and Security Associations.

Connection Security Rules

The Connection Security Rules node will list all the active IPSec configuration rules on the system. Here y'all can view information such every bit the rule name, the endpoints involved, and the authentication methods configured. You tin also view the backdrop for the dominion, to see more detailed information.

Security Associations

Security associations are stored secure connection data. At that place are two types of security associations: main style and quick manner. Primary mode negotiation is a negotiation between two computers which want to establish a secure connection. The negotiation includes establishing the secure cryptographic protection suite, determining the key method, and authentication.

Read total chapter

URL:

https://www.sciencedirect.com/scientific discipline/article/pii/B9781597499583000030

Mitigating Network Vulnerabilities

Thomas W. Shinder , ... Debra Littlejohn Shinder , in Windows Server 2012 Security from Finish to Edge and Across, 2013

Configuring IPsec Rules on Windows Firewall with Advanced Security

In club to use connection security rules, both of the computers involved in the communications must have IPsec policies configured. Authentication for connexion security rules can be based on Kerberos in an Active Directory domain, or on certificates or preshared keys. At that place are five different types of connection security rules that you tin can create:

▪: Isolation—allows you to restrict communication to merely those hosts that tin authenticate using specific credentials. For example, you can allow communications only to computers that are joined to an Active Directory domain.
▪: Authentication exemption—allows you to configure exemptions to the isolation rules, such equally an exemption to our previous instance that would allow connections to a DNS server without the requirement to authenticate.
▪: Server-to server—allows you lot to secure the connections between 2 specific computers, such equally a connectedness between a database and an application server.
▪: Tunnel—allows you lot to create rules that work in the same fashion as server-to-server rules merely are implemented through tunnels (site-to-site connections).
▪: Custom—allows y'all to create rules with special settings based on your specific needs.

The first step in securing communications with IPsec is to create a rule. In the WFAS console, correct-click Connection Security Rules in the left pane and select New Rule… or select it in the Activity menu or the right Action pane. The New Connection Security Dominion Wizard opens by asking you to select the rule type from the listing discussed in a higher place, as shown in Figure 11.30.

When yous create an isolation rule, the next pace is to select when you want authentication to take place. Yous take three choices hither, equally shown in Figure eleven.31:

▪: Y'all select Request authentication for inbound and outbound connections to have the communications authenticated whenever possible, but authentication is not required and then communication can still be established if the estimator on the other terminate does not back up it.
▪: You tin select Require hallmark for inbound connections and request authentication for outbound connections if you desire to ensure that just authenticated incoming communications will be immune. If the computer sending the request is unable to authenticate, the connexion will exist rejected. Outbound communications volition be treated in the same way as above—authenticated when possible but immune without authentication.
▪: For the highest level of security, you can select Require authentication for entering and outbound connections. With this selection, simply authenticated connections are allowed.

On the side by side folio of the wizard, shown in Figure 11.32, you specify what authentication method you desire to use for this rule.

You take four choices here:

▪: Yous can cull Default and utilize the authentication methods that are divers in the IPsec settings.
▪: You tin can choose Figurer and User to apply Kerberos v5 and restrict communications to connections from domain-joined users and computers just.
▪: You lot can choose Computer to utilize Kerberos v5 and restrict communications to connections from domain-joined computers only.
▪: You can choose the Advanced choice and specify custom settings for first and second authentication methods.

When yous cull to customize the hallmark methods, yous can list multiple methods to exist tried, and they will exist tried in the gild in which yous place them in the list. You do this for both first and 2d hallmark, and you tin can too choose whether to make first or second hallmark optional. You will non exist able to specify a second hallmark if a preshared cardinal is listed in the first authentication methods list.

The next footstep is to select the network blazon(s) to which the rule applies, just equally you do with firewall rules (domain, private, or public).

Then y'all give the rule a name (and clarification if yous want) and information technology will announced in your list of Connection Security Rules in the eye pane of the WFAS panel, as shown in Effigy 11.33.

To disable or delete it, right-click it and cull the appropriate option. To modify it, cull Properties. This opens its Backdrop sheet with tabs for General info, Remote Computers, Protocols and Ports, Authentication, and Advanced, as shown in Figure 11.34. Here, y'all can make changes to the selections yous fabricated in the wizard and as well configure some settings that did not appear in the sorcerer.

On the Remote Computers tab, you can specify the IP addresses of the endpoints to which you want the rule to apply. On the Protocols and Ports tab, you can utilise the rule only to specific protocol types (for instance, IPv6 or L2TP) or specific ports on each of the endpoints. On the Authentication tab, you can alter the authentication mode (Request/crave on inbound/outbound) and/or the authentication method that you ready in the wizard. On the Avant-garde tab, y'all can not only alter the network type(s) to which the rule applies but also specify that it applies only to certain interface types (local surface area network, remote admission, and/or wi-fi), and y'all can specify whether IPsec tunneling should exist used. When tunneling is used, yous need to ready the authentication mode to "Require inbound and outbound."

You can also create IPsec policies through the IP Security Policies snap-in in the Microsoft Management Panel, via the command-line netsh tool or PowerShell, but that is across the scope of this chapter.

Read full affiliate

URL:

https://www.sciencedirect.com/science/article/pii/B978159749980400011X

Microsoft Vista: Networking Essentials

In Microsoft Vista for IT Security Professionals, 2007

Configuring an Isolation Dominion

To configure an isolation connection security rule, select Isolation from the screen shown in Figure 6.29 then click Next. You volition and then be prompted to select one of the post-obit 3 authentication requirements for the new isolation rule:

■: Request authentication for entering and outbound connections
■: Require authentication for inbound connections and request hallmark for outbound connections
■: Require authentication for inbound and outbound connections

In one case yous accept made your selection, click Side by side. You will and so be prompted to select the authentication method that this rule should employ. Cull among the following:

■: Default.
■: Computer and User (Kerberos V5).
■: Computer (Kerberos V5).
■: Computer Certificate. If y'all select this option, you lot will be prompted to enter the proper noun of a CA on your network. You will also have the pick to have only NAP wellness certificates.
■: Advanced. If yous select this option, yous will be prompted to configure a custom authentication method equally described in the "Authentication Method" section, earlier in this chapter.

In one case you lot have made your choice, click Next. You will and then be prompted to select which Windows Firewall profile will apply this rule: Domain, Public, and/or Private. You tin can configure this rule to exist enforced under i, two, iii, or none of the Windows Firewall profiles.

Click Next to continue. You'll be prompted to enter a proper name and an optional description for this rule. Click Finish when you're done. Y'all'll be returned to the main MMC snap-in window, where y'all will see the newly created dominion listed in the main window. From here, you can right-click on the rule to disable or delete it, or you lot can select Properties to change whatever of the settings that you configured in the magician.

Read total chapter

URL:

https://world wide web.sciencedirect.com/science/commodity/pii/B9781597491396500108

Securing Windows 7

Jorge Orchilles , in Microsoft Windows seven Administrator's Reference, 2010

Advanced Firewall Settings

The basic firewall settings are limited to merely allowing certain applications through the Windows Firewall. Microsoft included in Windows 7 an MMC console called Windows Firewall with Advanced Settings for this reason. This console may be accessed from the Local Group Policy Editor, Local Security Policy, or Windows Firewall Control Console console and is illustrated in Effigy eight.27 . This MMC allows much more than granular configuration of the Windows Firewall, Inbound Rules, Outbound Rules, Connectedness Security Rules, and Monitoring.

The principal window of Windows Firewall with Advanced Security provides an overview of the firewall profiles. As shown in Figure 8.27, there are 3 unlike profiles: domain profile for the domain network location, individual contour for the dwelling and work network location, and public profile for the public network location. Under each profile is the Windows Firewall Backdrop associated with the profile. On the left console, there are the dissimilar rule sets including Inbound Rules, Outbound Rules, Connection Security Rules, and Monitoring, which is a simple view of each dominion type. The Action menu in the primary view allows administrators to import or consign firewall policy. This is very important for backing upwards Windows Firewall Policy and distributing a policy among other computers. The Action menu too can restore the policy to default.

To configure the Windows Firewall Properties:

1.

Click Windows Firewall Properties from the Overview window or from the Action menu.

two.

Select the profile to edit from the tabs: Domain Contour, Private Profile, or Public Contour (Figure 8.28). Annotation that the options are the same for each tab.

3.

Country:

a.: Firewall state – This option sets the firewall on or off for the selected contour.
b.: Inbound connections – This option can be fix to block all inbound connections, allow all entering connections, or block (default). Block volition block all entering connections except the ones specifically allowed through a rule.
c.: Outbound connections – This option can be set to cake or allow outbound connections except the ones specifically allowed or denied through a rule.
d.: Protected network connections – This option chooses what network connections may use the selected profile.

four.

Settings – Clicking the Customize button will allow y'all to configure:

a.: Display a notification – This will show a notification in the Action Center when an entering connection is blocked as shown in Figure viii.28.
b.: Allow unicast response – This allows the sending of unicast responses to multicast or broadcast network traffic as shown in Figure 8.28.
c.: Rule merging – This tin merge local policy rules with Group Policy rules as shown in Figure 8.28.

five.

Logging – Clicking the Customize button will allow you to configure:

a.: Name – The location to store firewall logs. Default is %SystemRoot%\system32\logfiles\firewall\pfirewall.log.
b.: Size limit – The maximum size of the log file. When the log is full, it will brainstorm overwriting the oldest data offset.
c.: Log dropped packets – This will log when packets are dropped. This may be useful to troubleshoot network issues.
d.: Log successful connections – This will log every successful connexion to the local estimator.

6.

IPsec settings – This configures the settings for connexion security rules. IPsec settings include Key substitution (main mode), data protection (quick manner), and authentication method.

7.

Click OK.

The Windows Firewall Properties are important because the Entering and Outbound Rules depend on the configuration. To view any of these rules, one must expand the Windows Firewall with Advanced Security node in the MMC and select the desired rules to view. Each dominion has a number of tabs and configurations. Understanding these backdrop will make creating Inbound and Outbound Rules much easier. To view the backdrop of a rule:

■: Double-Click the rule
■: Right-click the rule and select Properties
■: Select Backdrop from the Action card

The Backdrop for an Inbound or Outbound Rule are:

■

General – The General rule information and activity.

□

General – The name and description of the rule. A cheque box to enable or disable the rule.

□

Action – The options are to allow the connection, let the connection only if secure, or block the connection. If setting only to allow the connexion if secure, the administrator much choose to:

-: Allow the connection if it is authenticated and integrity-protected – This uses IPsec.
-: Crave the connections to be encrypted – This requires encryption every bit well as IPsec.
-: Allow the connection to use nada encapsulation – This only requires authentication.
-: Override cake rules

■

Programs and Services – This can configure the rule to a certain programme or service or both.

□: Programs – This selection is to allow all programs that encounter the conditions or specify a programme in particular.
□: Services – This specifies a particular service for the rule.

■

Computers – This tin set the rule to only let connections from sure computers or to skip the dominion for certain computers. To simply allow connections from certain computers, allow only if secure must be used in the General tab.

■

Protocols and ports – This is the basic network firewall configuration to select the following:

□: Protocol Blazon – Any or from a listing of protocol types including: HOPOPT, ICMPv4, IGMP, TCP, UDP, IPv6, IPv6-Route, IPv6-Frag, GRE, ICMPv6, IPv6-No Nxt, IPv6-Opts, VRRP, PGM, L2TP.
□: Protocol Number – This sets if the customer Protocol Type is set.
□: Local Port – This sets all ports, specific ports (allows ranges), RPC Dynamic Ports, RPC Endpoint Mapper, or IPHTTPS.
□: Remote Port – This sets for all ports or specific ports (allows ranges).
□: ICMP Settings – This can exist gear up to utilize to all ICMP types or specific ICMP types.

■

Scope – This sets the scope to any or specific local or remote IPs.

■

Advanced – This sets profiles, interface types, and edge traversal.

□: Profiles – This specifies which profiles the rule applies to.
□: Interface types – This applies the rule to all network interfaces or only selected interfaces.
□: Edge traversal – Setting for accepting unsolicited inbound packets through an edge device. One may block, let, or defer to user or application.

■

Users – Setting to only permit connections from certain users or exceptions for certain users.

As one can encounter the advanced settings for Inbound Rules and Outbound Rules contain many settings that can be tweaked to a very granular level. This flexibility proves the advances that Windows 7 has fabricated with Windows Firewall from its introduction in Windows XP.

Creating an Inbound Dominion or Outbound Dominion is very similar and uses the New Rule wizard. Right-click Inbound Rules or Outbound Rules on the left console depending on which will be created and select New Rule…. The New Rule wizard will ask a number of questions in reference to the dominion that will be created. The first screen will ask you to select a Program, Port, Predefined connection, or Custom rule type. Custom will permit yous to create a more specific rule equally referenced in this section.

The Connection Security Rules configure IPsec, which is a newer more secure Net Protocol (IP). It uses hallmark and encryption for each IP bundle at the commencement and during the session. IPsec may exist enabled between ii hosts such as a client and a server or between a security gateway and a host. Configuring IPsec is more circuitous than an Inbound or Outbound Rule. To create an IPsec rule, correct-click Connectedness Security Rules on the left pane and select New Rule…. The first screen of the Rule wizard will inquire for the rule type to be used. The options are:

■: Isolation – This bases authentication on domain membership or health status.
■: Hallmark exemption – This does not authenticate from sure computers.
■: Server-to-server – This authenticates betwixt two hosts.
■: Tunnel – This authenticates between security gateways.
■: Custom – This uses any of the higher up options or a combination of the above options.

The monitoring console displays a more than detailed view of the current firewall profile and the backdrop associated with it. Expanding the monitoring node will brandish Firewall, Connection Security Rules, and Security Associations where each of these may be viewed in a unmarried location.

Finally, Microsoft has changed the command line command for configuring the firewall. The new control is netsh advfirewall. For a listing of commands use netsh advfirewall /? as shown in Figure 8.29 or netsh advfirewall firewall /? in an elevated command prompt. These commands configure the firewall policy through the command line for scripts or remote management.

Read total chapter

URL:

https://www.sciencedirect.com/scientific discipline/article/pii/B9781597495615000085

Microsoft Windows Server 2008

Aaron Tiensivu , in Securing Windows Server 2008, 2008

802.1x Wired and Wireless Access

IEEE 802.1x standards define an effective framework for controlling and authenticating clients to a wired or wireless protected network—in this instance a NAP infrastructure. These standards define port-based hallmark on supported devices. These devices could be switches or wireless access points that support the IEEE 802.1x standard. The IEEE standard is significant because it has been accepted by hardware and software vendors—their products volition be designed with the standards in mind. What does this mean for you lot and me? All hardware that is 802.1x based should work with RADIUS and NAP.

An 802.1x deployment consists of iii major components that allow for the hallmark process to piece of work correctly (encounter Effigy 4.6 ).

▪: Supplicant a device that requests admission to our network and is connected via a pass-through authenticator.
▪: Pass-through authenticator a switch or access point that is 802.1x compliant.
▪: Authentication server when the supplicant connects to the laissez passer-through authenticator, the asking is passed to the hallmark server by the pass-through authenticator. The hallmark server decides whether the client is granted admission or denied.

Authentication is handled using the Extensible Hallmark Protocol (EAP). EAP letters used in the authentication process are transmitted betwixt the supplicant and pass-through authenticator using EAP over LAN (EAPoL). The pass-through authenticator talks to the RADIUS using RADIUS messages and EAP.

When NAP uses IEEE 802.1x, the authenticating pass-through authenticator uses the RADIUS protocol. NPS instructs the pass-through authenticator (wireless access-point or switch) to place supplicants that are not in compliance with NPS into a restricted network. The restricted network could exist a separate VLAN or a network with IP filters in place to isolate it from the secured network.

WLAN Authentication Using 802.1x and 802.3

NPS is responsible for network security and is used to provide secure wireless access through NPS. Windows Server 2008 too provides features that enable you to deploy 802.1x authenticated wired service for IEEE 802.3 Ethernet network clients. In conjunction with 802.1x capable switches and other Windows Server 2008 features, yous can control network access through Wired Network Policies in Windows Server 2008 Grouping Policies. Recall that NPS is used to configure remote connections. The 802.three wired network specification allows you to use the 802.1x specification to provide wired networking access. This is configured via NPS and uses Protected Extensible Authentication Protocol (PEAP) authentication. It is outside the scope of this book to discuss how to plan, configure, and deploy a WLAN hallmark method, only we will talk over these concepts to the extent you need to understand the changes in the Windows Server 2008 environment.

Allow's start with some definitions as a review. The 802.eleven standard defined the shared key authentication method for authentication and Wired Equivalent Privacy (WEP) for encryption for wireless communications. 802.xi ultimately concluded upwards being a relatively weak standard and newer security standards are available and recommended for use. The 802.1x standard that existed for Ethernet switches was adapted to the 802.11 wireless LANs to provide stronger authentication than the original standard. 802.1x is designed for medium to large wireless LANs that accept an authentication infrastructure, such every bit AD and RADIUS in the Windows environment. With such an infrastructure in place, the 802.1x standard supports dynamic WEP, which are mutually adamant keys negotiated past the wireless client and the RADIUS server. However, the 802.1x standard also supports the stronger Wi-Fi Protected Access (WPA) encryption method. The 802.11i standard formally replaces WEP with WPA2, an enhancement to the original WPA method.

Wireless and Wired Authentication Technologies

Windows Server 2008 supports several authentication methods for authenticating that a calculator or user is attempting to connect via a protected wireless connectedness. These same technologies back up 802.1x authenticated wired networks as well. These Extended Hallmark Protocols (EAP) methods are:

▪: EAP–TLS
▪: PEAP–TLS
▪: PEAP–MS–CHAPv2

Extended Authentication Protocol–Transport Layer Security (EAP–TLS) and Protected Extended Authentication Protocol–Send Layer Security (PEAP–TLS) are used in conjunction with Public Key Infrastructure (PKI) and computer certificates, user certificates, or smart cards. Using EAP–TLS, a wireless client sends its document (computer, user, or smart bill of fare) for hallmark and the RADIUS server sends its estimator certificate for authentication. By default, the wireless customer authenticates the server's certificate. With PEAP–TLS, the server and client create an encrypted session before certificates are exchanged. Clearly, PEAP–TLS is a stronger hallmark method because the hallmark session data is encrypted.

If there are no calculator, user, or smart card certificates available, y'all can use PEAP-Microsoft Claiming Handshake Authentication Protocol version 2 (PEAP-MS-CHAPv2). This is a password-based authentication method in which the exchange of the authentication traffic is encrypted (using TLS), making it difficult for hackers to intercept and utilize an offline dictionary attack to access hallmark exchange data. That said, it's the weakest of these three options for hallmark because information technology relies on the utilize of a password.

A Windows-based client running Windows Vista or Windows Server 2008 can be configured in the post-obit ways:

▪: Grouping Policy
▪: Command line
▪: Wired XML profiles

Using Grouping Policy, you lot can configure the Wired Network (IEEE 802.3) Policies Group Policy extension, which is role of Computer configuration Group Policy that can specify wired network settings in the AD surround. The Group Policy extension applies only to Windows Server 2008 and Windows Vista computers. The command line can exist used within the netsh context using the lan control (netsh lan). You tin can explore the available comments past typing netsh lan /? at the command line prompt. Wired XML profiles are XML files that comprise wired network settings. These can be imported and exported to Windows Server 2008 and Windows Vista clients using the netsh context as well. You can use netsh lan export profile or netsh lan add profile to export or import a wired contour using the command line.

For Windows XP SP2 or Windows Server 2003-basec computers, you tin can manually configure wired clients by configuring 802.1x authentication settings from the Authentication tab of the backdrop dialog box of a LAN connection in the Network Connections folder, as shown in Figure 4.7, which shows the Network Connections Properties dialog box from a Windows XP Pro SP2 computer.

Implementing Secure Network Access Authentication

Although it's outside the scope of this affiliate to get into the details of PKI, it is useful to look at some of the means PKI tin be used as part of a Windows-based authentication infrastructure for secure network access using the protocols discussed in this department.

▪: When using PEAP–MS-CHAPv2 for network access authentication, configure Group Policy for autoenrollment of reckoner certificates to install computer certificates on the NPS servers.
▪: When using certificates for computer-level network access authentication, you should configure Group Policy for autoenrollment of computer certificates. This applies if you're using EAP–TLS or PEAP–TLS for computer-level wireless authentication.
▪: When you are using certificates for user-level network access authentication, configure a certificate template for user certificates and also configure Group Policy for autoenrollment of user certificates. Every bit with computer-level certificates, this is needed when using EAP–TLS and PEAP–TLS.

Group Policy is too an important function of securing network access and authenticating computers and users. You lot can use Grouping Policy to deploy settings to install a root document on a domain member computer to validate computer certificates of the NPS servers. It can likewise be used to autoenroll user and reckoner certificates on domain fellow member computers for user- and estimator-level certificate-based authentication.

In addition to being useful in the deployment of document-based authentication, Group Policy is likewise useful in deploying configuration settings for:

▪: 802.11 wireless network profiles
▪: 802.1x wired network profiles
▪: Windows Firewall with Advanced Security connectedness security rules to protect traffic
▪: NAP client configuration

Notes from the Undercover…

Changes to Authentication Protocols

PPP-based connections no longer support the SPAP, EAP-MD5-CHAP and MS-CHAPv1 authentication protocols. Remote access PPP-based connections now back up the use of Protected EAP (PEAP) with PEAP-MS-CHAP v2 and PEAP-TLS. Go along this in heed as y'all plan out your new Windows Server 2008 remote access options.

EAPHost architecture in Windows Server 2008 and Windows Vista includes new features not supported in Windows Server 2003 and Windows XP including:

▪: Support for additional EAP methods
▪: Network discovery (as defined in RFC 4284)
▪: RFC 3748 compliance and support for expanded EAP types including vendor-specific EAP types
▪: Coexistence of multiple EAP types (Microsoft and Cisco, for example)

Configuring 802.1x Settings in Windows Server 2008

Y'all can configure wired policies from the Computer Configuration | Policies | Windows Settings | Security Settings | Wired Network (IEEE 802.three) Policies node in the Group Policy Direction Editor snap-in via the MMC. By default, there are no wired policies in place. To create a new policy, use the following steps:

1: Right-click the Wired Network (IEEE 802.3) Policies in the console tree of the GP Editor snap-in.
2: Click Create A New Windows Vista Wired Policy.
3: The New Windows Vista Wired Policy Properties dialog is displayed, shown in Figure 4.viii. It has two tabs: General and Security. The General tab is selected past default. Enter the policy name and description and ensure the checkbox for "Use Windows Wired Auto Config service for clients" is checked.

Figure 4.viii. New Vista Wired Network Policy Properties Security Tab
iv: Click the Security tab to set security options. On this tab, click the checkbox adjacent to "Enable apply for IEEE 802.1X authentication for network access" then click the dropdown box to select a network authentication method (EAP, PEAP, MS-CHAPv2). Also select the "Authentication Mode" from the second dropdown box. The options are User re-authentication, computer only, user authentication, or guest authentication. Too select the number of times the authentication can neglect earlier it is abandoned (1 is the default). The last setting in the Security tab is a checkbox whether to "Cache user information for subsequent connections to this network." If this checkbox is cleared, the credential information is removed when the user logs off. If the checkbox is checked, the credential data will be buried afterward user log off.
v: To access advanced settings, click the Advanced push on the Security tab. At that place are ii Advanced segments: IEEE 802.1X and Single Sign On, shown in Figure four.nine.

Effigy 4.nine. Advanced Settings for New Vista Wired Network Policy Properties
6: In the IEEE 802.1X section, click the checkbox to the left of "Enforce advanced 802.1X settings" to enable these options: Max Eapol-Showtime Msgs:, Held Period (seconds), Start Period (seconds), Auth Flow (seconds), Eapol-Start Message. In most cases, the default settings are fine; it yous believe you need these advanced settings, check the Microsoft documentation for details on how to gear up these.
7: In the Unmarried Sign On section, click the checkbox next to "Enable Single Sign On for this network" to enable the following options: Perform immediately earlier User Logon, Perform immediately subsequently User Logon, Set Max. delay for connectivity (seconds), Allow additional dialogs to be displayed during Unmarried Sign On, and This network uses different VLAN for authentication with machine and user credentials. Once more, every bit with the IEEE 802.1X Advanced settings, these tin exist modified if you have a specific demand to do so. Check Microsoft documentation for details on using these options within your network environment. A expert starting place is www.microsoft.com/technet/technetmag/problems/2008/02/CableGuy/default.aspx.
eight: Click OK to take configuration; click Cancel to exit without saving changes.