Download (direct link):
You can run both Microsoft and NetWare clients side by side without difficulty, but you can't mix Novell components and Microsoft components willy-nilly on any Windows machine. Therefore, you can use Microsoft software to access both Windows Server 2003 and NetWare servers or Novell software to access both Windows Server 2003 and NetWare servers. But you can't use Microsoft software to access Windows Server 2003 and NetWare software to access NetWare servers on the same machine.
Managing Access to Resources
Part of each request that a client makes for a network resource includes the client's own identification. Another part names the resources that the client is requesting from the network. Clients normally use a password to access resources on a peer-to-peer network, which Microsoft calls share-level access control (because each password applies to a single shared resource).
In a Microsoft client/server network, the user's level of permissions governs that user's ability to access resources. In Microsoft-speak, user-level access means that when a user identifies himself or herself in a request for service, the user's account name determines which requests the server can honor and which ones it must deny.
The server checks which resources the user has permission to access, and it checks also whether the operation that the user requests is allowed. For example, Bob may be allowed to read a certain file, but he may not be able to write to or delete that file. If he requests a read operation, the request is permitted, but if he requests a write or delete operation, that request is denied.
KEY CONCEPT Handing requests on a client/server network involves more work than may be immediately
apparent, because a security check controls access and restrictions. Setting up permissions requires an understanding of which names to attach to resources, to the domains in which they reside, and to the users who state such requests. Much of what you find out in Chapters 8,11-14, and especially inChapters 15.16. and 1_8 touch on these terms and concepts and explain them to your heart's content.
^ PREVIOUS I NEXT >
A Windows Network Services Sampler
In the previous sections, we covered the request/response mechanism that handles all requests for network services and the ways in which responses occur. In this section, we explain what you can do within this structure. The following is an alphabetical list of common services that you're likely to find on a Windows Server 2003-based network:
¦ Alerter: Provides the capability to send alarms and alerts to specific recipients when events occur in Event Viewer or thresholds are exceeded in System Monitor.
® Computer Browser: Manages the list of computer and resource names on a specific network, so users can browse a list of what's out there (and available) in Network Neighborhood and other utilities.
® Messenger: Provides a way for Windows Server 2003 to deliver on-screen messages to designated recipients in response to explicit commands or to alarms and alerts.
® Net Logon: Handles user attempts to log on to the network and ferries information among all domain controllers in a single Windows Server 2003 domain.
® Network DDE: Allows dynamic updates to occur across a network. DDE (Dynamic Data Exchange) refers to a dynamic update technology used to propagate updates from one file or document to another when embedded objects in one document must reflect changes to that object in another document.
® NTLM Security Support Provider: Provides a Windows Server 2003 security model that's compatible with LAN Manager (LM). This service handles encryption and delivery of logon requests that can't use more modern Windows security models.
® Plug and Play: Makes a Windows 2003 machine Plug-and-Play compatible.
® Print Spooler: Handles the storage of files for pending print jobs. This is the service that manages the scheduling and retention of pending print jobs until their turn to print comes up.
¦ Routing and Remote Access Service (RRAS): Covers a whole range of RRAS services. RRAS provides dial-in and dial-out communications services for up to 256 simultaneous connections on a single Windows Server 2003 and offers a range of routing services as well.
¦ Server: Acts as the basic listener process for requests for service on a Windows Server 2003. (In fact, stopping the Server service is a good way to temporarily disable network access to a server.) Although its name may suggest otherwise, this service is necessary on Windows client machines and Windows Server 2003 machines alike.
® Telephony Service: Makes it possible for Windows 2003 to use the built-in Windows Telephony
Application Programming Interface (TAPI) to access modems, telephones, Integrated Services Digital Network (ISDN), and general Digital Subscriber Line (xDSL) devices through a standard dialer and telephone book interface. Therefore, it is also a key component of RRAS service.