Features
- Cover Type: Paperback with 396 pages
- Published by: Charles River Media
- Edition: 1st Edition September 2004
- Written in: English
- ISBN 10 Number: 1584503483
- ISBN 13 Number: 978-1584503484
-
Book Dimensions:
9.1 x 7.3 x 1.1 inches
- Weighs: 1.8 pounds
Product Description
Troubleshooting can account for up to ninety percent of a network administrator's job, so effective troubleshooting skills will help administrators respond quickly in a crisis situation, and keep their networks running smoothly. It can be a quantum leap from network administrator to troubleshooting guru, but knowing how to implement the right technique at the right time can help administrators take their skills to the next level. The Real- World Network Troubleshooting Manual focuses on the methodology and process of network troubleshooting, and how to apply them in real-life situations. Designed to make any network administrator a troubleshooting expert, the book starts with an overview of some readily available, basic troubleshooting tools. From there, multiple real-world troubleshooting scenarios are covered, from basic problems to more advanced, including what to do if a workstation is unable to surf the Internet, wireless users cannot connect to the network, or a hacker attacks the Web site. Although the primary focus is on the Windows workstation and server environment, many of the troubleshooting scenarios are non-operating system specific and can be applied to any computing environment.
About The Author
Alan Sugano (Ranch Palos Verdes, CA) is the president of ADS Consulting Group Inc., specializing in networking, custom programming, Web development, SQL server development, and ACCPAC Plus accounting implementations. He has spoken at various industry conferences and writes regularly for Windows & .NET Magazine.
Reader ReviewsI just received this book from Amazon and was somewhat surprised by its contents. For the first: this book spends quite a few of its pages to discuss scenarios not *directly* related to network troubleshooting. For the second, many of the scenarios describe a problem that is specific to a particular vendor. I would have preferred content that was usable for networking issues regardless of vendor. For the third, the problem scenarios or the solution descriptions may not bring anything new to your personal solution arsenal (unless you have very little experience in this field). For the fourth, the book comes with a CD containing tools from SysInternals (such as Autoruns, Filemon, etc). Besides the fact that these tools can be freely downloaded from SysInternals web site, maybe more annoying is that the book provides no scenarios or advise on using these tools to troubleshoot problems. On the other hand, as an example, chapter 4 uses over 7 pages to list the Windows Recovery Console commands; the list seems to contain the same information that can be obtained using the HELP command inside the Recovery Console. Some examples of the scenarios: Chapter 3 (pages 45-91) deals with workstation troubleshooting. Example scenario: - Problem Scenario "12" on page 88 (User is unable to install NAV Corporate Edition on a workstation): This scenario discusses the problem as occurring on a Windows 2000 with SP4. The solution: re-apply SP 4. Chapter 4 (pages 93-158) deals with Windows Server troubleshooting; tools described in this chapter are the Windows Performance Monitor and Recovery Console. Example scenarios: - Problem Scenario "1" on page 134 (Data faction server does not boot): Discusses how a particular case of a server not booting was resolved. Solution: replace the power supply switch. - Problem Scenario "3" on page 142 (Inaccessible boot device error stop 0000007B): Discusses how to troubleshoot a server displaying a blue screen with the "Inaccessible boot device ..." message at start. The described temporary solution: run ChkDsk. A more permanent solution: replace the hard drive. Chapter 5 discusses SQL Server (pages 159-182) troubleshooting. Example scenario: - Problem Scenario "2" on page 176 (Poor performance on SQL Server): Discusses what to do when SQL Server takes unusually long to return query results. In this case a large amount of data had been uploaded to the SQL Server just before the problems started. The solution: to run the command "Update Statistics <table_name
Search for books at
