Chapter 10

Configuring Windows 95 Clients for Networking

Previous chapterNext chapterContents


In this chapter you learn how to

An ideal workstation operating system installs and configures the network client software and interface cards automatically, supports a wide variety of network transport protocols, provides a single unified logon to servers running different network operating systems, and accommodates virtually all existing hardware and software for Intel-based PCs. Microsoft Windows 95 meets all of these criteria. Although Windows 95 is not yet perfect, it's the most versatile operating system now available for networked PC clients, especially laptop and notebook PCs, as well as desktop PCs equipped with legacy adapter cards. (Microsoft defines legacy devices as hardware components that don't support Windows 95's Plug-and-Play standards.)

With multisite, multiplatform internetworks becoming common, and user demands for Internet access increasing, network administrators increasingly find that they must deal with multiple network transport protocols. The Internet and most private intranets run over TCP/IP, your legacy NetWare servers understand only IPX/SPX, and the peer-to-peer network down the hall uses NetBEUI. Your NetWare servers run NetWare Core Protocol (NCP), and your Windows NT servers run Server Message Block (SMB). The folks in sales need PPP dial-up networking. Tying all these diverse systems and protocols together requires a client operating system that allows you to support all these protocols simultaneously and still have enough memory left to run applications. Windows 95 fulfills this requirement.

Windows 95 Networking Features

Many network managers eagerly anticipated the retail release of Windows 95 on August 24, 1995. Windows 95 promised to eliminate most of the client-side problems that have plagued LAN administrators for years. Its built-in support for many networks and its extensible architecture provided these important networking features:

See "Calling Remote Procedures," (Ch 3)

Installing Network Support

If Windows 95 is installed on a client PC that already has a network interface card installed and is connected to an active network, the Setup program recognizes the situation and makes the decisions necessary to automatically install and configure Windows 95 to provide network services. If you need to convert a stand-alone PC running Windows 95 to a network workstation, you can easily modify your existing Windows 95 configuration to provide network services. Adding network support to a Windows 95 client is done from Control Panel's Network tool, and requires the following steps:

  1. Install a network adapter in the workstation and configure Windows 95 to recognize it. If both the workstation BIOS and the network adapter are Plug-and-Play compliant, Windows 95 will recognize the newly installed adapter and configure itself and the adapter automatically. Otherwise, you may have to install and configure the appropriate drivers manually.
  2. Install the client software for one or more network operating systems.
  3. Fill out the information required in the Identification page of the Network property sheet, providing a unique name for the workstation, identifying the workgroup to which it belongs, and providing a description for the workstation.
  4. Fill out the information required in the Access Control page of the Network property sheet, if the workstation shares file or print resources on the network.

When you've completed these steps, you've installed basic network support for Windows 95. The following sections describe each step in detail. Customizing the client software, installing and configuring protocols, and enabling other network services are covered later in this chapter.

Installing Network Interface Cards

When you install Windows 95, you can choose to have Setup locate installed network adapter cards. Windows 95 includes a large database of information about hundreds of popular NICs and their default settings. If a NIC is installed in the client, chances are that Windows 95 can automatically locate the NIC and load the proper drivers for it during the installation process.

If automatic identification fails, if you need to change settings for an installed adapter, or if you need to install a new adapter, you can do so from Control Panel's Network tool. Unlike earlier Windows versions, which required that some network settings be changed by manually editing text files in various locations, Windows 95 centralizes all network installation and configuration functions within Control Panel's Network tool.

To install a NIC manually, proceed as follows:

  1. Double-click Control Panel's Network tool. The Network property sheet appears with the Configuration page active (see fig. 10.1).

    10.1

    The Configuration page of Control Panel's Network property sheet.
  2. Click the Add button. The Select Network Component Type dialog appears (see fig. 10.2) from which you can add a client, an adapter, a protocol, or a service.

    10.2

    Selecting the network adapter in the Select Network Component Type dialog.
  3. Select Adapter and click the Add button to display the Select Network Adapters dialog (see fig. 10.3). From the Manufacturers list on the left, select the manufacturer of the adapter you're installing. A list of supported network adapters from the selected manufacturer appears in the Network Adapters list on the right. Select the appropriate adapter and click OK to install the drivers for the selected adapter.

    10.3

    Installing the drivers for a NIC in the Select Network Adapters dialog.
  4. If your network adapter doesn't appear in the list, you have two alternatives:

Changing NIC Settings

If Windows 95 appears to identify your NIC correctly but you still can't communicate with the network, the most likely cause is that the IRQ, DMA, or base address of the adapter doesn't match the settings used by Windows 95. This situation doesn't arise if you're using both a PNP BIOS and a PNP NIC, because Windows 95 automatically changes NIC settings as needed. If you're using an older BIOS and/or a legacy NIC, however, Windows 95 may install the NIC using the manufacturer's default settings, which may or may not correspond with the NIC's current settings. You can correct this mismatch by altering the settings from within Windows 95 for IRQ, DMA, or base address as needed to correspond to the actual settings of the adapter.

To view and change settings for your network adapter, proceed as follows:

  1. From Control Panel, double-click the System tool to open the System Properties sheet.
  2. Click the Device Manager tab to display the Device Manager page (see fig. 10.4).
  3. Click the + icon next to the Network Adapters item to show installed network adapters. Highlight the adapter to be viewed or changed (see fig. 10.5).

    10.4

    The Device Manager page of the System Properties sheet.

    10.5

    The Installed Network Adapters page of the System Properties sheet.
  4. Click the Properties button to display the property sheet for that adapter (see fig. 10.6). The General page shows basic information about the adapter, including type, manufacturer, and version.
  5. It also shows status information in the Device Status section. This section should always display the message This device is working properly. If another message appears here, your network adapter may be inoperable or misconfigured.
  6. If you use multiple hardware configurations, the Device Usage section allows you to select one or more boxes to indicate which configuration(s) this device should be used for.

    10.6

    The network adapter property sheet for an NE2000-compatible NIC.
  7. Click the Resources tab to display information about the IRQ, base memory address, and other resources used by the network adapter (see fig. 10.7). If your network adapter was detected automatically when you installed Windows 95, the Use Automatic Settings check box is marked, and the settings for each resource type are disabled. You must clear this check box before making any changes to the resource settings.
  8. At the bottom of the adapter's property page is the Conflicting Device List. If there are no conflicts, you may safely leave the settings as they are. If the Conflicting Device List shows one or more devices whose settings conflict with those of your network adapter, you must change settings for either the network adapter or the conflicting device in order to eliminate the conflict.


10.7

The network adapter resources page for an NE2000-compatible NIC.

Using the same settings for all network adapters makes it easier to maintain your network. Many network adapter manufacturers and many users have standardized on using IRQ 10 and Base Memory Address 300H for just this reason. On most computer systems, these values aren't already in use by other devices. For this reason, if a conflict arises between a network adapter set to these values and another device, it's usually better to change the settings for the other device and leave the network adapter as is.

Installing and Removing Network Clients

