To ensure that LAN Manager workstations can see and access resources on computers running File and Printer Sharing for Microsoft Networks
This section presents some technical information to consider if your network includes computers running Windows NT or earlier versions of Microsoft networking products in addition to computers running Windows 98.
Microsoft Windows NT Server networks use a domain structure and provide both client/server and peer networking with user-level security. You can run Windows 98 on a Windows NT network.
For a description of the support for running logon scripts from Windows NT Server, see Chapter 18, "Logon, Browsing, and Resource Sharing." For information about installing Windows 98 as a dual-boot operating system with Windows NT, see Chapter 5, "Setup Technical Discussion."
In Windows 98, computers are grouped logically in workgroups, where each computer in the workgroup maintains its own security system for validating local user logon and access to resources. Computers in workgroups do not share security with other computers, and they do not rely on other computers to provide security. On Windows NT–based networks, computers can be grouped into domains, which allow multiple servers and workstations to be grouped for unified administration. With Windows NT domains, centralized user accounts are used to validate user logon and access to resources. Thus, if you have five users on five computers, you can configure your network so you need to create and maintain only five user accounts.
Windows 98 and Windows NT use the same workgroup model for browsing network resources, so computers running File and Printer Sharing for Microsoft Networks can appear in the same workgroup as computers running Windows NT. A computer running Windows NT will always be the master browse server (the computer that maintains the list of servers in a workgroup), but Windows 98 – based computers might act as backup browse servers.
Users running Client for Microsoft Networks can gain access to the shared resources on a computer running Windows NT if both computers are using a common protocol. For a user running Windows 98 to get to Windows NT resources, the user must have been granted access to those resources and must have a valid user name and password. For a user running Windows NT to get to Windows 98 resources protected with share-level security, the user does not need to have been granted explicit access to the resource and needs only to know the password for the resource. For a user running Windows NT to get to Windows 98 resources protected with user-level security, the user must have been granted explicit access to those resources and must have a valid user name and password.
The Microsoft Windows NT Server operating system is the high-end member of the family of Microsoft Windows operating systems, providing a powerful, reliable, and scalable operating system to support the demands of client/server computing for workstations running Windows 98 or other operating systems.
Windows NT Server provides the ideal platform for the server backbone in a mixed-network environment. It is especially versatile and powerful for enterprise networks made up of LANs that use a variety of network types and require dial-in support for network access. Also, on a peer-to-peer network on which the computers are running Client for Microsoft Networks, you can add Windows NT to the network without changing the networking software on the existing computers.
Windows NT Server is designed to support complex business applications and administrative requirements. The following list summarizes important features.
Networking and workgroup support.
Windows NT Server provides built-in file and printer sharing capabilities for workgroup computing, and an open network system interface that includes built-in support for IPX/SPX, TCP/IP, NetBEUI, and other protocols. Windows NT Server also provides administrative tools for controlling network services, auditing system events, changing hardware configuration and system performance, managing and backing up disks, and so on. Additionally, Windows NT provides robust support for server-based and client/server applications.
Interoperability.
Windows NT Server is compatible with such networks as Windows 98, Novell NetWare, Banyan, UNIX, LAN Manager 2.x, and Microsoft Windows for Workgroups. Windows NT Server can add value to your current network environment without disruption. Even though networks and interoperability are complicated, a Windows NT network is easy to use and reliable, with automatic configuration provided wherever possible and remote administration available for most administration tasks.
A single network logon.
With Windows 98 with Windows NT Server, users can gain access to network resources, including client/server applications, using one user account and one password per user.
Centralized management of user accounts.
Using Windows 98 with Windows NT Server, network administrators can work from a single computer across divisions, departments, and workgroups.
Advanced data-protection features.
Using Windows NT Server, network administrators can take advantage of such features as disk mirroring, disk striping with parity (RAID 5), and uninterruptible power supply support.
Remote Access Service (RAS).
Users can gain access to network resources even when they are off-site, as when traveling or working at home. They can dial in over asynchronous telephone lines or Integrated Services Digital Network (ISDN) lines to reach the network from computers running Windows 98, MS-DOS, Windows for Workgroups, or Windows NT operating systems. Using RAS point-to-point tunneling protocol (PPTP), they can also dial an Internet Service Provider (ISP) and make a secure connection to their network over the Internet. Windows NT RAS also supports X.25 networks.
Access to Apple Macintosh resources.
When Services for Apple Macintosh is installed on a Windows NT server, Macintoshes and computers running Windows 98 can work together to share files, printers, and client/server applications. Macintosh users can gain access to resources on a computer running Windows NT Server.
Microsoft licenses Windows NT Server and Windows NT Workstation separately, allowing you to purchase only the components you need to build a network solution for your organization.
To get access to Windows NT Server from Windows 98 – based workstations, you need three types of licenses:
Microsoft offers two licensing options for Windows NT Server:
A Client Access License is required whether you use client software supplied by Microsoft or software from another vendor. In particular, for each computer running Windows 98, Windows for Workgroups, Windows NT Workstation, or any client software that Windows NT Server supports, a separate Client Access License is required.
You can convert a Per Server License to a Per Seat License at no cost and without notifying Microsoft. You cannot, however, switch from a Per Seat option to a Per Server option. Also, you are not required to license all your servers using the same option.
Note
It is a violation of the terms of the Server License to use Windows NT Server without an appropriate number of Client Access Licenses. For more information, see your Server License.
Client Access Licenses are available in single-client and 20-client configurations and in volume quantities through the Microsoft Select licensing program. For more information, contact your Microsoft reseller. If you have questions, in the United States, contact the Microsoft Sales Information Center at (800) 426-9400. In Canada, contact the Microsoft Canada Sales Information Centre at (800) 563-9048. For other locations, contact your local Microsoft subsidiary.
A workgroup in Windows 98 is analogous to a LAN Manager domain, in that it is a logical grouping of workstations. However, a workgroup in Windows 98 does not share any of the advanced security features offered as part of a LAN Manager domain. Windows 98 does not support using a LAN Manager domain controller as a security provider, so only share-level security can be used for computers running Windows 98 on LAN Manager networks. (User-level security requires a Windows NT domain.)
To ensure that computers running Windows 98 can browse for LAN Manager servers, make sure that at least one computer running Client for Microsoft Networks sets its workgroup name to the LAN Manager domain name. After a computer running Windows 98 becomes a member of the LAN Manager domain, it can distribute the names of LAN Manager servers in that domain to other computers running Windows 98 on the network. The configuration must be duplicated for each LAN Manager domain.
To ensure that LAN Manager workstations can see and access resources on computers running File and Printer Sharing for Microsoft Networks
The LM Announce setting ensures that the computer running Windows 98 peer resource sharing services announces its presence to LAN Manager workstations and servers. By default, the LM Announce property is set to No to reduce broadcast traffic on the network.
Note
IBM OS/2 LAN Server supports a domain model and is equivalent to LAN Manager for interoperating with Windows 98. Just as with Windows for Workgroups, the Client for Microsoft Networks in Windows 98 does not support LAN Server aliases.
Windows 98 uses the same workgroup model as Windows for Workgroups. Therefore, computers running File and Printer Sharing for Microsoft Networks can be seen by computers running Windows for Workgroups. A computer running Windows NT or Windows 98 will always be the master browse server. For a computer running Windows 98 and Windows for Workgroups to communicate, both computers must be running a common protocol.
Shared resources on Windows for Workgroups computers are password-protected. Therefore, a user running Client for Microsoft Networks can gain access to shared resources on a computer running Windows for Workgroups only if that user knows the password.
To get to Windows 98 resources protected with user-level security, a user running Windows for Workgroups must have been granted access to those resources and must have a valid user name and password. To get to Windows 98 resources protected with share-level security, this same user does not need to have been granted explicit access to the resource and needs only to know the password for the resource.
Computers running File and Printer Sharing for Microsoft Networks can appear in the same workgroup as a computer running the peer server supported in Workgroup Add-on for MS-DOS. For a list of peer servers to be available in the workgroup, there must be at least one computer in the workgroup configured as the master browse server that is running Windows 98, Windows 95, Windows for Workgroups, or Windows NT. A computer running Workgroup Add-on for MS-DOS cannot be a master browse server.
Users running Client for Microsoft Networks can gain access to the shared resources on a computer running Workgroup Add-on for MS-DOS if both computers are using a common protocol and if the user knows the password for the resource.
To get to Windows 98 resources protected with user-level security, a user running Workgroup Add-on for MS-DOS must have been granted access to those resources and must have a valid user name and password. To get to Windows 98 resources protected with share-level security, this same user does not need to have been granted explicit access to the resource and needs only to know the password for the resource. In both cases, both computers must be running a common protocol.