Networking Concepts Lesson 08 - Simple Network Operations - Eric Vanderburg

1. Chapter 8
Simple Network Operations
Networking Concepts – Eric Vanderburg ©2005

2. NOS
 DOS,
Windows 3x – LAN Manager
 OS Features
Bridges Hardware & Software (another layer to
minimize complexity)
 Memory management
 Multitasking – many processes at the same time

Preemptive – OS controls process access to CPU (uses
time slices) Win95 & higher
 Cooperative – OS cannot stop processes once they start
using the CPU

Networking Concepts – Eric
Vanderburg ©2005

3. NOS Functions
 Share
computer resources & peripherals
 Control remote machines
 Implement security for resources
 Authentication
 Permissions
 Rights
 Maintain
directory of resources
 Provide network services to applications
Networking Concepts – Eric
Vanderburg ©2005

4. Components
 Naming

Services
UNC (Universal Naming Convention)
ComputerNameShareName
 UNC Aware – allows R or W to network storage via UNC
path (non-UNC aware require mapped drives)

DNS
 NetBIOS

Only 8 character name allowed in DOS (8.3 rule)
 Certain illegal characters
 Hidden names (ComputerNameSecretShare$)

Networking Concepts – Eric
Vanderburg ©2005

5. Directory Services




Search for the resource you need
Restricts views based on ACL
Microsoft AD (Active Directory)
Novell eDirectory or NDS







NAL (NetWare Application Launcher) – does a network
inventory and stores it in eDirectory
Formerly used a flat file database called the Bindery (NW3x)
NW4x systems can run Bindery emulation to work with 3x
Linux NIS (Network Information System)
Sun Directory Server
X.500
LDAP (Lightweight Directory Access Protocol)
Networking Concepts – Eric
Vanderburg ©2005

6. Client Software
 Logon
 Requests
resources
 Redirector
 Designator – substitutes UNC name for
a mapped drive letter
Networking Concepts – Eric
Vanderburg ©2005

7. Access Control
 Who
can access what resources
 What they can do with those resources
 How many can access resources
simultaneously
 When can they access those resources
Networking Concepts – Eric
Vanderburg ©2005

8. Server Responsibilities
 Manage
users and groups
 Authenticate users
 Advertise resources, resolve names &
maintain a directory
 Management, logging, & auditing
 Provide redundancy
Networking Concepts – Eric
Vanderburg ©2005

9. Installation
 Before
you begin:
Consider server role
 Determine file system
 Available hardware
 Choose a name & naming conventions
 Understand network size, topology, and network
OS types
 Redundancy options

Clustering
 Mirroring
 Duplexing


Placement within forest & domain
Networking Concepts – Eric
Vanderburg ©2005

10. Naming Conventions
 Names
should be based on a system
 Users & resources
Eric Vanderburg, username:evanderburg
 Proper hierarchy

 Computer

names & DNS names
First Cleveland Domain Controller, name: CleDC01
 Educate
users to save files with proper file
name structures in the proper folders
 Titles of email messages
Networking Concepts – Eric
Vanderburg ©2005

11. Storage
 Partition
– logical section of disk space
 Multiple boot – select from many OS’s upon
computer startup
 Single partition, single drive, single OS
 Multiple partitions, single drive, single OS
Separation is good
 One drive so activity is high

 Multiple

partitions, multiple drives, single OS
Distributes drive activity
 Fault
tolerant storage
Networking Concepts – Eric
Vanderburg ©2005

12. File System








FAT (File Allocation Table)
FAT32
NTFS
CDFS
EFS (Extent File System)
GPFS (General Parallel File System)
Different file systems support different sized disks,
security options, file size, naming, and cluster sizes
Some file systems cannot be used in some OS’s
Networking Concepts – Eric
Vanderburg ©2005

13. Network Services
 Installing
Services
 Starting & stopping services
 Services in Linux
 Edit
config files
 Install new package
 Package manager may be available
Networking Concepts – Eric
Vanderburg ©2005

14. Sharing in Linux
 Use
NFS for Linux only share
 Use Samba for Linux to Windows shares
Networking Concepts – Eric
Vanderburg ©2005

15. Network Applications







Multiple concurrent use
Email
Messaging
Scheduling
Groupware
Databases
Architectures



Centralized – fully stored on server
File-system sharing – client app with shared storage area or
database
True client/server – some components are on the client and
some on the server. Effectively uses client processing
Networking Concepts – Eric
Vanderburg ©2005

16. Email






X.400
IMAP (Internet Message Access Protocol) –
downloads and displays messages, can be sent to a
client or run from a web based app, fault tolerant with
advanced controls for group collaboration.
MHS (Message Handling System) – Novell’s
messaging service
POP3 (Post Office Protocol version 3) – downloads
messages to the client, messages managed locally
SMTP – standard for sending mail messages
X.500 – improved directory and has a global address
database
Networking Concepts – Eric
Vanderburg ©2005

17. Messaging








Oscar – AIM protocol, now used for ICQ also, direct
connections do not go through AIM servers
File sharing services often have chat (Napster, Direct
Connect, eDonkey, ect..)
IRC – primarily for group chats, oldest (1989)
Jabber – Uses TCP & XML, email-like names used.
Can use other services also:
username@aim.jabber.org
Novell GroupWise Manager – uses SSL
Lotus Sametime
XMPP (Extensible Messaging & Presence Protocol)
SIMPLE (*SIP for Instant Messaging & Presence
Leveraging Extensions)
Networking
*SIP - Session Initiation Protocol Concepts – Eric
Vanderburg ©2005

18. Scheduling & Groupware
 Scheduling
 Calendars
 Integrated
into other programs
 Groupware
 Many
users collaborate on a single file
 Novell GroupWise
 Lotus Notes
 Microsoft SharePoint
Networking Concepts – Eric
Vanderburg ©2005