Back to the Unofficial MCP Page - Main
New link to the above mentioned site

Below is permission for this to be copied. He moved his site to another server and said he was taking this page down.

THIS PAGE IS GOING DOWN VERY SOON SO IF YOU WANT TO POST ANY OF THIS INFORMATION ON YOUR SITE PLEASE FEEL FREE TO COPY AND PASTE IT - ALSO IF YOU HAVE A LINK TO THIS SITE PLEASE TAKE IT DOWN!

My tips and links for the Microsoft Networking Essentials Exam

The Microsoft Self Study Kit is not as good as it should be, so I have put this page together. I will do my best to publish what I know to be correct. Thanks to all of you that have sent all that good info! Here we go:

The Scope: There are 58 questions and you have 75 minutes. Passing is 793 out of 1000 (the highest passing score I have ever heard of!). It replaces the Networking Basics test and counts as a core exam for the MCSE. It's a new exam so it should be around for a while. Microsoft has a Self Study Kit (SSK) - which is the only book I know of to help you study. You can get it from 1-800-MS-PRESS ($100) but it's much cheaper if you get it from a local vendor ($85). I also recommend getting the practice exam for Transcender. All questions are multiple choice or multiple answer - also there will be several scenario questions. When I took it I was blown away.. it is definitely the hardest test I have ever taken but I made a 896 first time around. I recommend that if you don't know the answer or you can't even understand the question try to look at the question logically - in other words pick out the obvious - if it looks wrong then it probably is - also mark it and come back, it might be answered in another question. I would guess that this page contains about 50% of the test so it should be a really good resource for you. And here is another page that is pretty good. GOOD LUCK!

Need help with the OSI Model? Click here and here.
Here is some great stuff on Ethernet and other networking info.
Nicholas Chung's MCP Page

Standards and Terminology

Crosstalk = overflow from an adjacent wire
Attenuation=The weakening or distorting of a transmitted signal as it goes further
Beaconing=The process of signaling computers on a ring system that token passing has been interrupted by a serious error.
Jitter=Instability in a signal wave form over time that could be caused by signal interference or an unbalanced ring in FDDI or Token Ring environments.
A UNC (Universal Naming Convention) \\computer name\share name for example \\Sales\MSWord
Peer to Peer - use when there are less than 10 computers and security is not an issue
Client/Server - use when there are more than 10 computers or it may be expanded in the future and security is an issue.
User Level Security - Security is implemented by the Admin - security is based on user name and password
Share Level Security - each user has control of their shared resources (or "share") - used on peer to peer
*Which is a feature of Win NT Workstation:
Shared resources with passwords (incorrect)
User level passwords (correct)
*Which is a feature of Win 95:
Shared resources with passwords (correct)
User level passwords (incorrect)
Connection oriented communication is reliable
Connection-less orientated communication is unreliable
PPP supports dynamic IP addressing and SLIP does not. Also SLIP does not support compression but CSLIP does.
CSMA/CD -Carrier-sense multiple access with collision detection - check the cable for traffic - if there is no traffic it can send
CSMA/CA - Carrier-sense multiple access with collision avoidance - signals the intent so send data b4 sending to help avoid collisions - is slower and less popular than CSMA/CD
NDIS and ODI are designed to bind multiple protocols to a single NIC.
For the OSI Model click here and here.
OSI Model - 7 layers
Application
represents the services that directly support user application, such as software for file transfer, database handle general network access, flow control, error recovery
Presentation
determines the format used to exchange data among networked computers -network's translator
protocol conversion encrypting the data
data compression
utility known as redirect operates at this layer
Session
allows two applications on different computers to establish, use and end a connection called a session performs name recognition like security placing checkpoints in the data stream dialog control between communicating processes
Transport
ensure that packet are delivered error free
break long message into several packet and repackage it when in receive mode
send an acknowledgment of receive
flow control, error handling
Network
addressing messages and translation logical addresses to physical addresses
determine the route from the source to the destination computer
packet switching, routing, controlling the congestion of data if the network card on the Router can't transmit a data chuck as large as the source PC sends, the network layer on the Router compensates by breaking the data into smaller units
Data Link
sends data frames from the network layer to the physical layer
receive end - it packages raw bits from the physical layer into data frames
provide the error-free transfer of these frames
sends a frame, it waits for an acknowledgment from the recipient
LLC (Logical Link Control) upper sublayer of DL - manages DL communication and defines the use of logical interface points - defined by 802.2
MAC (Media Access Control) lower sublayer of DL - provides shared access for the NIC Physical layer - is responsible for delivering error-free data between 2 computers - defined by 802.3, 802.4, 802.5, and 802.12
Physical
transmits the unstructured raw bit stream over a physical medium (cable)
defines how the cable is attached to the network adapter
responsible for transmitting bits (1 & 0)
easier way to remember the above:

