But if you find your PC still disconnected from the network (and/or the Internet) after it’s put through its paces, you can – and probably should – check on some (or all) of the following issues:ġ. The Windows network troubleshooter does a pretty thorough job of checking all of these things as it runs through its various tests. Third come all the various protocols used to support email, web, file transfer, and all the other Internet services that let users do things with networks they wish to access and use, along with the applications that support them (Outlook for email, Chrome or Firefox for Web access, and on and on). Second, the TCP/IP networking protocol (and wireless support, where applicable) may have issues with the software, or the addresses and services used to make it work – such as DHCP for local addresses, DNS for name resolution, and so forth. First, the hardware that lets information come and go from the device might have issues (these span a wide range of possibilities including outright failure, shorts, partial or intermittent malfunctions, incorrect set-up or configuration, or incompatibility with local network capabilities and connections). This applies equally to Windows PCs and other devices, but the details will differ. There are three basic ways in which networking can go wrong. But a restart will often clear whatever’s causing problems, so this is always worth a try if the network troubleshooter can’t fix what’s ailing your Windows network connection. But sometimes, Windows gets itself into a state where some things don’t work – including networking, in this context. Nowadays, if you use that same key combo, you’ll get the logout screen, from which you can indeed get to the restart button. Restart your PC: In the DOS and early Windows days this was sometimes called the “three-fingered salute” and worked if the key combination CTRL-ALT-DEL was entered. This is often signaled at the device itself (my Arris SAC2V1A has a status light that changes from blue to red to signal a connection problem, for example). In many cases (except when a service outage persists) restarting the boundary device will set things back to rights. I’ve seen power glitches, signaling issues, and even service outages show up as a boundary device issue. Anyone who uses a device at their network boundary to get off the LAN and onto an ISP’s network will see issues present at this device occasionally. Restart your modem, router, or access point (all three apply to Wi-Fi, and the first two to wired Ethernet). Notice the button that reads “Restart adapter.” This performs the same actions you could do yourself in Device Manager by disabling the adapter, then re-enabling it after a short wait (usually 30 seconds or so). Turning it off, then back on, will usually clear such temporary glitches. In some situations, signaling or traffic issues can cause the network interface to stop working temporarily. Restart the network adapter (Wi-Fi or wired Ethernet, depending…): this basically turns off the network interface and then turns it back on. See this sequence in Figure 8.įigure 8: Various Ping commands check the IP stack, the network interface, the default gateway, and Internet access, respectively. Ping a known working Internet address for whatever reason MS often uses ping as its check). Ping the nearest router or gateway (Use ipconfig to look up the IP address for the “Default Gateway” – on my network it’s at 192.168.1.1, so that means ping 192.168.1.1 is the command to use)Ĥ. Ping localhost (this checks that the current network interface device is up and running)ģ. Ping loopback (this checks that TCP/IP is working, and looks for a response from a synthetic address that’s always available).Ģ. In the background, the troubleshooter checks local network access, Internet gateway access and then actual Internet access through a series of “reachability checks.” You can do the same thing at the command line using the PING command as follows:ġ. But because websites go down, too, changing to a different one helps determine if the “other end” of the attempted connection is itself having problems. Try a different website: Any given website is, of course, somewhere on the Internet. Let’s walk through those items to discuss what the troubleshooters look for, what they might find, and related fixes. The various actions suggested in the troubleshooters cover a wide array of possible problem sources. Figure 7: The wireless version of the troubleshooter checks Wi-Fi connections and capabilities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |