10.4.1.3 Packet Tracer Multiuser - Implement Services Instructions

Packet Tracer Multiuser - Implement Services

Please click here to download topology
10.4.1.3 Packet Tracer Multiuser - Implement Services - Client Side
10.4.1.3 Packet Tracer Multiuser - Implement Services - Server Side

Topology

10.4.1.3 Packet Tracer Multiuser - Implement Services Instructions

Addressing Table

Device	IP Address	Subnet Mask
Server Side Player
WRS	172.16.1.254	255.255.255.0
S1	172.16.1.1	255.255.255.0
www.ptmu.test	172.16.1.5	255.255.255.0
NetAdmin	DHCP Assigned	DHCP Assigned
Client Side Player
S2	172.16.1.2	255.255.255.0
PC1	DHCP Assigned	DHCP Assigned
PC2	DHCP Assigned	DHCP Assigned

Objectives

Part 1: Establish a Local Multiuser Connection to another Instance of Packet Tracer

Part 2: Server Side Player - Implement and Verify Services

Part 3: Client Side Player - Configure and Verify Access to Services

Background

Note: Completing the prior activities in this chapter, including the Packet Tracer Multiuser - Tutorial, are prerequisites to completing this activity.

In this multiuser activity, two students (players) cooperate to implement and verify services including DHCP, HTTP, Email, DNS, and FTP. The server side player will implement and verify services on one server. The client side player will configure two clients and verify access to services.

Part 1:     Establish a Local Multiuser Connection to Another Instance of Packet Tracer

Step 1:     Select a partner and determine the role for each student.

a.     Find a fellow classmate with whom you will cooperate to complete this activity. Your computers must both be connected to the same LAN.

b.    Determine which of you will play the server side and which of you will play the client side in this activity.

-       The server side player opens Packet Tracer Multiuser - Implement Services - Server Side.pka.

-       The client side player opens Packet Tracer Multiuser - Implement Services - Client Side.pka.

Note: Solo players can open both files and complete the steps for both sides.

Step 2:     Configure the switches with initial configurations.

Each player: configure your respective switch with the following:

·         Hostname using the display name (S1 or S2).

·         An appropriate message-of-the-day (MOTD) banner.

·         Privileged EXEC mode and line passwords.

·         Correct IP addressing, according to the Addressing Table.

Step 3:     Server Side Player - Configure the PTMU link and communicate addressing.

a.     Complete the steps necessary to verify that the PTMU Link is ready to receive an incoming connection.

b.    Communicate the necessary configuration information to the client side player.

Step 4:     Client Side Player - Configure the outgoing multiuser connection.

a.     Client side player: Record the following information supplied to you by the server side player:

IP Address: _________________________________________

Port Number: ________________________________________

Password (cisco, by default) ___________________________

b.    Configure Peer0 to connect to the server side player’s PTMU Link.

c.     Connect the S2 GigabitEthernet1/1 to Link0 on Peer0.

Step 5:     Verify connectivity across the local multiuser connection.

a.     The server side player should be able to ping S2 in the client side player’s instance of Packet Tracer.

b.    The client side player should be able to ping S1 in the server side player’s instance of Packet Tracer.

Part 2:     Server Side Player - Implement and Verify Services

Step 1:     Configure WRS as the DHCP server.

WRS provides DHCP services. Configure DHCP Server Settings with the following:

·         Starting IP address is 172.16.1.11.

·         Maximum number of users is 100.

·         Static DNS 1 is 172.16.1.5.

·         Verify NetAdmin received IP addressing through DHCP.

·         From NetAdmin, access User Account Information web page at 172.16.1.5. You will use this information to configure user accounts in Step 2.

Step 2:     Configure services on www.ptmu.test.

The www.ptmu.test server provides the rest of the services and should be configured with the following:

·         A DNS record associating the IP address for www.ptmu.test server to the name www.ptmu.test.

·         Email services and user accounts according to the user list. The Domain Name is ptmu.test.

·         FTP services and user accounts according to the user list. Give each user permission to write, read, and list.

Step 3:     Verify that all services are implemented according to the requirements.

From NetAdmin, complete the following:

·         Configure the email client for the NetAdmin user account.

·         Send an email to the user at PC1.

·         Upload the secret.txt file to the FTP server. Do not change the file.

Note: The score for the server side player will be 43/44 until the client side player successfully downloads the secret.txt file, modifies the file, and then uploads it to the www.ptmu.test FTP server.

Part 3:     Client Side Player - Configure and Verify Access to Services

Step 1:     Configure and verify PC addressing.

a.     Configure PC1 and PC2 to automatically obtain addressing.

b.    PC1 and PC2 should be able to access the web page http://www.ptmu.test.

Step 2:     Configure and verify PC email accounts.

a.     Configure email accounts according to the requirements at www.ptmu.test/user.html.

b.    Verify that PC1 received an email from NetAdmin and send a reply.

c.     Send an email from PC1 to PC2. Note: Scoring will not change.

d.    Verify that PC2 received an email from PC1.

Step 3:     Upload and download a file from the FTP server.

a.     From PC2, access the FTP server and download the secret.txt file.

b.    Open the secret.txt file, change only the secret word to apple, and upload the file.

c.     The server side player score should be 44/44 and the client side player scored should be 33/33.