In the lecture we did a recap on the dry run of the Video Conference we done a couple weeks ago. What Paul did was he recorded the entire thing so that if we wanted to make any edit’s, we could edit it and then re-post it up on Moodle. we also examined the risks and thought up solutions and measures that could be in place to eliminate that risk:
- Make sure system is up to date
- Investigate Wi-Fi
- Warnings about wi-fi => 10 seconds delay on the tablet tethered to phone, phone was blackberry.
- Tablet and android apps can’t see full text iPhone can.
- Make sure the meeting is recorded at all times.
- If people have been logging in twice it will cause problems such as confusing them as a presenter.
- Presenters looking at projector instead of laptops and desktops
- Should say when questions can be answered in the conference
- Screen sharing does not work in google chrome
- If the presenter machine crashes the webcam and microphone will have to be enabled again
- Some presenters ran away
- Always put up phone number so people can contact us
- Links don’t work on mobile phone
- Sharing someone’s screen has to be investigated
- Have the closing message prepared before closing.
Here is the link for the video we did of the Dry Run Video Conference (unedited): http://connect.lsbu.ac.uk/p4xl8868bjv/?launcher=false&fcsContent=true&pbMode=normal
In the tutorial, we started using a new software called Cisco Packet Tracer. Cisco Packet Tracer is a powerful network simulation program that allows students to experiment with network behavior and ask “what if” questions. As an integral part of the Networking Academy comprehensive learning experience, Packet Tracer provides simulation, visualization, authoring, assessment, and collaboration capabilities and facilitates the teaching and learning of complex technology concepts.
The weeks leading up to Week 13, we are going to use Cisco Packet Tracer for our coursework/presentation. What we did for the duration for the tutorial session was experiment with it and looking for tutorials on the program itself and YouTube.
What i did first was create a Topology using a Network Switch which was linked up to 5 different PC’s:
Then I assigned each PC an IPV4 Class-3 address:
Then I pinged each PC using the command line:
Till next time…………………