80
A Vizioneer Studios Production

Implementing a network

Embed Size (px)

Citation preview

Page 1: Implementing a network

A Vizioneer Studios Production

Page 2: Implementing a network

You Will Learn:

Network Options

Network Requirement

Installing A Network Server

Page 3: Implementing a network

1. Practice active management.

2. Use managed wireless products.

3. Prioritize usage.

4. Develop a guest policy carefully.

5. Build security from the start.

Page 4: Implementing a network

One Of The First Duty Would Be Installing A Network

After All

If Zare Ez No Network

Zare Ez No Needz For You

Page 5: Implementing a network

Installing A Network Includes: Choosing The Right Type Of Network (i.e. Linux, Microsoft)

Choosing Between Peer To Peer and Client/Server n/w

Purchasing: Software Hardware

The Server NOS

Client Desktop System

Page 6: Implementing a network

By Now You Should Know The Difference Between A P2P Network and A Server Based Network

You Should Be Able To Choose Which Type Is Better Keeping Their Advantages And Disadvantages In Mind

Page 7: Implementing a network

With Peer To Peer Networks:

The advantage Is That You Don’t Need To Purchase Servers Hardware And The Network OS

On The Down Side However, The Network Is Limited To Ten Computers Max

Page 8: Implementing a network

With Server Based Networks:

You Can Use A Larger Amount Of Computers On The Network

However There Is The Cost For The Server And It’s OS

Also You’d Need To Purchase A Client Access License

Page 9: Implementing a network

A Client Access License Is Needed To Allow Your Clients To Connect To The NWOS

Note Though, A CAL Is Needed For Each Client That Is Connected To The Network

Page 10: Implementing a network

MS Networking

When It Comes TO Networking, MS Networks Have A Big Market Share.

The Most Popular Server Being MS Server `03

But MS Server `08 Is The Latest.

Page 11: Implementing a network

MS Networking

When installing A MS Server You Have A Number Of Choices To Make. Such As: Installing It As A Stand Alone Server

Installing It As A Domain Controller

Installing It As A Member Server

Page 12: Implementing a network

A Standalone Server Is One That Has A Local Secure Accounts Manager database (SAM database) Similar To That Of A WinXP System.

The SAM Database Is A Database Of Accounts That Resides On The Local System.

Its Used To Access Resources Only On The Local System

Page 13: Implementing a network

A Domain Controller (DC) Is A Server That Has Active Directory (MS Directory Service) Installed.

The Active Directory Database Allows You To Access Resources Across The Network.

Along With Dc Are 3 Terms That Must Be Known: Domain Tree Forest

Page 14: Implementing a network

A Domain Is A Logical Grouping Of Computers And Resources.

Its A Security Boundary And A Replication Boundary.

Page 15: Implementing a network

Trees Are A Hierarchy Of Domains That Have A Contiguous DNS Namespace.

Example A Domain May Have A Child Domain For Certain Areas That Connects To It

CCGDT

Public Library

College Library

Page 16: Implementing a network

A Forest Is Just A Collection Of One Or More Trees.

CCGDT

Public Library

College Library

Lime

Public Library

College Library

Page 17: Implementing a network

A Member Server Is A Machine That Is Part Of A Domain, Or A Member Of The Domain While Being A Resource To Other Computers.

Page 18: Implementing a network

Novell’s Directory Service Is Currently Called “Edirectory” Is Similar To Active Directory In That It Is A Database Of Network Accounts That Is Automatically Synchronized With Other Servers.

One Or More Netware Servers Sharing The Same Edirectory Database Is Called An Edirectory Tree.

Page 19: Implementing a network

One Major Benefits Of Edirectory Is That You Are Not Limited To Installing It On Netware Servers.

It Can Be Installed On Netware Servers, Windows Servers And Unix & Linux Servers!

The Updated Version Netware 6.5 Includes DirxmlDrivers Which Gives You The Freedom Of Synchronizing User Information With Any Other Type Of Directory Service

Page 20: Implementing a network