Windows 95 makes several default choices for a NIC, whether the NIC is automatically installed during Windows 95 installation or installed manually later. IPX/SPX (NWLink) and NetBEUI transport protocols are both installed, allowing the client workstation to operate with Windows NT Server, Novell NetWare, and Microsoft peer-to-peer (workgroup) networks. The Client for Microsoft Networks is installed as the Primary Network Logon. The Client for NetWare Networks is installed as a secondary client. These default choices are designed for the most common network environments.

There are two common reasons to change these default selections:

The following sections describe how to add and remove network client drivers.

Installing a Network Client.

In addition to the Client for Microsoft Networks and the Client for NetWare Networks, Windows 95 provides client drivers for Banyan VINES, FTP Software NFS Client (InterDrive 95), Novell 16-bit ODI NetWare, and SunSoft PC-NFS. Additional client driver packages and updates are also available on diskette from third parties. To install one of these additional network clients, follow these steps:

  1. From the Network property sheet, click Add to open the Select Network Component Type dialog (see fig. 10.8).

    10.8

    Selecting a network client in the Select Network Component Type dialog.
  2. Highlight Client and click Add. In the Select Network Client dialog, highlight the client you want to install and click OK (see fig. 10.9). Alternatively, you may install a third-party network client from disk by clicking Have Disk and following the prompts. In either event, you're returned to the main Network property sheet, where you continue setup and configuration.

    10.9

    Selecting a network client to add.
  3. The NetWare client software supplied with Windows 95 works well in a Novell NetWare 3.1x environment, but lacks support for NetWare Directory Services (NDS) used with NetWare 4.x servers. Until recently, if you needed NDS support, your only alternative was to run 16-bit real-mode Novell drivers under Windows 95, with additional memory consumption and performance penalties.

    Better alternatives are now available. Novell supplies a native 32-bit Windows 95 NetWare client that includes NDS support. Microsoft supplies Service for NetWare Directory Services, an update that's installed as a service.

Novell released in mid-February 1996 the NetWare Client 32 for Windows 95. This full-featured client software is available in two versions. The first version, a 4.6M file named c3295n_1.exe, is intended for installations from a local or network hard drive. The second version, a 5.6M file named c3295d_1.exe, can be used to create a diskette installation set. Both files are dated February 5, 1996. An 800K supplemental update file named c3295d.exe dated July 19, 1996, is also available in the same folder.

You can download either version of the NetWare Client 32 for Windows 95 from CompuServe (GO NWCL32). The two versions also are available on the Web at http://netwire.novell.com/, or via anonymous FTP at ftp.novell.com in the /pub/updates/nwos/nc32w952/ folder. A supporting 43K file named c32faq.exe includes a list of frequently asked questions and the corresponding answers. You also can purchase the client software on diskette for $99 from authorized Novell resellers.

Some users of the Novell NetWare Client 32 for Windows 95 dated February 5, 1996, have reported stability and compatibility problems with this release. Novell has acknowledged the problems.

The Microsoft Service for NetWare Directory Services is installed as a service that enhances the functionality of the original Client for NetWare Networks included with Windows 95. You can download the required files from the Web at http://www.microsoft.com/windows/software/msnds.htm.

Microsoft's Service Pack 1 for Windows 95 includes an update to Shell32.dll that lets you browse NetWare Directory Service printers from the Add Printer wizard. This update is applicable only if you've installed Microsoft's Service for NetWare Directory Services.

Service Pack 1 also fixes a potential security problem when using Windows 95's file and printer sharing that's described later in the "File and Printer Sharing for Microsoft Networks" section. You can download Service Pack 1 from http://198.105.232.5/windows/software/servpak1/sphome.htm. A complete list of the fixes in Service Pack 1 is included in the "Updating Shared Files with Service Packs" section near the end of this chapter.

Removing a Network Client.

You should remove a network client that's not being used, because extra clients consume resources and slow performance. To remove an extra network client in the main Network property sheet, highlight the unused network client and click Remove. The unused network client driver is removed immediately.

Completing the Identification Page

The Identification page of the main Network property sheet contains information about the client and the workgroup to which the client belongs (see fig. 10.10).


10.10

The Identification page of the Network property sheet, including the computer name and description, and the workgroup to which it belongs.

The Identification page consists of these elements:

Completing the Access Control Page

If a client shares its local file and print resources with other workstations on the network, the Access Control page of the Network property sheet is used to specify how permission to access these resources is determined (see fig. 10.11).


10.11

The Access Control page of the Network property sheet, which lets you specify share-level access control or user-level access control to determine which network users can access shared resources on your computer.

Share-Level Access Control.

Share-level access control allows each shared resource on the workstation to be protected by a workgroup password. Using Explorer, you right-click a local folder name and choose Sharing to specify whether that folder is to be shared. If the folder is shared, you may specify the following access security options:

Access to shared local printers is specified in a similar manner. Share-level access control may be used with file and printer sharing for Microsoft Networks. This feature isn't available if you're using file and printer sharing for NetWare Networks.

User-Level Access Control.

User-level access control allows a user seeking access to shared resources to be validated using the account information stored for that user on a Windows NT domain or on a Novell NetWare server.

When you select User-Level Access Control, the Obtain List of Users and Groups From text box is enabled. If you're using file and printer sharing for Microsoft networks, enter the name of a Windows NT domain or an individual Windows NT server here. If you're using file and printer sharing for NetWare Networks, enter the name of a NetWare 3.1x server, or the name of a NetWare 4.x server running in bindery emulation mode.

When a user attempts to access a shared resource on the local system, Windows 95 first validates that user with the specified server. If the user has no account on the specified server, he is refused access to the shared resource. If the user has an account on the server, Windows 95 then determines that user's access rights to the local shared resource.

Granting access with user-level access control is done in similar fashion as the preceding method for share-level access control, but with a further refinement. Share-level access control limits access based solely on a user's possession of the password for that shared resource. User-level access control adds an access control list (ACL), which allows access to a shared resource to be specified by individual user name and by groups. Either full or read-only access to a particular shared resource can be granted, with the access method determined separately for each user and group. User-level access control also allows you to refine access levels by defining custom access for specific users or groups.

Unlike share-level access control, user-level access control may be used with both file and printer sharing for Microsoft Networks or file and printer sharing for NetWare Networks.

Configuring Network Clients

By default, Windows 95 installs both the Client for Microsoft Networks and the Client for NetWare Networks. For most networks, these clients operate properly when installed with the default settings. Common configuration items can be changed by using Control Panel's Network property sheet for the client in question. Changes that affect the low-level operation of the client aren't usually needed. When low-level changes are needed, you make the modifications by using the System Policy Editor or by altering values in the Windows 95 Registry.

Configuring the Client for Microsoft Networks

The Client for Microsoft Networks Properties sheet contains a single page with the following sections (see fig. 10.12):


10.12

Configuring the Client for Microsoft Networks.

Configuring the Client for NetWare Networks