I learned OSI very well, esp p172-175. You must also know where the network protocols live. They will give you a picture of it somewhere in your exam if you forget the order (esp of Transport and Network layers).
Application layer: layer7 Applications, e-mail, into user apps, initiates and accepts requests, higher level protocols live here, FTP,telnet,SMNP, SNMP, NFS and error RECOVERY.
Presentation Layer:layer6 Protocol conversion. The redirector lives here. Redirector grabs anything meant for network (files, prints anthing) and redirects to right place. All the different formats from all sources and all kinds are made into like a uniform common format that the rest of the OSI model can understand.
Session layer: layer5 Syncs & sessions. Connects two computers and controls, who send when, for how long, how, speeds, and oversees total control of packets. TCP, NWLink, named pipes, netBIOS and remember thatDLC lives here. This was one of the questions. Also remember that TCP(microsoft) is like SPX(Novell) and IP(microsoft) is like IPX (Novell). The above 3 layers are the application-level network service users.
Transport layer: layer4 "Trains" well I try and remember that the data streams breaks up into what looks like coaches of a train. The transport services layer. The error handling is done here. Differentprotocols have different requirements for length of data per packet, eg Token ring, Ethernet ATM all use different lenghts and these are formed and reformed in this layer. NDIS3, IP, SPX live here. Look p215.
The above 4 layers use gateways. There are Qs on which layers useg/.ways. ie App Pres. Session. Trans.
There are also Qs on Physical= repeater (or hub)
Data link layer=bridge
Network=router
These are gift marks so know them.
Where does SMB reside? Where do you find DLC?
Network layer layer3; Think of a big network, where the traffic is routed to, this being done by adding source and destination addresses, choosing best routes.(and uses routers.)
Data Link Layer layer2: look at the movies on the CD with Net essentials and see that DLL add CRC to other end of the data frames. Bridges work here, and the book is very terse on explantations. Basically the packets use network addresses (source and destination addresses) to get around; they can move around the world using logical addresses and are part of networking software, like Novell or Windows.This whole "network structure" actually sits on top of,( like another thing) ,on top of the LAN. The LAN being the basic underlying network, that's the nitty gritty physical network, where the the acual Network cards talk to each other. The LAN really is only local and the DATA LINK LAYER conrols it. DLL is split into two LOGICAL LINK CONTROL and MEDIA ACCESS CONTROL. This may seem difficult at first but its not too bad. Think that the Media Access Control (MAC) controls the type of media being accessed ie media being Token ring, ethernet etc. also learn the 802.3~"ethernet", 802.4 ~arcnet (really only used by GM and obsolete), 802.5~token ring, and 802.12 Fiber. The LOGICAL LINK CONTROL equates to 802.2 and is the "lowest level" controlling and managing the media.
Physical layer; layer 1; This is the hardware and physical cables. Repeaters (or hubs) amplify attenuated or wek signal here. (Another gift Q.) It just has to send 0 and 1, hi's and lows, on's and off's .
Data frames work at the two bottom layers and only inside the LAN using Physical or MAC addresses (usually factory or hard wired addresses). On page 176 looks like 10 of the gift Qs we got. These bottom 2 layers are called networking services. P179 talks about SAPs.
All People Seems To Need Data Processing or
Paula Did Networking Till She Passed Away
IEEE 802 Committees
802.1 Internetworking
802.2 Logical Link Control (LLC)
802.3 CSMA/CD NETWORK (Ethernet)*
802.4 Token Bus NETWORK
802.5 Token Ring NETWORK*
802.6 Metropolitan Area Network (MAN)
802.7 Broadband Technical Advisory Group
802.8 Fiber-Optic Technical Advisory Group
802.9 Integrated Voice/Data Networks
802.10 Network Security
802.11 Wireless Networks
802.12 Demand Priority Access NETWORK (100VG-AnyLAN)

