Today I opened a terminal to use as an interface instead of Coolterm. In the terminal I typed ifconfig return to confirm that I was on the switch. Then I typed telnet, return to start a connection between my computer and the switch. Telnet is a network protocol that enables us to connect remotely with other switches.

In order to confirm that the network connection was working I opened a terminal and pinged Ken using his client address 192.168.16.101. I was able to connect with Ken.

I kept two terminals open, one to use for telnet. To connect to the switch I typed the command: telnet 192.168.25.254, return
login: admin
password: swtich

I also kept another terminal open.

I learned that it is faster to use the command prompt to configure switches.

To open the WebView I typed the address 192.168.25.254 in the address bar.
login: admin
password: switch

We used Webview to open and review our routing tables. To get into Webview we typed the address of our switch (192.168.25.254) into the web browser. Once in Webview, we went to open network, IP, routes, then select the table we wanted to see (i.e. forwarding).

To compare the routes on telnet vs. Webview, we typed the command: show ip route into telnet. Figure 1 is a picture of our table and identifies the addresses our switch will forward to.


Figure 1

After learning about the routing tables we began our task of updating the server by adding DNS services, a File server and a DHCP server.

After booting our workstation using the Knoppix operating system we began the initial configuration (this Initial Configuration Task opened upon booting). Next under the section: Customize this server we selected >Add features.

First we enabled file sharing; we captured screen shots of the steps required to share files and these pictures are house on Google Doc:

https://docs.google.com/document/d/12Z-o8DzBzpHrAwc_rGCvKbw-QroYAgUvOKA9EXesdhI/edit?hl=en_US

Then we added DNS services. We captured screen shots of the steps required to add DNS services. These pictures are house on Google Doc:
https://docs.google.com/document/d/1TXN3-aTTxfuFRJ1a8iH7mTwzcH3YXbnVU_Yg3gxjfd0/edit?hl=en_US

Next we added a DHCP server. We captured screen shots of the steps required to add a DHCP server. These pictures are house on Google Doc:

https://docs.google.com/document/d/1mysX0kmehxQUm4BEJ_vQ1AAfwN5oGYind3OljP-f-Jc/edit?hl=en_US

One challenge today arose when we were trying to install the DHCP server because we were not sure about the Domaine Name. Sandie told us to use network5769.local and explained that this will allow us to manage our computers.

The greatest challenge today was identifying missing drivers. This required some investigation and experimentation but finally we were able to find the three missing Chipset drivers. Finally we downloaded the correct drivers from the Dell site.

To check connectivity we opened a terminal and pinged the following addresses:

- our network: 192.168.25.69
- switch Vlan 1: 192.168.25.254
- our switch Vlan 2: 10.0.25.254
- our server: 192.168.25.50
- the core switch Vlan 1: 10.0.1.254)
- he core switch Vlan 2 (10.10.1.100)
- the firewall (192.168.1.1)

When all of these connected we knew that we would be able to connect both in and outside of our Vlan.