DOCSLIB.ORG

Recent Operating System Class Notes 05 Sharing Resources March 24, 2004

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Recent Operating System Class Notes 05 Sharing Resources March 24, 2004 Recent Operating System Class notes 05 Sharing Resources March 24, 2004 Sharing folders and printers makes them available to other domain or workgroup members. Since Windows XP supports various networks and simultaneous use of multiple networking protocols, systems running other types of operating systems can share resources with other computers on the network. Windows XP support two basic types of sharing concepts: • Simple File Sharing • Classic Sharing Simple File Sharing Windows XP introduced a new concept called “simple file sharing” which removes confusion from sharing resources over a network. Therefore, simple file sharing makes sharing your resources easy, but limits your ability to configure sharing options and permissions. When you select the share option, Windows XP uses the guest account for all network logins. Classic Sharing Similar to file sharing in Windows 2000, when resources are shared, you grant users permission for using the resource. You can also limit the number of simultaneous connections. This type of sharing requires more experience and effort to configure. Each networked system must be set up with the appropriate user accounts. By default, the guest account is disabled (i.e. sharing is disabled). Also, Windows XP home edition supports only Simple File Sharing. Windows XP professional supports both sharing models. There are two types of sharing permission control: • Shared Resource permissions • NTFS permissions Shared Resource permission Control network access to a shared resource. These permissions do not affect local users. This type of permission control is defined in the sharing tab of a folder’s properties window. NTFS permission Apply to folders and files on an NTFS formatted drive. These permissions provide detailed control over an object. Users who are granted access can be given specific types of permissions, including the following: • Run programs • View folder contents • Create new files • Change existing files 1 NTFS permission is also defined on the sharing tab of a folder’s properties window. Both types of permission controls are combined in a restrictive manner. The user permission is first determined by the shared resource permissions. The NTFS permissions can “strip away” some of those permissions but cannot extend them. Enabling Simple File Sharing To enable Simple File Sharing, use the following steps: 1. Open Windows Explorer and right click the file or folder you want to share. 2. From the pop-up menu, choose sharing and security. 3. On the file or folder’s Properties window, click the sharing tab. 4. Under Network Sharing and Security, check the Share This Folder on the Network check box. 5. Enter a share name in the Share Name text box. Add a dollar sign to the end of the share name to make it invisible but can still be accessed. 6. If you want users to view the files only on this share, uncheck the Allow Network Users to Change My Files check box. If you leave this check box checked, users will be able to read and write to the share. Sharing Folders with Classic Security If you are logged on as an administrator, you can share resources with others on the network. To set file sharing with the classic security model, use the following steps: 1. Open Windows Explorer and right click the file or folder you want to share. 2. From the pop-up menu, choose sharing and security. 3. On the file or folder’s Properties window, click the sharing tab. 4. Under Network Sharing and Security, check the Share This Folder on the Network check box. 5. Enter a share name in the Share Name text box. Add a dollar sign to the end of the share name to make it invisible but can still be accessed. 6. If you want users to view the files only on this share, uncheck the Allow Network Users to Change My Files check box. If you leave this check box checked, users will be able to read and write to the share. 7. Click the Allow This Number of Users option to limit the number of users who can connect to the resource. 8. Click the permission button to open the Permission Window. 9. In the group or User Names list, select the name or the user or group you need to set permissions for when accessing this resource. 10. Select one or more of the following permissions: 1. Full Control: Lets users create, read, write, rename, and delete files in the shared resource. Users can also change permission settings and take ownership of files on NTFS volumes. 2. Change: Lets users read, write, rename, and delete files in the shared resource. 3. Read: Lets users read files in the shared resource. 11. Click the OK to return to the Sharing tab. 12. When done assigning permissions, click OK. 2 With Windows XP professional, you can also use the Shared Folders Snap-In, which provides a centralized approach to managing shared folders. To use this snap-in, you must be logged in as an administrator and have simple file sharing disabled. To use the shared folders snap-in, use the following steps: 1. Right click My computer and choose manage from the pop-up menu. 2. Navigate to the System Tools\Shared Folders directory. 3. View or modify the permissions for a shared folder by right clicking the folder and choosing properties from the pop-up menu. You can also send messages to users that are connected to shared resources on your system. To send a message: 1. Right click My Computer and choose Manage from the pop-up menu. 2. In the computer management window, navigate to the Systems Tools\Shared Folders directory. 3. Right click the shares folder, and then choose All Tasks | Send Console Message from the pop-up menu. 4. The send console message dialog box, shown next, automatically inserts the names of users with active session and open files in the recipients list. Type the message and click send. Windows XP also offers managing resource sharing via command line options using the Net.exe utility. To get more information using the Net.exe command see “net help” or “net help share”. See table below for examples: Table one: Examples of net share commands Net Command Description Net share Displays a list of system’s shared resources Net share sharename Displays information regarding the shared resource Net share sharename/delete Deletes the specified shared resource Net use Displays a list of resources to which you are currently connected to. Net session Displays a list of clients that are accessing your shared resources Net file Displays a list of open shared files including file ID Net file ID/close Closes the file specified by the ID Internet Connection Firewall On a small network with only one Internet connection, you can share that Internet connection with other systems on the network using the Internet Connection Sharing (ICS) feature. If you enable ICS, the Internet Connection Firewall (ICF) is automatically enabled. The firewall protects your shared resources from unauthorized users. If your system is isolated from the Internet by a residential gateway, proxy server, or another firewall, you can disable the firewall feature. The firewall monitors inbound and outbound communication between the computers it protects. To enable the firewall: 1. Open the control panel and select Network and Internet Connections. 3 2. Click Network Connections to open a list of network connections in the Network Connections window. 3. Right click the network connection that directly connects to the Internet, and then choose properties from the pop up menu. 4. On the Connection Properties window, click the advanced tab. 5. Make certain the “Protect my computer and network by limiting or preventing access to this computer from the Internet” option is checked. Sharing Printers To share your printer, which is attached to your computer, use the following steps: 1. Open the control panel and select Printers and Other Hardware. 2. Click view installed printers or fax printers. 3. Right click the printer you want to share, and then select sharing from the pop-up menu. 4. In the sharing folder of the properties window that opens by default, click the share this printer option. 5. Type a printer name in the share name text box. This is the name the users will see when connecting to the device. 6. If some users are running other operating systems, click the additional drivers button and install the required drivers. 7. Click the advanced tab to specify the times when the printer will be available. 8. Click OK. NetBIOS/NetBEUI The original networking model used by IBM, Microsoft, and others was created in 1984. IBM and Sytek released a LAN (Local Area Network) message interface system named the Network Basic Input/Output System (NetBIOS). NetBIOS is a generalized program- to-program communication facility that enables peer-to-peer and client/server communication between PCs operating in a LAN environment. NetBIOS communicates through three key services: 1. Name Service: Each PC using NetBIOS is assigned a logical name, and other PCs use that name to communicate with that PC. PCs learn about each other’s names by listening to announcements PCs make when they join the LAN or by broadcasting a discovery request for a name. Each PC keeps track of the names of other PCs in a local dynamic table. 2. Session Service: A PC can establish a session with another PC by “calling” it by name. Once the target PC agrees to communicate with the requesting PC, the two PCs can exchange message with one another until one of them “hangs up”. Session service is a connection-oriented service. NetBIOS provides message sequencing and message acknowledgements to insure that all messages sent are properly received.
Load more

