B efore you roll out a new Web site, or change an existing site, you should make sure it has as few bugs as possible. A new site is kept “private” until its launch date. When it is rolled out, everyone is allowed in to try it out. You should only make your site public once you have ironed out most of the bugs. | Internet Troubleshooting i-NET EXAM OBJECTIVES COVERED IN THIS CHAPTER J Identify problems related to legacy clients . TCP IP sockets and their implication on the operating system . Content could include the following Checking revision date manufacturer vendor Troubleshooting and performance issues Compatibility issues Version of the Web browser J Explain the function of patches and updates to client software and associated problems. Content could include the following Desktop security Virus protection Encryption levels Web browsers E-mail clients J Describe the process of pre-launch site application functionality testing. Content could include the following Checking hot links Testing different browsers Testing to ensure it does not corrupt your e-commerce site Load testing Access to the site Testing with various speed connections Copyright 2000 SYBEX Inc. Alameda CA. J Describe when to use various diagnostic tools for identifying and resolving Internet problems. Content could include the following Ping winipcfg ipconfig ARP Trace Routing Utility Network Analyzer Netstat Copyright 2000 SYBEX Inc. Alameda CA. ugs and errors infest the World Wide Web expect them to crop up on your Web site. Bugs stop people from using your Web site and can permanently damage your reputation. So although some bugs are inev itable it is important to reduce the number and effect of bugs that sneak into your site. In the preceding chapter you learned the importance of advance planning for the back and front ends of your Web site. Careful planning will reduce the number of bugs and errors that your users experience but bug detection and fixing is an ongoing process. In this chapter you ll learn about important areas of troubleshooting and debugging Fixing bugs before your audience sees them Resolving Internet problems Virus protection Software updates Legacy clients A clear understanding of these topics will limit the number of bugs you inflict on your users
