Figure C: The Status screen provides summary information related to the connectionIf you look at the bottom of Figure C, you will notice the Configure and Diagnose buttons. Clicking the Configure button simply takes you to the connection’s configuration screen. This screen is very similar to the one that you are used to seeing in Windows XP. What’s more interesting though is the Diagnose button.
Clicking the Diagnose button takes you to a diagnostic tool that you can use to figure out why the connection is not working. This tool is a neat concept, but it’s one of those areas where Microsoft needs to do a little more work.
As I mentioned earlier, IPv6 is kind of a big deal in Windows Vista. IPv6 is Vista’s preferred protocol, but Vista runs IPv4 along side IPv6 for backward compatibility with existing networks. The reason why I say that Microsoft needs to do a little more work on the diagnostic tool is because as you saw in Figure C, my network connection is working fine. The only catch is that I am using IPv4 instead of IPv6. However, when I click the Diagnose button, Windows returns a bunch of errors related to IPv6, which I am not actively using, as shown in Figure D.
Clicking the Diagnose button takes you to a diagnostic tool that you can use to figure out why the connection is not working. This tool is a neat concept, but it’s one of those areas where Microsoft needs to do a little more work.
As I mentioned earlier, IPv6 is kind of a big deal in Windows Vista. IPv6 is Vista’s preferred protocol, but Vista runs IPv4 along side IPv6 for backward compatibility with existing networks. The reason why I say that Microsoft needs to do a little more work on the diagnostic tool is because as you saw in Figure C, my network connection is working fine. The only catch is that I am using IPv4 instead of IPv6. However, when I click the Diagnose button, Windows returns a bunch of errors related to IPv6, which I am not actively using, as shown in Figure D.
No comments:
Post a Comment