ChAPTER 12 in Visual Studio .NET

Create QR-Code in Visual Studio .NET ChAPTER 12

You can use the following questions to test your knowledge of the information in Lesson 1, Troubleshooting Network Issues. The questions are also available on the companion CD if you prefer to review them in electronic form.

Answers to these questions and explanations of why each answer choice is correct or incorrect are located in the Answers section at the end of the book.

1. 2. 3.

Which of the following network troubleshooting tools is not included with the Windows 7 operating system

Which of the following network communication technologies is not capable of automatically negotiating the use of a common protocol for client/server communications

a. Wireless security protocols B. Wireless communication protocols c. Virtual private networking protocols D. Virtual private networking authentication protocols

Which of the following TCP/IP configuration settings, when incorrectly configured, completely prevents the computer from communicating on the network (Choose all correct answers.)

Even with network connectivity confirmed, users still might be unable to access the net-work resources they need. In nearly all cases, users must authenticate themselves to confirm their identities before they can gain significant access to network resources. After the authentication, the system must authorize the users, to provide them with a specific degree of access to selected resources. If either one of these two processes fails, users cannot access the network.

After this lesson, you will be able to:

Recognize account problems affecting authentication and authorization. Recognize workstation problems affecting authentication and authorization. Recognize Kerberos problems affecting authentication and authorization.

When a user reports an inability to log on to an Active Directory Domain Services (AD DS) network, the troubleshooter is faced with a list of potential problems that range from mundane usability issues to extremely complex directory service matters. The first step in troubleshooting an authentication failure is to make sure that it really is an authentication failure. All of the net-working issues discussed in Lesson 1 of this chapter can prevent a user from logging on, but a true authentication problem assumes that network connectivity is intact. Therefore, troubleshooters should begin by confirming that the computer experiencing the logon problem is not affected by one of the standard permanent or transient network communication issues. The next step as usual is to determine the scope of the problem. If one user cannot log on to the AD DS domain from a particular workstation, can a different user log on from that workstation Can the first user log on from a different workstation Answering questions like these enable you to determine whether the problem lies in the user s account, in the workstation, or in the AD DS domain itself.

Inability to log on to an AD DS domain could be the result of account problems, caused either accidentally or deliberately. This is particularly likely if only one computer or user is affected. You can make sure that the computer account for the workstation is not disabled in the AD DS domain and that the user account attempting to log on is not disabled. When the computer account is disabled, a message like the one shown in Figure 12-10 appears as the system starts. When the user account is disabled, the logon fails because the domain controller does not accept the credentials.

You might find that another administrator has disabled one or the other of these accounts for some reason, or that the user has been locked out due to an excessive number of failed logon attempts. These are the simplest things to check, using the Active Directory Users And Computers console, as shown in Figure 12-11, and the simplest problems to remedy.