Lab Building a Simple Client-Server Network Objectives

Lab 2. Building a Simple Client-Server Network
Objectives
Client-server networks are found in all but the smallest organizations. Although client-server networks are more difficult to configure than a peer-to-peer network, they are more scalable and can grow larger than peer-to-peer networks can. S7ith more than a handful of computers, a peer-to-peer network quickly becomes unwieldy. In a client-server network, however, you can manage user accounts and network resources such as printers from a single machine. For instance, to change the printer used by all users on a peer-to-peer network, you would need to go to each machine and configure the new printer. Imagine having to do this on 500 machines! In a client-server network, however, you can typically change this setting on the server for all users.
The goal of this lab is to become familiar with the methods for establishing a simple client-server network. During this lab, you will be introduced to the hardware and software required to connect one or more workstations to a server. As part of the setup for this lab, both the server and the workstation need to be configured with an IP address. Computers and other network devices use the IP address to find other computers.
After completing this lab, you will be able to:

• 
  Build a simple client-server network
  
• 
  Add a Windows 8.1 or 7 client computer to a Windows Server 2012 R2 domain
  

Materials Required
This lab will require the following:

• 
  One computer named SERVERI running Windows Server 2012P.2, or an equivalent virtual image, with an Ethernet port or NIC, configured with an IP address of 192.168.54.1
  
• 
  SERVERI configured as the domain controller for the netpluslab.net domain
  
• 
  A user account named netplus in the Users group in the netpluslab.net domain on SERVER l
  
• 
  A second computer named WORKSTATION1 running Windows 8.1 or Windows 7, or an equivalent virtual image, with an Ethernet port or NIC, configured with an IP address of 192.168.54.2; this computer should not be configured as a member of a domain
  
• 
  Access to WORKSTATIONI as a regular user
  
• 
  Both computers should be connected either virtually or through a switch or home router
  

Lab 2.3. Troubleshooting Client Logon Problems

In this lab, you will troubleshoot a scenario in which a user cannot log on to the server. From a user's perspective, when they cannot log on to the server, the network is unavailable, no matter what the reason. However, the ultimate cause of the problem might be anything from a hardware failure on the server to an expired password.

When troubleshooting problems, you should attempt to be as methodical as possible. You can start by determining the scope of the problem. Is only one user affected, or are all users affected? Then determine if the user's computer (or the users' computers, if multiple users are affected) and the server have physical connectivity. Do all the NICs seem to be working properly? Is the switch functioning and is the network cabled properly? After establishing that physical connectivity is not the problem, determine whether the user's computer has network connectivity. Can you ping the server from the user's computer? After you have determined that network connectivity is not the problem, try to determine if the application is functioning properly.
Keep in mind that being able to log on to a computer does not necessarily indicate that the network is functioning properly. Windows computers cache passwords for usernames, so that a user can still log on to a computer during a network outage.
In this lab, you will first verify that the network, the client computers, and the server are all functioning properly by logging on to two client computers. Then your instructor or another set of lab partners will do something to prevent at least one of the computers from logging on to the server. Your assignment will be to identify and solve the problem. After completing this lab, you will be able to:

• 
  Follow a logical troubleshooting methodology to determine the nature of client connectivity problems.
  
• 
  Identify a network problem by interpreting the results of diagnostic utilities such as Ping and Ipconfig