Microsoft KB Archive/92451

{| = WG0667: Peer-to-Peer vs. Client-Server Networks =
 * width="100%"|

Last reviewed: May 1, 1997

Article ID: Q92451 3.10 3.11 WINDOWS kbnetwork kb3rdparty kbfile kbappnote The information in this article applies to:


 * Microsoft Windows for Workgroups versions 3.1, 3.11

Microsoft has an Application Note that discusses the differences between the peer-to-peer and client-server networking models.

NOTE: The text for this Application Note was taken from the Windows for Workgroups Resource Kit.

You can obtain this Application Note from the following sources:


 * Microsoft's World Wide Web Site on the Internet
 * The Internet (Microsoft anonymous ftp server)
 * Microsoft Download Service (MSDL)
 * Microsoft FastTips Technical Library
 * Microsoft Product Support Services

For complete information, see the &quot;To Obtain This Application Note&quot; section at the end of this article.

THE TEXT OF WG0667
Microsoft(R) Product Support Services Application Note (Text File) WG0667: PEER-TO-PEER VS. CLIENT-SERVER NETWORKS Revision Date: 11/93 No Disk Included The following information applies to Microsoft Windows(TM) for Workgroups versions 3.1 and 3.11.
 * INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY   |
 * ACCOMPANY THIS DOCUMENT (collectively referred to as an           |
 * Application Note) IS PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY     |
 * KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO   |
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A    |
 * PARTICULAR PURPOSE. The user assumes the entire risk as to the    |
 * accuracy and the use of this Application Note. This Application   |
 * Note may be copied and distributed subject to the following       |
 * conditions: 1) All text must be copied without modification and   |
 * all pages must be included; 2) If software is included, all files |
 * on the disk(s) must be copied without modification [the MS-DOS(R) |
 * utility DISKCOPY is appropriate for this purpose]; 3) All         |
 * components of this Application Note must be distributed together; |
 * and 4) This Application Note may not be distributed for profit.   |
 * Copyright 1992 Microsoft Corporation. All Rights Reserved.        |
 * Microsoft and MS-DOS are registered trademarks and Windows        |
 * is a trademark of Microsoft Corporation.                          |
 * Novell and NetWare are registered trademarks of Novell, Inc.      |
 * Novell and NetWare are registered trademarks of Novell, Inc.      |

A COMPARISON OF CLIENT-SERVER AND PEER-TO-PEER NETWORKS --- This application note discusses the differences between the peer-to- peer and client-server networking models. NOTE: The text for this application note was taken from the Windows for Workgroups Resource Kit. Part of a network's overall design includes a decision about how network resources will be shared and managed. Early networks used central file servers to manage access to shared files and printers. These servers were often workstations dedicated to sharing resources or running network file server-related applications (for example, database engines). Examples of network operating systems (NOSs) that support the central file server model include Microsoft LAN Manager and Novell(R) NetWare(R). The peer-to-peer network model was developed more recently. Network workstations in a peer-to-peer model can access resources shared by another user and share resources on their local workstations to allow access by other members of their workgroup. Windows for Workgroups supports the peer-to-peer networking model. The central file server model requires that all file sharing take place on the LAN server itself. That is, if the file server is the central repository of information, then all exchanges of information between workstations on a LAN must first pass through the file server. This model is commonly implemented in an environment where the workstations don't have the processing power or the resources capable of supporting networking server functionality. For example, the workstations may not have enough memory or may have small-capacity hard disks.

In the peer-to-peer networking model, each workstation (or at least one workstation) in a file-transfer scenario acts as both a client and a server. As a client, the workstation can access the network resources shared by another workstation. This model is commonly implemented in an environment where workstations have the processing power and resources to provide network server functionality or where the cost of dedicating a workstation as a server is prohibitively high. The peer-to-peer model is more flexible than the central file server model because a workstation can directly access the shared resources of another workstation.

To illustrate the differences between the central file server model and the peer-to-peer networking model, let's say two workstations, Workstation A and Workstation B, want to share a document. The document was created on Workstation A and resides on Workstation A's hard disk.

In the central file server model, Workstation A must connect to the server, place the document on the server's hard disk, then inform Workstation B that the document is available. Workstation B can then connect to the server and access the document left there by Workstation A. In the meantime, unless Workstation A is working with the specified document directly on the file server (that is, making modifications to the version of the document that resides on the file server), the version of the document that may reside on Workstation A's hard disk will likely become out of sync with the version of the document Workstation B is now using.

In the peer-to-peer networking model, Workstation A simply grants Workstation B permission to access the directory where the files are located on Workstation A's hard disk. Workstation B can then directly connect to Workstation A and access the document. Another way to provide Workstation B with the document that Workstation A created is to have Workstation B give Workstation A access to a shared directory on Workstation B. Then Workstation A can copy the document from its hard disk to the shared directory on Workstation B--however, the latter procedure suffers from the same scenario as the central file server model where the versions of the documents may get out of sync. Since both workstations are considered to be peers, both support client and server functionality.

TO OBTAIN THIS APPLICATION NOTE
You can find WG0667.EXE (size: 15276 bytes) , a self-extracting file, on the following services:   Microsoft's World Wide Web Site on the Internet On the www.microsoft.com home page, click the Support icon. Click Knowledge Base, and select the product. Enter kbfile #|WG0667.EXE (size: 15276 bytes), and click GO! Open the article, and click the button to download the file.   Internet (anonymous FTP) ftp ftp.microsoft.com Change to the Softlib/Mslfiles folder. Get WG0667.EXE (size: 15276 bytes)   Microsoft Download Service (MSDL) Dial (425) 936-6735 to connect to MSDL Download WG0667.EXE (size: 15276 bytes) 

For additional information about downloading, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q119591 TITLE    : How to Obtain Microsoft Support Files from Online Services You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (425) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area.
 * }