Penguin
Diff: ServerMessageBlock
EditPageHistoryDiffInfoLikePages

Differences between current version and revision by previous author of ServerMessageBlock.

Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History

Newer page: version 6 Last edited on Wednesday, January 28, 2004 3:23:45 pm by AristotlePagaltzis
Older page: version 4 Last edited on Friday, October 17, 2003 10:17:01 am by StuartYeates Revert
@@ -1,12 +1,10 @@
-ServerMessageBlock ( [SMB]) is a client/server protocol similar to remote procedure calls ([RPC]), but specialised for file system access. It is the native method of file and print sharing for [Microsoft]'s operating systems, where it is called [Microsoft] Networking. [Windows] for Workgroups, [Windows] 95, and [WindowsNT] all include [SMB] clients and servers. 
+ServerMessageBlock, usually only referred to by its abbreviated form [SMB], is a client/server [Protocol] similar to remote procedure calls ([RPC]), but specialised for file system access. It was developed by [Intel], [Microsoft], and [IBM] in the early 1980s, and also had input from [Xerox] and [3Com] . It is the native method of file and print sharing for [Microsoft]'s operating systems, where it is called [Microsoft] Networking, and is also used by [OS/2], Lan Manager and Banyan Vines . [Windows] for Workgroups, [Windows] 95, and [WindowsNT] all include [SMB] clients and servers. [SMB] originally ran on top of the lower level [Protocol]s NetBEUI and NetBIOS, but now typically runs over [TCP/IP]
  
-But [SMB] is also used by [OS/2], Lan Manager and Banyan Vines, and there are [SMB] servers and clients for Unix, for example [Samba] and smbclient(1) . The protocol was developed by [Intel ], [Microsoft ], and [IBM] in the early 1980s . It has also had input from [Xerox ] and [3Com ]. 
+There are [SMB] servers and clients for Unix, as well . The most popular one is a reverse-engineered OpenSource implementation of the [Protocol ] called [Samba ]. It allows Unix machines integrate networks consisting of Windows clients. [Samba ] can even act as a "domain controller", removing the need for expensive [Windows ] server licences
  
-[SMB] originally ran on top of the lower level protocols NetBEUI and NetBIOS , but now typically runs over [TCP/IP ]. 
+While it is mainly used for file and printer sharing between computers, [SMB] is a presentation layer [Protocol] with provisions for much more. It is structured as a large set of commands (called "Server Message Blocks", hence the name) to support sharing of files, printers, and serial ports , and also user authentication, resource browsing, communications abstractions such as named pipes and mail slots, as well as other miscellaneous functions. Clients and servers may implement different versions ("dialects") of the [Protocol ], and will negotiate the version to use before starting a session. A redirector packages [SMB] requests into a network control block (NBC) structure that can be sent across the network to a remote device
  
-While it is mainly used for file and printer sharing between computers, it has provisions for much more. [SMB] is a presentation layer protocol structured as a large set of commands (Server Message Blocks). Clients and servers may implement different versions ("dialects") of the protocol, and will negotiate the version to use before starting a session. There are commands to support sharing of files, printers, serial ports, for user authentication, resource browsing, communications abstractions such as named pipes and mail slots, and other miscellaneous functions. A redirector packages [SMB] requests into a network control block (NBC) structure that can be sent across the network to a remote device.  
-  
- [Microsoft] have developed an extended version of [SMB] for the [Internet ], the Common Internet File System ( [CIFS ]), which in most cases replaces [SMB]. [CIFS] runs only runs over [TCP/IP]. 
+[Microsoft] have extended [SMB] into [CIFS ], slated as a replacement of the [Protocol ] for the InterNet which runs only runs over [TCP/IP]. 
  
 ----- 
 CategoryProtocols