Planning

Ethernet topologies:

RG-58 /U = Solid copper core - 50ohm impedance
RG-58 A/U = Stranded wire core
RG-58 C/U = Military spec. of RG-58 A/U
RG-59 = Broadband transmission such as cable TV
RG-6 = Larger in diameter and rated for higher frequencies than RG-59, but used for broadband transmissions as well
RG-62 = arcane networks
What is the difference in RG58U and RG58AU?
A/U signifies a stranded wire core instead of solid for thinnet. RG 58 U cable (solid core conductor) is NOT compatible with for ThinNet and is different that RG 58 A/U which IS used for ThinNet *HINT* replace RG58 U with RG58 A/U
1 meter =3.281 feet
*Know the different categories of UTP cable and what bandwidth they're capable of.

Incorrect frame types can really throw off an IPX/SPX network.
IPX/SPX is great for Peer-to-Peer networking if NetBEUI is not availabe
NetBEUI is a Transport protocol and is not routeable mainly used on Microsoft networks.
Mesh - uses routers to dynamically select the best path for the data
Know what a Mesh topology looks like (I had one that showed an exhibit of a mesh and asked me what it was). Check out page 782 of the SSK.
A subnet mask is used to mask a portion of the IP address so that TCP/IP can distinguish the network ID from the host ID. TCP/IP hosts communicate by using the subnet mask to determine whether the destination host is located on a local or remote network. The following is a valid subnet mask: 255.255.0.0.
Repeater = Physical layer - takes a weak signal and regenerates it - doesn't translate or filter anything - can move packets from on physical media to another (i.e. can connect thinet to fiber-optic) - they are cheap - will pass a broadcast storm
Bridge = Data Link layer - does everything a repeater does - reduce traffic by segmenting the network by using a routing table- regenerate the signal at the packet level - not suited to WANs slower than 56K - will pass broadcast storms - read the source and destination of every packet - pass packet with unknown destinations - connect dissimilar networks (i.e. Token Ring and Ethernet)
Router = Network layer - does filtering and isolating traffic - forwards particular protocols to particular addresses (other routers) - connect network segments - not all protocols are routeable (LAT and NetBEUI) - are used in complex network situations because they provide better traffic mgmt. than brides - don't pass broadcast traffic.
Brouter = combines best qualities of both a bridge and a Router - can act like a Router for one protocol and bridge all of the others (nonroutable) - delivers more cost-effective and more manageable internetworking than separate bridges and routers - connect 2 networks and limit unnecessary traffic - separate administrative networks - in other words use a brouter when using routeable and nonroutable protocols
Gateway = link 2 systems that don't use the same protocols, data formatting structures, languages and architecture (i.e. NT and SNA) - stripes protocol stack and repackages it - used to connect a mini and mainframe (NT and an AS/400) - task-specific, slow and expensive.
Multiplexer= a device that can divide transmission into 2 or more channels
In addition to protocol levels for each device, know what kind of compatible network each can join:
*Bridges - connect two similar networks and keep local IP address traffic local, but broadcasts go to the other side.
*Routers - connect similar protocol networks but only propagate packets that are not addressed to the local network and know about the router (in network control panels it the default gateway or route table that has to know about routers).
*BRouters are devices that can act like bridges or routers.
*Gateway (not to be confused with default gateways) are protocolconverters they change TCP/IP to IPX/SPX etc.
*Ethernet Switches - they confine network traffic by actually only making connections between the source and destination systems. Wont help with broadcasts though, but will cut down traffic on backbone.
*Know the differences between Repeaters, Routers, Bridges, Brouters, Gateways, Hubs, etc, and in which cases you would need one or the other.
*In addition to protocol levels for each device, know what kind of compatible network each can join:
*repeater: different media, e.g, thicknet & thinnet
*bridge: same as repeater AND different architecture, e.g., token ring to ethernet
*gateway: same router AND different PROTOCOLS

