22. NT, UNIX and Novell NetWare

Slides:



Advertisements
Similar presentations
Chapter 7 LAN Operating Systems LAN Software Software Compatibility Network Operating System (NOP) Architecture NOP Functions NOP Trends.
Advertisements

1 Linux Networking and Security Chapter 2. 2 Configuring Basic Networking Describe how networking devices differ from other Linux devices Configure Linux.
Active Directory: Final Solution to Enterprise System Integration
Networks Adapting Computers to Telecommunications Media.
Linux+ Guide to Linux Certification, Second Edition Chapter 14 Network Configuration.
Network+ Guide to Networks, Fourth Edition Chapter 10 Netware-Based Networking.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
Understanding Networks I. Objectives Compare client and network operating systems Learn about local area network technologies, including Ethernet, Token.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
Chapter 12 Reading assignment n From “Running Linux”, on reserve at PSU Main library (2-hour checkout) Chapter 1 (pages 1 through 41)Chapter 1 (pages 1.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 1: Introduction to Windows Server 2003.
A centralized system.  Active Directory is Microsoft's trademarked directory service, an integral part of the Windows architecture. Like other directory.
Securing Access in a Heterogeneous Network Environment Providing Interoperability between Microsoft Windows 2000 and Heterogeneous Networks Securing Authentication.
1.  A protocol is a set of rules that governs the communications between computers on a network.  Functions of protocols:  Addressing  Data Packet.
Introduction to Networks Networking Concepts IST-200 VWCC 1.
1 Chapter Overview Understanding the Windows 2000 Networking Architecture Using Microsoft Management Console.
Directory services Unit objectives
INTRODUCING MICROSOFT WINDOWS SERVER 2003
BASIC NETWORK CONCEPTS (PART 6). Network Operating Systems NNow that you have a general idea of the network topologies, cable types, and network architectures,
1 Chapter Overview Network Operating Systems Network Clients Directory Services.
CHAPTER Protocols and IEEE Standards. Chapter Objectives Discuss different protocols pertaining to communications and networking.
1 Guide to Novell NetWare 6.0 Network Administration Chapter 13.
INSTALLING MICROSOFT EXCHANGE SERVER 2003 CLUSTERS AND FRONT-END AND BACK ‑ END SERVERS Chapter 4.
Microsoft Active Directory(AD) A presentation by Robert, Jasmine, Val and Scott IMT546 December 11, 2004.
2002 Networking Operating Systems (CO32010) 1. Operating Systems 2. Processes and scheduling 3.
COMP1321 Digital Infrastructure Richard Henson February 2014.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 1: Introduction to Windows Server 2003.
Linux+ Guide to Linux Certification Chapter Fifteen Linux Networking.
Chapter Two Defining Network Objects. Chapter Objectives Describe how a workstation communicates with the network, and list the software components required.
Linux+ Guide to Linux Certification, Second Edition Chapter 14 Network Configuration.
1 Windows 2008 Configuring Server Roles and Services.
OS Services And Networking Support Juan Wang Qi Pan Department of Computer Science Southeastern University August 1999.
© Wiley Inc All Rights Reserved. MCSE: Windows Server 2003 Active Directory Planning, Implementation, and Maintenance Study Guide, Second Edition.
1 Linux Networking and Security Chapter 5. 2 Configuring File Sharing Services Configure an FTP server for anonymous or regular users Set up NFS file.
1 Chapter Overview Network Communications The OSI Reference Model.
1 Chapter Overview Network Communications The OSI Reference Model.
Network protocols –Nodes of a network must obey some rules if they want to communicate with each other. The set of rules is called network protocol. –The.
Network Infrastructure Microsoft Windows 2003 Network Infrastructure MCSE Study Guide for Exam
17 Establishing Dial-up Connection to the Internet Using Windows 9x 1.Install and configure the modem 2.Configure Dial-Up Adapter 3.Configure Dial-Up Networking.
Introduction to Active Directory
1 Active Directory Service in Windows 2000 Li Yang SID: November 2000.
Active Directory. Computers in organizations Computers are linked together for communication and sharing of resources There is always a need to administer.
1 CEG 2400 Fall 2012 eDirectory – Directory Service.
LO2 Understand the key components used in networking.
COMP1321 Digital Infrastructure Richard Henson March 2016.
Some Network Commands n Some useful network commands –ping –finger –nslookup –tracert –ipconfig.
Application Layer Functionality and Protocols Abdul Hadi Alaidi
Introduction to Operating Systems
Network Communications Technology
Microsoft enterprise concepts
File System Implementation
Application Layer Honolulu Community College
Introduction to Operating Systems
What the OSI Protocol Layers Do
Lec 2: Protocols.
(ITI310) SESSIONS 6-7-8: Active Directory.
Using MIS 2e Chapter 6 Appendix
Objectives Differentiate between the different editions of Windows Server 2003 Explain Windows Server 2003 network models and server roles Identify concepts.
Lecture 6: TCP/IP Networking By: Adal Alashban
Chapter 3: Windows7 Part 4.
Networks Software.
An Introduction to Computer Networking
Computing Over Distance
Course Name : Network Operating System Course Code: CNET 332 These slides are only meant for course delivery. For all your Exams refer to your text book.
A Network Operating System Edited By Maysoon AlDuwais
Windows Server Administration Fundamentals
Course Name : Network Operating System Course Code: CNET 332
Cengage Learning: Computer Networking from LANs to WANs
Instructor: Mort Anvari
Objectives: 1.Identify different internet protocol (IP) 2.Configure sample of IP address 3.Appreciate and relate protocol in our life.
Presentation transcript:

22. NT, UNIX and Novell NetWare

Domain (my_d) Local audit policy Success Failure • User login/logout ü File and object access ´ Use of user rights User and group management Security policy changes Restart/shutdown Process tracking \\bills_ pc \\ freds _ \\server1 Domain audit policy Success Failure etc

UNIX file attributes

UNIX TCP/IP for its communications. NFS for mounting files over a network. ICMP (for ping, traceroute, and so on). RIP (for routing). ARP (for determination of MAC addresses). DNS (for determining domain names). BOOTP (for IP address allocation). FTP (for file transfer). TELNET (for remote login). NIS (for creating domains). RPC (for remote processing execution). SMTP (for e-mail). SNMP (for network management)

Transport Driver Interface (TDI) Application Presentation Session Transport Network Data link Physical NetWare (SPX/IPX) UNIX/ Internet (TCP/IP) Windows (NetBEUI) Media Access Control Ethernet/ ATM/ ISDN/ etc. Application program Network Device Interface Specification (NDIS) NDIS Wrapper NDIS NIC Driver NIC

Application programs NetWare shell (NETx) NCP (network core protocol) software SPX/IPX ODI (open data-link interface) NetWare client: Windows NT, Windows 3.1, Unix, OS/2, Mac or DOS NIC (network interface card) hardware server

Problems with Novell NetWare 3 It uses SPX/IPX which is incompatible with TCP/IP traffic. It is difficult to synchronize servers with user information. The file structure is local to individual servers. Server architecture is flat and cannot be organized into a hierarchical structure (Bindery services).

NDS Hierarchical server structure. Network-wide users and groups. Global objects. NDS integrates users, groups, printers, servers, volumes and other physical resources into a hierarchical tree structure. System-wide login with a single password. This allows users to access resources which are connected to remote servers. NDS processes logins between NetWare 3.1 and NetWare 4/5 servers, if the login names and passwords are the same. Supports distributed file system.

NDS (cont.) Synchronization services. NDS allows for directory synchronization, which allows directories to be mirrored on different partitions or different servers. This provides increased reliability in that if a server develops a fault then the files on that server can be replicated by another server. Standardized organizational structure for applications, printers, servers and services. This provides a common structure across different organizations. It integrates most of the administrative tasks in Windows-based NWADMIN.EXE program. It is a truly distributed system where the directory information can be distributed around the tree. Support for NFS server for UNIX resources. Multiple login scripts, as opposed to system and user login scripts in NetWare 3.1. Windows NT support.

Organization Electrical Mechanical Production Administration BINS/VOL1 Q_LASER CD_DISK SYS/VOL2 Container objects Root

[ROOT]. This is the top level of the tree [ROOT]. This is the top level of the tree. The top of the NDS tree is the [ROOT] object. C=Country. This object can be used, or not, to represent different countries, typically where an organization is distributed over two or more countries. If it is used then it must be placed below the [ROOT] object. NDS normally does not use the Country object and uses the Organization Unit to define the geographically located sites, such as SALES_UK.[ROOT], SALES_USA.[ROOT], and so on. L=Locality. This object defines locations within other objects, and identifies network portions. The Country and Locality objects are included in the X.500 specification, but they are not normally used, because many NetWare 4 utilities do not recognize it. When used, it must be placed below the [Root] object, Country object, Organization object, or Organizational Unit object.

Leaf Objects (CN - Common Name) Apart from the container objects (C, O, OU, and so on) there are leaf objects. These are assigned a CN (for Common Name). They include: CN=AFP Server CN=Bindery CN=Bindery Queue CN=Computer CN=Directory Map CN=Group CN=Organizational Role CN=Print Queue CN=Print Server CN=Printer CN=Profile CN=Server CN=User CN=Volume

LP=Licensed Product. This object is automatically created when a license certificate is installed. When used, it must be placed below the [Root] object, Country object, Organization object, or Organizational Unit object. O=Organization. This object represents the name of the organization, a company division or a department. Each NDS Directory tree has at least one Organization object, and it must be placed below the [Root] object (unless the tree uses the Country or Locality object). OU=Organization Unit. This object normally represents the name of the organizational unit within the organization, such as Production, Accounts, and so on. At this level, User objects can be added and a system level login script is created. It is normally placed below the Organizational object.

Primary server NIC MSL adapter Secondary server Duplexed traffic Network connections