Subject: My Braindumps for Networking Essentials
High pass mark (793). Lots of scenario questions – read every word. Hard questions seemed to come early on – I ignored all scenario questions and did the simple "one paragraph of text with 4 choices" questions first.
Also, I started the 15 min tutorial, but then wrote down the following, which was useful:
7. Application Packet building starts here!
6. Presentation Redirector, SMB
5. Session TCP, NWLink, Named Pipes, NetBIOS, DLC
4. Transport NDIS 3, SPX, IP
3. Network Routers/BRouters
2. Data Link Bridges
MAC 802.3/4/5/12
LLC 802.2
1. Physical Hubs/Repeaters
(Gateways use layers 4- 7)
802.3 Ethernet
802.4 Token Ring Bus
802.5 Token Ring Normal
802.12 Anything running at 100 Mbs
10Base2 RG58 A/U, 10Mbs, 185 Mtrs, Thinnet, .25", 50Ohm
10Base 5 10Mbs, Thicknet, 500Mtrs, .5" dia, 50Ohm, Vampire Tap
10BaseT UTP/STP Cat 3/4/5, 10Mbs, 100Mtrs
100Base… UTP Cat 5 only, 100Mtrs
Com2 = 3
Com1 = 4
LPT2 = 5 (normally available)
LPT1 = 7
10,11,15 normally available
User wants to access IBM 3090 via Terminal Emulation, what device? A: Gateway
What is designed to replace analog phones? A: Basic Rate ISDN
Complex NetBIOS Naming Scenario Main point is NetBIOS names <= 15 chars.
Main: Needed to link 30,000 devices with NetBIOS
Desire: Meaningful naming scheme.
Solution 1: Use unique 15 char hex number
A: Will work, but not meaningful
Solution 2: Use 1st 8 chars for location, 4 for function and 2 for something
else. Users use their e-mail address for NetBIOS name (Email address defined
elsewhere in the question as <=12 chars).
Point here being it’s meaningful and is not > 15 chars, therefore
fulfills all requirements.
120 users evenly spread across 3 servers, TCP/IP.
Main: Want to decrease network utilisation
Desire: Minimise Cost, expandibility and something else.
Solution 1: Replace Hubs, NICs and wiring with 100Mbs kit.
A: Works, but does not minimise cost (segmentation would have been cheaper)
Solution 2: Reduce packet size from 1514 to 768, increase TCP/IP window
from 4k to 16k and something else stupid.
A: Complete rubbish – doesn’t fulfil any requirements.
Mixed network of Win 95/NT and Apple Mac. Brouters between LANs. Mixed
protocols.
Main: Reduce Network Traffic without altering functionality.
Solution involved removing all protocols leaving just IPX. Turn off Bridging
part of Brouters.
A: Doesn’t fulfil as the Macs won’t work with just IPX.
3 sites in 3 cities.
Main: Want to ensure any PC can access any other PC or Server across
3 sites.
Desire: Continue working if single link fails and Continue working with
1Mbs link speed if single line fails.
Solution 1: 2 x T1 lines (T1 = 1.5 Mbs)
A: Main OK, no good if single link fails
Solution 2: 3 x T1 lines in triangle
A: Fulfils everything
What Topology is this (Exhibit) 5 PCs each linked to each other (looks like Star of David)
A: Mesh
Mixed DOS, UNIX, NT network. New NT server, UNIX boxes only can’t see it.
A: Protocol mismatch between UNIX and new server. (All other options would have caused additional symptoms – for instance the option "Faulty Cable to new server" is wrong because the DOS based PCs could see the new server.)
Intermittent network problems on Thinnet. Mix of RG58 /U Solid Core and RG58 A/U Stranded cable.
A: Replace RG58 /U with A/U. (The two are not compatible).
Install NIC on Interrupt 3, what could it conflict with?
A: Com 2
If in doubt on a multiple choice, the answers seem to be Protocol Analyser or ATM!! (3 Protocol analyser questions and 2 ATM questions) For instance, What would you use to log network activity at the packet level? Meter, TDR, PA or Oscilloscope?.
A: PA. PA includes software so is the only device of those offered which can create logs or monitor anything over time or look at packets.
Know your Resistance on Thinnet! Network fault – get 0 on coax cable centre to edge, 50 Ohm on T piece and 50 Ohm on terminator. What do you do?
A: Replace coax cable.
Know characteristics of Thinnet and UTP. Q on Thinnet specification, A was it uses BNC T connectors and on UTP where the answer was it requires Cat 3, 4 or 5 cable.
Several Questions on new computers not working but the network software seems to have initialised (which rules out interrupt and base-address conflicts). Answers were wrong transceiver type set on NIC and (for NWLink which is IPX) wrong frame type.
5 Users WfW network, which protocol. A: IPX (NetBIOS wasn’t offered as an option).
Which protocols are routable? (Everything apart from NetBEUI and DLC)
Some SLIP and PPP. SLIP does not support dynamic IP addressing, nor compression (CSLIP supports compression).
Some Security – W95 = share level, WNT = User Level (but needs a server for user list).
Network performance accessing server decreasing. NT Server Utilisation stats are CPU 8%, Page Faults 2 per second and Disk Utilisation 25%.
A: Install RAID Disk Striping of some sort (to speed up disk access).
What do NDIS and ODI give you?
A: NICs independent from Protocol.
2 PCs can’t communicate over LAN. Using Network diagnosis tools, both have identical hardware and NIC settings (including MAC address, which should of course be unique!).
A: Reset MAC address to factory settings. (MAC address can be altered in software driver, but this is not visible if diagnosing from the network.)
What do you need in a UNC Name? Server Name, Computer Name, Domain Name, Share Name?
A: Computer and Share.