Overview / The most commonly used NOS types and versions are Novell’s NetWare
and Open Enterprise, Microsoft’s Windows Server (most recently Windows
Server 2003), UNIX, Linux, and Apple’s Macintosh (most recently with OS
X). In many ways, these different NOSs are very similar, but they also have
striking differences. It is important that you can recognize both the
similarities and the differences and use that as part of your basis when
selecting an NOS.
During this project, you will review various NOS types along with their
characteristics and features.
Outcomes / After completing this project, you will know how to:
c compare NOS characteristics
c compare NOS features
What you’ll need / To complete this project, you will need:
c the worksheet below
Completion time / 20 minutes
Precautions / None
Grading / Part A – 1 point for each characteristic correctly identified with the
proper NOS (8 points)
Part B – 1 point for each feature correctly identified with the proper
NOS (10 points)
Part C: NOS characteristics
Below is a table with NOS types and a list of statements that describe one or more of them. Check the boxes for the letters that best describe each NOS. Each statement applies to at least one NOS. Some statements may apply to multiple NOS types.
A. Defaults to TCP/IP as a network protocol.
B. Supports bindery as a downlevel authentication method.
C. Supports NTLM as a downlevel authentication method.
D. Provides a user interface for running standard applications.
E. Deployed as a dedicated server.
F. Based on or emulates a UNIX kernel.
G. Uses a directory system to locate network objects and resources.
H. Can be downloaded, deployed, and used at no charge.
NOS / A / B / C / D / E / F / G / HNovell Netware/Open
Enterprise / X / X / X / X
Windows Server 2003 / X / X / X / X
UNIX / X
Linux / X / X / X
Mac OS X / X
Part D: NOS features
Below is a table with NOS types and a list of features. Check the boxes for the letters that best describe each NOS. Each statement applies to exactly one NOS.
A. Uses Samba to support Windows clients.
B. Uses the Open Directory system.
C. Includes NWLink protocol support.
D. Provides a management interface only.
E. Uses X Windows as GUI user interface.
F. Saves documents in PDF format as native file format.
G. Runs on SUSe Linux.
H. Native requests for services use SMB protocol requests.
I. Native support for printers and printer management uses LPD/LPR protocols.
J. Includes Keychain for password storage.
Table 9-2: NOS features
NOS / A / B / C / D / E / F / G / H / I / JNovell Open / X
Enterprise / X
Windows
Server 2003 / X / X
UNIX/Linux / X / X / X / X
Mac OS X / X / X / X / X
Project 9 B / Determining Server Placement
Overview / Windows XP Professional can be configured to support both incoming and
outgoing dial-up connections. You will want to be cautious when
configuring an incoming dial-up connection because it is an entry point to
your computer from anywhere with a phone line. This is particularly true if
your computer is connected to a network.
In this project, you will identify where to place various servers to meet
network design requirements.
Outcomes / After completing this project, you will know how to:
c identify the impact of server placement in various scenarios
c find ways to avoid or minimize network problems
What you’ll need / To complete this project, you will need:
c the worksheet below
Completion time / 30 minutes
Precautions / None
Grading / 2 points for each correct answer (32 points)
Part E: LAN configuration
The questions in Part A refer to the configuration shown in Figure 1. The network is a routed TCP/IP LAN. Some of the current network servers are shown. The servers are as follows:
• Serv1—Domain controller
• Serv2—Domain controller and DNS
• Serv3—Domain controller
• Gen1—File and print server
• Gen2—File and print server
Figure 1 shows the logical network organization. Physically, all servers are kept in the same secure room. The network supports approximately 90 hosts, including servers.
Figure 1: Routed LAN
1. The network was configured as a routed LAN without completely considering network requirements. You are considering combining the subnetworks. What is the main network characteristic that you must consider before doing this and why?
Ans: The Domains should be considered. Is there a need for three domains on one subnet? Also, I would consider the protocols that are being used on each client. If the clients use protocols that broadcast a lot, then the network could suffer from performance degradation on the LAN.
2. Other than removing the routers and physically connecting the central connection devices, what would the change require?
Ans: The addressing scheme would have to change. DNS would most likely have to be reconfigured on the clients as well.
3. What is the most likely impact on the network if Serv2 fails?
Ans: If this server failed, then the client machines would not be able to locate other clients by name due to the fact that the DNS server would be un-operational.
4. How can you minimize the potential problems?
Ans: Add another DNS server on the network in case one fails, and configure the file servers for redundancy in case one fails.
5. If you were deploying a single DHCP server for the network, where would you place it to minimize overall network traffic and why?
I would place the DHCP server within one of the DNS servers to help balance the amount of network traffic. I would also make sure that these are isolated from internet hosts.
6. What if you were deploying two DHCP servers?
In the case of two DHCP servers, I would most likely have either two dedicated servers or combine both of them with DNS serves. Again they must stay isolated from internet hosts.
Part F: Demand-dial configuration
The questions in Part B refer to the configuration shown in Figure 2. The network is a routed TCP/IP LAN. It is also configured as a Windows Active Directory domain. Some of the current network servers are shown. The servers shown are as follows:
• Serv1—Demand-dial router
• Serv2—Demand-dial router
• Serv3—Demand-dial router
• Currently, connections between each subnet are made over the public-switched telephone network (PSTN) using dial-up modems. Each server is configured with one modem. Access permissions are configured so that access to print and file servers is limited to hosts on the same subnet.
Figure 2: Demand-dial network
1. What are the biggest concerns in relation to communication between subnets?
Ans: Speed would be a major concern. Using the dial in method would mean decreased bandwidth.
2. You are planning to deploy a domain controller in each subnet. Justify this decision.
Ans: By adding a domain controller on each subnet you would decrease the amount of network traffic due to the fact that login generates a lot of traffic on its own.
3. What traffic will be required between the subnets?
Ans: The domain controllers in the other subnets would be used for fault tolerance. If one goes down then the traffic between the subnets would be for login purposes.
4. Each subnet’s NetBIOS name resolution requirements are for the local subnet only. What do you need to do to support name resolution while keeping traffic and administrative requirements to a minimum?
Ans: Implement a WINS server.
Part G: Heterogeneous network
The questions in Part C refer to the configuration shown in Figure 3. The network is a routed TCP/IP LAN. Some of the current network servers and clients are shown. The computers shown are as follows:
• Linux1—Linux file server also used as a user workstation
• Mac1—Mac OS X computer used primarily as a graphics and multimedia file server
• Mac2—Mac OS X client used for commercial art and high-resolution graphics
• Mac3—Mac OS X client used for commercial art, movies, and high-resolution graphics
• Serv1—Windows Server 2003 file, print, and intranet web server
• Serv2—Windows Server 2003 database server
• Serv3—Windows 2000 Server print server with high-resolution graphics printer
The majority of the client computers run Windows XP or Windows 2000 Professional. There are also a few Linux workstations used as client computers. The only computers that need access to Mac1 are Mac2 and Mac3. Mac2 and Mac3 also need to access Serv1. The Macintosh computers print both draft and final copies of graphics files to the printer connected to Serv3. Client computers access Serv2 using various custom database applications. All clients need access to Serv2. Linux1 supports Windows and Linux clients only.
Figure 3: Heterogeneous network
1. In order to minimize administrative overhead, what should you use as the primary NOS for this network? Why?
Ans: The primary NOS should be Windows Server 2003 because most of the clients are either XP or 2000 systems. Windows Server 2003 also supports integration with Linux and Mac.
2. What would be necessary for Linux1 to provide the necessary client support? Why?
Ans: Linux1 would need to have Samba services in order to support the Windows clients along with LDAP and Kerberos support for authentication.
3. What authentication protocol would be used based on your proposed configuration? Explain your answer.
Ans: I would use Kerberos because it is a primary component of Active Directory in Windows Server 2003.
4. What other authentication protocols, if any, would be needed?
Ans: If anything; LDAP.
5. Of the computers shown in Figure 3, what changes could you make to computer placement to reduce the traffic through the router and why?
Ans: Mac2 should be moved onto the same subnet as Mac1 and Mac3 because the only servers that need access to Mac2 are Mac 1 and Mac3. Serv2 could be moved to the same subnet as Serv1 and Serv3 because the clients need access to this for database services.
6. How would this affect the placement of Serv2, if at all?
Ans: Serv2 would now be on a separate subnet than the Mac computers. All traffic between the two would now go through the router.
Part H: Build an Enterprise network that spans 3 different cities: Los Angeles, New York, and New Mexico City. There are 1500 computers in the Corporate Los Angeles LAN, 200 computers in the New York LAN, and 350 computers in the New Mexico City LAN (all together 2050 computers in the network). Create a diagram with the following requirements:
· New York and New Mexico City require a dedicated connection to Los Angeles (Los Angeles is the Corporate Office)
· New Mexico City and New York only need to communicate one-third of the time. (hint)
· All devices need to be shown in the diagram
· Show the server room/closet of the network
· Show the old network (provided) and new network implementations such that the new system allows uninterrupted (for the most part) communication between all LAN networks
Old Network System:
Old Server Room
New Network System
New Server Room
Reference
Ciccarelli, P., Faulkner, C., Fitzgerald, J., Dennis, A., Groth, D., Skandier, T., Miller, F.,(2007). Networking Basics. New Jersey. Wiley.
IP Addresses. (n.d.). Retrieved January 12, 2010, from http://www.faqs.org/docs/linux_network/x-087-2-issues.ip-addresses.html.
Netware: Novell Network Operating System and Protocol Suite. (n.d.). Retrieved February 9, 2010, from http://www.javvin.com/protocolNetWare.html.
NOS-Network Operating System. (n.d.). Retrieved February 9, 2010, from http://compnetworking.about.com/od/softwareapplicationstools/I/bldef_nos.htm
OSI Model. (n.d.). Retrieved December 12, 2009, from http://www.vlsm-calc.net/models.php.
TCP/IP Reference Page. (n.d.). Retrieved January 5, 2010, from http://www.protocols.com/pbook/tcpip1.htm.
Type of Connections. (2007). Retrieved February 2, 2010, from http://www2.cit.cornell.edu/computer/connect/greek/conection_types.html.
Wide Area Networks (WAN). (n.d.). Retrieved February 5, 2010, from http://www.comptechdoc.org/independent/networking/cert/netwan.html.