X.25 = slow because of error checking and retransmission
Frame Relay = fiber optic
ATM = 155Mbps to 622Mbs
ISDN = divided into 3 channels 2 are 64Kbps (128Kbs combined,B channels, data stream) 3rd is 16Kbs (D channel, signaling and link mgmt.)
FDDI = 100Mbps - 500 computers over 100kilometers (62 miles) -
SONET = 51.84 Mbps
SMDS = 1Mbps to 34 Mbps
*What speed can X.25 and Frame Relay support?
1. Frame relay is cool. Frame relay gives you as much bandwith (transfer rate) as you want. You just pay for the bits transferred, instead of the time connected or the lease or watever. It does this by routing the packets through all of the provider's meshed network, (The cloud) just like the internet does. I guess it's only limited to the connection that you have to your provider. X.25 is like frame relay except it's a little older and employs tons of error checking because its medium was plain old telephone wires (crosstalk and interference galore!) I guess these are related to your question about sliding TCP windows above, because they have to have packet assemblers/disassemblers (PAD's) ---the packets have to sit into the window and wait until everyone has gotten there and everyone is put in order before more can be sent. Of course, they don't nececarily have to be using a TCP sliding window. The PAD is actually at a lower level in the OSI model compared to tcp's sliding windows, I think.
2. X.25 can support up to 56 Mbps. Frame Relay, according to AT&T, is capable
of "burst rates up to 1.5 Mbps initially and potentially 45 Mbps in later
releases."

Implementation

