This section summarizes some issues you should consider when using Windows 98 with Client for Microsoft Networks, whether your site uses server-based or peer-to-peer networking.
If you are currently using a peer-to-peer network but you want to take advantage of remote administrative features or user-level security, consider a small server-based network using Windows NT. For example, the Microsoft BackOffice® Small Business Server provides server software for companies with 25 or fewer personal computers. For more information about Small Business Server, see http://www.microsoft.com/backofficesmallbiz/.
On server-based networks, central servers running Windows NT Server or Microsoft LAN Manager version 2.x act as file and print servers and provide support for managing network logon and security. For information about the benefits of server-based networks using Windows NT Server, see "Running Windows 98 with Windows NT" later in this chapter.
The following list describes issues to consider when planning for a server-based network:
With Windows 98, Client for Microsoft Networks includes the capability to connect to a distributed file system (Dfs) tree.
The Microsoft distributed file system for Windows NT Server enables Windows NT Server administrators to build a single, integrated directory tree that spans many servers and shares in the corporate network. This directory tree presents data logically, no matter where that data is physically located. This provides the following advantages:
For example, suppose the network contains the following servers and shared network directories:
This share includes a directory called Forms, which includes the files Tulip_Form and Begonia_Form.
This share includes a directory called Inventory, which is currently empty.
This share includes two directories: Tulip_Seeds and Begonia_Seeds. Each directory includes a file named Seeds.txt.
With Dfs, Windows NT network administrators can construct the following Dfs tree:
\\TerraFirm\Corp
\Retail\Forms(points to \\Retail\Accounting\Forms)
\Supply(points to \\Supply\Flower_Seeds)
\Inventory(points to \\Supply\TerraCotta\Inventory)
Note
This Dfs tree contains several different junction points (places where the Dfs path points to a destination share and subdirectories). For example, \\TerraFirm\Corp\Supply is a junction point.
Figure 16.1 shows what a Windows 98 user will see. Items in bold are part of the Dfs tree.
Figure 16.1 Dfs directory structure
With Windows 98, users can now gain access to Dfs volumes. Windows 98 users can browse directory trees created using Dfs in exactly the same way they browse ordinary servers and shares. For example, the user can gain access to the file Seeds.txt in the directory Tulip_Seeds in the following location:
\\TerraFirm\Corp\Supply\Tulip_Seeds\Seeds.txtUsers can also map one drive to the root of the Dfs tree and then transparently gain access to any resources in that part of the tree. For example, a user could map a drive to the root of the Dfs tree by using the following command:
net use Z: \\TerraFirm\Corp
The user can then gain access to the same file in the following location:
Z:\Supply\Tulip_Seeds\Seeds.txt
Thus, users can connect to many different servers without needing to map drives to each server.
Administrators can also create multiple Dfs directory trees and then merge them using interlinks. With interlinks, the leaf of one Dfs tree is the same as the root of another Dfs tree.
Windows 98 Dfs support is limited to server message block (SMB)–based resources, such as Windows NT servers. Any non-SMB resources will be invisible to Windows 98. For example, NetWare servers, which use NetWare Core Protocol (NCP), will be invisible. There is one exception: If the Windows NT server also uses Gateway for NetWare Networks, the Windows NT server network administrator can configure the gateway so that Windows 98 can also access NetWare servers by using NCP.
For more information about Dfs, see http://www.microsoft.com/.
In the peer-to-peer networking model, at least one computer must act as both a client and a server. If desired, every computer can act as both a client and a server. As a client in a peer network, the computer can access the network resources shared on another computer.
A peer network can be easy to set up for a small number of users, but it becomes slower, less secure, and harder to maintain with a large number of users. Thus, a peer network is more appropriate for small offices with about five to ten users.
Any computer running Windows 98 can act as both a client and a server on peer networks. If you have the technical expertise, you can establish the wiring for a small peer network of Windows 98 computers; otherwise, use the services of a system integrator. The following sections summarize issues either you or the system integrator need to consider for peer networking with Windows 98. For technical information about configuring and using File and Printer Sharing for Microsoft Networks, see Chapter 18, "Logon, Browsing, and Resource Sharing."
Thinnet (also called thin Ethernet or thin coax) is the simplest method of cabling ten or fewer connections on a network. It is appropriate only for Ethernet networks, not token-ring networks. Thinnet cabling uses coaxial cable with a BNC connector at each end. The cable attaches to each computer with a BNC T-connector. The major disadvantage in using thinnet cabling is that a fault in the cabling at any computer affects all computers on the network. Thinnet cabling is appropriate only for Ethernet topologies.
Unshielded twisted-pair (also called UTP or simply twisted-pair) cabling is based on standard telephone wiring technology, using connectors similar to those inserted in telephone jacks. Twisted-pair cabling is appropriate if your network has (or will have) more than ten computers, and if computers are located in low-interference environments such as an office — it is not appropriate for manufacturing or warehousing environments. You can use twisted-pair cabling for Ethernet or token-ring networks.
When cabling the network, make sure not to use twisted-pair wiring that was previously used for telephone systems or that is more than five years old, because it might not be reliable enough for network activity. For networks of more than two computers, you need additional components such as hubs and concentrators. These components can also help to isolate cabling failures. For more information about cabling, see Networking Essentials, Second Edition from Microsoft Press.
This section summarizes issues for the following tasks:
Choosing protocols and other networking components.
Microsoft NetBEUI is a fast protocol, requiring no additional configuration settings; it is a good choice for peer-to-peer networks. Microsoft TCP/IP and the IPX/SPX-compatible protocol are other alternatives for small peer-to-peer networks. You also need an NDIS 3.1 or later network adapter driver. For information about these components, see Chapter 15, "Network Adapters and Protocols."
Setting up security and automated backup.
Share-level security is the only security option available on peer-to-peer networks. With share-level security, you create passwords to restrict access to shared resources on a peer server, so that only users with the password can gain access to the resources. For information about managing passwords in Windows 98, see Chapter 9, "Security." If you need to control access to individual files or to particular computers based on user identity, you must create a server-based network using Windows NT Server.
You can use any backup software that is compatible with Windows 98 to back up files on peer servers and other computers. To make sure data on the network is backed up automatically, use a server-based network.
Setting up peer servers.
Each computer that is running File and Printer Sharing for Microsoft Networks can act as a server, so that other computers can connect to it to use files or printers created on that peer server. Because a peer server can slow down if many users are requesting services from it, you might want to dedicate one computer to servicing print requests. In this configuration, users can return to work immediately after printing, while the dedicated computer can perform the printing tasks.
For optimal performance on a computer used extensively as a file or print server, use the System option in Control Panel to optimize the performance of the file system for network server activities. For information, see Chapter 26, "Performance Tuning."
Managing a peer network.
Most of the remote administration features in Windows 98 rely on user-level security, which requires a server running Windows NT or NetWare to provide pass-through authentication of users for access to resources on remote computers. Therefore, on peer-to-peer networks, you cannot use Microsoft Remote Registry Services or any administrative features that require remote access to the registry. However, you can use Net Watcher to manage the file system on remote computers, as described in Chapter 23, "System and Remote Administration Tools."