Download Chapter 12 - FTP Directory Listing

Transcript
Troubleshooting Methodology
621
who cannot properly use the embossing control software. Now you have solved one
problem, but created another. In this situation, it would have been wise to ask the software vendor about their upgrade’s compatibility with all the other operating systems
your company uses. If the vendor told you about a problem with Windows 98 workstations, you could have kept the old installation on the server for these users, then installed
the new version of the software in another directory for use by Windows 2000 users.
Be aware of the security implications of your solution, because it may inadvertently
result in the addition or removal of network privileges for a user or group of users.The
consequence may be simply that a user can no longer access a data file or application he
is used to accessing. But a worse consequence is that you could create a security opening that allows unauthorized people to access your network.
You should also consider the scalability of the solution you intend to implement. Does
it position the network for additions and enhancements later on, or is it merely a temporary fix that the organization will outgrow in a year? Ideally, your solution would be
perfectly suited to your network and allow for future growth. But a temporary fix is not
necessarily wrong, depending on the scenario. For example, you might walk into the
office one day to find that none of your users can access the network. You may track
down the problem as an internal hardware problem with your IP gateway. Since the gateway is under warranty, you quickly call the manufacturer to either get the gateway
replaced or fixed immediately.The manufacturer may tell you that while they don’t have
the identical gateway available in their local office, they can substitute a different, smaller
model to get your users reconnected today and meanwhile order the identical gateway
that you can install when you have more time. In this situation, it is preferable to take
the temporary gateway and restore functionality than to wait for the ideal solution.
Another factor to consider when implementing your solution is cost. Obviously, replacing one patch cable or faulty network adapter is a fairly inexpensive proposition, and
you don’t need to analyze cost in these cases. But if the solution you have proposed
requires significant dollars for either software or hardware, you should spend time carefully considering your options. For example, you may discover a problem with performance on your network. After some investigation you may determine that the best
solution is to replace all of your 400 workstations’ network adapters with newer, faster
network adapters. If you purchase quality NICs, this solution could cost over $10,000
for the hardware alone, not to mention the time it will take technicians to replace the
devices, which may cost more. Also you should consider when these workstations will
be replaced and if you will have to either discard or remove the network adapters you
just installed. It may be more prudent to identify where the network’s performance is
poor and address those areas separately—for example, by adding a switch to a busy segment or adding a more powerful server for a heavily used application.
12