|
The Networking
Components of Windows 9x
Almost every company is using one ore more types of networks. Windows 9x was "born to network," and makes an excellent network client because of its flexibility and security. The improvements in Windows 9x over earlier versions of Windows may be most remarkable in the networking area. This chapter begins with an overview of the major network protocols that Windows 9x supports. Next, it describes the network architecture
of Windows 9x, explaining how it corresponds with the OSI (Open Systems Interconnection) reference model. Then you will learn how Windows 9x can function as a net-work client or server. Finally, it introduces the Network Neighbourhood, which provides easy access to network resources.
The Protocols
A Quick Overview
Networks must use some kind of protocol to communicate. The three major protocols that Windows 9x supports are TCP/IP (Transmission Control Protocol/Internet Protocol), IPX/SPX (Internet Packet Exchange/Sequenced Packet Exchange), and NetBEUI (Network Basic Extended User Interface). Support for DLC (Data Link Control) and NETBIOS (Network Basic Input/ Output System) is also available. Here is a brief overview of these protocols, which are each discussed in more detail in later chapters:
n TCP/IP: This protocol is popular for many reasons, including its open design, its non-proprietary heterogeneous support, and the Internet. TCP/ IP, and how it is installed and configured on a Windows 9x computer. Suffice it to say that every network administrator needs to be at least familiar with, if not an expert in, TCP/IP.
n IPX/SPX: This is a proprietary protocol that Novell developed for use in its NetWare networks. In the past, Microsoft called its compatible protocol NWLink; now it is called by the very inventive name "IPX/SPX compatible protocol." Almost every application that works with, and expects, Net-Ware's IPX/SPX will also work with Microsoft's IPX/SPX compatible protocol. In order to communicate with NetWare servers, the IPX/SPX compatible protocol must be installed. Installing and configuring IPX/SPX.
n NetBEUI: This protocol was developed by IBM for small, interoffice net-works. NetBEUI has severe limitations, because it was designed for up to only 254 nodes and can't be routed. Interoffice mail may be a good analogy for NetBEUI: Interoffice mail is quick and cheap inside your company, but if an envelope is put in the regular mail bin, there is no way of delivering it, since it has no address (other than the person's name) on it. This protocol is almost never used as a regular protocol, but can be useful as a dial-up protocol.
n DLC: This protocol must be used in conjunction with another protocol' TCP/IP, IPX/SPX, or NetBEUI. DLC is used to communicate with IBM mainframe computers and Hewlett-Packard (HP) JetDirect adapters.
n NETBIOS: This is not a protocol per se, but is a specification that protocols and applications can be designed to support. IPX/SPX adds support for NETBIOS via TSRs (terminate-and-stay resident programs), but Microsoft's IPX-compatible protocol, TCP/IP, and NetBEUI come with native NETBIOS support. Microsoft's networking, as well as many applications, require NET-BIOS support in order to function correctly. Last chapter discusses NETBIOS in more detail.
The Network Architecture
of Windows 9x
Networking is a very complex matter. Fortunately, it can be broken down into smaller parts to make it easier to understand.
The OSI model is one of the most prevalent models used to break down networking. First, we will review the OSI model.
Windows 9x components to their respective layers. This approach will help you understand how Windows 9x implements networking and where the various pieces fit.
The OSI Model
There are several different ways of looking at networking, just as there are several ways of looking at building a house. The OSI model is presented here because it is both a popular and well-defined model for breaking down net-working into more manageable pieces. Just as a set of blueprints for a house can be read and used by any competent contractor, the OSI model provides a blueprint for networking that can be (and usually is) followed (to one degree or another) by most major software and hard-ware companies. If you build a house, you should be able to hire any plumber subcontractor and any electrician subcontractor, and your plumbing and electricity should be installed to standard specifications and function as you expect.
The OSI model, and the standards built around it, has the same goal; that is, you should not be forced into using equipment from a particular manufacturer' you should be able to use software and hardware from any company and make them communicate. (It's a nice idea in theory, but sometimes you can still get tied to a proprietary solution.)
The OSI model, developed by the ISO (International Standardization Organization), is a conceptual framework used to describe how to connect any combination of devices for purposes of communication. Although there are other networking models developed by other organizations, the OSI model is the standard for network layered architecture and the most widely accepted model for understanding network communications. The OSI model does not perform any functions in the communication processes; this work is done by the appropriate software and hardware. The model's purpose is to define the tasks that need to be done and which protocols will handle those tasks.
The OSI model has seven layers:
n Application: The layer that the user's applications communicate with. This layer consists of API (Application Programming Interface) calls that applications can make. Its purpose is to allow transparent access to operating system or networking functions. For instance, an application shouldn't need to know which protocol or brand of network card is being used, as long as that protocol or card is compatible with Windows 9x.
n Presentation: The layer that is responsible for translating the input from the application (and thus the user) into a form that can more easily be transmitted across the network. ASCII and EBCDIC are two examples of how the alphabet can be translated into bits and bytes. This layer is also responsible for data encryption and compression.
n Session: The layer that is in charge of the big picture. It makes sure that the overall networking session happens by synchronizing and sequencing the elements (packets) in a network connection. This layer also deals with any errors that are not the network's or a protocol's fault (such as running out of paper), makes sure that the transmission is complete, and ensures that appropriate security measures are taken during the connection.
n Transport: The layer that makes sure that the packets are delivered correctly. This layer is where the connection is made for the TCP and SPX protocols.
n Network: The layer that is in charge of addressing the packets so they are delivered to the correct network. Network routers work at this level. Routers examine the destination network address and pass the packet on its way.
n Data Link: The layer that consists of the driver for the network card. This layer, often referred to as the MAC (Media Access Control) layer, helps watch for errors in the transmission and conversion of signals, and is responsible for delivering packets between computers without errors. Network bridges function at this layer. A bridge put in between two segments of the same network will examine each packet, and if the destination is on the other side of the bridge, it will let it pass; otherwise, the bridge keeps the traffic local.
n Physical: This layer consists of the network card, which is in charge of translating bits and bytes to and from electrical impulses. Network repeaters operate at this level. Their job is to boost the network signal (without doing any analysis on the signal).
One way to help remember the OSI model layers (and their order) is the saying All People Seem To Need Data Processing. Data is passed from applications down through the layers of communications until it reaches the network card and cabling system. It is then transmitted back up the network layers until it reaches the appropriate application on the receiving side.
Windows 9x and the OSI Model
Microsoft presents its networking components in a model that is similar to the OSI model.
Microsoft's model includes the following seven layers:
n Application Interface: Like the OSI model's Application layer, this layer is where the API calls are made by user applications. Windows 9x provides APIs for file access as well as printing.
n Network Providers: Like its OSI model counterpart, this layer translates the API calls into a language that other computers can understand. Windows 9x has support for 16-bit networking calls (for compatibility), as well as 32-bit providers for Microsoft, NetWare, and other servers.
n File System Interface: This layer provides a "railroad switch" function' it figures out whether a request can be fulfilled locally or needs to come from across the network. The IFS (Installable File System) manager is the Windows 9x component that fulfills this role. Windows 9x was designed so that resources look the same whether they are local or across the network.
You can see how the transparency of network access works in Windows 9x by going into Network Neighbourhood and showing the resources on your machine (something that Windows for Workgroups couldn't do). Network Neighbourhood is discussed later in the chapter.
n Redirectors and Services: Redirectors function when Windows 9x acts like a client, and services are used when Windows 9x is acting like a server or providing a function on the network.
n Transport Driver Interface: This layer allows applications, redirectors, and services to communicate via NETBIOS or socket connections. (NET-BIOS is discussed later.) The Transport Driver Interface ensures that applications have transparent access to network resources.
n Transport Protocols: This layer is where TCP/IP, IPX/SPX, and/or Net-BEUI are implemented.
n Device Driver Interface: This layer is where the software driver that comes with the network card operates. Windows 9x can use drivers written to the ODI (Open Data-link Interface, for NetWare) specification, but ODI drivers are real-mode (16-bit). Microsoft uses the NDIS (Network Driver Interface Specification) standard for network card adapters.
There are four versions of NDIS for Windows: Version 2.0, real-mode (16-bit), is the lowest type usable by Windows 9x; Version 3.0, protected mode (32-bit), is the lowest type usable by Windows NT; Version 3.1, protected mode, adds Plug and Play for Windows 9x; and Version 4.0 adds PPTP (Point-to-Point Tunneling Protocol) and better network monitor support and better network monitor for Windows NT 4.0.
Windows 9x as a Client
Windows 95 excels as a networking client. In order to understand your options when installing client software for Windows 9x, it is important to know how networking works for both Novell and Microsoft networks. There are various new features in Windows 9x that offer a compelling reason to upgrade from earlier versions. Windows 9x also works very well in mixed environments; it can easily handle two or more different types of servers concurrently.
Windows 9x Networking Features
Windows 9x has many more networking features than earlier versions of Windows, including the following:
n Graphical, standardized way of making networking changes: All networking functions can be changed from one spot' the Network Control Panel. Using the Network Control Panel to make changes is much easier than the methods available in previous versions of Windows. Use of the Network Control Panel is covered later.
n Simultaneous client connections to dissimilar servers: Although Windows3.x could connect to different types of networks, it wasn't designed from the ground up for networking, and conflicts often resulted. With the appropriate software, Windows 9x can connect to both NetWare and Microsoft servers.
n Plug-and-Play support for network adapters: Windows 9x adds this support, which makes installing and configuring network cards easier. The procedures for installing and configuring network cards are discussed down.
n Automatic reconnection of lost connections: Windows 95 will attempt to reconnect if a connection is broken. Often, the user doesn't even know the connection was broken and re-established.
n Client-side caching of network data: Windows 9x uses Vcache (the new protected-mode cache program) to cache data from the network to increase performance.
n Long filename support: Long filenames can be stored on both Microsoft and NetWare servers. NT servers automatically save long filenames. Net-Ware servers need the OS2 support enabled.
n Support for user profiles and system policies: User profiles allow more than one user to save user settings on a computer. System policies allow administrators to enforce rules on the network.
n Real-mode (16-bit) network driver support: Windows 9x can use older real-mode (16-bit) drivers if 32-bit ones are not available. This will affect performance, but at least the drivers will function
n Protected-mode (32-bit) network driver support: Windows 9x can use all protected-mode drivers for network connectivity. In this mode, networking components use no conventional memory. This allows DOS programs that are run under Windows 9x to have much more conventional RAM than they would have under DOS.
Communicating with Servers
Novell NetWare servers communicate using a language called NCP (NetWare Core Protocol). This language is spoken by both the NetWare clients and servers.
When you install the Client for NetWare Networks, you are enabling Windows 9x to communicate (using NCP) with NetWare servers. Microsoft servers communicate using a language called SMB (Simple Message Blocks). By installing the Client for Microsoft Networks, you enable Windows 9x to communicate with Microsoft (Windows NT) servers.
Windows 9x is flexible enough to have both client languages (NCP and SMB) installed at the same time. This allows Windows 9x to simultaneously communicate with both NetWare and Microsoft servers.
Using SMB or NCP is independent of which network protocol is in use. SMB and NCP are used at a higher level of the OSI model (the Application layer); protocols are used at a lower layer (the Data Link layer).
Another way to allow Windows 9x to communicate with both NetWare and Microsoft servers is to have both servers speak a common language, and install just one client on Windows 9x. A product from Microsoft, called File and Print Services for NetWare (FPNW), makes this possible. With this product installed, Windows NT servers speak the NCP language as well as their own native SMB language.
Getting Windows 9x to communicate with other types of servers (such as Banyan Vines) is basically done in the same way. By installing the appropriate client software, you allow Windows 9x to communicate with almost any server.
Computer Names and Usernames
Because Microsoft follows the NETBIOS specifications, and all Windows 9x computers could possibly be servers as well as clients, all computers are required to have a unique computer name, even if they are participating only on a NetWare network (where names are required only for servers). Computer names must be unique, and they can be up to 14 characters long.
If your computer names are not unique, upon rebooting your computer, you will get an error message stating that networking services have not been started because of a duplicate computer name. You will need to either change your computer name or find the duplicate and change that computer name.
Usernames don't need to be unique. However, any pop-up message or notification will be sent to all users who are logged in as the target recipient.
Accessing Resources with UNC
UNC (Universal Naming Convention) is a NETBIOS specification that lets you easily specify the computer and shared resource you want to access. The format of a UNC is:
\\Server\Shared_Resource
Here is a typical command:
Net Use S: \\Server\Shared Folder
This would connect the S: to the shared folder, and whenever the S: is used, it would actually be the shared folder. For example, if you typed DIR S:, you would get a directory listing of the shared folder.
Connecting a drive via a UNC is like mapping a drive under NetWare.
Most applications are now UNC-aware; that is, you can use a UNC where you would normally use a local drive and directory (when saving files, input-ting the path to new software, and so on).
Windows 9x as a Server
Besides functioning as a client, Windows 9x can also function as a server, allowing others to connect to shared drives or shared printers. Such an arrange-ment is called a peer-to-peer network. Windows 9x can perform both client and server functions simultaneously, but larger networks tend to have dedicated servers for security and performance reasons. However, small offices may have neither the budget nor the need for a dedicated server.
Windows 9x operates as a peer-to-peer server when it uses Share level security (the default). Windows 9x can also act like a dedicated server when it uses User level security. Both of these security options are discussed later.
Windows 9x can be installed as either a Microsoft or a NetWare server, not both. Only Windows NT can simultaneously be both a Microsoft and NetWare server (by using File and Print Services for NetWare to provide NCP support).
You can have Windows 9x share its resources as a Microsoft server by installing File and Printer Sharing for Microsoft Networks.
This allows both folders and printers to be shared. Installing and configuring sharing are covered in detail later.
For Windows 9x to act like a NetWare server, you need to install File and Printer Sharing for NetWare Networks. This allows NetWare clients to use the server's folders and printers. The major restriction is that a NetWare server must already be in place on the network before you can set up a Windows 9x server.
The Network Neighbourhood
The Network Neighbourhood in Windows 9x introduces an integrated way of looking at network resources as if they were merely an extension of your local computer's resources. The Network Neighbourhood presents network resources from a hierarchical viewpoint, starting with the domain or workgroup you are a member of. Network Neighbourhood can be found on the Desktop.
If you have the Explorer open, the Network Neighbourhood is shown at the same level as My Computer. You can view other domains or workgroups by choosing Entire Network.
In order to see Microsoft servers, you need the Microsoft client installed. To see NetWare servers, you need the NetWare client installed.
The Network Neighbourhood's context menu (which appears when you high-light the Network Neighbourhood and right-click) has the following options:
n Open: Presents the servers in your domain or workgroup in a folder format. You can then open a server to see the shared folders available.
n Explore: Presents the network in an Explorer fashion, and also shows My Computer and the Recycle Bin.
n Find Computer: Bypasses the browser, and allows you to see the server you are searching for, regardless of the state of the browsing service. This command is very valuable, because sometimes servers do not register themselves with the browser service, which is responsible for maintaining the Network Neighbourhood lists.
n Map Network Drive: Lets you connect a drive letter to a shared folder on the network. The drive letter will then appear in My Computer. This is the same as using the Net Use command from a DOS prompt.
n Disconnect Network Drive: Lets you disconnect a drive letter from a net-work folder.
n Create Shortcut: Makes a shortcut to the Network Neighbourhood. You can also make shortcuts to a server or a shared folder by right-dragging the server or folder to your Desktop and choosing Create Shortcut.
n Rename: Lets you rename the Network Neighbourhood.
n Properties: Brings up the Network Control Panel (same as selecting Control Panel , Network).
Summary
Windows 95 comes with full IPX/SPX, NetBEUI, and TCP/IP protocol support, which makes hooking it to existing networks, and to the Internet, a breeze. This chapter provided a brief introduction to the use of these protocols.
They are covered in more detail in the following chapters. Understanding the process of networking will help you in both supporting and troubleshooting Windows 9x systems. As you learned in this chapter, the OSI model was developed to break networking down into its basic components. Analysing networking functions based on the OSI model is a popular way to help isolate functions and understand how networks work. Microsoft has a networking model similar to the OSI model. Windows 9x networking components match up well to the OSI model.
Windows 9x can function as a network client in Novell NetWare, Microsoft, and other types of networks, and can do it simultaneously and without any conflicts. Configuring Windows 9x as an NT client is discussed here.
Windows 9x can also act like a server, allowing either Microsoft or NetWare clients access to its resources. Windows 9x can be a server for only one type of network at a time. Configuring Windows 9x as a Microsoft network server is covered later.
Whatever type of network you are connected to, the Network Neighbourhood provides easy access to available resources. The Network Neighbourhood presents network resources in a hierarchical structure, starting with your domain or workgroup.
Exercise Questions
1.Which Microsoft layer talks to the network card?
A.Device Driver Interface
B.Physical Driver Interface
C.Transport Driver Interface
D.Session Driver Interface
2.Which is not a protocol that Windows 9x supports?
A.IPX/SPX
B.Frame0
C.NetBEUI
D.TCP/IP
3.Which NDIS specification was designed for Windows 9x?
A.NDIS 2.0
B.NDIS 2.1
C.NDIS 3.0
D.NDIS 3.1
4.Windows 9x supports auto reconnect.
A.True
B.False
5.What does UNC stand for?
A.Universal Network Convention
B.Universal Naming Convention
C.Universal NETBIOS Convention
D.Universal NetWare Convention
6.Microsoft servers communicate natively with which language?
A.NCP
B.MMP
C.BTT
D.SMB
7.Windows 9x can be both a Microsoft and a NetWare client.
A.True
B.False
8.Windows 9x can be both a Microsoft and NetWare server.
A.True
B.False
9.Computer names must be unique.
A.True
B.False
10.Usernames must be unique.
A.True
B.False
11.TCP/IP can cross a router.
A.True
B.False
12.What new feature of Windows 9x lets you see network resources?
A.My Computer
B.Network Resources
C.Network Servers
D.Network Neighbourhood
Networking with Microsoft Servers
Connecting a Windows 9x computer to a Windows NT network is fairly straightforward. All of the software needed to connect Windows 9x to an NT computer is included on the Windows 9x CD-ROM, and is relatively easy to install. The major decision that must be made is whether to allow each Windows 9x computer to share its resources (acting like a server) as well as being a client on the network.
As explained in above, when computers act as both clients and servers, it is called a peer-to-peer network. Peer-to-peer networks are great for small offices (such as a dentist's or doctor's office), but with more than about six to eight computers, keeping track of all of the shares and passwords on the net-work can get rather confusing and time-consuming. After a network grows to eight or more machines, companies often find it easier to dedicate one computer to being a server (even if it can still do client functions), and let the rest of the clients be just plain clients.
In this chapter, you will learn how to install and configure the Client for Microsoft Networks software so that Windows 9x can connect to Windows NT servers. You will also learn how to allow a Windows 9x computer to share its resources. We will discuss setting up shares and selecting a security level.
Finally, we'll cover the network browsing service, which allows users to see the shared resources on the network. Windows 9x can act as a browser client and/or browser server.
Windows NT Client Installation
Microsoft servers communicate using a language called SMB (Server Message Blocks). By installing the Client for Microsoft Networks, you enable
Windows 9x to communicate with Microsoft (Windows NT) servers.
There are several steps involved in installing the client software for Windows NT:
n Check licensing agreements to ensure legality.
n Install the network card and drivers.
n Install the client software.
n Configure the network card.
n Configure the protocols.
n Configure the client software.
Each of these steps is explained in the following sections.
Licensing the Client
By purchasing Windows 9x, you have bought a license to use it on a single computer, but not necessarily on a network. If you connect the Windows 95 computer to an NT server, you will need to make sure you have a Client Access License (CAL) for each client attached.
There are two different client licensing schemes:
n Per Server: Licenses are purchased with the Windows NT Server package. These allow a certain number of simultaneous connections to that server.
n Per Seat: Licenses are purchased for each client that needs to connect to NT servers. These licenses allow the client to connect to any NT server on the network.
When you buy additional licenses, you usually just get a piece of paper that proves you are legal, in case of an audit.
Installing a Network Card and Driver
The first step in installing network support in Windows 9x is to install the physical card in the computer. If the card is an older, legacy card (its settings are made by jumpers and/or switches), you should make a note of its settings.
If the card is a Plug-and-Play variety, Windows 9x should be able to automatically detect and configure the card to the correct settings. If Windows 9x can auto detect the card, it may install the driver automatically.
You can force Windows 9x to search for new hardware by starting the Add New Hardware Wizard from the Control Panel and selecting Yes.
If Windows 9x doesn't install the driver automatically, you will need to install it manually. Start the Add New Hardware Wizard from the Control Panel, and click on the No button to tell Windows 9x not to try to detect the device. Windows 9x displays a list of hardware devices for which it has drivers. If your network card has a newer driver on a disk, click on the Have Disk button, and insert the driver disk that came with your network card. Windows 9x will install the driver from the floppy disk.
Installing the Client Software
By installing the client software, you allow Windows 9x to see and connect to Windows NT servers. You install the software through the Network Control Panel. First choose to add a client, as shown in Figure 11.3. Then pick the type of client from the Network Control Panel's Select Network Client dialog box. Follow the steps in Exercise 11.1 to install the Client for Microsoft Networks software.
If you already have the Client for Microsoft Networks software installed and you would like to practice reinstalling it, remove it, and then follow the steps in Exercise 11.1.
Configuring the Network Card
Windows 9x should detect and install the correct drivers for your network card. Every device connected to your computer needs to be assigned a unique IRQ, I/O port, and memory address (if used):
n IRQ or interrupt: This is like a doorbell that devices use to get the attention of the CPU. Every device needs a unique IRQ or your accessories may not be able to talk to the CPU. IRQs range from 0 to 15. IRQs 5, 10, 11, and 12 are commonly used for accessories.
Installing the Client for Microsoft Networks
1. Go to Control Panel , Network and choose Add.
2. Highlight Client and choose Add.
3. Highlight Microsoft in the list of Manufacturers.
4. Highlight Client for Microsoft Networks in the list of Network Clients.
5. Click on OK.
6. Reboot Windows 9x.
n I/O port: This is like a doorway that data travels through to get to and from the CPU. Every device needs a unique I/O port assigned to it. The I/O port ranges are from 200 to 3E0. I/O ports 210, 220, 300, and 310 are often used by accessories.
n Memory address: This is like a waiting room outside the CPU. Token Ring cards often require a memory address, which must then be excluded from the range that Windows 9x is using . CC00 to FF00 is a common range that accessories use (if they need one). If more than one device is assigned a particular setting, you will need to resolve the conflict before Windows 9x will work properly.
How you change the settings of your network card depends on whether it is a Plug-and-Play card or a legacy (jumpers) card. If it is a Plug-and-Play card, you should be able to change its settings in Device Manager by going to the property sheet for the card and choosing Change Setting. After you reboot, the card should be set to the new settings. Device Manager is one of the best utilities included in Windows 9x, because it allows you to see, troubleshoot, and control your hardware settings. To open Device Manager, go to Control Panel, System and choose the Device Manager tab.
If your card is a legacy card, you will need to power off the computer, and then change the jumpers or switches on your card to the new settings. When you are finished, turn on your computer and start Windows 9x, and then make the changes in Device Manager. Reboot for the changes to take effect.
Configuring Protocols
Although the default settings for the protocols work almost all of the time, you can change many of the settings for each of the protocols. If you have more than one protocol installed, you can designate one as your default protocol.
You should designate the protocol you use the most often as the default protocol, since it will be slightly faster than the other protocols. Setting your default protocol is also important because certain applications (like Microsoft's System Management Server, SMS) will use only the default protocol for certain network communications.
Configuring IPX/SPX
There are only a couple of settings you may need to change on a regular basis when using the IPX/SPX protocol: selecting the frame type and enabling NET-BIOS support.
The most important setting to check when using the IPX/SPX protocol on an Ethernet network is the frame type. There are four basic frames that can be run under Ethernet:
n Ethernet 802.2
n Ethernet 802.3
n Ethernet_II
n Ethernet_Snap
Microsoft's IPX/SPX default frame selection is Automatic, which means that Windows 9x will try to determine the frame type being used and match itself to that. If a frame cannot be determined, it will default to 802.2 (which is the default for NetWare 3.12 and higher).
If you were using IPX/SPX from Novell and had different frame types on two computers, the two computers would not see each other at all. When you are using Microsoft's version of IPX/SPX, if the wrong frame type is selected, the computers may still connect, but the communication will be extremely slow.
You also may be able to see servers with different frames, even though Windows 9x is using only one, because a server is routing, or converting, to the other frame type. For best performance, you should run the same frame type on all your computers.
The Automatic setting will bind to only the first frame it finds. If you have multiple frames on your network, Windows 9x may bind to the wrong one. If you have servers with various frame types, you should specify the frame for the client software so it will see the correct servers. The Frame Type setting is on the Advanced tab of the IPX/SPX Compatible Protocol Properties dialog box. Follow the steps in Exercise 11.2 to set the frame type manually.
Another parameter you may need to set is whether to support NETBIOS over IPX/SPX. NETBIOS is a specification that some programs require in order to work on a network. The documentation for the network application should specify which protocol(s) are supported, and if NETBIOS support is required. Older network applications often require NETBIOS support; newer applications seldom do. If you have applications that require NETBIOS support, you will need to select the option. This setting is on the NetBIOS tab of the IPX/SPX
Compatible Protocol Properties dialog box. Follow the steps in Exercise 11.3 to enable NETBIOS support.
EXERCISE 1 1 .2
Setting the Frame Type Manually
1. Go to Control Panel , Network.
2. Highlight IPX/SPX and choose Properties.
3. Choose the Advanced tab.
4.Choose Frame Type.
5.Change the Value from Automatic to Ethernet 802.2.
6.Click on OK.
7.Reboot Windows 9x.
Configuring TCP/IP
Installing and configuring TCP/IP are covered in detail above. Your configuration choices are whether to use DHCP (Dynamic Host Configuration Protocol) to dynamically assign addresses and subnet masks or to manually assign addresses and subnet masks. The addresses of DNS servers, WINS servers, and default gateways can also be assigned manually or by DHCP.
Configuring NetBEUI
NetBEUI parameters will rarely, if ever, need to be changed. Changing these settings affects only real-mode NetBEUI. The protected mode NetBEUI parameters are dynamically adjusted by Windows 9x. Remember, NetBEUI can handle only up to only 254 nodes, and NetBEUI packets cannot cross a router. Although this protocol is rarely used as a regular protocol, it can be useful as a dial-up protocol. There are only two parameters that can be changed for real-mode NetBEUI: maximum sessions and NCBs (Network Control Blocks). These settings are on
the Advanced tab of the NetBEUI Properties dialog box.
EXERCISE 1 1 .3
Enabling NETBIOS Support
1.Go to Control Panel , Network.
2.Highlight IPX/SPX and choose Properties.
3.Choose the NetBIOS tab.
4.Check the I Want to Run NetBIOS over IPX/SPX box.
5.Click on OK.
6.Reboot Windows 9x.
Configuring the Client
Several options can be configured for the client software, including the protocols bound to the network card and which client (NetWare, NT, or another client) software will be the primary one (the one that Windows 9x loads and logs in to first). These settings are usually set during installation of the computer, when the client is first set up, and rarely need to be changed. An item that may need to be changed on a regular basis (if the security policy of the server requires it) is the user password. Windows 9x will cache user-names and passwords that you use to connect to various shared resources so it can automatically reconnect to those resources after you log in. You may want to disable the password cache for security reasons.
Choosing a Primary Network Logon
Windows 9x keeps a local database of usernames and passwords. If you are logging on to a domain or another type of server, you must choose whether to have Windows 9x first log you in to the domain and then the local computer, or first log in to the local computer and then the domain. You have the following choices for primary logon:
n Windows logon
n Client for Microsoft Networks (if installed)
n Client for NetWare (if installed)
n Other clients such as Banyan Vines or DECNET (if installed)
You should set the client that you use most often as your primary client.
Some features of Windows 9x (such as roaming user profiles, work only if the Client for Microsoft Networks is set as the primary client. If security is not an issue, in order to keep Windows 9x from prompting you for a password, set Primary Network Logon to Windows Logon, and make your password blank. Although this is not secure, it is convenient.
The Primary Network Logon setting is on the Configuration tab of the Net-work
Control Panel. Follow the steps in Exercise 11.4 to choose your primary logon.
Logging into an NT Domain
Another logon option you have is whether you log in to a workgroup or a domain. If you choose to log on to a domain, you must already have an account on that domain (usually created by a network administrator).
A workgroup is a loose association of computers that has no central database of users, groups, or passwords. A domain has one or more Windows NT servers acting as controllers. Each controller has a copy of a user database and can validate logon requests.
The benefit of logging in to a domain is that once you are validated, you should never need to enter your username and password again (during your session) to access resources on the network. The controllers on the domain create an access token when you log in, and that token is used by all the servers in the domain. It is much like getting your ticket stamped at an amusement park and being able to go on any of the rides (because you have been authenticated at one of the ticket windows).
The option to log in to a Windows NT domain is in the Client for Microsoft Networks Properties dialog box. Follow the steps in Exercise 11.5 to set up Windows 9x to log in to an NT domain.
Changing Your Primary Network Logon
1.Go to Control Panel , Network.
2.From the Primary Network Logon drop-down list, choose where you want to log on first. Select Windows Logon for a peer-to-peer network or Client for Microsoft if you log in to an NT domain.
3.Click on OK.
4.Reboot Windows 9x.
Setting Windows 9x to Log in to an NT Domain
1.Go to Control Panel , Network.
2.Highlight Client for Microsoft and choose Properties.
3.Put a checkmark in the Log on to Windows NT Domain box.
4.Type the name of the domain in the text box. If you don't currently have a real domain, enter Domain1.
5.Click on OK.
6.Reboot Windows 9x.
Changing Your Password
You can change both your Windows 9x local password and your NT password from the Password Properties dialog box. Windows 95 will also allow you to change passwords, such as those for screen savers, from the same Properties dialog box.
Exercise 11.6 shows the steps for changing the Windows password, as well as the NT domain and screen saver password.
Changing Your Passwords
1.Go to Control Panel , Passwords.
2.Click on Change Windows Password.
Password Caching
Windows 9x can cache, or remember, the usernames and passwords with which you connect to shared resources. While convenient, caching passwords poses a security risk if the password file is de-encrypted. The caching of passwords happens if you select the Reconnect at Logon box when using a network resource.
3.In the Change Windows Password dialog box, select the Microsoft
Networking (to change your NT domain password) and the Windows
Screen Saver boxes, as shown below.
4.Click on OK.
5.In the next dialog box, change your password by typing the old one
once, and the new one twice, as shown below.
6.Click on OK.
7.Reboot Windows 9x to use your new password.
When you log in to Windows 9x, the system uses the cached passwords to automatically re-establish all the drive connections you had the last time you logged off.
The password encryption that comes with the standard Windows 9x is easy to break. Download the new version at Microsoft's Web site for added security, or turn off password caching.
Password caching can be disabled by using a system policy.
Sharing Resources as a Server
Windows 9x computers can have an additional service installed that allows them to share resources and act like Windows NT file and print servers.
Allowing users to share their resources does make sharing information more convenient, but it is also makes more work for those who maintain and administer the network and is a lot less secure. You now have many administrators to train and supervise, instead of just a few. Problems can arise if users share their drives incorrectly and sensitive information gets out, or if users have too many rights and delete files.
Many smaller companies love the fact that they don't need a dedicated, expensive computer in order to share a few files and printers. Larger companies tend to have more resources for both hardware and administrators, and usually don't allow users to share their local resources on the network. Restrictions can be enforced with system policies.
When all is said and done, Windows 9x is a great PC operating system and network client, but it's much better to leave the role of a powerful server to NT or NetWare.
The following are the steps to setting up and managing shared resources:
n Choose a security model (Share level versus User level).
n Install File and Printer Sharing for Microsoft Networks.
n Configure File and Printer Sharing.
n Create shared resources.
n Modify shared resources.
These steps are discussed in detail in the following sections.
Choosing a Security Model
There are two types of security systems that Windows 9x can use to share resources: Share level and User level. The way you create and modify shared resources depends on whether you set Share level or User level security. You will need to reset sharing of all your resources if you switch between the two security types. When you switch, Windows 9x will turn off sharing of all folders and printers. There is no way for Windows 9x to convert rights from one scheme to another, so it doesn't even try.
Share Level Security
Share level is the same as it is in Windows for Workgroups; that is, a password is assigned to a shared resource when the shared resource is created. This is the default level of security. With Share level security, if a user knows the passwords, he or she can access the resources, even if the original owner did not intend that particular user to have access to those shared resources.
Using Share level security has the advantages of being easy and fast. How-ever, it has the following disadvantages:
n It is not secure.
n Specific users cannot be blocked.
n The passwords can be discovered.
n There is no centralized control (central Information Systems is no longer in charge).
n Changing passwords requires informing all intended users.
Share level security is the default security setting for the sharing service for Microsoft networks.
User Level Security
Because of the limitations of Share level security, Microsoft added a more advanced option in Windows 9x that is much more secure. The User level system bases its security on an existing server of some sort: either a Windows NT server (NT Workstation, NT Server, or a domain controller) or a NetWare server. After a new share is made, existing users or groups are then given rights to the share. This means that you must have some kind of server in place before you can switch to User level security.
User level security has the following advantages:
n Rights can be assigned to a user or group.
n It allows centralized control of users and groups.
n It's more flexible than Share level (custom rights can be assigned).
There are a few disadvantages of using User level security, however:
n Some kind of server must be in place.
n It's more complex than Share level.
n A live network connection to the server must be maintained when
assigning rights and shares.
You can switch to User level security when you configure sharing services, as
described later in the chapter.
Installing File and Printer Sharing for Microsoft Networks
A Windows 9x computer can have many different client pieces installed simultaneously, but it can have only one sharing service installed at a time. Installing File and Printer Sharing is quite easy. This is a network service, which you can install from the Network Control Panel.
Another way to access the network configuration dialog box is by right-clicking on Network Neighbourhood and selecting Properties.
Follow the steps in Exercise 11.7 to install the sharing service for Microsoft networks.
Installing File and Printer Sharing for Microsoft Networks
1.Go to Control Panel , Network.
2.Choose Add in the Select Network Component Type dialog box.
3.Highlight Service and choose Add.
4.Highlight Microsoft and choose File and Printer Sharing for Microsoft Networks.
5.Click on OK.
6.Reboot Windows 9x.
Configuring File and Printer Sharing for Microsoft Networks
The major decision when configuring File and Printer Sharing is which security model to use. If you are in a workgroup, without any central server, Share level security is probably your best (if not only) option. If you have a central server (either NetWare or NT), User level security is probably the better option. In either case, the mechanics of sharing resources is the same, but the security options are different.
Changing the Security Mode
As explained earlier, the default security model is Share level, which allows you to put passwords on shared resources. User level is more secure, and is thus preferred if users will be allowed to share their resources. Before you can change to User level, you need a server (either NetWare or NT) in place.
You switch to User level security through the Access Control tab of the Net-work Control Panel. If you set User level to an NT server that is not a domain controller, you will need the server name. If you set User level to an NT domain, you will need the domain name. Exercise 11.8 shows the steps for switching the security model to User level, based on an NT domain.
To switch back to Share level, follow the steps in Exercise 11.8 to return to the Access Control tab, and select Share Level Access Control.
The process of creating shared folders is similar for both Share level and User level security settings, but the types of security settings you can pick are different. The following sections describe the procedures for sharing folders and managing shares for both Share level and User level sharing.
Creating Shares Using Share Level Security
When you share a folder using Share level security, you have three basic security options:
n Read-Only: Allows users on the network to see and run applications in that folder, and to see and open files.
n Full: Allows all of the above rights, plus gives users the rights to modify and delete programs and files, and to create new files.
n Depends on Password: Allows you to set different passwords for Read-Only and Full access. You then give the appropriate password to users based on which rights you want them to have.
Switching to User Level Security
1.Got to Control Panel , Network.
2.Choose the Access Control tab.
3.Select User Level Access Control.
4.Enter the name of the NT server or domain. Use Domain1 if you don't have a real domain to use.
5.Click on OK.
6.Reboot Windows 9x.
If you select Read-Only or Full access, users don't need to use a password; in that case, the shares are wide open to any and all users on your network even those who have not been authenticated by any server!
These options are listed on the Sharing tab of a folder's Properties dialog box.
Follow the steps in Exercise 11.9 to share a folder and set the security using passwords.
You can check all of your shares by going to the Network Neighbourhood. Under your computer name, all the shares should be listed.
Creating a Share Using Share Level Security
1.Create a folder called ShareMe.
2.Highlight the folder and right-click. Sharing should appear in the pop-up menu, as shown below, if you installed the Sharing service correctly (see Exercise 11.7).
3.Select Sharing to display the Sharing tab of the ShareMe Properties dialog box.
4.Select the Shared As button.
5.As the Share Name, leave the default name SHAREME, or enter another name.
Note that if your share name ends with a $ (dollar sign), the share will be hidden from the browser. The only way to connect to this share will be to use the Map Network Drive command and type in the UNC.
Creating Shares Using User Level Security
When you share folders with User level security, you are able to grant rights to users or groups. The Sharing tab of the shared folder's Properties dialog box looks different than one that has Share level security.
The rights you can grant are Read Only, Full Access, or Custom, as shown You can grant rights to users or groups from the domain, or to The World, which is all users on the network.
EXERCISE 11.9 (CONTINUED FROM PREVIOUS PAGE)
6.Select Depends on Password.
7.Enter Readme in the Read-Only Password box.
8.Enter Fullcontrol in the Full Access Password box.
9.Retype the passwords when prompted, as shown below.
10.Click on OK to save your new share.
11.You should now see the folder with a hand under it, signifying it is
shared, as shown below.
If you choose Custom, you can set individual rights.
These include the following:
n Read Files: Allows the user to open or run files or applications.
n Write to Files: Allows the user to edit existing files.
n Create Files and Folders: Allows the user to create new files or folders.
n Delete Files: Allows the user to delete files or folders.
n Change File Attributes: Allows the user to change file or folder attributes.
n List Files: Allows the user to show files and folders.
n Change Access Control: Allows the user to change security settings. Follow the steps in Exercise 11.10 to create a new share using User level access, and assign rights to users and groups.
Managing Existing Shared Folders
To modify the properties of existing shares, return to the Sharing tab of the shared folder's Properties dialog box by right-clicking on the folder and choosing Sharing from the menu (as in Exercises 11.9 and 11.10). From the Sharing tab of a share using Share level security, you can change the share name, how it is shared, or the passwords. From the Sharing tab of a User level security share, you can change the share name, how it is shared, or which users and groups have rights to the share.
Creating a Share Using User Level Security
1.Make sure you are using User level security (see Exercise 11.8).
2.Create a folder called ShareMe.
3.Select the ShareMe folder, right-click on it, and choose Sharing.
4.Choose the Shared As button.
5.Leave the default name of SHAREME as the Share Name or enter a different name.
6.Click on the Add button.
7.In the Add Users dialog box, highlight the Domain Users group and click on the Read Only button.
8.Highlight the Domain Admins group and click on the Full Access button.
9.Highlight the Administrator user and click on the Custom button.
10.Click on OK. The Change Access Rights for the Administrator user appears.
11.Choose all custom access rights except Delete Files.
12.Choose OK twice to save your new share.
Browsing on a Microsoft Network
The network browsing service is designed to allow clients to access a complete list of available servers, shared folders, and shared printers, without needing to keep their own copy of the list. When a computer browses the net-work, it downloads a list of available servers and shares from a central computer that maintains the list. As the number of clients increases, Windows (both NT and 95) will increase the number of servers keeping lists. The default number of browse servers is one server for every 32 clients. If Windows 9x is part of a domain, the primary domain controller (PDC) of the domain will be the browse master for the entire domain, and will have helper servers (backup browsers) to give lists to clients. When a browse master or backup browser is turned off, there will be an "election" to pick a new browse master. The order of precedence is as follows:
n Windows NT Server
n Windows NT Workstation
n Windows 9x
n Windows for Workgroups
You can "stuff the ballot box" by editing the registry to make one server preferred over another to become browse master. For example, you may have two Windows 9x computers' one is a 486 with 8MB of RAM, and the other is a Pentium 200 with 64MB of RAM. Obviously, the Pentium computer would make the faster browse master. Browse Master is a property of File and Printer Sharing for Microsoft Net-works. There are three settings for this property:
n Automatic: This is the default. It means that the computer can be elected to become a browse master if it is needed.
n Enabled: This means that the computer will always be a browse master.
n Disabled: This means the computer will never become a browse master. Follow the steps in Exercise 11.11 to make a Windows 9x computer a preferred browse master.
Setting Windows 9x to a Preferred Browse Master
1.Go to Control Panel, Network.
2.In the Configuration tab, highlight File and Printer Sharing for Microsoft Networks and choose Properties.
3.Highlight Browse Master and choose Enabled.
4.Choose OK twice to save your changes.
5.Reboot Windows 9x.
Summary
As you learned in this chapter, connecting a Windows 9x computer to a Windows NT network is fairly straightforward. Installing the Client for Microsoft Networks software allows Windows 9x to connect to Windows NT servers and use their shared resources as if they were its own. A network usually consists of a few servers, with the majority of computers configured as clients.
Before you install the client, you need to install the network card and drivers. Windows 9x can automatically detect and configure Plug-and-Play cards. You can configure the network protocols and client software through the Network Control Panel.
Windows 9x can also be set up to share its local resources in a peer-to-peer network. When a Windows 9x computer shares its resources, it can use either Share level security, the default, which puts passwords on the shared resource, or User level security, which grants rights to existing users and groups from an NT or NetWare server. User level security is tighter than Share level security, but does require an existing NT or NetWare server to link to. Browsing allows Windows 9x to see the servers and shared resources available on the network. By default, there is one browse server for every 32 clients.
When Windows 9x is part of a domain, there is a browse master for the entire domain. You can enable the Browse Master property for a Windows 95 machine (through its File and Print Sharing for Microsoft Networks property sheet) to make it always be the browse master.
Exercise Questions
1.When installing a network card, what items may you need to configure?
A.Interrupt
B.I/O port
C.Memory address
D.Slot number
2.You can use which program(s) to configure the network card?
A.Control Panel , Network , Properties of the card
B.Network Neighbourhood , Properties , Properties of the card
C.Control Panel , Devices , Properties of the card
D.Control Panel , System , Device Manager , Properties of the card
3.By installing the Client for Microsoft Networks, you allow Windows 95 to understand which language?
A.NCPs
B.MMPs
C.NTBs
D.SMBs
4.If Windows 9x is set up to use IPX/SPX, and it cannot auto detect a frame type, what frame will it pick?
A.No frames
B.All frames
C.Ethernet_802.2
D.Ethernet_II
5.Which service allows automatic assignment of TCP/IP addresses?
A.DHCP
B.WINS
C.DNS
D.DXNP
6.NetBEUI packets can cross a router.
A.True
B.False
7.You can change your NT password from within Windows 9x.
A.True
B.False
8.Windows 9x can be a client to NT while it is acting as an NT server as well.
A.True
B.False
9.You can set Read-Only rights using just Share level security.
A.True
B.False
10.A stand-alone Windows 9x computer can use User level security.
A.True
B.False
|