Raid 0 - disk striping - disk striping divides data into 64k block and spreads it equally in a fixed rate and order among all disks in an array
Raid 1 - disk mirroring - actually duplicates a partition and moves the duplication onto another physical disk duplexing - is a mirrored pair of disks with an addition disk controller on the second drive
Raid 2 -Disk striping with ECC - when data is written the block is divided up and put across all drives - ECC is Error correction code
Raid 3 - ECC stored as parity - same as 2 but the ECC is cut down so that is only counts the number of 1's.
Raid 4 - disk guarding - one drive is a dedicated parity drive, data is striped to multiple drives and then its parity sum is calculated, which is written to the dedicated parity drive
Raid 5 - striping with parity - data is striped across multiple drives and then its parity sum is calculated, which is also striped across multiple drives (not a dedicated parity drive) needs a min of 3 drives.
Sector spacing - hot fixing automatically adds sector - recovery capabilities to the file system while the computer is running if bad sectors are found during disk I/O. the fault tolerance driver will attempt to move the data to good sector and map out the bad sector -only for SCSI, not EIDE or IDE
IRQ2(9)=EGA/VGA
IRQ3=COM2, COM4
IRQ4=COM1, COM3
IRQ5=LPT2 or Sound Card or NIC
IRQ6=Floppy Disk Controller
IRQ7=LPT1
A valid NetBIOS name must be under 15 chars, and have valid characters, (You know, not these kind: !@#$%^&*()|", etc, etc.) and it also must be unique on the netowork.
*Remember that Netbios names can be made valid over a WAN(i.e. routable) if you use IPX/SPX with Netbios support as the protocol.

Troubleshooting

Digital Volt Meter (DVM) is the most basic, all-purpose electronic measuring tool. Can tell you if cable is continuous or broken - can revel if two parts of the same cable are exposed and touching or a broken part of the cable is touching another conductor (piece of metal).
Protocol Analyzer=can look at packets to generate stats on network traffic - have a built in TDR - can provide insights into the network's behavior
Time Domain Reflectometer= sends sonar like pulses - looks for a break, short or imperfection in a cable - can locate a break within a few feet of the actual separation in the cable
Oscilloscopes=can display shorts, crimps, breaks and attenuation in cable.
When only one computer cannot connect to the network - it's probably a physical problem like the NIC or the cable connection - if you are using IPX/SPX it's probably an incorrect frame type.
*Know that you cannot wire-tap a FDDI network like you can Ethernet.

Misc.

*Know what protocol is used to determine # of hops to a destination.
Routing information protocol (RIP) uses distance-vector algorithms to determine routes.

*Ethernet has an MTU (maximum transfer unit) of 1514 bytes compared to Token Ring's 4k+.
*Your bridge/router between the two networks affects (effects?) the file transfer as well as the lan protocol (IPX/IP/NetBeui) you are using.
*Note2: For MS Networking Essentials Readers please substitute 'gateway' for the above mention bridge/router.
*There were a lot of questions on bridges vs. routers vs. gateways (when to use which one in this or that scenario). There were also a lot of 10base2, 10baseT comparison questions.
*Definitely know about which 802.x refers to which wire type (thick coax, thin coax, 10baseT, baseband vs. broadband, bus vs. star, Collision Detection vs. Token passing etc.
*DLC, LAT and NetBEUI are not routable. Almost everything else likely to be on the test is routable.
---- this question was on the test and replacing the RG 58 U cable with RG 58 A/U was the only correct answer ---
*Which of the following supports compression and error control: PPP and SLIP -- SLIP doesn't support compression --- *Which of the following are routable protocols (name 5): TCP/IP, NWLink SPX, Apple Talk, NetBEUI and DLC (not NetBEUI or DLC and DLC is not a valid peer-to-peer network protocol for computers)
*Know when to use a bridge, router, or gateway. There are about 12 questions where it puts you in a scenario and gives an action and asks if the action meets all or part of the goal. Those ones seem hard but if you've studied you can figure it out with deductive reasoning. It doesn't ask any questions on definitions of the OSI model per se, but will ask how it pertains to network hardware. Know ATM, FDDI, etc and what they can be used for. Also have ALL the ethernet 802.3 characteristics down to a SCIENCE! There;s also a few where it asks something like "You've set up a PC and it inserts into the ring, but you can't see some of the servers, what is the problem?"
*Which is used for at least 100mbps: ATM, X25, 52kbps Digital line (ATM)
*Understand that if you are upgrading to 100BaseTX, you will need to also change network cards, hubs, etc
*Know that a terminator impedance is usually always 50 ohms
*Know the difference between a file & print server and an application server, i.e. the application server performs processor calculations
*you gotta know your TCP/IP quite well-ask about windows size changes lots of stuff in the situation questions.etc. Lots on Packet switching, ATM, switching hubs, T1 lines.
*OSI Layer wasnt asked so much except where does repeater(1) bridge(2) router(3) and gateway (4,5,6,7) fit in.
*Also, be prepared to answer some questions on some network troubleshooting equipment, a topology question that is obviously MESH that isn't in the self study guide, and an assortment of how long of a cable run can you have with 10-base-T, 10-Base-2, etc.
*Know the different types of coax and what they're used for (RG-8, RG-11, RG-58, RG-62)
*Know the difference between a Volt-Ohm Meter, a Protocol Analyzer, and a Time Domain Reflectometer, and what each one is used for.
*Know what protocol (RIP) is used to determine # of hops to a desination.
*Know the different types of network services (ATM, X.25, ISDN, Frame Relay, etc.) and what bandwidth they're capable of.
*Know what a Mesh topology looks like (I had one that showed an exhibit of a mesh and asked me what it was).
*Know that you cannot wire-tap a FDDI network like you can Ethernet.
*IPX/SPX is great for Peer-to-Peer networking if NetBEUI is not a choice (hint: that's one of the questions on the test).
* Acronyms suchs DHCP, WINS, NFS
* Different diagnostics tools such as TDR Time Domain Reflectometer, Sniffers, VOM Volt-Ohm Meter, oscilloscope
* Memorize the Media Types, UTP, ThickNet ThinNet, etc. max distances, how to implement.
* Using a router to resolve broadcast storms (freebie)
* Different network topologies including Mesh

Thanks to all of you that have answered my questions and shared your information to make this page possible!