But Novell Had Been On The Constant Move In Terms Of Progress.

As A Result Of Their Progress, They’ve Changed Their Names A Few Times.

Page 21: Implementing a network

The First Name Was Bindery.

Bindery Was Bout During Netware 2.X And

With Bindery, The Network Account Database Is Stored On Each Server

The Down Side However Was That It Was Not Synchronized With Any Other Servers

Page 22: Implementing a network

Next Came Novell Directory Services.

NDS Came About For NetWare 4.x and 5.x

This Update Repair The synchronization between servers Deficiency.

Page 23: Implementing a network

Finally There Is eDirectory.

NDS Lacked Sufficient Storage And eD Gave Them That Storage.

eD supports efficient storage of billions of objects

As A Result almost every aspect of Novell environment configurations is stored in eDirectory.

Page 24: Implementing a network

Linux Is Starting To Command A Lot Of Attention In The IT Industry Because Of Its Reliability And Its Secure Architecture

Linux (And UNIX) Environments Can Store User Account Information In Files

For Example: /Etc/Passwd Holds User Account Information

/Etc/Shadow Holds Encrypted User Passwords, And /Etc/Group Holds Group Membership Information)

Page 25: Implementing a network

Networking Hardware

Page 26: Implementing a network

The First Thing That You Will Need Is Hardware.

In Each Of The Systems Or Hosts That Will Participate On The Network A Network Interface Card Is Mandatory.

Page 27: Implementing a network

You Will Also Need To Have:

A Hub Or A Switch (This Act As A Central Connection Point For All The Systems.)

Router (This Aids In Sending Data To Another Network)

More Than 1GB RAM

Multiple CPUs On The Motherboard (Optional)

Page 28: Implementing a network

It Is Extremely Important To Understand What The Network’s Software Requirements Are.

There Are Four Software Components You Will Certainly Need Somewhere On The Network.

Page 29: Implementing a network

Service

A Service Is Typically The Reason For The Network

It Is What Is Being Provided To Clients On The Network

For Example, File And Printer Sharing Services,

Even Web Services

Page 30: Implementing a network

Client

A Client Is A Piece Of Software That Connects To The Service And Makes The Network Request.

For Example A Web Browser (Client) Makes

Requests To A Web Server (Service) For Different Web Pages On The Web Server.

Page 31: Implementing a network

Protocol

A Protocol Is The Networking Language That A System Uses To Send The Request From The Client To The Service.

If You Want Two Systems To Communicate, They Will Obviously Need To Speak The Same Language (Protocol),

Page 32: Implementing a network

Network Card Driver

Without The Network Card Driver, The NC Is Just A Thing Sitting In Your Motherboard

In Order For All Of This To Work, You Will Need To Make

Sure That The Network Card Driver Has Been Installed On The System

This Is The Only Way That That The System Can Send And Receive Data

Page 33: Implementing a network

The Theory Before You Install

Page 34: Implementing a network

Server Name

You Will Need To Decide What The Name Of The Server Will Be Because Clients Will Connect To The Server By Name When Accessing Folders And Printers.

Page 35: Implementing a network

Domain Name

If Your Server Will Be Joining A Domain, You Will Need To Type In The Name Of The Domain.

Also If You Are Joining A Domain, You Will Also Need To Know The Username And Password Of The Administrator Account That Has Permission To Add Servers To The Domain.

Page 36: Implementing a network

Server As Domain Controller

You Will Need To Know Before You Start The Installation Whether Or Not The Server Will Be A Domain Controller.

If The Server Is To Be A Domain Controller, You Will Need To Install It As A Standalone Server And Then Run dcpromo.exe To Promote It To A Domain Controller

Page 37: Implementing a network

Hardware Support

Make Sure That Your Server Hardware (Network Card, Video Card, And What’s Now) Will Work With The Server Operating System By Checking Out The Windows Server Catalog.

The Link Is Usually

Http://Windowsservercatalog.Com/

Page 38: Implementing a network

