mcts training kit 70 - 685 Windows 7 Enterprise Desktop Support Technician phần 9 docx

520 APPENDIX D Troubleshooting Hardware, Driver, and Disk Issues ■ Turn Off Non Volatile Cache Feature Enable this policy to completely disable all use of the nonvolatile cache. ■ Turn Off Solid State Mode Enable this policy to prevent frequently written fi les such as the system metadata and registry from being stored in the nonvolatile cache. How to Troubleshoot Driver Problems Drivers are software features that Windows uses to communicate with hardware accessories. Windows typically has dozens of drivers active at any given point, allowing it to communicate with your graphics card, hard disks, sound card, USB devices, and other hardware. Without a driver, hardware cannot function properly. Additionally, you might have problems with hardware if a driver is outdated or unreliable. The following sections describe how to work with drivers to solve hardware problems. How to Find Updated Drivers Microsoft or hardware vendors occasionally release updated drivers to improve hardware performance and reliability. Many updates are available directly from Windows Update. To fi nd and download any updates available for a computer, follow these steps: 1. Click Start, click All Programs, and then click Windows Update. 2. If available, click Check For Updates. 3. If Windows Update displays any optional updates, click View Available Updates. 4. Windows displays any driver updates if available. Select the update and then click Install. 5. Windows Update downloads any selected updates, creates a system restore point, and then installs the updates. Additionally, hardware manufacturers might release updated drivers directly to users before they are available on Windows Update. Check manufacturer Web sites for updated drivers. How to Use Driver Verifi er Windows 7 (and all versions of Windows since Microsoft Windows 2000) includes the Driver Verifi er (Verifi er.exe). You can run either graphical or command-line versions of the Driver Verifi er. To run a command-line version, open a command prompt and then type Verifi er.exe. To run the graphical version, click Start, type Verifi er.exe, and then press Enter. Driver Verifi er is useful for isolating a problematic driver that is causing a computer running Windows to intermittently fail, because you can use the tool to confi gure Windows to actively test potentially problematic drivers. After driver verifi cation has been confi gured for a driver, Z04A627093.indd 520Z04A627093.indd 520 2/8/2010 11:28:46 AM2/8/2010 11:28:46 AM How to Troubleshoot Driver Problems APPENDIX D 521 Windows puts additional stress on the driver during normal operations by simulating conditions that include low memory and verifi cation of I/O. Enabling driver verifi cation for a problematic driver is highly likely to initiate a Stop error that identifi es the driver. To use Driver Verifi er Manager to troubleshoot problems that might be related to a driver, enable driver verifi cation for all drivers that might potentially be causing the problems. Restart the system and then wait. Driver verifi cation happens in the background while the system performs normal tasks and might not yield immediate results. If a verifi ed driver returns an inappropriate response, Driver Verifi er will initiate a Stop error. If a Stop error has not occurred after several days, the verifi ed drivers might not be the source of the problem you are troubleshooting. After you have completed the troubleshooting process, use Driver Verifi er to delete the settings and disable driver verifi cation. NOTE Use Driver Verifi er only on nonproduction systems to identify a problematic driver. Using Driver Verifi er greatly increases the likelihood of a Stop error occurring and decreases system performance. To verify unsigned drivers, follow these steps: 1. Click Start, type Verifi er, and then press Enter. 2. Click Create Standard Settings and then click Next. 3. Click Automatically Select Unsigned Drivers and then click Next. As shown in Figure D-7, Driver Verifi er Manager fi nds unsigned drivers, enables verifi cation of those drivers, and then displays the list of unsigned drivers. FIGURE D-7 Driver Verifier Manager can help you identify problematic drivers. 4. Click Finish. 5. Click OK and then restart the computer. N OT E Use Driver Verifi er only on nonproduction systems to identify a problematic E driver. Usin g Driver Verifi er g reatl y increases the likelihood of a Stop error occurrin g a nd decreases system per f ormance . Z04A627093.indd 521Z04A627093.indd 521 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM 522 APPENDIX D Troubleshooting Hardware, Driver, and Disk Issues To verify all drivers, follow these steps: 1. Click Start, type Verifi er, and then press Enter. 2. Click Create Standard Settings and then click Next. 3. Click Automatically Select All Drivers Installed On This Computer and then click Finish. 4. Click OK and then restart the computer. To disable driver verifi cation, follow these steps: 1. Click Start, type Verifi er, and then press Enter. 2. Click Delete Existing Settings and then click Finish. 3. Click Yes. 4. Click OK and then restart the computer. How to Use the File Signature Verifi cation File Signature Verifi cation (Sigverif.exe) detects signed fi les and allows you to ■ View the certifi cates of signed fi les to verify that the fi le has not been tampered with after being certifi ed. ■ Search for signed fi les. ■ Search for unsigned fi les. NOTE Unsigned or altered drivers cannot be installed on x64-based versions of Windows. Driver signing is a multistage process in which device drivers are verifi ed. For a driver to earn this certifi cation, it must pass a series of compatibility tests administered by the Windows Hardware Quality Labs (WHQL). Because of stringent WHQL standards, using signed drivers typically results in a more stable system. When troubleshooting a problem that might be caused by a driver, you might choose to remove unsigned drivers to eliminate the possibility that the unsigned driver is causing the problem. Although most unsigned drivers will not cause problems, they have not been verifi ed by Microsoft and therefore have a higher risk of causing problems than signed drivers. Microsoft digitally signs drivers that pass the WHQL tests, and Windows performs signature detection for device categories such as: ■ Keyboards ■ Hard disk controllers ■ Modems ■ Mouse devices ■ Multimedia devices ■ Network adapters ■ Printers NOT E Unsigned or altered drivers cannot be installed on x64-based versions of Windows. E Z04A627093.indd 522Z04A627093.indd 522 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM How to Troubleshoot Driver Problems APPENDIX D 523 ■ SCSI adapters ■ Smart card readers ■ Video adapters A Microsoft Corporation digital signature indicates that a driver fi le is an original, unaltered system fi le that Microsoft has approved for use with Windows. Windows can warn or prevent users from installing unsigned drivers. If a driver is not digitally signed, the user receives a message that requests confi rmation to continue. Microsoft digitally signs all drivers included with Windows or distributed by Windows Update. When you download updated drivers from a manufacturer’s Web page, always select drivers that are signed by Microsoft. The following tools are useful for troubleshooting problems caused by unsigned fi les: ■ File Signature Verifi cation ■ Device Manager ■ Driver Verifi er Manager To identify unsigned drivers, follow these steps: 1. Click Start and then type Sigverif. Press Enter. 2. In the File Signature Verifi cation window, click Start. 3. After several minutes, the Signature Verifi cation Results page displays unsigned drivers. Unsigned drivers can be reliable, but they have not undergone the same testing that is required of signed drivers. If you are experiencing reliability problems, you should replace unsigned drivers with signed versions from Microsoft. 4. Click Close to return to the File Signature Verifi cation window. 5. Click Close again. How to Use Device Manager to View and Change Resource Usage Installing new hardware or updating drivers can create confl icts, causing devices to become inaccessible. You can use Device Manager to review resources used by these devices to manually identify confl icts. Typically, however, you should let Windows automatically allocate resources. With modern hardware, there is almost never a valid reason to adjust resource usage manually, and you might cause more problems than you resolve. To use Device Manager (Devmgmt.msc) to view or change system resource usage information, follow these steps: 1. Click Start, right-click Computer, and then click Manage. 2. Click Device Manager and then double-click a device. 3. Click the Resources tab to view the resources used by that device. 4. Click a resource and then clear the Use Automatic Settings check box. 5. Click Change Setting and then specify the resources assigned to the device. Z04A627093.indd 523Z04A627093.indd 523 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM 524 APPENDIX D Troubleshooting Hardware, Driver, and Disk Issues How to Use System Restore System Restore regularly captures system settings so that you can restore them later if you experience a problem. Using System Restore to return your computer to an earlier state should be one of your last troubleshooting steps, however, because it might cause problems with recently installed applications and hardware. You can run System Restore from within either the System Recovery tools or from within Windows. To use System Restore from System Recovery tools (which is necessary only if Windows will not start), see Appendix C. To use System Restore from within Windows, follow these steps: 1. Click Start, click All Programs, click Accessories, click System Tools, and then click System Restore. The System Restore Wizard appears. 2. If this is the fi rst time you are running the System Restore Wizard, click Next to accept the default restore point. Then, skip to step 4. 3. If you have run System Restore previously and it did not solve the problem, click Choose A Different Restore Point and then click Next. 4. On the Restore Your Computer To The State It Was In Before The Selected Event page, select the most recent restore point when the computer was functioning correctly. Click Next. 5. On the Confi rm Your Restore Point page, click Finish. When prompted, click Yes. 6. System Restore restarts your computer. When the restart has completed, System Restore displays a dialog box to confi rm that the restoration was successful. Click Close. If System Restore does not solve your problem, you can do one of two things: ■ Undo the system restore The problem might not be the result of changes to your computer at all, but rather a hardware failure. Therefore, using System Restore might not solve your problem. Because restoring the computer to an earlier state might remove important changes to your system confi guration, you should undo any restorations that do not solve your problem. To undo a system restore, simply rerun System Restore using the steps in this section and choose the default settings. ■ Restore an earlier restore point Your problem may be caused by recent changes to your computer, but the negative changes occurred before the most recent system restore. Therefore, restoring an earlier restore point might solve your problem. Repeat the steps in this section to restore to an earlier restore point. How to Troubleshoot USB Problems The most common way to connect external devices to a computer is USB. USB provides expandability without the complexity of connecting internal devices such as PCI cards. Connecting USB devices is so simple that most users can connect and confi gure USB devices without help from the Support Center (provided that they have suffi cient privileges). Z04A627093.indd 524Z04A627093.indd 524 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM How to Troubleshoot USB Problems APPENDIX D 525 However, users do occasionally experience problems with USB devices. The following sections provide guidance for troubleshooting USB problems. How to Solve USB Driver and Hardware Problems If you do experience problems, following these steps might solve them: 1. Restart the computer. Some software might require the computer to be restarted before functioning properly. Additionally, restarting the computer forces Windows to detect the USB hardware again. 2. Install updated driver software, if available. Check Windows Update and the hardware manufacturer’s Web site for updates. 3. Uninstall the device’s driver and software, disconnect the USB device, restart the computer, and then follow the manufacturer’s instructions to reinstall the software. Many USB devices require a driver. Typically, the driver should be installed before connecting the USB device. If you are experiencing problems with a USB device, the most likely cause is a driver problem. For information on how to troubleshoot the driver problem, see the section titled “How to Troubleshoot Driver Problems” earlier in this appendix. External storage devices such as USB fl ash drives and external hard drives typically do not require a driver, because the required software is built into Windows. 4. Disconnect the USB device and reconnect it to a different USB port. This can cause Windows to detect the device as new and reinstall required drivers. Additionally, this will solve problems related to a specifi c USB port, such as a failed port or power limitations. 5. Replace the USB cable with a new cable or a different cable that you know works properly. Understanding USB Limitations If you installed the USB device’s software correctly and you are using the most up-to-date version of the driver, you still might have problems because of USB’s physical limitations. Limitations that can cause problems include: ■ Insuffi cient power Many USB devices receive power from the USB port. Connecting too many unpowered devices to a USB hub can result in a power shortage, which can cause a USB device to not respond properly. This is particularly common when using an unpowered external USB hub. To quickly determine whether a problem is power related, disconnect other USB devices and connect each USB device directly to the computer one by one. If devices work when connected separately but fail when connected simultaneously, the problem is probably power related. Decrease the number of devices or add a powered USB hub. ■ Excessive length USB devices can be no more than 5 meters (16 feet) away from the USB hub to which they are connected. Although USB devices will never ship with cables longer than 5 meters (16 feet), some users connect USB extenders to allow longer distances. Depending on the quality of the cable and possible sources of interference, Z04A627093.indd 525Z04A627093.indd 525 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM 526 APPENDIX D Troubleshooting Hardware, Driver, and Disk Issues you might experience problems with shorter distances. To determine whether length is the source of problems, remove any USB extenders and connect the USB device directly to the computer. ■ Too many devices USB can support up to a maximum of 127 devices connected to a single USB host controller, which is more than enough for the vast majority of client computer scenarios. You can have a maximum of seven layers of USB hubs connected to the computer’s USB host controller, and no more than fi ve external hubs. ■ Insuffi cient bandwidth Most USB devices are designed to work within USB bandwidth limitations. However, video cameras in particular might need more bandwidth than USB is capable of providing. If you receive a “Bandwidth Exceeded” message, fi rst try disconnecting other USB devices. If the message continues to appear, attempt to reduce the bandwidth used by the device by lowering the resolution of the camera. For best results with a video camera, connect it to an IEEE 1394 (also known as Firewire or iLink) port. NOTE If you see the message, “Hi-speed USB device is plugged into non-hi-speed USB hub,” the USB device is USB 2.0, but the USB port is an earlier version. The device will probably work, but it will work slowly. You can improve performance by adding a USB 2.0 port to the computer. How to Identify USB Problems Using Performance Monitor If you are concerned that you may have a USB bandwidth or performance problem, you can identify the problem by using the Performance snap-in: 1. If the problem you need to identify occurs when you are actively using a USB device, connect the USB device that you want to troubleshoot and turn it on. If the problem occurs when you fi rst connect the USB device, do not connect the device until after you have begun logging. 2. Click Start, right-click Computer, and then select Manage. 3. Expand System Tools, Performance, Monitoring Tools, and then click Performance Monitor. 4. On the Performance Monitor toolbar, click the green Add button. 5. In the Add Counters dialog box, in the Available Counters group, expand USB. If you are troubleshooting the failure of a USB device, add the following counters for the <All Instances> instance: •• Iso Packet Errors/Sec •• Transfer Errors/Sec If you are troubleshooting a USB performance problem, add the following counters for the <All Instances> instance: •• Bulk Bytes/Sec •• Avg. Bytes/Transfer 6. Click OK to add the counters to Performance Monitor. NOT E If you see the message, “Hi-speed USB device is plugged into non-hi-speed USB E h ub,” the USB device is USB 2.0, but the USB port is an earlier version. The device will probably work, but it will work slowly. You can improve performance by adding a USB 2.0 p ort to the computer. Z04A627093.indd 526Z04A627093.indd 526 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM How to Troubleshoot USB Problems APPENDIX D 527 Performance Monitor begins collecting data about your USB devices and connections. Attempt to reproduce the problem (for example, by copying a fi le to a USB hard disk or connecting a video camera). If you are troubleshooting performance problems, right-click the Performance Monitor display and click Clear immediately after you begin using the device to ensure the counters include only data created during your test. The longer you allow the test to run, the more accurate it will be. You should stop Performance Monitor before your test ends. After reproducing the problem, pause Performance Monitor by clicking the Freeze Display button on the toolbar or by pressing Ctrl+F. Because you added performance counters for all instances, you probably have a large number of counters. To browse individual counters to identify the specifi c source of your problems, press Ctrl+H to enable highlighting. Click the fi rst counter in the list. After you select a counter, the graph related to that counter will be shown in bold. Examine the values for that particular counter. If the counter shows an error, make note of the USB controller and device causing the problem. Press the down arrow on your keyboard to select the next counter and continue analyzing USB performance values. USB errors should not occur under normal circumstances; however, Windows can automatically recover from many USB errors without affecting the user. After you identify the source of the USB problems, follow the steps in the section titled “How to Solve USB Driver and Hardware Problems” earlier in this appendix. If you are troubleshooting USB performance problems, examine the Bulk Bytes/Sec counter to identify the instance that relates to the device you are using. Then select the counter and make note of the Average value. Theoretically, USB 2.0 can transfer a maximum of 60,000,000 bytes/sec. However, this theoretical maximum will never be realized. More realistically, you might be able to achieve half that value. USB storage devices are often much slower, and performance will vary depending on the performance of the device itself. USB hard disks typically average less than 10,000,000 bytes/sec but can peak over 20,000,000 bytes/sec. Performance of hard disks will also vary depending on the portion of the disk being written to or read from, the size of the fi les being accessed, and the disk fragmentation. How to Examine USB Hubs Connecting a USB device to a computer can include several different layers: ■ A USB host controller, which is connected directly to your computer USB host controllers are often built into the computer’s motherboard, but you can add them by using an internal adapter or a PC card. If the name of the controller includes the word “Enhanced,” the controller supports USB 2.0. ■ A USB root hub, which is connected directly to the USB host controller Typically, USB root hubs are built into the same device that contains the USB host controller— your computer’s motherboard or an adapter card. ■ Optionally, additional USB hubs that connect to the USB root hub to create additional USB ports USB hubs can be external devices that you add, they can be an internal device within a computer, or they can be built into a docking station. Z04A627093.indd 527Z04A627093.indd 527 2/8/2010 11:28:47 AM2/8/2010 11:28:47 AM 528 APPENDIX D Troubleshooting Hardware, Driver, and Disk Issues You can use Device Manager to examine the USB controllers and hubs in a computer, determine their power capabilities, and examine the power requirements of the connected devices. This can help you to identify the source of a USB problem. To examine USB devices, follow these steps: 1. Click Start, right-click Computer, and then select Manage. 2. In the Computer Management console, click Device Manager (under System Tools). 3. In the right pane, expand Universal Serial Bus Controllers. 4. Right-click an instance of USB Root Hub (there might be several) and then click Properties. 5. Click the Power tab, as shown in Figure D-8. This tab displays the power capabilities of the hub and the power requirements of every connected device. To determine the requirements of any specifi c device, disconnect the devices and connect them again one by one. FIGURE D-8 View USB root hub properties to determine power capabilities and requirements. How to Troubleshoot Bluetooth Problems Bluetooth is a wireless protocol for connecting accessories to computers. Bluetooth is commonly used to connect keyboards, mice, handheld devices, mobile phones, and global positioning system (GPS) receivers. Bluetooth is simple enough to confi gure that most users can connect Bluetooth devices without help from the Support Center. However, users may occasionally have problems Z04A627093.indd 528Z04A627093.indd 528 2/8/2010 11:28:48 AM2/8/2010 11:28:48 AM Troubleshooting Tools APPENDIX D 529 initiating a Bluetooth connection. Other times, a connection that previously worked may stop working for no apparent reason. If you cannot successfully connect a Bluetooth device, try these troubleshooting steps: 1. Verify that the device is turned on and that the batteries are charged. 2. Place the device within a few feet of your computer (but not too close to your Bluetooth adapter). Additionally, verify that the device is not near other devices that use radio frequencies, such as microwave ovens, cordless phones, remote controls, or 802.11 wireless networks. 3. Verify that the device has Bluetooth enabled and that it is confi gured as discoverable. For security reasons, many devices are not discoverable by default. For more information, refer to the instructions that came with the device. 4. Install any updates available from Windows Update. 5. Download and install updated software and drivers for your hardware. Hardware manufacturers often release updated software for hardware features after they release the hardware. You can typically download software updates from the manufacturer’s Web site. 6. Verify that Windows is confi gured to accept incoming Bluetooth connections. 7. Verify that security is confi gured correctly. You might have confi gured a nondefault passkey for your device. By default, many devices use 0000 or 0001 as a passkey. 8. Remove and reinstall the Bluetooth device. Troubleshooting Tools The sections that follow describe free Microsoft tools that can be useful for advanced troubleshooting. DiskView DiskView shows how fi les are physically laid out on your disk and allows you to view where specifi c fi les are stored. To run DiskView, save the fi le to a folder that is allowed to run executable fi les, such as C:\Program Files\. Specifi cally, you cannot save it to a Temporary Files folder. Then, right-click DiskView.exe and click Run As Administrator. Click the Volume list and select the volume you want to analyze. Then, click Refresh. DiskView will spend several minutes examining the contents of the disk. As shown in Figure D-9, the main window displays how fi les are laid out on a section of your disk. Below the main window is a map that shows your entire disk. The black overlay shows which portion of the disk is displayed in the main window. Z04A627093.indd 529Z04A627093.indd 529 2/8/2010 11:28:48 AM2/8/2010 11:28:48 AM [...]... ARP cache, open a command prompt and run the following command arp –a Interface: 192 .168.1.132 - 0xa Internet Address Physical Address Type 192 .168.1.1 0 0-1 1 -9 5-bb-e2-c7 dynamic 192 .168.1.210 0 0-0 3-ff-cf-3 8-2 f dynamic 192 .168.1.241 0 0-1 3-0 2-1 e-e 6-5 9 dynamic 192 .168.1.255 ff-ff-ff-ff-ff-ff static 224.0.0.22 0 1-0 0-5 e-0 0-0 0-1 6 static How to Clear the ARP Cache If you determine that one of the entries in... here Tracing route to support. go.microsoft.contoso.com [10.46. 196 .103]over a maximum of 30 hops: 0 contoso-test [ 192 .168.1.2 07] 4 10.125. 39. 213 5 1 10.211.240.1 3 10.128. 191 .73 6 tbr2-p012101.cgcil.ip.contoso.com [10.122.10.106] 8 gbr4-p50.st6wa.ip.contoso.com [10.122.2.54] 9 gar1-p 370 . stwwa.ip.contoso.com [10.123.203. 177 ] 10 10.1 27 .70 . 6 13 Z05A6 270 9 3.indd 550 10.128. 191 .245 tbr2-p013501.cb1ma.ip.contoso.com... routing loop between the routers at 10.128. 191 .245, 10.128. 191 .73 , and 10.125. 39. 213 Tracing route to support. go.microsoft.contoso.com [10.46. 196 .103]over a maximum of 30 hops: 0 contoso-test [ 192 .168.1.2 07] 1 10.211.240.1 3 10.128. 191 .73 4 10.125. 39. 213 5 6 10.128. 191 .73 7 10.125. 39. 213 8 10.128. 191 .245 2 10.128. 191 .245 10.128. 191 .245 10 9 10.128. 191 .73 10.125. 39. 213 (…continued…) Routing loops are generally... 10.128. 19. 245 0/ 100 = 0% | 10.128. 19 .73 0/ 100 = 0% | 10.12. 39. 213 0/ 100 = 0% | gbr1-p70.cb1ma.ip.contoso.com [10.12.40 .98 ] 0/ 100 = 0% | 6 40ms tbr2-p013501.cb1ma.ip.contoso.com [10.12.11.201] 0/ 100 = 0% | 7 62ms tbr2-p012101.cgcil.ip.contoso.com [10.12.10.106] 0/ 100 = 0% | 8 107ms gbr4-p50.st6wa.ip.contoso.com [10.12.2.54] 0/ 100 = 0% | 9 111ms gar1-p 370 . stwwa.ip.contoso.com [10.12.203. 177 ] 0/... [fe80::28db:d21:3f 57: fe7b%11]: 190 0 UDP [fe80::28db:d21:3f 57: fe7b%11]: 496 43 *:* UDP [fe80::a54b:d9d7:1a10:c1eb%10]: 190 0 *:* UDP Z05A6 270 9 3.indd 544 0.0.0.0:0 0.0.0.0: 491 52 TCP 544 0.0.0.0:33 89 TCP [fe80::a54b:d9d7:1a10:c1eb%10]: 496 41 APPENDIX E *:* *:* 1512 1360 1360 1360 1360 Troubleshooting Network Issues 2/18/2010 2:10: 17 PM Notice that the line in bold is listening for incoming connections on TCP port 33 89, which... intermittent problem RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9} The repair option appears to have successfully fixed the diagnosed problem ■ Applications and Services Logs\Microsoft \Windows\ Diagnostics-Networking\ Operational This event log details the inner workings of the Windows Troubleshooting Platform and will be useful primarily when escalating problems to Microsoft support IPConfig IPConfig (Ipconfig.exe)... : 0 0-1 3-D 3-3 B-5 0-8 F DHCP Enabled : Yes 538 Z05A6 270 9 3.indd 538 APPENDIX E Troubleshooting Network Issues 2/18/2010 2:10:16 PM Autoconfiguration Enabled : Yes Link-local IPv6 Address : fe80::a54b:d9d7:1a10:c1eb%10(Preferred) IPv4 Address : 192 .168.1.132(Preferred) Subnet Mask : 255.255.255.0 Lease Obtained : Wednesday, September 27, 20 09 2:08:58... running Windows that has Remote Desktop enabled Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 884 TCP LISTENING 1512 0.0.0.0:0 LISTENING 592 192 .168.1.132:1 39 0.0.0.0:0 LISTENING 4 TCP 192 .168.1.132:33 89 192 .168.1. 196 : 173 2 ESTABLISHED 1512 TCP [::]:135 [::]:0 LISTENING 884 TCP [::]:445 [::]:0 LISTENING 4 TCP [::]:28 69 [::]:0 LISTENING 4 TCP [::]:33 89. .. [wininit.exe] TCP 0.0.0.0: 491 53 Eventlog [svchost.exe] TCP 0.0.0.0: 491 54 nsi [svchost.exe] TCP 0.0.0.0: 491 55 Schedule [svchost.exe] TCP 0.0.0.0: 491 56 [lsass.exe] TCP 0.0.0.0: 491 57 [services.exe] TCP 1 69. 254.166.248:1 39 TCPView, a free download from Microsoft, provides similar functionality with a graphical interface TCPView is described later in this appendix Tools for Troubleshooting Z05A6 270 9 3.indd 545 APPENDIX... replaced before it can be used with Windows 7 532 APPENDIX D Z04A6 270 9 3.indd 532 Troubleshooting Hardware, Driver, and Disk Issues 2/8/2010 11:28:48 AM APPENDIX E Troubleshooting Network Issues NOTE E This material was originally published in a slightly different form in Windows 7 Resource Kit by Mitch Tulloch, Tony Northrup, Jerry Honeycutt, Ed Wilson, and the t Windows 7 Team at Microsoft (Microsoft Press, . –a Interface: 192 .168.1.132 0xa Internet Address Physical Address Type 192 .168.1.1 0 0-1 1 -9 5-bb-e2-c7 dynamic 192 .168.1.210 0 0-0 3-ff-cf-3 8-2 f dynamic 192 .168.1.241 0 0-1 3-0 2-1 e-e 6-5 9 dynamic 192 .168.1.255. 192 .168.1.132 0xa Internet Address Ph y sical Address T yp e 192 .168.1.1 0 0-1 1 -9 5- bb -e2-c7 dy nam i c 192 .168.1.210 0 0-0 3- ff -c f -3 8-2 f dynamic 192 .168.1.241 0 0-1 3-0 2-1 e-e 6-5 9. 192 .168.1.241 0 0-1 3-0 2-1 e-e 6-5 9 d y namic 1 9 2.1 68 .1.2 55 ff-ff-ff-ff-ff-ff static 224.0.0.22 0 1-0 0-5 e-0 0-0 0-1 6 stat ic Z05A6 270 9 3.indd 537Z05A6 270 9 3.indd 5 37 2/18/2010 2:10:16 PM2/18/2010 2:10:16