The Client for NetWare Networks uses the NWLink IPX/SPX compatible transport protocol exclusively, and normally requires little configuration. Compared with using native Novell client software, the biggest change that most users will notice is that the Client for NetWare Networks doesn't support the Novell NWPOPUP utility. Microsoft supplies WINPOPUP as a substitute. Like NWPOPUP, WINPOPUP allows users to send messages to and receive them from each other. Unlike NWPOPUP, WINPOPUP doesn't respond to NetWare system messages, such as new mail notifications, by popping up a message box over the running application.

The General page of the Client for NetWare Networks Properties sheet lets you set logon parameters for the NetWare server (see fig. 10.13).


10.13

The General page of the Client for NetWare Networks Properties sheet.

Specify the following items on the General page:

To ensure that workstations with various hardware configurations can use consistent network drive letter assignments, you should leave room for additional local drives by setting this parameter to a higher drive letter than F. Many organizations use H as the first network drive letter, assigning it to the user's Home folder as a mnemonic. Using H as the first network drive provides room for three or four local fixed-disk drive volumes, a CD-ROM drive, and a removable disk drive.

The Advanced page of the Client for NetWare Networks Properties sheet lets you select a Value from a drop-down list for each Property displayed (see fig. 10.14).


10.14

The Advanced page of the Client for NetWare Networks Properties sheet.

Setting the Primary Network Logon

The Primary Network Logon determines which client software handles startup functions, such as user authentication and running logon scripts. By default, Windows 95 sets the Client for Microsoft Networks as the Primary Network Logon. You can set one of the other installed network clients as your Primary Network Logon if you prefer your startup functions to be performed by that client. You also can select Windows Logon as your Primary Network Logon, if you prefer not to connect automatically to the network each time you start Windows 95.

To specify your preferred Primary Network Logon, select the client in the Primary Network Logon drop-down list of the Network property sheet (see fig. 10.15) and click OK. The Network property sheet closes and the System Settings Change message box appears, informing you that changes don't take effect until the next time you start Windows. Click Yes to restart Windows immediately and put your changes into effect.


10.15

Setting the Primary Network Logon with the Network property sheet.

Configuring Network Protocols

One of Microsoft's objectives for Windows 95 was to minimize the need for user intervention to configure network protocols. In most cases, Windows 95's default configuration for the protocols you choose are satisfactory. If not, the following sections describe how to configure Windows 95's network protocols manually.

Configuring NetBEUI

NetBIOS Extended User Interface (NetBEUI) is a fast and simple transport protocol used by Windows for Workgroups 3.1+ and other DOS and Windows peer-to-peer LANs. NetBEUI packets don't contain network header information, so NetBEUI isn't routable; thus, NetBEUI is inappropriate for large networks. If Windows 95 detects the presence of NetBEUI on the network during installation, the Setup program automatically installs NetBEUI support. You normally don't need to make changes to the NetBEUI configuration.

To display the NetBEUI Properties sheet for the network, select the NetBEUI entry that's bound to your NIC and click the Properties button. (Alternatively, double-click the NetBEUI entry.) The NetBEUI Properties sheet displays the Bindings page (see fig. 10.16). If you don't plan to share your files or a printer attached to your computer with other members of your workgroup using NetBEUI, click the File and Printer Sharing for Microsoft Networks entry to clear the check box.


10.16

The Bindings page of the NetBEUI Properties sheet.

The Advanced page of the NetBEUI Properties sheet (see fig. 10.17) lets you specify values for Maximum Sessions and NCBS for the real-mode NetBEUI driver. These tuning parameters affect only the real-mode driver, which Windows 95 normally doesn't use. The protected-mode NetBEUI driver is configured dynamically.


10.17

The Advanced page of the NetBEUI Properties sheet.

The Set This Protocol to Be the Default Protocol check box, if selected, sets NetBEUI as the default protocol. This option should always be deselected if your network includes Windows NT Server or NetWare servers. It should be selected only if you're running a peer-to-peer network, and only then if that network includes workstations that aren't running Windows 95.

Configuring NWLink

NWLink is Microsoft's implementation of the IPX/SPX transport protocol originally developed by Novell for NetWare. The default transport protocol used by Windows NT Server, NWLink is fully interoperable with IPX/SPX running on NetWare servers and clients. Windows 95 installs the NWLink protocol automatically when the Client for NetWare Networks is installed, because the Client for NetWare Networks uses the NWLink protocol exclusively. NWLink can also be used to support other client software, including the Client for Microsoft Networks.

Most client PCs require few or no changes to the default settings for NWLink. If the client is running Novell client software when Windows 95 is installed over an existing Windows 3.x installation, the setup program configures Windows 95 NWLink settings to correspond to the settings specified in the Novell NET.CFG configuration file.

The Bindings page of the IPX/SPX-Compatible Protocol Properties sheet lets you specify which clients and services use NWLink transport (see fig. 10.18). For better performance, clear the check boxes for network components that don't need to use NWLink.


10.18

The Bindings page of the IPX/SPX-Compatible Protocol Properties sheet.

The Advanced page of the IPX/SPX-Compatible Protocol Properties sheet lets you specify parameters that affect the low-level functioning of the NWLink protocol (see fig. 10.19). With one exception (Frame Type), these values are set dynamically and shouldn't be changed.


10.19

The Advanced page of the IPX/SPX-Compatible Protocol Properties sheet.

If an otherwise functional Windows 95 network workstation can't see a NetWare server on an Ethernet network, the problem is almost certainly a frame type mismatch. NetWare can use any of four Ethernet frame types: Ethernet_802.2, Ethernet_802.3, Ethernet_II, and Ethernet_SNAP. The frame types being used by the server and the workstation must be identical for communication to take place.

The Windows 95 IPX/SPX protocol defaults to frame type Auto, which usually succeeds in detecting the frame type being used by the NetWare server. If auto detection fails, you must explicitly set the frame type in the Advanced page of the IPX/SPX-Compatible Protocol Properties sheet. You can set the frame type to the following values: Auto, Ethernet 802.2, Ethernet 802.3, Ethernet II, Token Ring, or Token Ring SNAP.

NetWare 3.11 and earlier servers default to the Ethernet_802.3 frame when using Ethernet. The corresponding Windows 95 frame type is Ethernet 802.3. NetWare 3.12 and higher servers default to Ethernet_802.2 frames, for which the corresponding Windows 95 frame type is Ethernet 802.2.

For an Ethernet network, Novell recommends using the Ethernet_802.2 frame type, and Microsoft recommends that Windows 95 be set to frame type Auto. Both recommendations are wrong.

Ethernet 802.2, which is the most recent standards-based Ethernet frame, uses the OSI 802.2 LLC specification. Ethernet II is an older specification, which was originally developed by Digital Equipment, Intel, and Xerox. Newer isn't always better, however. The majority of Ethernet traffic worldwide still uses Ethernet II frames. All active components understand how to handle Ethernet II frames. On the Internet, Ethernet II always works. The same can't be said for Ethernet 802.2.

If your workstations need Internet access, if your network includes a UNIX host, or if you plan to use SNMP management on your NetWare servers, run Ethernet II. Even if you have no current need for these services, using Ethernet II now makes the transition to these services easier. There are no performance penalties or other drawbacks to using Ethernet II instead of Ethernet 802.2. Set your Windows 95 frame type to Ethernet II and add Ethernet_II frame support to each of your NetWare servers.