http://windowsservercatalog.com/

Page 39: Implementing a network

Partition Setup

Plan Your Partition Strategy Before The Installation So That You Are Prepared.

During The Installation, You Will Have The Opportunity To Create And Delete The Partitions On The Hard Disk Of The Server.

Plan Carefully

Page 40: Implementing a network

File System

After Partitioning The Disk, You Will Need To Format The Partition With A File System Such As FAT32 (File Allocation Table) Or NTFS (New Tech File System).

For The Best Security It Is Advised That You Should Always Go With The NTFS File System On Microsoft Servers

Page 41: Implementing a network

Licensing

When Installing A Windows Server, You Will Have To Choose Either Per Seat Or Per Server Licensing.

With Per Server Licensing, You Obtain

A Client Access License (CAL) For Each Connection To The Server.

With Per Seat Licensing, You Purchase A License For

Each Individual Client That Will Access The Server

Page 42: Implementing a network

With Installation There Are Two Phases To The Installation Process:

The First Is The Text-mode Portion Of The Installation, Where You Partition The Disk And Format The Partition. Then The Setup Files Are Copied From The CD-ROM To The Hard Drive.

Page 43: Implementing a network

The Second Is The GUI-mode Portion Of The Installation Will Ask For Information Such As Your Product Key Computer Name, And Administrator

Password.

Page 44: Implementing a network

The 30 Steps Guide (Steps 1-17)

Page 45: Implementing a network

1. Place Your Windows Server 2003 CD In The Drive And Then Power On The Computer.

Page 46: Implementing a network

2. After Some Setup Files Are Copied To The System, The Welcome To Setup Screen. To Install Windows Server 2003, Press Enter

Page 47: Implementing a network

3. Press F8 To Agree To The License Agreement.

Page 48: Implementing a network

4. You Will Be Shown A List Of Drives And Partitions On Which Windows Server 2003 Can Be Installed Make Sure That The First Drive Is Selected. Choose C To Create A Partition

Page 49: Implementing a network

5. Type 15000 MB As The Partition Size (Or What Ever The Limitations On Your System Is) And Press Enter.

Page 50: Implementing a network

6. The newly created partition is displayed; select it and press enter to install the OS to that partition.

Page 51: Implementing a network

You Will Now Format (Quick) The Partition For NTFS By Selecting The Option Shown And Pressing Enter.

Page 52: Implementing a network

8. The partition is formatted, and setup files are copied to the hard disk. After that, the GUI portion of the installation starts and installs Windows.

9. Select Next to accept the English language.

Page 53: Implementing a network

10. Type your name and organization as shown and then choose Next.

Page 54: Implementing a network

11. Type your product key and then choose Next.

Page 55: Implementing a network

12. Choose to have 100 Per Server licenses and choose Next. This 100 means that it will allow for 100 clients to connect to the server at one time.

Page 56: Implementing a network

13. Choose A Name For Your Computer Name And A Password.

Click Next.

14. Choose Your Time Zone And Click Next.

15. Choose Typical For The Network Settings And Click Next.

16. Choose No To Being Part Of A Domain And Choose Next.

Page 57: Implementing a network

17. Setup Finishes, And Then You Are Presented With The Windows Logon Screen. Log On As Administrator, Type A Password And Click OK.

Page 58: Implementing a network

The 30 Steps Guide (Steps 18-30)

Page 59: Implementing a network

18. You Will Now Install Active Directory On This System By Running Dcpromo.Exe. Select Start Then Run And Then Type Dcpromo. Click OK.

19. At This The Active Directory Installation Wizard Begins; Click Next.

20. Click Next On The Operating System Compatibility Screen.

Page 60: Implementing a network

21. Choose Domain Controller For A New Domain and choose Next.

Page 61: Implementing a network

22. Choose Domain In A New Forest and choose Next.

23. Type the DNS name for the new domain (eg. I have used glensworld.loc) and then choose Next.

Page 62: Implementing a network

24. Choose Next To Accept The NetBIOS Name.

