Networking Final Project
This is going to be 2/3 of your final test grade, which is 60% of your overall grade for the Semester. Please note:
F Written
portfolio and drawings, implementation on your LAN: 20% Note that this is REQUIRED to get the
English Cross Credit in this class.
F Benchmarks:
60%
F Written
test: 20%
Read
the case study below and do the following:
1. Design a network topology that answers all of the needs of the customer. Create a network portfolio to present to the customer. This portfolio should include all of the following:
a. A cover page with your company name and logo on it.
b. An outline of the needs of your customer with your solution to meeting those needs.
c. A network drawing with all components properly labeled, including
i. Cabling
ii. Speed
iii. Servers (label the role of each server)
iv. Hardware
v. Topologies; logical and physical
d. A spreadsheet of prices of:
i. Hardware
ii. Cabling
iii. Servers
iv. Client access licenses for all versions of Windows 2003 Server and Windows XP Professional Workstation
v. CALs for Terminal Services use
vi. CALs for all workstations
vii. Internet access
viii. Domain name purchase/lease
e. A proposal for the setup of user accounts, groups, and organizational units.
i. A description of the proposed username syntax.
ii. A list of groups created for the network.
iii. A list of organizational units created for the network.
f. Group policies to be implemented within the domain—A complete list.
g. Set up the Active Directory structure within your virtual server.
When
you have made all of these decisions you must create a network together with
your partners that emulates the network you are designing. While you may work
together on all parts of this project, each student MUST turn in a portfolio
that is their own work and completely separate from every other student, no
exceptions.
Grammar, punctuation, and spelling do count on this. You are proposing this project to a CUSTOMER. Make it look and sound good. It must be ENTIRELY your own work.
Case Study
Background
The Sno Isle Skills Center is a
The
Building
One houses:
C
Computers,
Servers, and Network—A high tech program for students interested in careers in
IT
o
24 lab
computers
o
24
production computers
o
5
servers Server 2008
§ 2 Active Directory servers
§ 1 Server that houses DHCP and WINS
§ 1 Dfs Server that houses files that are
spread out across all 5 servers, this also acts as the file server
o
Two
networks
§ 192.168.1.0
§ 10.25.0.0
·
Subnetted
to 255.255.0.0
·
This is
the ENTIRE staff network on this site.
o
One
teachers station
o
One
demonstration station
C
Computer
Web Programming—A program for students who are interested in careers in
programming and webpage design
o
26 lab
computers
o
1
Demonstration Station
o
1
Teachers station
o
1 file
server
o
2
printers
o
Two
networks
§ 192.168.4.0
§ 10.25.0.0
·
Subnetted
to 255.255.0.0
·
This is
the ENTIRE staff network on this site.
C
Server
Room for Sno Isle
o
3
student servers
§ Sitech1—Active Directory
§ Sitech2—Backup AD
§ Sicad—Runs programs for the Precision
machining program
·
Mastercam
·
Solidworks
·
Both
programs require a dongle that activates the hasp. The dongles are USB and look
like flash drives
o
1 Staff
Server
§ Snoisland
§ File server for on-site staff
C
Medical
Assisting
o
24 lab
computers
o
1
demonstration station
o
1
teachers station
o
3
Printers
§ 1 teacher
§ 1 color laser
§ 1 regular laser
C
Robotics
o
24 lab
computers
o
1
demonstration station
o
1
teachers station
C
Nurses
assisting
o
8 lab
computers
o
1
teachers station
o
2
printers
C
Dental
assisting
o
1
teachers station
o
1 laptop
for demonstration
o
24 lab
computers
o
2
printers
o
1 laptop
that interfaces with DEXA X-Ray Machine
C
o
8 lab
computers
o
1
teachers station
C
Testing
center
o
1
administrative computer
o
2
testing computers
o
Prints
to printer in study center
C
Administration
o
Six
administration computers
o
3 mobile
laptop/projector stations
o
1
printer for each station
Building
Two houses:
C
Precision
Machining
o
24 lab
computers
o
1 file
server
o
Hardware
that uses Mastercam and Solidworks
o
Must
retain connection to SICAD
o
2
printers
C
Diesel
Mechanics and Auto Technology
o
These
programs share 24 student computers
o
5
Netbooks
o
Wireless
network
o
3
teachers stations
o
3
printers
Building
Three Houses
C
Construction
Trades
o
1
teacher computer
o
1 teacher
laptop
o
4
student laptops
o
1
printer
C
Fire
Technology
o
12
student computers
o
1
demonstration station
o
1
teacher station
o
2
printers
Building
Seven Houses
C
Fashion
Merchandising
o
8
student computers
o
1
teachers station
o
1 custom
embroidery machine that interfaces with one computer
o
2
printers
C
Veterinary
Technician
o
1
teacher computer
o
6
student computers
o
2
printers
Building
One in 2009 sustained irreparable damage in a devastating fire. They lost all
of their equipment as well as all media. They have now rebuilt and are moving
everything back to the rebuilt buildings. They have hired YOU to set up the
network. Where do you start?
Existing IT Overview
All buildings were wired
using three T1s to communicate among them. The building that burned contained
the main trunk for phones and data. Data and phone have been restored via on
site tech staff and Verizon.
Client/Server LAN Environment
There are two discreet
networks on campus; Sno.tech and Si.tech. There were three servers that served
sno.tech; sitech1, sitech2, and sicad. There is one server that serves si.tech;
snoisland.
We
currently have one server at West Campus and one at Main. Both will need to be
relocated to the server room at main which will be in building one. The server
room and wiring closet is currently in building two.
You
will need to decide on and install needed services such as DNS, WINS, AD, DHCP,
Dfs, etc.
Applications
The new computers will all
run Office 2007, deployed via Group Policy. Other software is needed in
different classrooms. You will need to determine what software will be needed.
Using
a DFS structure on the student side, set up shares to handle things like
commonly needed software, and other shares that you determine.
INTERVIEW DISPLACED TEACHER
I got lots of new computers
this year, but they all need to be moved and we need to make sure they all work
by the first day of school. Can you ensure this? How?
Also
we, apparently, lost ALL of the student data. There was a backup plan, but the
backups burned up! What can we do in case something like this happens again? Do
we have a new backup plan?
The
old network was slow. Can we get a faster network?
IT Manager
I am running around like a chicken with my head cut off. Everyone wants to
have everything five minutes ago, and I can’t get much completed due to the
interruptions.
I
need your help with “triage” of all the tasks that need to be done to rebuild.
Please present to my staff a timeline of when things will get done and in what
priority.
Office
staff will be moving from portables into offices in building one. They are
going to need all of the following done:
·
Installing
software
·
Installing
printers
·
Fixing
individual student computer needs in a working lab (one or two bad computers)
·
Recreating
the domain structure
·
Rejoining
computers to the domain from the buildings not affected
·
Setting
up student stations from affected classes
o
Which
classes need their computers first and why
o
Which
classes can wait a little and why
·
Setting
up staff machines for communication and required reporting
·
New IP
structure or old?
·
Recreating
student accounts…do we do all of them, some for some classrooms and individual
accounts for others? How do we do this as quickly as possible?
·
Updating
Windows on all machines without taking the network to a crawl
USER
Network seems very slow at times. Sometimes it takes several minutes to find a
resource such as a file or a printer. Locating servers on the network is also a
very slow process especially during the morning hours. The best part is when
the network goes completely down. At that point we just fire up solitaire…
School Network Vision: General Requirements
All network services must
provide redundancy for fault tolerance. A single protocol must be used in the
client/server network. This protocol must be scalable enough to meet any
anticipated growth.
All buildings need to be networked together; however network traffic must be
minimized between building 1 and building 2 due to the slow coaxial backbone
between the buildings until new cabling is laid, which will happen in July. The
inside also needs cabling. What should we go with to maximize bandwidth without
compromising a school b udget?
All
computers need to be moved and set up in the classrooms in building 1. Building
2 has Robotics, Police, and math setup already, but the rest of the courses
will need to be set up.
All
teachers will have client computers that are running Windows XP. Windows 7 is
going to be tested in the early Fall and hopefully we’ll put it in the entire
school by semester.
Sometimes
we have guests come who need to use the computers. Set up a plan so they can
use Study Center computers without compromising the security of our network,
using a simple login.
Because
in a school, student data is confidential any remote access traffic must be
secure and only authorized users must be allowed to dial in. The strongest
possible encryption must be used for all connections.
Internet access is a must, but data must be filtered. We need a hardware
solution for this. Is there a gateway that would work?
All
workstations (except the four in manufacturing) should be updated to Windows 7 by semester. All servers should be updated
to Windows 2008 Server. All new hardware will be a MINIMUM of 64 bit dual core
processors. What specs should we get all those computers?
Switches
and routers will be GB capable, but older ones may still be only 100 Mbps.
Existing
computers range from Pentinum III with 512 MB RAM to Pentium IV with 1 GB of
RAM. They are running Windows XP Workstation with all service packs applied.
Build in suggestions for future upgrades.
They
must have an Active Directory structure set up that allows them to secure their
student records, and control the access of their users. They would like the
domain organized in a reasonable fashion that allows the users access only to
things they need.
Restrictions
The backbone between buildings 1 and 2 is gone. The backbone between 2 and
3 is old, but stable. It cannot be replaced at this time, but we’d like it
replaced down the line.
Workstation
access to servers must be fault tolerant.
A
budget has been allowed for new equipment; at most 2 servers.
A
budget has been allowed for new software.
Enough money is available to upgrade existing OS on all systems. All licensing
requirements must be met. Be sure to include the cost of OS licenses and Client
Access Licenses (CALs).
One
of the remote locations that the school is looking at uses Novell Netware as
their network operating system. Connectivity between the Sno Isle computers and
the Novell network must take place at some point. Demonstrate how this could
occur using a software solution (free).
Anticipated growth
As much as 50% over the next 5 years with growth in students and personnel
as programs are added. The programs to be added will require at least two full
computer labs.
The physical location is growing slightly as building one will be complete in
July. The new programs include:
·
Airplane
Technician (8 lab computers, one teacher station)
·
Two more
classes in
o
Medical
Assisting (28 lab stations, one teacher station)
o
Fire
Safety (10 lab computers, one teacher station)
·
Digipen
Programming (28 lab computers, one demo station, one teacher station)
·
Autobody
Collision Repair (10 lab computers, 5 netbooks, one teacher station)
·
Each
program must have a printer available to both teacher and students, but
remember they are on separate subnets.
·
You
choose laptops/netbooks/desktops and justify the choice.
Create
a project plan to deal with all of the company needs and be prepared to present
it to the company within two weeks.
Network Setups
Create
a network that emulates the company layout. Each building will be its own
domain in one tree. Each domain should be on a separate subnet.
Set up the following in your networks:
F
RRAS
with a VPN
F
Active Directory
(one in each domain with replication among the domains)
F
DHCP
(one in each domain)
F
WINS
(one in each domain)
Also
set up all policies, create 25 users in each domain. Create all groups and organizational units. Assign permissions
to folders within the domain.
When
both domains are set up and completed, create a TRUST relationship between your
two domains. It should be a non-transitive trust so that Sno.Tech trusts Si.Tech,
but not the other way around.
Create
a global group in Si.Tech that will allow users to access a folder named “Staff
Lounge Secrets” in the Sno.Tech domain. Create a domain local group within Sno.Tech
that will contain that global group. Assign permissions appropriately.
(Remember Microsoft’s rule.)
See your benchmarks sheet for all of the
requirements of this final!
New Stuff
Wow, there is new
stuff on this project! That’s odd…well actually it isn’t. Often you are called
upon to implement a new technology that you’ve not worked with before.
However in the
interest of time, I’m going to give you resources for installing these services
and the purpose of them.
|
Service |
Purpose |
Installation
Instructions |
|
Routing and Remote Access |
RRAS is a service
that allows you to set up your server as a proxy server to connect to the
Internet, as a software router, or setting up a VPN. |
|
|
Configure a VPN Client |
Allows your
workstation to load into your VPN through the Internet. |
Take the following
steps to configure a Virtual Private Network (VPN) client:
|
|
Set disk quotas |
When you have a
large network you want to limit the amount of hard drive space the users use
on your server. |
Take the following steps to apply disk quota limit:
|
|
Create a baseline using system monitor |
A baseline is how
your computer is running when you first set it up. A good administrator will
test a computer when setting it up, then test it periodically as part of
his/her normal routine. |
Take the following
steps to create a baseline report:
|
|
Creating a Non-Transitive Trust |
|
1.
With the administrator of the
other domain, agree on a secure channel password to be used in establishing
the trust. (Since you’re the administrator in both domains, talk to yourself
and agree. No arguing.) 2.
In the first domain, log on as
a member of Domain Administrators. 3.
In Active Directory Domains and
Trusts, expand your domain, and then right-click your domain (aka
teechur.com. 4.
Click Properties, and then click
the Trusts tab. 5.
Next to the Domains trusted by this domain box, click Add. 6.
In the Trusted domain box, type the trusted domain name.
If you are adding a Windows 2000 domain, type the full DNS name (teechur.com in this example). 7.
In the Password box, type the agreed-upon password. 8.
In the Confirm password box, retype the password, and then
click OK. 9.
A message appears that says the
trust cannot be verified. Click OK. Note: The reason for this error is that Windows is attempting to
verify the secure channel. It cannot verify the secure channel at this time
because the other side of the trust is not yet created. 10.
Next to the Domains that trust this domain box, click Add. 11.
In the Trusting domain box, type the trusting domain name.
If you are adding a Windows 2000 domain, type the full DNS name. 12.
In the Password box, type the agreed-upon password. 13.
In the Confirm password box, retype the password, and then
click OK. 14.
A message appears asking if you
want to verify the trust. Click Yes. 15.
Click OK to close the Properties sheet. Note: If the trust is successfully created in
the domain, click Yes to verify the trust. If the trust is
not created, clicking Yes returns an error. When the trust is
created in your domain, the trust takes effect. You do not need to verify the
trust for the trust to take effect. |
Installing a DHCP Server
Complete this after you have installed your Active Directory and DNS Servers.
Windows 2008 uses/installs as default TCP/IP
protocol. While in a small home network it is easy to assign manually the
IP-addresses (or use the Windows98/ME
Auto-IP-configuration and / or the Windows2000
Auto-IP-configuration), you will on an office network like
to use the "comfort" of using a DHCP-server
to control and manage the distribution of IP-addresses.
Note: on the system, where the DHCP-server
is getting installed, you MUST
use a static (= manually assigned) IP-address.
·
Before
you do this lab, you’re going to make sure your host is NOT connected to the
network.
Your lab now becomes standalone. No network/Internet access, so you MUST
authenticate all OSes before doing this!
·
Give
a static IP address to your servers…both of them. They should already have them, but double
check. Do not give one to your workstation. That will get an address from your
DHCP server. If your workstation has an address, go into the TCP/IP properties
for the workstation and set it to automatically obtain IP address.
·
Write
down the IP address of your servers:
o Server Name:
o IP
o Server Name:
o IP
|
Now let’s install
DHCP. Run the Manage Your Server wizard to set up a DHCP server. m StartàProgramsàAdministrative
toolsàServer
Manager m Click on “Roles” in the left pane to add a role. In the right pane click “Add Roles”
Click next |
|
m
You will see a
list of server roles. The ones that are installed will have a check next to
them and will be greyed out. m
m
Select DHCP
server and click next. |
|
An Introduction
to DHCP will come up. Read it and answer the following questions: 1.
What does DHCP
stand for? 2.
What does it
“do”? 3.
What do you have
to have at least one of on your host computer? 4.
When should you
plan your subnets? |
|
m
Next it will ask
you what network connection to bind it to. If you have more than one network
card, choose the one that you want to answer the DHCP requests. If you only
have one, choose that one. It should say IP Address 192.168.1.x and IPV4 (IP
Version 4). |
|
m
m
Type in your
domain name. m
Type in the IP
address of your DNS server that you KNOW works. Click validate to make sure
you got it right. m
Type in the IP
address of the OTHER DNS server and validate it. |
|
m
m
Now we get to
define a scope. A scope is the IP addresses you will have available in your
network to assign to users’ computers and printers and anything that connects
to your network. You can’t pass out IP addresses until you define a scope. m
Scopes should be
planned very carefully. You don’t want to end up assigning out the IP address
of a computer that has that IP assigned to it statically! That would be bad!
So you’re going to use the following IPs on your computers. In our case we’re
just going to use the 192.168.1.0 network. Be sure your computers are
disconnected from the network, OR create a new virtual network and do NOT
bind it to your network card. m
Click Add to add
a new scope. o
Name
the Scope “HappyScope” o
Make
the starting IP address: 192.168.1.10 o
Make
the ending IP address: 192.168.1.20 o
Subnet
mask: 255.255.255.0 o
Default
Gateway: 192.168.1.1 o
Click
“Activate this Scope” o
It
is a wired lease so by default it’ll have a 6 day lease. (After six days the
IP address returns to the pool if the computer using it doesn’t request to
use it again.) o
You
can change that if needed down the road. For example, if you’re setting up
DHCP for a coffee shop with wireless, you may want a lease to be as short as
an hour. m
Click
OK and the scope gets added and activated! Activation means it can now start
sending out addresses right away. m
Click
next. |
|
m
Next
it’s going to ask you if you want to assign IPV6 addresses. Leave it in
Stateless Mode. Stateless Mode means the computer will assign itself an IPV6
address, if that protocol is installed. So go ahead and ENABLE the stateless
mode. |
|
m
Finally
you have to authenticate your DHCP in AD so that AD can tell the other
computers “Yo, the DHCP server is right here!” m
Since
you’re logged in as an administrator, go ahead and use current credentials. m
Finally!
Whew! You should get a screen that tells you what you’re about to do. Take a screen shot of this page and paste it into Paint (runàmspaint) and save it. That way if something doesn’t work
I can take a look at what you did. m
It’s
going to install. Spend some time contemplating the meaning of life, or
making modern art with belly button lint. It might take awhile. |
|
After
forever and a day you will see something that tells you DHCP has been
installed. Well it’s about doggone time! Sheesh! Like we have all day for
this kind of stuff. Oh wait, we do. The reason it takes so long is that it is
checking to make sure there are services available to fulfill this role (new
services have “dependencies” which means they often “depend” on another
service to do their job. Just like if you’re working with a partner to make a
sandwich. You might “depend” on him to lay out the bread. If he’s not there,
you can’t make the sandwich because…no bread. |
|
|
|
|
Configuring
your DHCP Server |
||
|
1.
Select DHCP from the
Administrative Tools menu. 2.
You should see that your scope you
created (HappyScope) is there. Let’s create another scope. 3.
The first thing you’ll do is define
a range of IP addresses called a scope. Your users will be assigned one of
these IP addresses when they log on. 4.
Right click on your server and
select New Scope in the drop down menu. |
||
|
|
||
|
1.
2.
Define a name for your scope. Name
it domainxx-scope. (If my domain is domain04 I would name my scope
domain05-scope.) 3.
Give it a happy description. |
||
|
4.
Click next. Define a range of IP
addresses. You have to make sure your own static IP address is NOT in that
range or all sorts of problems will occur. 5.
Use the following syntax for ranges a.
Start IP address: 192.168.1.100 b.
End IP address: 192.168.1.200 c.
Use the subnet mask 255.255.255.0 d.
Use the DNS of your server IP. e.
Use the default gateway of your
server IP. |
||
|
|
||
|
6.
Click next. You are going to be
asked to define exclusions. These are addresses you do NOT want to give out. 7.
Let’s set an exclusion for the
following IP: 192.168.1.150. 8.
Start IP would be 192.168.1.150 and
so would End IP. 9.
Set an exclusion as well for your
servers so those addresses don’t get assigned. 10.
11.
12.
Let’s set our lease time to 2 days. |
||
|
|
||
|
13.
Click next. On the next screen you
are asked if you want to configure other DHCP options. Say yes and click
next. You need to tell the DHCP server to also assign a default gateway and
DNS server(s) addresses. 14.
Your default gateway is the same IP
address as your server. So type in the IP address of your server. Click Add.
Click next. |
||
|
|
||
|
15.
If you had more than one DNS server
or other special servers on a WAN you would want to tell the DHCP server
where those other servers are located. Since you don’t have this, leave the
next screen as is and click next. |
||
|
16.
Go ahead and configure your server
IP in the WINS server window. We’re going to install WINS next. |
||
|
17.
If you’re ready for clients to start
using your DHCP server you want to activate your scope. If not, you don’t. We
are so click Activate Scope on the next screen, then click next. |
||
|
|
||
|
18.
Is there a typo on that screen? How
odd! 19.
Anyhow, you’re done setting up your
DHCP server so on the next screen click finish! However, you are not really
done. You still have one more thing to do. You have to authorize your DNS
server. 20.
In the DHCP applet right
click on your server and select Authorize to authorize this server to
act as a DHCP server in your domain! Whew! You’re done! |
||
|
|
||
|
A
few more housekeeping items: 1.
Close DHCP and re-open it. You
should be able to click on your DHCP server and it should say “running.” 2.
Click your scope. Click the button
as indicated below. You want to tell your server to always let DNS know when
someone gets a new IP address. 3.
Click the options as shown below.
This will ensure your computers can be found by DNS, and that the DNS doesn’t
fill up with useless lookup files. |
||
|
|
||
|
4.
You have to set up your clients to
request IP addresses. a.
Leave this server running. b.
Boot up your workstation. c.
Make sure the TCP/IP v4 properties
are set to get IP address automatically. |
||
|
5.
On the workstation, open the command
prompt. 6.
Type IP config /all 7.
If your IP address starts with 169
and it says autoreconfiguration
address then something went wrong. Go back and check a few things: a.
Go into the properties of your
network card and ensure it says “Obtain IP address automagically.” b.
Go to the server and make sure there
is a green arrow on the server name. If it is red, it isn’t completely
authorized. c.
Try restarting the server. 8.
Type ipconfig /release this will
release the IP address. 9.
Type ipconfig /renew this will do
the DHCP request process and obtain an IP address. 10.
Keep working on this until your
workstation is getting an IP address from YOUR server! Remember your scope?
It must be within those numbers so if your scope was 192.168.1.5-192.168.1.20
and the IP address assigned is 192.168.5.4 then you’re getting an IP address
from someone else! 11.
Get a screen shot of your IP
address, print it out. Attach it to your lab report. Okay, now you’re REALLY done! |
||
|
Answer
the following questions by poking around your DHCP server 1.
Which IP addresses are currently
leased? 2.
What is the MAC address of the
computer that leased the first IP in the list? 3.
Right click on one of the IP address
leases and release that address. What happens? 4.
Let’s set up a reservation. Click on
reservations and add a new IP address reservation of the address that ends
with 192.168.yy.10. Now how many IP addresses do you have available for
leasing? 5.
Can you set up more than one address
scope? |
||
Installing WINS
Generally you don’t need a WINS server if your domain is all Windows 2000 or above, but just in case you have a Windows 98 floating around in there somewhere, let’s install WINS!
Let’s try a new way to install a service on Windows Server.
|
|
|
|
According to Microsoft, the default settings for the WINS server are all you need. There isn’t a lot of configuring you should do, although you can configure things if you need to. This would come with more advanced server management. That was painful wasn’t it? |
|
Make sure your
workstation is registering on WINS |
|
Start up the workstation on your partner’s computer. |
|
Make sure it is set up to obtain an IP address from your DHCP server. |
|
Make sure it is obtaining an IP address from your server by either: m Checking the DHCP server to see if that computer name is getting an IP from you m Type ipconfig /all at the workstation command prompt to make sure the IP address is obtained from the correct scope |
|
Open your WINS server (it’ll be in the administrative tools on your server). |
|
In the console tree, select Active Registrations |
|
On the Action menu select Display Records. |
|
Click find now. |
|
The entire WINS database should show and in there you should be able to find your workstation’s registration. Do a print screen of this and attach it to your lab report. |
|
How
to Create a Dfs on Server 2008
|
