by Rob Tidrow
Windows 98 can be configured as a node on several different network configurations, including Windows NT, Novell NetWare, and Banyan VINES. One problem with these types of networks is the cost of implementing and supporting them. If you cannot afford or do not require a network setup based on one of these larger network operating systems, you can set up two or more Windows 98 machines in a peer-to-peer network. You also can set up Windows 98 in a peer-to-peer network even if you're running another network operating system.
With a Windows 98 peer-to-peer network, users can share resources without the overhead of a dedicated server managing access to resources. This way, you can use all your PCs for sharing resources and for performing workstation duties, such as running applications for a user. The only extra hardware required is a network interface card (NIC) and cable, such as coaxial, twisted-pair, or fiber-optic cables, or wireless devices. If you plan to connect more than two PCs, you might also want to invest in a workgroup hub, which is used in a star topology network.
NOTE: In a star topology network, workstations are connected to a hub, much like the points of a star connect to its center. A topology is the way a network's nodes are connected to each other.Another popular topology is the bus topology, in which nodes are connected in linear segments. Each node is connected to a main (backbone) cable. One disadvantage of bus topology networks is that if there is cable failure anyplace in the segment, the entire network is affected. On the other hand, cable failures on a star topology affect only those nodes using that particular cable connection.
Some features of a Windows 98 peer-to-peer network include the following:
NOTE: You can use Microsoft Backup to back up files on your hard disk to another computer on the network.
You've read a little about how you can limit access to shared resources using passwords. On a pure Windows 98 peer-to-peer network, you have only one type of security level: share-level security. With share-level security, you can share printers and folders with other users on the network. These users can access resources with or without a password, depending on how you've set up the shared rights to them.
Unlike user-level security, which is supported on Windows NT and NetWare networks, share-level security does not enable you to grant permissions on a per-user, per-group, or per- resource level. This means that you need to be aware of who is part of your peer-to-peer network and set up shares only to those resources you want shared. If, for instance, you have a folder in which you store confidential documents, do not share your entire drive. Instead, share only those folders that do not contain confidential documents. This might mean going through the process of sharing 49 of 50 folders (if you have 50 folders on your drive, for instance), but the time is well spent if your documents are protected. You're shown how to share folders in the "Sharing Drives and Folders" section later in this chapter.
NOTE: On a Windows 98 peer-to-peer network, you also cannot restrict and permit access on a per-file level because the Windows 98 file system does not allow file-specific access rights.
To set up a Windows 98 peer-to-peer network, install network interface cards in the PCs you want to connect. You also need to connect the PCs with a cable of some sort.
After your PCs are connected, install the Client for Microsoft Network client on each computer. Then configure the clients so that they can communicate with one another across the LAN. Finally, configure shared resources. The following sections show how to perform these tasks.
To begin configuring workstations for a Windows 98 peer-to-peer network, you need to install the Client for Microsoft Networks component. This installs the 32-bit networking client that enables your computer to speak to other Windows 98, Windows 95, Windows for Workgroups, and Windows NT computers running the Client for Microsoft Networks client.
To add the Client for Microsoft Networks, do the following:
FIG. 24.1 Use the Select Network Component Type dialog box to select the networking components to install, including Client for Microsoft Networks.
FIG. 24.2 The Select Network Client dialog box includes type of clients you can install for your networks.
The Client for Microsoft Networks appears in the network components list on the Network properties sheet. You next have to install the protocols you want to use over your new network.
For your Windows 98 computers to communicate with each other over the LAN, they must all use the same protocol. Protocols are a set of "rules" for communicating among computers, governing format, error control, timing, and sequencing. If the other computers on the network are running IPX/SPX, for example, you must install that protocol on your Windows 98 computer.
The TCP/IP, NetBEUI, and IPX/SPX-compatible protocols are installed by default when a network adapter driver is installed. You might want to keep these protocols for your network, or use another one, such as the Novell IPX ODI protocol. Unless you are required to use a third-party protocol to communicate with other computers, such as if your company has adopted another protocol, you should use one of the Microsoft protocols provided with Windows 98 to take full advantage of the Windows 98 networking features. Not only is it easier in most cases to use the Windows 98-provided protocols, but the third-party protocols often require extra components, licenses, and configuration.
The three most popular protocols to use over a Windows 98 peer-to-peer network include the following:
To install a protocol on a Windows 98 computer, follow these steps:
FIG. 24.3 Select the protocol you want to use on your network from this dialog box.
The new protocol is added to the list of installed components. It is also automatically bound to an installed adapter, which you might not want. For instance, if you have the Dial-Up Adapter installed for an Internet connection, you do not need it bound to any other protocol except TCP/IP. If this is the case, select the protocol bound to that adapter and click Remove.
After you install the protocol for your LAN, you can configure properties for it. The following sections show properties for three of the most common protocols.
IPX/SPX Protocol Configuration Settings The IPX/SPX protocol can be configured in the following way:
FIG. 24.4 You can configure IPX/SPX settings from this properties sheet.
FIG. 24.5 The Advanced tab for the IPX/SPX-compatible protocol.
FIG. 24.6 Select the component that will use the protocol over the LAN.
NetBEUI Protocol Configuration Settings If you decide to run NetBEUI as your LAN protocol, you can configure it using the following steps:
FIG. 24.7 The NetBEUI Properties sheet includes the Bindings and Advanced tabs.
FIG. 24.8 On the Advanced tab, you can set Maximum Sessions and NCBS settings.
TCP/IP Protocol Configuration Settings To configure the TCP/IP protocol on a Windows 98 computer, follow these steps:
CAUTION: An incorrect IP address or subnet mask can cause communication problems with other TCP/IP nodes on the network. If an IP address is the same as another already on the network, the machine that attaches to the network second will disable its TCP/IP support. Make sure that you assign unique TCP/IP addresses to each client.
FIG. 24.9 The IP Address tab of the TCP/IP Properties sheet.
FIG. 24.10 On Windows 98 peer-to-peer networks, you cannot set up a WINS configuration.
FIG. 24.11 You can specify IP router addresses on the Gateway tab.
FIG. 24.12 You probably won't have a DNS server on your Windows 98 peer-to-peer network, so this tab can be left unchanged.
FIG. 24.13 The NetBIOS tab allows you to configure whether you want NetBIOS applications to run over TCP/IP.
Your network is not complete until you've set up the service that enables you to share file and printer resources. To do this, take the following steps:
FIG. 24.14 Use the Select Network Service dialog box to choose the file and printer sharing for Microsoft Networks service.
The File and Printer Sharing for Microsoft Networks services appears on the Configuration tab. You now need to enable the service for your computer:
FIG. 24.15 You must enable file and print sharing so that others can access resources on your computer.
You read earlier in the "Add Protocols: IPX/SPX, NetBEUI, and TCP/IP" section that when you add a new protocol it automatically binds to all available adapters. If, however, you want to change the bindings for an adapter, take the following steps:
FIG. 24.16 The Bindings tab shows all the protocols installed and which ones are bound to the selected adapter.
TIP: The more bindings an adapter uses will greatly affect its performance. If you notice your network is slow, see whether you can disable one or more bindings. Remember that every computer on the network must use the same protocol, so make sure that you don't disable the protocol(s) shared by other PCs.
To identify your PC on the network and to specify the workgroup to which your PC belongs, you use the Identification tab (see Figure 24.17) of the Network properties sheet.
FIG. 24.17 The Identification tab provides fields for identifying this computer on the network.
In the Computer Name field, enter a name for the computer. Each computer on the network must have a unique name given to it to distinguish it from other computers. You might use proper names, usernames, or numbers to identify the computers. Each name can be up to 15 characters and cannot include spaces.
In the Workgroup field, enter a workgroup to which this computer belongs. A workgroup is a logical grouping of computers, such as in teams, divisions, or other setups. You might, for instance, create a workgroup for all users in the accounting department. Another workgroup could be set up for users in the engineering department. Or, you can opt to have one workgroup, to which all users belong.
Finally, fill in a description of this computer in the Computer Description field. Other users on the network will be able to see this description by viewing the properties sheet of the computer (see Figure 24.18).
FIG. 24.18 An example of viewing a computer's properties sheet from Network Neighborhood.
Another task you must perform is to enable share-level access for this computer. Do this by clicking the Access Control tab and selecting Share-Level Access Control (see Figure 24.19). This will enable users to share resources on your PC.
FIG. 24.19 If users can't access resources on your computer, make sure that the Share-Level Access Control option is selected.
Click OK to save your new network settings. Click Yes to restart your computer. When Windows restarts, notice the Network Neighborhood icon on your desktop (if you didn't have any network support installed prior to these steps).
Your network is only as good as what it can enable users to share or communicate with one another efficiently. A network without some sort of shared resource or email configuration is not that helpful. Out of the box, Windows 98 enables you to share folders (and files within them), printers, and drives. The following sections show how to set up these resources.
If you have File and Printer Sharing for Microsoft Networks installed, you can share your drives, folders, and files with other users on the network.
To set up shares for these resources, follow these steps:
FIG. 24.20 The Sharing tab includes controls for setting up shared folders.
7. Click OK to save your settings.
Shared folders appear with a small hand holding the contents of the folder. You can use these same steps to set up shares to drives.
To share a printer, you use the Sharing tab of the printer's properties sheet. To do this, use the following steps:
FIG. 24.21 You can share a printer using the Sharing tab.
A hand holding a printer icon appears to indicate that the printer is now shared.
If you're connected to a peer-to-peer Microsoft Network, you can use another user's printer across the network. If someone else on your network has designated his or her printer, for example, as a shared resource and designated you as having access to that resource, you can print to that printer from any of your Windows applications.
Installing a network printer is similar to installing a printer connected to your own computer. To install a network printer, follow these steps:
Windows 98 supports deferred printing (also known as offline printing), which enables you to create print jobs when your computer is not physically connected to a printer. When you do connect to a printer, the print jobs are then sent from your PC to the printer.
To use deferred printing, the printer to which you want to print is usually set up as a network printer. Deferred printing is set up automatically for your portable computers when you are not connected to the network printer and you send a print job to it.
You also can turn on deferred printing manually from the Printers folder. Open this folder by choosing Start, Settings, Printers. Select the network printer and choose File, Work Offline. A check mark indicates that the Work Offline command is turned on. The printer icon in the Printers folder also becomes dimmed when the Work Offline command is turned on.
TIP: Even if your printer is not on a network, you can defer print jobs until later. To defer a print job on a standalone computer (that is, a computer that never is connected to a network), navigate to the Printers folder and select the printer on which to defer print jobs. Choose File, Pause Printing. Jobs you send to this printer will now be held until you're ready to print them. At that time, choose File, Pause Printing again to turn off the Pause Printing command. Your print jobs will begin printing.
After you have deferred printing set up, you send print jobs to the deferred printer as you do any other printer. When you get back to the office and reattach to the network, open the Printers folder and deselect Work Offline. Windows sends your print jobs to the printer.
Adding a shared fax modem from your network is similar to adding a regular modem (one that is connected to your computer system) to the Microsoft Fax server. The Microsoft Fax configuration program is started from the Control Panel Mail and Fax sheet. Select the Microsoft Fax profile and click the Properties button to begin configuring this service.
CAUTION: You must have the Microsoft Exchange or Windows Messaging service installed in Windows 95 and then upgrade to Windows 98 to have the shared fax modem service available. See Appendix B, "Configuring Windows Messaging and Microsoft Fax," for more information.
On the Microsoft Fax properties sheet, select the Modems page to configure the network modem. Click the Add button to add a new modem to the fax service. This brings up the Add a Fax Modem dialog box, which asks you to specify the type of modem you are adding. You should select Network Fax Server.
You now need to enter the shared fax folder in the usual \\COMPUTER\FOLDER form. If you are not sure of the computer or folder name, ask your network administrator.
After you have specified the network fax folder, you should be able to use the Microsoft Fax service.
NOTE: If you use Microsoft Exchange or Microsoft Messaging as your primary fax software, faxes you receive on a shared fax modem are not automatically routed to the proper recipient. Instead, the fax messages are saved on the machine that receives them, and the administrator or other user must manually distribute the faxes to each recipient, such as by electronic mail.
CD-ROM drives that are shared on the network are mounted just like any other directory shared on your network. You can mount a shared CD-ROM drive by choosing Tools, Map Network Drive in the Explorer. The system prompts you for the machine name and share name; if you don't know these, open the Network Neighborhood and look for the machine that has the CD-ROM shared on it.
After you have found the machine and the share name, you can mount the CD-ROM on your system. It appears as a new drive letter and can be accessed from the Explorer or My Computer icon. You can specify the drive letter on the Map Network Drive sheet.
© Copyright, Macmillan Computer Publishing. All rights reserved.