25. Choose Next To Accept The Location Of The Active Directory Database Files.

26. Choose Next To Accept The Location Of The sysvolFolder, Which Is Where Policies Are Stored.

Page 63: Implementing a network

27. Accept the default choice to install DNS on this system and choose Next.

Page 64: Implementing a network

28. Choose Next On The Permission Compatibility Screen.

29. Type A Password For The Directory Service Restore Password. This Is Used To Restore Active Directory.

30. Click Next On The Summary Screen. Active Directory Installs On Your System.

Click Finish When It Has Completed; You Will Then Need To Reboot.

Page 65: Implementing a network
Page 66: Implementing a network

Wi-fi Networks Don’t Stay In Top Condition On Their Own.

The Inevitable Moving, Additions And Changes Of People, Furniture And Everything Else Within An Organization Will Cause The Network To Degrade Over Time.

As A Result Providing Less-than-optimum Service To Users.

Page 67: Implementing a network

Wi-fi Networks Are Amazingly Fault-tolerant.

They Can Survive The Loss Of Access Points And The Addition Of Interference Without Registering Significantly Perceptible Effects.

Page 68: Implementing a network

That Being Said Though, Problems Might Go Unnoticed Without Active Monitoring.

Good Network Management Practices, Including The Regular Scanning Of Logs And The Active Monitoring Of Devices And Usage.

Page 69: Implementing a network

Airespace, Aruba and Trapeze developed technology that treated the entire wireless network as a single entity, rather than as a series of individual APs (Access Points)

Thus was born the fully managed wireless solution.

Page 70: Implementing a network

The Technology Today Can Handle Issues Such As: Mobility,

Keeping An IP Address And Connection Alive While A User On A VoIP Call Walks Between Rooms, Floors And Even Buildings.

Page 71: Implementing a network

It Is Important Though That The Network Team Should Be Careful To Distinguish Between Fully Managed Solutions And Those That Only Offer Configuration Control And Log Collection.

Simply Capturing The Configurations Of Each Ap And Pushing Changes To Them Uniformly Is Not True Wireless Management.

Page 72: Implementing a network

In The First Few Days After A Network Is Turned On, The Smartphones Of At Least 10 To 20 Percent Of The People In The Building Will Connect Automatically.

These Devices Will Consume Bandwidth Even When No One Is Using Them.

Page 73: Implementing a network

If The Building Is On A High School Or College Campus, That Figure Will Be Closer To 80 To 90 Percent.

In Other Words, A Wireless Network Can Reach Near Capacity Even When No One Is Actively Using It.

Page 74: Implementing a network

The Solution Isn’t To Prohibit Casual Use, But Simply To Make Sure That Mission-critical Applications

By Using Management Configuration, Firewalls Or Wi-Fi Multimedia (WMM), It’s Possible To Throttle Bandwidth.

Page 75: Implementing a network

Accommodating Guest Access To Wireless Networks Is Generally Considered A Requirement For Enterprise Wireless Installations.

Guests Commonly Have A Legitimate Need To Connect To The Internet While Visiting An Organization

Page 76: Implementing a network

Therefore Guest Policy Must Balance Its Requirements For Accountability And Prevention Of “Drive-by” Connections.

The Entire Goal Should Be To Make Guest Connections Simple And Quick.

Page 77: Implementing a network

Security Managers Tend To Be Fairly Suspicious Of Wireless Networks.

If User Credentials Are All That Is Required To Connect, Then Confidential Info Would Only Be A Stolen Set Of Credentials Away

Page 78: Implementing a network

While Many Techniques Exist To Increase Overall Security For Wireless Users, It Pays To Have The Organization’s Security Teams Involved From The Beginning.

Doing So Will Make It Possible To Incorporate Their Requirements Into The Architecture Design And Product Selection Phases Of The Project.

Page 79: Implementing a network

CompTIA Network+ Certification Study Guide 4th Ed.

EDTech http://www.edtechmagazine.com

Page 80: Implementing a network