Recommended publications
  • OES 2 SP3: Novell CIFS for Linux Administration Guide 9.2.1 Mapping Drives from a Windows 2000 Or XP Client
    www.novell.com/documentation Novell CIFS Administration Guide Open Enterprise Server 2 SP3 May 03, 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Service Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Shared Resource Matrix Methodology: an Approach to Identifying Storage and Timing Channels
    Shared Resource Matrix Methodology: An Approach to Identifying Storage and Timing Channels RICHARD A. KEMMERER University of California, Santa Barbara Recognizing and dealing with storage and timing channels when performing the security analysis of a computer system is an elusive task. Methods for discovering and dealing with these channels have mostly been informal, and formal methods have been restricted to a particular specification language. A methodology for discovering storage and timing channels that can be used through all phases of the software life cycle to increase confidence that all channels have been identified is presented. The methodology is presented and applied to an example system having three different descriptions: English, formal specification, and high-order language implementation. Categories and Subject Descriptors: C.2.0 [Computer-Communication Networks]: General--se- curity and protection; D.4.6 ]Operating Systems]: Security and Protection--information flow controls General Terms: Security Additional Key Words and Phrases: Protection, confinement, flow analysis, covert channels, storage channels, timing channels, validation 1. INTRODUCTION When performing a security analysis of a system, both overt and covert channels of the system must be considered. Overt channels use the system's protected data objects to transfer information. That is, one subject writes into a data object and another subject reads from the object. Subjects in this context are not only active users, but are also processes and procedures acting on behalf of the user. The channels, such as buffers, files, and I/O devices, are overt because the entity used to hold the information is a data object; that is, it is an object that is normally viewed as a data container.
    [Show full text]
  • Shared Resource
    Shared resource In computing, a shared resource, or network share, is a computer resource made available from one host to other hosts on a computer network.[1][2] It is a device or piece of information on a computer that can be remotely accessed from another computer transparently as if it were a resource in the local machine. Network sharing is made possible by inter-process communication over the network.[2][3] Some examples of shareable resources are computer programs, data, storage devices, and printers. E.g. shared file access (also known as disk sharing and folder sharing), shared printer access, shared scanner access, etc. The shared resource is called a shared disk, shared folder or shared document The term file sharing traditionally means shared file access, especially in the context of operating systems and LAN and Intranet services, for example in Microsoft Windows documentation.[4] Though, as BitTorrent and similar applications became available in the early 2000s, the term file sharing increasingly has become associated with peer-to-peer file sharing over the Internet. Contents Common file systems and protocols Naming convention and mapping Security issues Workgroup topology or centralized server Comparison to file transfer Comparison to file synchronization See also References Common file systems and protocols Shared file and printer access require an operating system on the client that supports access to resources on a server, an operating system on the server that supports access to its resources from a client, and an application layer (in the four or five layer TCP/IP reference model) file sharing protocol and transport layer protocol to provide that shared access.
    [Show full text]
  • Resource Management in Multimedia Networked Systems
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science May 1994 Resource Management in Multimedia Networked Systems Klara Nahrstedt University of Pennsylvania Ralf Steinmetz University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Klara Nahrstedt and Ralf Steinmetz, "Resource Management in Multimedia Networked Systems ", . May 1994. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-94-29. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/331 For more information, please contact [email protected]. Resource Management in Multimedia Networked Systems Abstract Error-free multimedia data processing and communication includes providing guaranteed services such as the colloquial telephone. A set of problems have to be solved and handled in the control-management level of the host and underlying network architectures. We discuss in this paper 'resource management' at the host and network level, and their cooperation to achieve global guaranteed transmission and presentation services, which means end-to-end guarantees. The emphasize is on 'network resources' (e.g., bandwidth, buffer space) and 'host resources' (e.g., CPU processing time) which need to be controlled in order to satisfy the Quality of Service (QoS) requirements set by the users of the multimedia networked system. The control of the specified esourr ces involves three actions: (1) properly allocate resources (end-to-end) during the multimedia call establishment, so that traffic can flow according to the QoS specification; (2) control resource allocation during the multimedia transmission; (3) adapt to changes when degradation of system components occurs.
    [Show full text]
  • Novell Cluster Services,. for Linux. and Netware
    Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines
    [Show full text]
  • Novell® Platespin® Recon 3.7.4 User Guide 5.6.4 Printing and Exporting Reports
    www.novell.com/documentation User Guide Novell® PlateSpin® Recon 3.7.4 September 2012 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • OSI Model and Network Protocols
    CHAPTER4 FOUR OSI Model and Network Protocols Objectives 1.1 Explain the function of common networking protocols . TCP . FTP . UDP . TCP/IP suite . DHCP . TFTP . DNS . HTTP(S) . ARP . SIP (VoIP) . RTP (VoIP) . SSH . POP3 . NTP . IMAP4 . Telnet . SMTP . SNMP2/3 . ICMP . IGMP . TLS 134 Chapter 4: OSI Model and Network Protocols 4.1 Explain the function of each layer of the OSI model . Layer 1 – physical . Layer 2 – data link . Layer 3 – network . Layer 4 – transport . Layer 5 – session . Layer 6 – presentation . Layer 7 – application What You Need To Know . Identify the seven layers of the OSI model. Identify the function of each layer of the OSI model. Identify the layer at which networking devices function. Identify the function of various networking protocols. Introduction One of the most important networking concepts to understand is the Open Systems Interconnect (OSI) reference model. This conceptual model, created by the International Organization for Standardization (ISO) in 1978 and revised in 1984, describes a network architecture that allows data to be passed between computer systems. This chapter looks at the OSI model and describes how it relates to real-world networking. It also examines how common network devices relate to the OSI model. Even though the OSI model is conceptual, an appreciation of its purpose and function can help you better understand how protocol suites and network architectures work in practical applications. The OSI Seven-Layer Model As shown in Figure 4.1, the OSI reference model is built, bottom to top, in the following order: physical, data link, network, transport, session, presentation, and application.
    [Show full text]
  • Importance of DNS Suffixes and Netbios
    Importance of DNS Suffixes and NetBIOS Priasoft DNS Suffixes? What are DNS Suffixes, and why are they important? DNS Suffixes are text that are appended to a host name in order to query DNS for an IP address. DNS works by use of “Domains”, equitable to namespaces and usually are a textual value that may or may not be “dotted” with other domains. “Support.microsoft.com” could be considers a domain or namespace for which there are likely many web servers that can respond to requests to that domain. There could be a server named SUPREDWA.support.microsoft.com, for example. The DNS suffix in this case is the domain “support.microsoft.com”. When an IP address is needed for a host name, DNS can only respond based on hosts that it knows about based on domains. DNS does not currently employ a “null” domain that can contain just server names. As such, if the IP address of a server named “Server1” is needed, more detail must be added to that name before querying DNS. A suffix can be appended to that name so that the DNS sever can look at the records of the domain, looking for “Server1”. A client host can be configured with multiple DNS suffixes so that there is a “best chance” of discovery for a host name. NetBIOS? NetBIOS is an older Microsoft technology from a time before popularity of DNS. WINS, for those who remember, was the Microsoft service that kept a table of names (NetBIOS names) for which IP address info could be returned.
    [Show full text]
  • Characterizing Peer-Level Performance of Bittorrent
    Characterizing Peer-level Performance of BitTorrent DRP Report Amir H. Rasti ABSTRACT 1. INTRODUCTION BitTorrent is one of the most popular Peer-to-Peer During the past few years, peer-to-peer appli- (P2P) content distribution applications over the cations have become very popular on the In- Internet that significantly contributes in network ternet. BitTorrent in one of the most popu- traffic. lar peer-to-peer applications providing scalable peer-to-peer content distribution over the In- In BitTorrent, a file is divided into segments ternet. Some recent studies [8] have shown that and participating peers contribute their outgoing BitTorrent is accountable for approximately bandwidth by providing their available segments 35% of the Internet traffic. BitTorrent is a to other peers while obtaining their missing peers scalable peer-to-peer content distribution sys- from others. Characterization of BitTorrent is use- tem that enables one-to-many distribution of ful in determining its performance bottlenecks as large files without requiring a large access link well as its impact on the network. bandwidth at the source. Similar to other peer- In this study, we try to address the following two to-peer systems, it uses resources of participat- key questions through measurement: (i) What are ing peers to increase the capacity of the system. the main factors that affect observed performance The main shared resource in BitTorrent is the by individual peers in BitTorrent?, and (ii) What up-link bandwidth of individual peers. The file are the contributions of these factors on the per- being distributed is divided into a large number formance of individual peers? To address these of segments.
    [Show full text]
  • Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM Eserver I/O IBM Systems Group, Austin, Texas [email protected]
    Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM eServer I/O IBM Systems Group, Austin, Texas [email protected] Abstract • Low latency - the total time required to transfer the first bit of a message from the local application to the remote appli- Enterprise and technical customers place a diverse set of cation, including the transit times spent in intermediate requirements on server I/O networks. In the past, no single switches and I/O adapters. network type has been able to satisfy all of these requirements. As • High throughput - the number of small block transactions a result several fabric types evolved and several interconnects performed per second. The size and rate of small block I/O emerged to satisfy a subset of the requirements. Recently several depends on the workload and fabric type. A first level technologies have emerged that enable a single interconnect to be approximation of the I/O block size and I/O throughput rates required for various I/O workloads can be found in used as more than one fabric type. This paper will describe the “I/O Workload Characteristics of Modern Servers” [4]. requirements customers place on server I/O networks; the various • High bandwidth - the number of bytes per second sup- fabric types and interconnects that have been used to satisfy those ported by the network. Typically, used to gauge perfor- requirements; the technologies that are enabling network mance for large block data transfers. Peek bandwidth convergence; and how these new technologies are being deployed describes the bandwidth provided by a given link; whereas on various network families.
    [Show full text]
  • Operator's Guide
    MILITARY POWER SUPPLY Operator’s Guide Ethernet & SNMP MPS-4000-1U MPPS-4000-1U Made in USA 1.888.567.9596 (USA only) | SynQor Headquarters 155 Swanson Road, Boxborough, MA 01719-1316 USA | www.synqor.com QMS: 006-0006748 Rev. E 01\19\2021 MPS with Ethernet Interface Contents 1 Overview ............................................................................................................................................... 2 2 Initial Configuration .............................................................................................................................. 2 2.1 DHCP Server .................................................................................................................................. 2 2.2 NetBIOS Hostname ....................................................................................................................... 2 2.3 Local Connection ........................................................................................................................... 2 3 Web Interface ....................................................................................................................................... 3 3.1 MONITOR Page ............................................................................................................................. 4 3.2 CONTROL Page .............................................................................................................................. 5 3.3 NETWORK Page ............................................................................................................................
    [Show full text]
  • NFS Gateway for Netware 6 Administration Guide October 22, 2003
    Novell Confidential Manual (99a) 11 September 2003 Novell * NFS Gateway for NetWare® 6 www.novell.com ADMINISTRATION GUIDE October 22, 2003 Novell Confidential Manual (99a) 11 September 2003 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903;5,633,931; 5,652,859; 5,671,414;
    [Show full text]