Setup installs the default network configuration described at the beginning of this chapter. You can also install and configure networking support after installing Windows 98 by using the Network option in Control Panel. In the Network option, you can set properties for the following:
In the procedures presented in the following sections, it is assumed that Windows 98 and the appropriate networking hardware have already been installed on your computer. You might also need to install or configure various supporting components, such as security, mobile networking components, agents for remote administration software, and support for user profiles and system policies.
This section summarizes how to install networking support by using the Network option in Control Panel after Windows 98 is installed. Specific issues for installing various network components are discussed in other chapters of the Microsoft Windows 98 Resource Kit. The following procedures describe the general steps that are required for installing networking components.
The following procedure describes how to install a driver for a legacy network adapter card.
Important
You should not add Plug and Play – compatible network adapters manually. Instead, you should let Windows 98 detect the network adapter. If the Select Device box prompts you to select a network adapter, click the Have Disk button and type in the location of your network adapter drivers.
To install a driver for a legacy network adapter after Windows 98 is installed
Tip
You can configure network properties either from the Network option in Control Panel, or by right-clicking the Network Neighborhood icon on the desktop, and then clicking Properties on the context menu.
To install networking components after Windows 98 is installed
Table 14.1 Network component types
Component | Description |
---|---|
Client | Installs client software for the types of networks the computer is connected to. You can use either a 32-bit network client (which needs no real-mode components) or older real-mode networking clients. There is no limit to the number of 32-bit network clients you can install, but you can have only one real-mode network client installed at a time. Some clients are supported only as primary network clients. For information, see Chapter 17, "Windows 98 on Third-Party Networks." |
Adapter | Installs drivers for the network adapters in the computer. However, the recommended method for installing a new legacy adapter is to use the Add New Hardware option in Control Panel. For Plug and Play network adapters, you should let Windows 98 detect the network adapter. Then, if the Select Device dialog box prompts you to select a network adapter, you should click the Have Disk button and type in the location of your network adapter drivers. You can configure the type of driver to use (such as enhanced-mode NDIS, real-mode NDIS, or ODI), specify the resources for the adapters you are using (such as I/O, interrupt request [IRQ], and transceiver type), and define other options for the adapter. For information, see Chapter 15, "Network Adapters and Protocols." |
Protocol | Installs network protocols and sets related options. For information, see Chapter 15, "Network Adapters and Protocols." |
Service | Installs peer file and printer sharing services and other types of network services, such as Service for NetWare Directory Services, Microsoft Remote Registry, and Network Monitor. For information, see Chapter 23, "System and Remote Administration Tools." |
Note
Most network components require that you shut down and restart the computer after installing them.
You can also install and configure networking components by using custom setup scripts or system policies. For information, see Chapter 3, "Custom Installations," and Chapter 8, "System Policies."
Windows 98 requires that you define a workgroup and computer name for each networked computer, independent of the type of networking software you use. You can also change the computer name or workgroup after Setup is complete.
To specify the computer name, workgroup, and description for a computer
Table 14.2 Computer identification settings
Setting | Description |
---|---|
Computer name | The computer name must be unique on the network. It can be up to 15 characters long, with no blank spaces. The computer name can contain only alphanumeric characters, as well as the following special characters:
|
Workgroup | The workgroup name does not need to be unique, but it uses the same naming conventions as the computer name. For information about using Wrkgrp.ini for specifying the workgroup that can be selected, see Chapter 3, "Custom Installations." |
Computer Description | This information is displayed as a comment next to the computer name when users are browsing the network while viewing it in Details mode. |
Caution
Because computer and workgroup names can contain the special character %, and Msbatch.inf uses the special character % to indicate variables, Windows 98 does not behave as you expect if you use variables in Msbatch.inf for computer and workgroup names. For more information about this problem, see Knowledge Base Article Q170846, "Computer or Workgroup Name Not Set Properly Using Msbatch.inf."
You can use WinPopup to send a message to one person or to a whole workgroup. WinPopup can also display a message from someone else on your network or from a printer on a Windows NT server when your print job is done. With WinPopup, you can send and receive messages and alerts from LAN Manager, Windows for Workgroups, Windows NT, and Windows 98 servers and clients.
On a NetWare network, you can also use WinPopup to send messages in the following cases:
Note
If you are running both Client for NetWare Networks and Client for Microsoft Networks, and if the message reaches the specified computer or user through Windows 98 networking, the message is not also sent through the NetWare server.
WinPopup is installed automatically with either Microsoft Client for NetWare Networks or Client for Microsoft Networks. You can configure it to start automatically every time the user starts the computer, or you can start it manually.
To configure WinPopup to start automatically on a client computer
To start WinPopup manually
If your computer uses 32-bit, protected-mode networking components exclusively, you do not need statements in Autoexec.bat or other startup batch files to start the network when you start the computer. The installation of the correct protected-mode network client, protocol, and network adapter driver, as shown in the Network option in Control Panel, is all you need to ensure that networking is available whenever you start Windows 98.
If your computer uses any real-mode components for the client, protocol, or network adapter driver, you must include commands to start the network in Autoexec.bat or a batch file that is called from Autoexec.bat. This is because real-mode components must be inserted properly in the startup sequence to be available to other parts of the system.
For real-mode components on NetWare networks, the Net.cfg or similar file is used to start and configure networking during system startup. The user or network administrator must maintain this file. For Microsoft networks, the net start statement in Autoexec.bat is used to start any real-mode networking components.
The Protocol.ini file stores settings for real-mode networking components. The only sections that might be read are [Protman$], [netcard], and [Ndishlp$]. For information about the content of Protocol.ini, see Chapter 16, "Windows 98 on Microsoft Networks."
Windows 98 includes the Windows Scripting Host, a language-independent scripting host for 32-bit platforms. With Windows Scripting Host, scripts written with the Visual Basic Scripting Edition or JScript scripting engine, or any other language that provides a Microsoft ActiveX scripting engine can be executed directly on the Windows desktop or command console.
Windows Scripting Host supports several functions that make it easier to configure networking features on your user’s computers, such as mapping drives and printers, launching applications, modifying registry keys, and managing your users’ environment.
For more information about Windows Scripting Host, see Chapter 23, "System and Remote Administration Tools." See also http://www.microsoft.com /management/.