- Shopping Bag ( 0 items )
Networking For Dummies, 5th Edition provides valuable updates on the latest tools and trends in networking including Windows 2000, NetWare 5.1, Linux 6.2, and home networking. Networking For Dummies, 5th Edition is straightforward in its approach to guide professional and novice administrators through building, managing, and ...
Ships from: Sparks, NV
Usually ships in 1-2 business days
Ships from: St Louis, MO
Usually ships in 1-2 business days
Ships from: Reno, NV
Usually ships in 1-2 business days
Ships from: Atlanta, GA
Usually ships in 1-2 business days
Ships from: Toledo, OH
Usually ships in 1-2 business days
Networking For Dummies, 5th Edition provides valuable updates on the latest tools and trends in networking including Windows 2000, NetWare 5.1, Linux 6.2, and home networking. Networking For Dummies, 5th Edition is straightforward in its approach to guide professional and novice administrators through building, managing, and securing both large and small networks.
PART I: The Absolute Basics: A Network User's Guide.
Chapter 1: Networks Will Not Take Over the World, and Other Network Basics.
Chapter 2: Life on the Network.
Chapter 3: Using a Network Printer.
Chapter 4: Becoming a Server.
Chapter 5: Mr. McFeeley's Guide to E-mail.
Chapter 6: Help! The Network's Down!
PART II: Building Your Own Network.
Chapter 7: The Bad News: You Have to Plan Ahead.
Chapter 8: Choosing Your Weapon (Or, Which Network Should You Use?).
Chapter 9: Planning Your Servers.
Chapter 10: Oh, What a Tangled Web We Weave: Cables, Adapters, and Other Stuff.
Chapter 11: Configuring Your Network Computers.
PART III: Network Management For Dummies.
Chapter 12: Help Wanted: A Network Manager's Job Description.
Chapter 13: Who Are You? (Or, Big Brother's Guide to Network Security).
Chapter 14: If I Could Save Time in a Bottleneck: Optimizing Your Network's Performance.
Chapter 15: Things That Go Bump in the Night: How to Protect Your Network Data.
Chapter 16: How to Stay on Top of Your Network and Keep the Users.
off Your Back.
PART IV: Webifying Your Network.
Chapter 17: Welcome to the Internet.
Chapter 18: Connecting Your Network to the Internet.
Chapter 19: Hosting Your Own Web Site.
Chapter 20: Creating an Intranet.
PART V: More Ways to Network.
Chapter 21: Networking Your Home.
Chapter 22: Dialing In to Your Network.
Chapter 23: Using Microsoft Office on a Network.
Chapter 24: Networking Older Computers.
Chapter 25: Welcoming Macintosh Computers to Your Network.
Chapter 26: Using a Linux Server.
PART VI: The Part of Tens.
Chapter 27: Ten Big Network Mistakes.
Chapter 28: Ten Networking Commandments.
Chapter 29: Ten Things You Should Keep in Your Closet.
Chapter 30: Ten Network Gizmos Only Big Networks Need.
Chapter 31: Ten Layers of the OSI Model.
Chapter 32: Ten Hot Network Buzzwords Guaranteed to Enliven a Cocktail Party.
Book Registration Information.
In This Chapter
It really is true that there's no such thing as a free lunch. When you network your computers, you reap the benefits of being able to share information and resources such as disk drives and printers. But there are also many costs. There is the cost of purchasing network cards, cable, and software, plus the cost of the time required to install the network, learn how to use it, and keep
There's another cost of networking you may not have considered yet: the performance cost. No matter how hard you try, you can't hide the ugly truth that putting a computer on a network slows it down. It takes a bit longer to retrieve a word processing document from a network disk than it does to retrieve the same document from your local disk drive. Sorting that big database file takes a bit longer. And printing a 300-page report also takes a bit longer.
Notice that I've used the word "bit" three times now. Lest my editor chide me for Overuse of a Three-Letter Word, I'd better point out that I used the word three times to make a point. The network inevitably slows things down, but only a bit. If your network has slowed things down to a snail's pace-so that your users are routinely taking coffee breaks whenever they save a file- you've got a performance problem you can probably solve.
The term bottleneck does not in any way refer to the physique of your typical computer geek. (Well, I guess it could, in some cases.) It is, rather, a phrase coined by computer geeks when they discovered that the tapered shape of a bottle of Jolt Cola limited the rate at which they could consume the beverage. "Hey," a computer geek said one day, "the narrowness of this bottleneck limits the rate at which I can consume the tasty caffeine-laden beverage contained within. This draws to mind an obvious analogy to the limiting effect that a single slow component of a computer system can have upon the performance of the system as a whole."
"Fascinating," replied all the other computer geeks who were fortunate enough to be present at that historic moment.
The phrase stuck and is used to this day to draw attention to the simple fact that a computer system is only as fast as its slowest component. It's the computer equivalent of the old truism that a chain is only as strong as its weakest link.
For a simple demonstration of this concept, consider what happens when you print a word processing document on a slow dot-matrix printer. Your word processing program reads the data from disk and sends it to the printer. Then you sit and wait while the printer prints the document.
Would buying a faster CPU or adding more memory make the document print faster? No. The CPU is already much faster than the printer, and your computer already has more than enough memory to print the document. The printer itself is the bottleneck, so the only way to print the document faster is to replace the slow printer with a faster one.
Funny you should ask. Here they are, in no particular order:
1. The CPU in the file server. If the file server will be used extensively, it should have a powerful CPU - Pentium is best. This is especially true if you're using NetWare.
2. The amount of memory in the file server. You can set up the file server to take advantage of lots of extended memory. A few extra megabytes of server memory can almost always be put to good use.
3. The file server computer's bus. Oops . . . this is kind of technical, so I'll put the details in a sidebar you can skip. The nontechnical version is this: Buy a server computer that has a high-speed local bus if you can afford it.
4. The network card. Use 16-bit network cards; cheaper 8-bit cards slow things down. Better yet, use EISA or PCI bus cards.
5. The file server's disk drive. If possible, use EIDE or SCSI drives. Sorry! I went technical on you again. Time for another sidebar.
6. The file server's disk controller card. All disks must be connected to the computer via a controller card, and sometimes the bottleneck isn't the disk itself, but the controller card. A beefed-up controller card can do wonders for performance.
7. The configuration options setup for the server. Even simple peer-to-peer networks have all sorts of options you can configure. Some of these options can make the difference between a pokey network and a zippy network. Unfortunately, there aren't any hard-and-fast rules for setting these options. Otherwise, there wouldn't be options.
8. Windows! If you use a peer-to-peer network, don't run Windows on the server. You'll just bog things down. (Of course, you can't avoid running Windows on the server computer if you use Windows for Workgroups, Windows 95, or Windows NT Server.)
9. DOS! No matter how hard they try, DOS-based networks will never be as fast as NetWare or Windows NT networks. NetWare and Windows NT have an advantage because they are written specifically to take advantage of the fast features of 386, 486, and Pentium processors. DOS is not.
10. The network itself. If you have too many users, the network can become bogged down. The solution is to divide the network into two smaller networks connected with a cool little black box called a bridge.
The hardest part about improving the performance of a network is determining what the bottlenecks are. With sophisticated test equipment and years of experience, network gurus can make pretty good educated guesses. Without the equipment and experience, you can still make pretty good uneducated guesses.
There are two ways to tune your network. The first is to think about it a bit, take a guess at what may improve performance, try it, and see whether the network seems to run faster. This is the way most people go about it.
Then there's the compulsive way, suitable for people who organize their sock drawers by color and their food cupboards alphabetically by food groups, or worse, alphabetically within food groups. The compulsive approach to tuning a network goes something like this:
1. Establish a method for objectively testing the performance of some aspect of the network.
This is called abenchmark. For example, if you want to improve the performance of network printing, use a stopwatch to time how long it takes to print a fairly large document.
2. Now, change one variable of your network configuration and rerun the test.
For example, if you think increasing the size of the disk cache will improve performance, change the cache size, restart the server, and run the benchmark test. Note whether the performance improved, stayed the same, or became worse.
3. Repeat Step 2 for each variable you want to test.
If possible, test each variable separately-in other words, reverse the changes you've made to other network variables before proceeding.
When you use a peer-to-peer network such as LANtastic, there are lots of options you can fiddle around with to improve the performance of your server computers. The time spent is worthwhile to a point because the effect of a more efficient server computer is noticed by all users of the network.
When you first install your network, make no attempt to tune the server for efficient performance. In fact, do what you can to make sure that the server runs as inefficiently as possible. Then, after the network has been running a week or two, announce that you're sick and tired of lackluster network performance and you're not going to take it any more. Apply the basic performance-tuning techniques described here and you'll be a hero.
The numero uno thing you can do to boost the performance of a server is to use a program called a disk cache. A disk cache dramatically improves the performance of your disk drives. Here's how it works. (This is a bit complicated, so make sure that you're sitting down before you continue.)
It's a given that computer memory (that is, RAM) can be accessed faster than disk storage, right? A disk cache works by setting aside a portion of memory to hold disk data that's frequently accessed. Whenever a network user tries to read data from the disk, the cache program checks first to see whether the data is already in the cache memory. If so, the data is read directly from memory, much faster than if it had to be accessed from the disk.
The more memory you set aside for the cache, the more likely it is that when a network user needs to retrieve data from the server's disk, the data can be retrieved quickly from cache memory instead. So the general rule is this: Set aside as much memory as humanly possible for disk cache. The cache is the reason you can never have too much memory in a network server.
If you use the LANCACHE command with no parameters, it will figure out how much memory your computer has and set aside an appropriate amount to use for cache memory, up to 2MB.
If the server computer has more than 2MB of available memory, you may want to tell LANcache to create a larger cache. Then you have to add a switch to the LANCACHE command, something along these lines:
If you have DOS Version 6.0, 6.2 or 6.22, you have the latest and greatest version of Micro-soft's disk-caching program, affectionately known as SMARTDRV. To activate SMARTDRV, add a command to your AUTOEXEC.BAT like this one:
You should place the command near the top of AUTOEXEC.BAT, preferably immediately after the PATH command.
SMARTDRV checks the amount of memory your computer has to decide how much memory to use for the cache. If your computer has 4MB of memory or less, SMARTDRV uses 1MB of memory for the cache. If more than 4MB is available, SMARTDRV creates a 2MB cache.
You can change the size of the cache SMARTDRV creates by typing the size of the cache you want to use on the command line:
This command tells SMARTDRV to create a 4MB cache. (The number you type in this command specifies the number of kilobytes you want to use for cache memory; 4MB is the same as 4096K.)
Like LANcache, SMARTDRV uses the risky delayed-write feature unless you specifically tell it not to. With DOS 6.0, you tell SMARTDRV to forget about the delayed-write feature by listing all the drives you want cached, following each drive letter with a plus sign. If you have two hard disks - C and D - you type the SMARTDRV command like this:
smartdrv c+ d+
Confusing? Yup. Microsoft saw the error of its ways and decided that DOS 6.2 would let you disable delayed-write simply by adding /X to the command:
This command tells LANcache to create a 4MB cache. (The number you type in this command specifies the number of kilobytes you want to use for cache memory; 4MB is the same as 4096K.)
LANcache uses the risky delayed-write feature unless you add the /NODELAYED_WRITES switch to the LANCACHE command, like this:
If you are using Windows for Workgroups 3.11, you can improve the disk performance on your server computers by enabling a new feature called 32-bit file access, sometimes also known as VFAT (VFAT stands for Virtual File Allocation Table, but that won't be on the test). VFAT enables Windows for Workgroups to completely bypass MS-DOS when reading or writing on your disk drive. That means faster disk access.
To enable VFAT, open the Control Panel and double-click on the 386 Enhanced icon. Next, click the Virtual Memory button and then click the Change button. This brings up the dialog box shown in Figure 13-1. Click the Use 32-Bit Disk Access checkbox if it is not already checked. Then set the Cache Size control to an appropriate amount. Finally, click OK.
How much memory should you allocate for the cache? There are no hard-and-fast rules, but the following list gives some reasonable suggestions based on how much RAM the computer has:
RAM Cache size
Here are a few tidbits to ponder as you lie awake tonight:
Most peer-to-peer networks let you play around with several variables that affect the performance of a file server. The standard settings for these options aren't always the best settings for the majority of systems, so it almost always pays to read about what options are available and make a few adjustments.
Figure 13-2 shows the settings you can change for a LANtastic server. Other networks have similar settings. I won't describe each of these configuration options here; instead, I'll zero in on the ones that are most likely to improve your network's performance if you adjust them.
Notice that the screen in Figure 13-2 is titled "Server Startup Parameters." That's because these settings are read by the network server program when you start it. You can change these settings while the network is running, but the new values you specify won't take effect until you restart the server.
Because adjusting these settings requires that you frequently restart the server, you have to ask everyone to stay off the network for a while so that you can experiment with various settings. If you're really dedicated, you may want to do this on a Saturday or in the evening.
Try adjusting the following options, as you think they are appropriate to your situation:
Maximum Users. This option says how many users can be logged in to the server at one time. The default is five; if you have more than five users on the network, you should increase this value. Increasing this value takes memory away from other functions, so you should set it to just a few more than the actual number of users you have.
Network Buffer. This option tells LANtastic how much data should be transferred from the server to the workstations each time a workstation requests disk data. The default setting for this option is 4096 (that's 4K). Most networks run better if you increase this value to 8192 (that's 8K). Try it and see. If not, you can always change it back to 4096.
If you change the server's Network Buffer setting, you also should change the /size parameter on the REDIR command found in each computer's STARTNET.BAT file. The /size value and the Network Buffer setting should be the same.
Network Tasks. This setting tells LANtastic how many network requests the server can handle simultaneously. The default is 1, which means that network requests are handled one at a time. If a user requests data from the server while the server is busy handling another user's request, the second user will just have to wait.
Your network's performance will almost surely improve if you increase this setting to 3. The benefit of additional network tasks beyond 3 is usually small.
Each task requires a separate network buffer, so if you specify 3 network tasks and an 8K network buffer, a total of 24K is set aside for the network buffers.
Printer Buffer. This option specifies the size of the buffer used for network printing. The default is a paltry 512 bytes. You almost always can improve printing performance by specifying a larger value, especially if you have a relatively fast printer. Try specifying 4096 or 8192 and see what happens.
Printer Tasks. You should set this option to the number of printers that are attached to the server. Most servers have only one printer, so the default setting of 1 is appropriate. A separate printer buffer is created for each printer task.
Run Buffer Size. This option sounds important, but it's not. It only affects the seldom-used NET RUN command, so don't worry about it.
Request Size. When a workstation requests some action from the server, the request is held in a small area of the server's memory called a request buffer until the server can process it. The default size of this request buffer is 32 bytes. Increasing this value often can improve performance, though not usually dramatically. Try increasing the request size to 512 and see what happens.
A separate request buffer is created for each network user allowed by the Maximum Users setting.
Run Burst. This setting lets you tell the server whether to place more emphasis on servicing network tasks or local tasks. The default setting of 2 means that the server will concentrate solely on network tasks for 2 "clock ticks" before checking to see whether there is any non-network processing to be done. Each clock tick is 1/18th of a second, so a run burst of 2 means that the server stops processing network tasks 9 times every second.
If a server operates as a dedicated file server, you should increase this value. I like to set it to 18 so that the server checks for local work once per second. The maximum value for this setting is 255.
LANtastic considers print despooling to be a local task. Therefore, if a server functions as both a file server and a print server, increasing the Run Burst setting improves file I/O at the expense of printer I/O. This is one of the main reasons it is best to have separate file servers and print servers if possible. To set this value appropriately for a combined file/print server, you must do what Mr. Miyagi says in the Karate Kid movies: "Find balance."
Seek Cache Size. The seek cache duplicates the function provided by the DOS FASTOPEN command: It keeps track of the locations of files on disk. The default setting is "NO CACHE," but you can change it by specifying a cache size from 1 to 64K. Most networks will benefit from FASTOPEN or a modest seek cache (16 to 32K), but there's no point in using both FASTOPEN and a seek cache.
Cached Resources. Information about each network resource (shared disk drive, printer, and so on) can be stored in cache memory to improve performance. This option sets the number of resources that are held in memory. You should set it to the number of resources defined for the server-that is, the number of shared disk drives and printers.
File Lookup Cache. Use this option only if the server has a CD-ROM drive.
LANtastic comes with a program that you can run to improve the performance of a dedicated network server. This program is called ALONE.
ALONE temporarily prevents you from running any other program at the server. The server is then free to concentrate on running the network.
If the server tuning options for LANtastic left you with a migraine, you'll love the Windows 95 approach to tuning. The following procedure shows how to tune a Windows 95 server computer:
1. Choose SettingsÍControl Panel from the Start menu and then double-click the System icon.
The System Properties dialog box appears.
2. Click the Performance tab.
3. Click the File System button.
The dialog box shown in Figure 13-3 appears.
4. Set the drop-down list box labeled Typical role of this machine to Network Server.
Your computer is now tuned as a network server.
5. Click OK to dismiss the File System Properties dialog box.
You are returned to the System Properties dialog box.
6. Click OK to dismiss the System Properties dialog box.
That's all there is to it.
Tuning a NetWare server is both easier and more difficult than tuning a peer-to-peer server. It's easier because NetWare is an inherently more efficient network operating system. Because it doesn't run under DOS, you don't have to worry about the built-in limitations of DOS, such as the 640K limit on conventional memory. It's more difficult because NetWare provides more options you can adjust.
The biggest network performance benefits are gained by tuning the network servers because the effort you spend tuning one computer results in improved performance for every user who uses that server. Still, you shouldn't neglect performance tuning for the individual clients on the network.