The NetBIOS page of the IPX/SPX-Compatible Protocol Properties sheet lets you enable the use of NetBIOS over IPX/SPX (see fig. 10.20). Windows 95 workstations can communicate with each other, and with Windows NT Server and NetWare servers directly, by using only the NWLink protocol. However, some network applications, such as IBM/Lotus Notes, require NetBIOS to communicate. Disable NetBIOS over IPX/SPX support unless you have applications that specifically require NetBIOS.


10.20

The NetBIOS page of the IPX/SPX-Compatible Protocol Properties sheet.

Configuring TCP/IP

Windows 95 doesn't install support for the TCP/IP transport protocol by default. If your network includes UNIX hosts, or if your clients need access to the Internet, you must install TCP/IP support as described earlier in the "Installing a Network Client" section. After TCP/IP is installed, you must configure the protocol. TCP/IP is designed for use in internetworks and requires that the administrator have both a deeper understanding of the protocol and the willingness to configure and manage the protocol.

See "Integrating Windows NT Server with UNIX," (Ch 17)

The following sections describe how to configure the TCP/IP protocol by using the six pages of the TCP/IP Properties sheet.

Allocating an Internet Protocol Address.

The IP Address page of the TCP/IP Properties sheet lets you specify how your workstation is allocated an Internet Protocol (IP) address (see fig. 10.21).


10.21

The IP Address page of the TCP/IP Properties sheet.

Following are the parameters that you can specify in the IP Address page:

Use extreme care when you enter the IP Address and Subnet Mask values. If either value is entered incorrectly, problems ranging from subtle address conflicts to a network crash will result.

Using the Windows Internet Naming Service.

The WINS Configuration page of the TCP/IP Properties sheet (see fig. 10.22) lets you specify whether this client uses the Windows Internet Naming Service (WINS) and, if so, which server or servers provide WINS. For more information about WINS, see Chapter 17, "Integrating Windows NT with Heterogeneous Networks."


10.22

The WINS Configuration page of the TCP/IP Properties sheet.

You can set the following parameters in the WINS Configuration page:

Specifying a TCP/IP Gateway.

The Gateway page of the TCP/IP Properties sheet lets you add and remove gateways used by the Windows 95 client (see fig. 10.23). The term gateway can be used in two ways: In the OSI Reference Model, gateway refers to a device that translates upper-level protocols. In the Internet community, gateway refers to a router. (Microsoft uses gateway to refer only to a router.)


10.23

The Gateway page of the TCP/IP Properties sheet.

See "Routers," (Ch 5)

Enter the IP address of the gateway and click the Add button to add a gateway to the Installed Gateways list. To remove an installed gateway, highlight the entry and click the Remove button.

The first gateway appearing in the Installed Gateways list is the default, which is used when available. If the default gateway is unavailable, Windows 95 attempts to access other installed gateways in the order in which they appear in the Installed Gateways list.

Binding the TCP/IP Protocol to Clients and Services.

The Bindings page of the TCP/IP Properties sheet lets you specify which clients and services use the TCP/IP transport protocol (see fig. 10.24). For better performance, clear the check box next to clients and services that don't need to use TCP/IP transport.


10.24

The Bindings page of the TCP/IP Properties sheet.

The Client for Microsoft Networks normally should be bound to TCP/IP. File and printer sharing for Microsoft Networks should be bound to TCP/IP only if you plan to use these services across a TCP/IP-based internetwork.

Setting Low-Level TCP/IP Parameters.

The Advanced page of the TCP/IP Properties sheet lets you alter low-level TCP/IP configuration parameters and specify TCP/IP as your default protocol (see fig. 10.25).


10.25

The Advanced page of the TCP/IP Properties sheet.

Selecting the Set This Protocol to Be the Default Protocol check box causes Windows 95 to use TCP/IP transport as the default. Most installations that support TCP/IP use TCP/IP as the default protocol.

Using the Domain Name Service to Resolve IP Addresses.

The DNS Configuration page of the TCP/IP Properties sheet (see fig. 10.26) lets you enable or disable the use of Domain Name Service (DNS) to resolve IP addresses and, if DNS is enabled, to provide DNS configuration information to the client. DNS translates character-based addresses, such as server names, to numeric IP addresses.


10.26

The DNS Configuration page of the TCP/IP Properties sheet.

