--Pieces of the printer puzzle

--Client--->Server--->Printer

--Some printers are servers themselves

--Printing

--Client issues print request

--Redirector looks for designated port (usually LPT1) and when it isn't found on the client, sends the print job to a server on the network

--Server grabs and stores the file(s) in a queue for printing

--Print jobs are held in printer's RAM (AKA spooler)

--Transferring print jobs to printer is spooling

--Often notification of completed print job(s) is returned to the client

--SERVER: feeds data to the printer

--REDIRECTOR: sends data from local printer port to server

--SPOOLER: printer's RAM that holds print info

--DLC - mainframe communications and printer protocol (not routable!)

--PDL: Page description language Ex: Postscript

--Printer converts generic PDL into specific information to be processed by the printer

--Clients must provide identification to the server in order to access shared resources

--The most important thing to know when working with printers is how to kill a print job

--to truly kill a print job you have to stop printing at the device level even when the job is deleted from the queue the printer will keep printing until it's buffer is cleared of information .Often recycling the printer will clear the buffer of information

--Administrators can reorder and kill print jobs in the queue

--Network OSes allow remote administration of printing from any workstation that has the necessary utility installed

--MAILBOX: stores email for users

--X.500: OSI/CCITT directory services protocol, used heavily by universities and SPRINT

--X.400: mail protocol

--GATEWAY: translates incoming email messages to a format the OS can understand

--MTA: Message transfer agent

--server to server

--acts on behalf of the users

--UA: User agent

--software below the email client that allows email to be upload to server

--MTS: Message Transfer servers

--provides actual transfer of messages from one server to another

--actually software rather than an agent

Memorize: pp 381: Five client/server message based functions

1. Scheduling

2. Messaging services

3. Group information sharing

4. Forms

5. Application design

--Network allows you to do management on demand of documents in a centralized repository

--Exchange Server is designed to work with existing email applications and networks

--3 types of Microsoft Mail

--Workgroup Mail

--peer to peer

--on machine takes on the store and forward responsibilities

--Microsoft Mail

--client based

--Microsoft Exchange

--server based

--mail is uploaded to the server and handled there

--Exchange provides no only email but other similar services

--Advanced groupware accommodates multiple platforms

--Redirector is key to serving client OSes on one network

--client has network access that allows the computer to interact with the Network --AKA requestor

--the requestor only handles packets sent inthe protocol it understands

--client and server must be able to speak and same protocol

--Services make server appear to clients as if they are running the same OS

--slows down network communications

OSI Model

--usefulness:

--layers

--modular

--peer/partner layers

--Top application layers are usually mirrors or otherwise similar

-- NDIS - a multiplexor director and converter, links/binds one or more protocols to one or more NICs

--NDIS 2.0 - multiple protocols to 1 NIC

--NDIS 3.0 - multiple protocols to multiple NICs

--NDIS 3.1 - plug and play

--Front End=user interface

--presents data on the client computer

--formats user input data

--SQL: Structured Query Language

--translates user input into a format the database understands

--Primary server roles:

--data storage

--data management

**pp 417 case study

--Administrator logs onto a network first

--User account contains security info

--user name

--password

--permissions

--Network utilities allow administrator to create and copy user profiles for quick and efficient account setups

--PROFILE: user's logon environment as configured and maintained by the network administrator

--guest account is for temporary access

--can be used to hack network (BAD)

**Important to understand the basics of NT domains

**pp447-449 - types of groups and defaults

--Groups allow for multiple user management

--Rights are ability to access network resource4s as established by permissions

--Once a user is deleted they have no access to the network because there is no record of them in the SAM

--To monitor network performance you look for common errors as well as bottlenecks

--SNMP: Simple Network Management Protocol

--TCP/IP is the protocol for managing networks

--must turn on SNMP service to use performance monitor

--Agents monitor network traffic

--not their only use

**pp 474-476 Physical security

**pp 477 Named Permissions (KNOW THESE)

For the exam, knowledge of NetWare of 2.0 and 3.0 will be assumed.

NetWare 4.0 and NDS is not covered by the current exams.

--First step in security is protecting hardware

--Permissions

--AKA user level security

--can be assigned on an individual or group level

--Shares are defined on a per resource basis

--Read Only=read and copy but not modify

--Defining the share allows sub-share groups

--ACL: Access Control Lists

--Security logs keep track of user account and activity

--Diskless computer boot from info on the Network Adapter Card RAM

**pp 490 types of backups

--Backups

--first line of defense against data loss

--need to be performed on a regular schedule

--maintain a log of backups for easier file recovery (on paper)

--reduce traffic by putting backup machine on a seperate segment

**pp 496-499 Levels of RAID

-- RAID 0 - no fault tolerance