The DNS Configuration page offers the following settings:

  • Disable DNS, if selected, causes the client not to use DNS to resolve IP addresses.
  • Enable DNS, if selected, causes the client to use DNS to resolve IP addresses.
  • Host is the name of the client computer system-for example, AR_1.
  • Domain is the Internet domain-not to be confused with the Windows NT domain, of which the client is a member. In figure 10.26, the client is a member of the ttgnet.com Internet domain.
  • The DNS Server Search Order section lets you add and remove the IP addresses for one or more servers that provide DNS services. The IP address that appears first in this list is the primary DNS and is used whenever the device at the address is available. The IP address that appears second in the list is the secondary DNS and is used only if the primary DNS device is unavailable.
  • The Domain Suffix Search Order section lets you add and remove Internet domains to be searched. This feature allows partially qualified names to be resolved. For example, if your primary Internet domain is widget.com but you frequently access a host named NTS that belongs to the domain gadget.com, specifying gadget.com as a secondary search domain allows that host to be resolved when specified simply as NTS rather than as NTS.gadget.com.
  • Installing File and Printer Sharing

    Windows 95 offers two ways to share your local files and printers with other clients on the network. If the client runs the Client for Microsoft Networks, you can install the Server Message Block (SMB) file and printer sharing for Microsoft Networks. If the client runs the Client for NetWare Networks, you can install the NetWare Core Protocol (NCP) based file and printer sharing for NetWare Networks. Only one of these services can be installed on a client. The following sections describe how to set up file and printer sharing on both types of networks.

    File and Printer Sharing for Microsoft Networks

    File and printer sharing for Microsoft Networks lets you share the local disk and printer resources of a client with any other computer on the network that supports SMB services, including systems running Windows NT Server and Workstation, Windows for Workgroups 3.11, LAN Manager, and DEC PATHWORKS. Using file and printer sharing for Microsoft Networks requires that the client run the Client for Microsoft Networks service. If you're using user-level security, a Windows NT Server domain controller must be used to provide authentication.

    See "Understanding Domain Architecture and Security," (Ch 16)

    To install file and printer sharing for Microsoft Networks, follow these steps:

  • From Control Panel, double-click the Network tool.
  • In the Configuration page of the Network property sheet, click the Add button.
  • In the Select Network Component Type dialog, double-click Service.
  • In the Select Network Service dialog, select Microsoft in the left list. Then select File and Printer Sharing for Microsoft Networks on the right, as shown in figure 10.27. Click OK to close the open dialogs.

  • 10.27

    Installing file and printer sharing for Microsoft Networks.

    After you install file and printer sharing for Microsoft Networks, you must enable file sharing, printer sharing, or both. To enable one or both of these services, follow these steps:

  • From Control Panel, double-click the Network tool to open the Network property sheet.
  • Click the File and Print Sharing button to open the File and Print Sharing dialog (see fig. 10.28).
  • Select either or both of the check boxes of the File and Print Sharing dialog to enable file sharing, printer sharing, or both.

  • 10.28

    Enabling file and print sharing services.

    The preceding process only enables the client to provide File and Print Sharing services. You must determine which files and printers you want to share, if any, and explicitly specify sharable resources as described earlier in the "Share-Level Access Control" section. Shared resources are visible to any Microsoft Networking client that browses the network.

    In October 1995, Microsoft announced that a potentially serious security problem existed for users running file and printer sharing for Microsoft and NetWare Networks. A fix for this and other problems is included in Windows 95 Service Pack 1, mentioned earlier in the chapter. Service Pack 1 is now available as a 1.2M file named Setup.exe from Microsoft's Web site at http://www.microsoft.com/windows/software/servpak1/enduser.htm or from the Microsoft Download Service BBS. Before you install and enable file and printer sharing for Microsoft Networks or for NetWare Networks, make sure that you first install Windows 95 Service Pack 1 on the client. A complete list of the fixes in Service Pack 1 is included in the "Updating Shared Files with Service Packs" section near the end of this chapter.

    File and Printer Sharing for NetWare Networks

    File and printer sharing for NetWare Networks lets you share the local disk and printer resources of a client with other computers on networks that support Novell NetWare Core Protocol (NCP) services, including Novell NetWare for DOS and Windows-based clients, other clients running Windows 95 that use the Client for NetWare Networks, and systems running Windows NT. Using file and printer sharing for NetWare Networks requires that the client run the Client for NetWare Networks instead of the Novell-supplied client software. Share-level security isn't available with the Microsoft implementation of this service. If you're enabling user-level security, a NetWare server must be used to provide authentication.

    To install file and printer sharing for NetWare Networks, follow these steps:

  • From Control Panel, double-click the Network tool to open the Network property sheet.
  • On the Configuration page of the Network property sheet, click the Add button.
  • In the Select Network Component Type dialog, double-click Service.
  • In the Select Network Service dialog, select Microsoft in the left list. Then select File and Printer Sharing for NetWare Networks in the right list and click OK to close the dialogs.
  • As is the case for file and printer sharing for Microsoft Networks, after you install file and printer sharing for NetWare Networks, you must enable file sharing, printer sharing, or both. To enable one or both of these services, follow these steps:

  • From Control Panel, double-click the Network tool to open the Network property sheet.
  • Click the File and Print Sharing button to open the File and Print Sharing dialog.
  • Select either or both of the check boxes to enable file sharing, print sharing, or both.
  • A client that's sharing resources using file and printer sharing for NetWare advertises its availability as a peer-to-peer server and the availability of the shared resources using either Workgroup Advertising or Novell Service Advertising Protocol (SAP). The visibility of shared resources to other clients browsing the network depends both on what client software the remote computer uses and which of the two advertising methods is used by the peer server, in accordance with the following rules:

  • Another client running the Client for NetWare networks sees shared resources provided by a peer server exactly as any other shared resources on the network. If the peer server is using Workgroup Advertising, it appears in a workgroup. A peer server running SAP isn't presented as a member of a workgroup, but instead appears only when you view the entire network.
  • Another client running the Novell NETx shell or VLM redirectors sees shared resources on a peer server only if the peer server is running SAP advertising. Shared directories appear as volumes on the server, and shared printers appear as Novell print queues. If the peer server runs Workgroup Advertising, its shared resources aren't visible to clients running Novell-provided clients.
  • A potentially serious security problem exists for users running file and printer sharing for NetWare Networks. Refer to the caution in the earlier "File and Printer Sharing for Microsoft Networks" section for details.

    Managing Windows 95 on the Network

    Windows 95's network installation and administration features are a significant improvement over Windows 3.x. Like Windows 3.x, Windows 95 can be installed to a local client fixed-disk drive from distribution files stored on a network drive, or can be installed as a shared copy to run from the network server. (Using a shared copy of Windows 95 isn't a recommended practice due to the amount of network traffic-sharing Windows 95 generates.) Unlike Windows 3.x, Windows 95 provides a wealth of features intended to ease management of client configurations and of the network itself.

    Installing Windows 95 from the Network

    You can install Windows 95 to the network server by using Server-Based Setup. This process copies the Windows 95 distribution files to the network server, and allows Windows 95 clients to be installed directly from the server. After the files are installed to the server, Machine Directory Setup allows you to create machine directories, which contain files specific to the hardware configurations of particular workstations.

    Installing Windows 95 to the Server Using Server-Based Setup.

    In Windows 95, the Server-Based Setup program, Netsetup.exe, prepares the server for installing Windows 95 clients from the network. Netsetup.exe replaces the Administrative Setup procedure (SETUP /A) used in Windows for Workgroups 3.1+. The Server-Based Setup program creates and maintains shared machine directories on the server and creates setup scripts to automate the client installation process. After the Windows 95 distribution files are installed and configured on the server using Netsetup.exe, clients can run Windows 95 Setup.exe from the server to complete the local installation.

    Before beginning this procedure, make sure that you have at least 80M of free disk space on the server volume to which the Windows 95 distribution files are to be installed.

    To install a setup copy of Windows 95 on Windows 4.0 NT Server from a Windows 95 client, follow these steps:

  • From the Start menu, click Run and browse the Windows 95 CD-ROM for the program \win95\admin\NETTOOLS\NETSETUP\Netsetup.exe. Double-click Netsetup.exe and then click OK to run the program. The Server Based Setup dialog appears (see fig. 10.29).

  • 10.29

    Setting the server install path, performing machine directory setup, and making setup scripts in the Server Based Setup dialog.

  • In the Set Server Install Path section, click the Set Path button. Type the path name for the server folder in which to install the Windows 95 setup files. If the specified folder doesn't exist, you're asked whether you want to create the folder.
  • After entering the installation path, the Install button is enabled. Click Install to open the Source Path dialog (see fig. 10.30).

  • 10.30

    Selecting the type of network installation and specifying the installation path in the Source Path dialog.

  • Decide where you want shared files to be installed and indicate your choice in the Install Policy section by selecting Server, Local Hard Drive, or User's Choice:
  • If you choose Server, shared files are always run from the server, saving disk space on clients at the expense of creating substantial additional network traffic.
  • Choosing Local Hard Drive means that the shared files are installed to each client's local hard disk, occupying additional drive space but reducing network traffic.
  • Choosing User's Choice lets you decide each time Windows is installed from the network whether to run the shared files from the server or from the local hard disk.
  • Unless you have a very compelling reason to allow users to run Windows 95 shared files from the server, choose Local Hard Drive.
  • Verify that the Path to Install From entry is correct, changing the path if necessary. The Path to Install To is displayed in a text box but can't be changed at this point. (If you must change the installation path, click Cancel to return to the previous dialog and then click Change Path to respecify the path.) After verifying that all the information is correct, click OK.
  • The Create Default dialog lets you choose to accept a default setting of options that the Server-Based Setup program uses to create batch setup scripts to automate the installation process (see fig. 10.31). Unless you have a specific reason for doing otherwise, click the Create Default button.

  • 10.31

    Specifying the default option settings for server-based setup in the Create Default dialog.

  • If you choose to create defaults, the Server Based Setup Default Properties sheet appears (see fig. 10.32). This sheet displays a hierarchical listing of all policy items that can be edited for use as defaults during automated installation. After you finish editing these items, click OK to close the property sheet.

  • 10.32

    Editing default setup values in the Server Based Setup Default Properties sheet.

  • A dialog appears with a prompt to enter your product identification number. Enter the number that appears on the case of the Windows 95 CD-ROM and click OK.
  • The copy process begins (see fig. 10.33). This process copies more than 80M of files to your server drive, so make sure that you have adequate disk space available before beginning the installation. After all files are copied to the installation directory, the setup program marks the files as read-only. The program then tells you that installation is complete.


    10.33

    Progress of the copying process shown by the Copying Files message box.

    Performing a Machine Directory Setup.

    After the files are installed to the network server, you're returned to the Server Based Setup dialog. The next step is to create any needed machine directories. Although only a small subset of the Windows 95 files are specific to a particular client, these files are too large to fit on a floppy disk. If a particular client boots from a floppy drive, or is diskless and uses Remote Initial Program Load (RIPL), that client's files can be stored in a specific machine directory on the server. Files stored in a machine directory are specific to an individual client configuration. To install a machine directory, proceed as follows:

  • In the Machine Directory Setup section of the Server Based Setup dialog, click the Add button to add a machine folder using the Set Up Machine dialog.
  • At any time during this process, you can click the View button to display existing machine directories.

  • In the Set Up Machine dialog, select Set Up One Machine to create a machine directory for a single client (see fig. 10.34). Type the name of the client in the Computer Name text box.

  • 10.34

    Creating a folder for computer-specific installation in the Set Up Machine dialog.

  • Type the path name for the machine directory in the Path to Machine Directory text box.
  • Attempting to use mapped drive letter syntax, such as f:\folder, causes an error. Use UNC syntax for the directory name: \\Servername\Foldername.

  • If you want to generate a setup script for this client, select the Generate Setup Script check box.
  • To change default policy values, click Edit Script to display the Computername Properties sheet (see fig. 10.35). Edit the policies as needed for this client. When your changes are complete, click OK to return to the Set Up Machine dialog.
  • Click OK to create the machine directory, save the information, and close the Set Up Machine dialog.

  • 10.35

    Editing computer-specific setup policies in the Computername Properties sheet.

    You can select Set Up Multiple Machines in the Set Up Machine dialog to create machine directories for several similar clients simultaneously. In this case, type the path and name of a file that contains the names and directories for the group of clients for which machine directories are to be set up. The Set Up Multiple Machines selection is useful primarily for a large number of identically configured clients.

    Updating Shared Files with Service Packs.

    Microsoft has committed to releasing Windows 95 updates periodically. The first such update, Windows 95 Service Pack 1, was released in early 1996. As noted earlier in the chapter, this 1.2M update may be downloaded from http://www.microsoft.com/windows/software/servpak1/enduser.htm. For complete instructions on installing the service pack in a network environment, refer to the Admin.doc file included with the distribution file, Setup.exe.

    Windows 95 Service Pack 1 includes the following enhancements and fixes:

  • OLE32 Update fixes a potential security hole with Microsoft Office 95 applications using OLE. Previously, slack space in the application data files could contain data from deleted files, which could be viewed using Notepad or another editor.
  • Shell Update fixes a file-copy problem that could result in zero-length files when copying a file onto itself using two views of the same network resource. If you've installed the Service for NetWare Directory Services update, the Shell Update also makes it possible to browse NDS printers from the Add Printer wizard.
  • Common Dialog Update for Windows 3.1 Printer Drivers fixes problems when using 32-bit applications to print with Windows 3.1 drivers.
  • File and Printer Sharing for Microsoft Networks fixes a security hole that exists when using file and printer sharing for Microsoft Networks on a network using Samba SMBCLIENT. It also fixes a security hole when using user-level security.
  • Samba fixes a situation in which the different file-naming conventions used by Windows 95 and UNIX could cause problems. This update to Vredir traps file names that are legal UNIX file names but not legal Windows 95 file names.
  • File and Printer Sharing for NetWare Networks fixes a security hole that might have allowed unauthorized users to access restricted data.
  • Password List fixes a potential security hole that occurred when connecting to a password-protected resource and saving the password. The original distribution used an easily broken encryption method to store the passwords. This update makes the stored encrypted password almost impossible to recover by illicit means.
  • System Agent fixes Sage.dll to correct problems with floating-point calculations performed while System Agent was running.
  • Exchange updates the version of the Microsoft Exchange client shipped with Windows 95 to add various enhancements and fixes.
  • Printer Port adds support for ECP ports used by newer laser printers and fixes some minor timeout problems.
  • Setting Up User Profiles on the Server

    Many companies need to accommodate roving users-those who may log on at different workstations-by making sure that a user's personal profile is used at whatever workstation he uses to log on. This need is accommodated by storing user profile information on the network server, where it's accessible from any connected workstation. After user profiles are enabled, Windows 95 handles this process automatically, synchronizing user profile information between the server and the local hard disk.

    If your network server is running Windows NT Server, the only special requirement for handling roving users is that a home directory must exist for each such user on the server. If the server is running Novell NetWare, a mail directory must exist for the user.

    When a roving user logs into a Windows 95 client workstation, Windows 95 first examines the local hard drive and that user's home directory on the server to locate a User.dat file for that account. If a User.dat file exists for that user in both places, the most recent copy is used. If it exists in only one place, that copy is used, but is then saved to both the local and network drives. If it exists in neither place, the default is used and is then saved under that logon name to both the local hard drive and to the home directory on the server.

    If that same roving user then logs into a different Windows 95 client workstation, the process is repeated. If a User.dat exists on both the local hard drive and the server, the latest version is used, and is then saved to both the local hard drive and the server.

    Because Windows 95 always checks for multiple copies of User.dat in different locations, uses the latest version for the current session, and then saves the latest version to all locations where a User.dat was found for that user, a roving user will always be using the latest version of his User.dat. All of these processes occur automatically and transparently to the user. It's simply the way Windows 95 is designed to work. The only requirements for it to occur are as follows:

  • The user has an account and a home directory on the Windows NT server or a mail directory on the NetWare server, and
  • User profiles are enabled on the User Profiles page of the Password Properties sheet (see fig. 10.36), and either
  • Client for Microsoft Networks is the primary network logon if the profiles are to be stored on the NT Server
  • or
  • Client for NetWare Networks is the primary logon if the profiles are to be stored on a Novell server.

  • 10.36

    The Passwords Properties sheet's User Profiles page.

    A user profile is stored in the user's home directory on a Windows NT Server. Creating a user account on a Windows NT server doesn't automatically create a home directory for that user, so you must manually create the directory if that user roves.

    A user profile is stored in the user's mail directory on a Novell server. This directory is created automatically when the NetWare user is created, so no further action is needed.

    The Windows 95 Registry comprises two files-User.dat and System.dat. User.dat contains information about user settings and preferences. System.dat contains information about system hardware configuration and settings. Using user profiles allows more than one user to use the same Windows 95 system while maintaining individual settings for each user. Windows 95 updates and maintains user profile information automatically after user profiles are enabled. You can use mandatory user profiles to limit users' ability to alter desktop settings and to provide a consistent interface throughout the network, making training and client-management issues considerably easier to deal with.

    User profile information can be stored either locally on the client or on the network server. If the user profile information is stored locally, Windows 95 uses the settings for a specific user when that user logs on to that client, allowing each user of the client to have his own desktop settings and other preferences available at logon. If the user profile information is instead stored on the network server, a user can log on to any Windows 95 client running a 32-bit protected-mode client and still be presented with his preferred settings.

    Because user profiles store only user information and not system information, various client hardware configurations are each handled by the local System.dat file specific to the individual client, whereas desktop settings and other user-specific information are retrieved from the user profile information of User.dat stored on the server's home directory for the user.

    Using System Policies

    System policies are defined in a policy file stored on the network server. When a user logs on, local Registry values are superseded by those stored in the system policy file. Using system policies lets you enforce mandatory system configurations and control what users are permitted to do and change on the desktop. You can use system policies to standardize such network settings as client and protocol configurations and peer-based resource sharing.

    You can create and change system policies by using the System Policy Editor, Poledit.exe (more commonly called PolEdit). You can use PolEdit to change Registry settings on either a local or remote computer. You can create a standardized set of Registry settings, store them in a system policy file, and then use this to standardize the Registry on many systems. You can apply these system policy settings individually or to groups already defined on a Windows NT Server or a NetWare server.

    Installing the System Policy Editor.

    PolEdit isn't installed by default when you install Windows 95. To install PolEdit on a Windows 95 management client, proceed as follows:

  • Double-click Control Panel's Add/Remove Programs tool to open the Add/Remove Programs Properties sheet.
  • Click the Windows Setup tab to show the Windows Setup page (see fig. 10.37).
  • Click the Have Disk button to open the Install From Disk dialog (see fig. 10.38).

  • 10.37

    The Windows Setup page of the Add/Remove Programs Properties sheet.


    10.38

    Using the Install From Disk dialog for installing Poledit.exe.

  • Click Browse and locate the admin\apptools\poledit directory of the Windows 95 CD-ROM. Two .INF files appear: grouppol.inf and poledit.inf (see fig. 10.39).
  • Select grouppol.inf and click OK. You're returned to the Install From Disk dialog with \admin\apptools\poledit\grouppol.inf specified as the Copy Manufacturer's Files From location (see fig. 10.40).

  • 10.39

    The Open dialog for installing Poledit.exe from a network drive.


    10.40

    Specifying the location of Poledit.exe in the Copy Manufacturer's Files From text box.

  • Click OK to display the Have Disk dialog (see fig. 10.41) and to choose the Components to be installed. Select Group Policies to install group-based support for system policies. Select System Policy Editor to allow setting system policies for your network. Click Install to begin installing the software.
  • When the Add/Remove Programs Properties sheet reappears, click OK to complete the installation. You're prompted to restart your computer for the changes to take effect.

  • 10.41

    The completed Have Disk dialog with Group Policies and System Policy Editor added.

    Using the System Policy Editor.

    You can use PolEdit in the following modes:

  • Registry mode lets you edit the Registry of a local or remote computer directly. Any changes you make to the Registry take effect immediately.
  • Policy File mode lets you create and modify .POL system policy files that can subsequently be used on other clients. Changes you make to a policy file take effect only when the policy file is invoked during the user's next network logon.
  • To use Registry mode to make changes to a local Registry, run PolEdit. From the File menu choose Open Registry. Two icons appear-Local User and Local Computer. Clicking Local User, which corresponds to data contained in the User.dat portion of the Registry, displays a hierarchical tree showing user items that may be edited. Clicking Local Computer similarly lets you edit items contained in the System.dat part of the Registry.

    Configuration changes are stored in the Registry. Using Control Panel tools to make Registry changes is far safer than other methods and conceals the intricacies of the Registry from the person making the changes. PolEdit permits direct editing of a subset of the Registry. The Registry Editor, Regedit.exe (also known as RegEdit), permits direct editing of the entire Registry and is the most powerful-as well as most dangerous-choice. Use the least powerful Registry editing tool that accomplishes your editing objective.

    To use Registry mode to make changes to a remote Registry, run PolEdit. From the File menu choose Connect. When prompted, enter the name of the remote computer to open that computer's Registry for editing. If you have administrative privileges on that computer, if user-level access control is enabled on the remote computer, and if the Remote Registry service is enabled on both the local and remote computers, you can edit the remote Registry as though it were local.

    To use Policy File mode to create and modify system policy files, run PolEdit. From the File menu, choose New File to create a new system policy file, or Open File to open an existing system policy file. Changes that you make to the System Policy file are saved when you exit PolEdit but take effect only when the policy file is invoked during the user's next network logon.

    Managing Windows 95 Clients Remotely

    Windows 95 provides several tools designed to allow you to manage networked clients running Windows 95 from a central management client rather than make on-site visits to the client. These remote management tools include the following:

  • System Policy Editor, described in the preceding section, lets you make direct changes to remote clients on an individual basis and to create system policy files that control the behavior of multiple clients on the network.
  • Registry Editor is another tool that you can use to make direct changes to the Registry of a remote client. Unlike the Policy Editor, which can change only a subset of Registry entries, Registry Editor has full access to the Registry.
  • System Monitor reports performance information across the network, using virtual device drivers to monitor many aspects of system performance. System Monitor is a much simpler version of the Simple Network Management Protocol (SNMP).
  • Net Watcher lets you manage shared resources across the network when you're using the peer-to-peer LAN features of Windows 95.
  • Backup agents are provided for Cheyenne ARCserve and Arcada Backup Exec to allow you to back up client files from a central server that uses Cheyenne or Arcada backup software, respectively.
  • The following sections describe how to enable remote management of clients over the network and how to use the System Policy Editor, Registry Editor, System Monitor, and Net Watcher with remote clients.

    Enabling Remote Management

    Before you can use the remote management features provided by Windows 95, you must first enable some functions on the remote clients to be managed and on the central management client. Although the specific requirements vary with the remote management features you want to use, making the following changes on the remote client provides full remote management access:

  • Enable user-level security, as discussed earlier in this chapter. Although some remote management functions are available with only share-level security enabled on the remote client, enabling user-level security gives you access to all remote management functions.
  • Enable remote administration, if necessary. If the remote client has user-level security enabled, remote administration is enabled automatically. If the remote client uses share-level security, remote administration must be enabled manually. To do so, double-click Control Panel's Passwords tool and select the Enable Remote Administration of This Server check box. For share-level security, enter a password to control access to remote administration. For user-level security, add specific users as administrators.
  • Grant remote administration privileges to the administrator. With user-level security enabled, certain users are automatically granted remote administration privileges, as follows:
  • On a Windows NT Server network, members of the DOMAIN ADMINISTRATORS group
  • On a Novell NetWare 3.1x network, the user SUPERVISOR
  • On a Novell NetWare 4.x network, the user ADMIN
  • Install file and printer sharing, as detailed earlier in this chapter.
  • Install Microsoft Remote Registry service. From Control Panel, double-click the Network tool. Click Add and choose Service. Click the Have Disk button and specify the \admin\nettools\remotreg directory on the Windows 95 distribution CD. Select Microsoft Remote Registry (see fig. 10.42) and click OK to install the remote Registry service.

  • 10.42

    Installing Microsoft Remote Registry service from the Windows 95 CD-ROM.

    In addition to the items in the preceding list, the following changes are needed on the central management client:

  • Install Remote Registry services, as described earlier.
  • Verify transport protocol support to ensure that the management client has at least one protocol (NWLink, TCP/IP, or NetBEUI) in common with each remote client to be managed.
  • Using Remote Management

    After you enable remote management, you can use the System Policy Editor, Registry Editor, and other tools to manage remote clients, as described in the following sections.

    Using Policy Editor Remotely.

    You can use Policy Editor to make changes to the Registry on a remote client. Most of these changes take effect immediately, but some require that the remote client be restarted for them to take effect.

    To use Policy Editor remotely, follow these steps:

  • Run Policy Editor and choose Connect from the File menu to open the Connect dialog.
  • In the Connect dialog, type the name of the remote client with the policy to be edited. If the proper services are installed and enabled on both your client and the remote client, and if you have the necessary permissions, the Registry of the remote client is loaded into Policy Editor. The title bar of Policy Editor shows the name of the remote client whose Registry is being edited (see fig. 10.43).
  • Make the necessary changes and save them.

  • 10.43

    Policy Editor displaying the Local User and Local Computer icons for a remote Windows 95 computer (OAKLEAF3).

    Using Registry Editor Remotely.

    Like Policy Editor, the Registry Editor can be used to make changes to the Registry of a remote client. To use Registry Editor remotely, follow these steps:

  • Run Registry Editor. From the Registry menu, choose Connect Network Registry.
  • In the Connect Network Registry dialog, type the name of the remote client to be edited. If you have the proper services loaded and permissions granted, the Registry of the remote client is loaded into Registry Editor, appearing as a branch below the existing Registry information for the local machine (see fig. 10.44).
  • Make the necessary changes and save them.

  • 10.44

    Registry Editor displaying the Registry keys of the local (OAKLEAF1, My Computer) and a remote (OAKLEAF3) Windows 95 computer.

    Using System Monitor Remotely.

    You can use the System Monitor to view performance statistics of a remote system. Using System Monitor remotely requires that the remote client have Remote Registry service installed.

    To use System Monitor to view performance statistics on a remote system, do the following:

  • Run System Monitor. From the File menu choose Connect.
  • In the Connect dialog, type the name of the remote client to be monitored and then click OK. If the necessary services are installed on both computers and if you have the appropriate permissions, System Monitor displays parameters for the remote system (see fig. 10.45).

  • 10.45

    Monitoring processor usage and file system bytes read of a remote Windows 95 computer (OAKLEAF3).

    Using Net Watcher Remotely.

    Net Watcher lets you monitor and control shared resources on the network. By using Net Watcher, you can add and delete shared resources on remote clients, display shared resources and connected users, close files left open by users, and disconnect users. Using Net Watcher to control remote clients requires that the remote clients have File and Print Sharing enabled. With File and Print Sharing enabled, a client can share resources with other clients on the network, and is referred to as a peer-to-peer server, peer server, or simply a server.

    To use Net Watcher to connect to a remote client, follow these steps:

  • Run Net Watcher and choose Select Server from the Administer menu.
  • In the Select Server dialog, type the name of the remote client (peer server) you want to control. Alternatively, click the Browse button to browse a list of available servers.
  • Type the password for the peer server you select, if necessary. You're connected to the remote client, and Net Watcher displays the default shares for the selected client in the right pane (see fig. 10.46).

  • 10.46

    Using Net Watcher to display the users sharing folders of a remote Windows 95 computer (OAKLEAF3).

    To use Net Watcher to add shared folders on a remote client, do the following:

  • After you connect to the remote client as described in the preceding steps, choose Shared Folders from the View menu to display the Shared Folders dialog.
  • Click Add Shared Folder to display the Enter Path dialog.
  • Type the name of the folder to be shared. Alternatively, click the Browse button to browse for the folder to be shared and select the drive or folder you want to share. When you click OK, the Sharename property sheet appears, with the Not Shared option selected.
  • Select the Shared As option, complete the share information (see fig. 10.47), and click OK to close the dialog. The information you supply here depends on whether you're using share-level access or user-level access, as described earlier in this chapter. (Fig. 10.47 shows the entries for user-level access.) After you complete this step, the newly shared folder is added to the Shared Folder view and is accessible to other users (see fig. 10.48).

  • 10.47

    Setting up a share on a remote Windows 95 computer (OAKLEAF3) with user-level access.


    10.48

    The additional server share (DROOT) displayed by Net Watcher.

    To use Net Watcher to remove shared folders on a remote client, follow these steps:

  • After you connect to the remote client (as described earlier in this section), choose Shared Folders from the View menu to display the Shared Folders dialog.
  • Select the folder that's no longer to be shared; click Stop Sharing Folder; and, when prompted, confirm that you want to stop sharing that folder. The shared folder is removed from the Shared Folder view and is no longer accessible to other users.
  • From Here...

    One of the primary responsibilities of Windows NT Server 4.0 network administrators is to assure that Windows 95 clients, whether desktop or portable PCs, gain the maximum possible benefit from Windows NT networking. This chapter described how to set up and administer Windows 95 clients to accommodate NetBEUI, TCP/IP, and IPX/SPX protocols. If you're migrating from Novell NetWare to a Windows NT Server 4.0 environment, Windows 95's capability to run multiple network protocol stacks without consuming conventional DOS memory is an important consideration. Combinations of NetBEUI for high-speed network communication in departmental Windows NT networks and TCP/IP for wide area networking, including access to intranets and the Internet, also is common.

    The following chapters contain information related to or complementing the content of this chapter:

  • Chapter 11, "Connecting Other PC Clients to the Network," describes how to set up Windows 3.1, Windows for Workgroups 3.1+, Windows NT Workstation 3.5+ and 4.0, and Apple Macintosh clients for networking with Windows NT Server 4.0.
  • Chapter 12, "Managing User and Group Accounts," describes how to optimize the structure of and manage client accounts on Windows NT 4.0 servers.
  • Chapter 17, "Integrating Windows NT with Heterogeneous Networks," discusses how to optimize the use of Windows NT Server 4.0 with Novell NetWare and UNIX networks, with emphasis on TCP/IP connectivity.

  • Previous chapterNext chapterContents