![router settings
Identify the IP subnet [and, if applicable, virtual LAN (VLAN) ID]
assigned to that SSID. Upon successful connection, your Wi-Fi
client should receive a local IP address from this subnet.
Identify the router or AP's own local IP address that should be
reachable through this subnet (and, if applicable, VLAN).
Check your router's events log or status GUI to verify that an IP
address from this subnet is indeed assigned to your Wi-Fi client
when it connects.](https://image.slidesharecdn.com/howtotroubleshootwirelessconnectionproblems-170109091536/85/How-to-troubleshoot-wireless-connection-problems-12-320.jpg)
How to troubleshoot wireless connection problems
- 2. Step 1: troubleshoot LAN connection problems (1-888-269-0130) Networks are finicky at best. Wireless or Ethernet, almost everyone has had their share of network connection problems. It could be anything from not being to access the Internet despite being connected to the network, to not being able to connect to the network at all. Unfortunately, network connection problems are sometimes hard to diagnose. A few articles here on Make Use Of give some help. Guy McDowell’s about weak wireless signals, and Karl about some simple diagnosis steps are both great resources.
- 3. Step-2 Check WAN and LAN connections (1-888-269-0130)(1-888-269-0130)
- 4. Check WAN and LAN connections (1-888-269-0130) To view the file in Windows XP, just open up Notepad and go to File->Open. Then, navigate to your C drive, then to the “Windows” Folder, then “System32” folder, then “drivers” folder, then “etc” folder and finally, open the file named “hosts“. You may have to change where it says “Text Documents” to “All Files” to see the hosts file. Connect another Ethernet-capable device, such as a laptop, to the affected AP or router port. If link status LED s change, the device that you just replaced may be failing link auto- negotiation. Check port configurations at both ends and reconfigure as needed to match speed and duplex mode.
- 5. Step3- Verify wireless adapter (1-888-269-0130)
- 6. Step 3 : Verify wireless adapter (1-888-269-0130) It should only have the heading stuff and maybe the line designating the local host. Anything else should be deleted. The instructions are the same for Vista and Windows 7, only instead of just opening Notepad, you have to right click the Notepad icon and choose to “Run as administrator” to edit the file. When using a Windows client, select your wireless network adapter from the Network Connections Control Panel and check to see if its status is Enabled. If not, right-click to enable the connection. If this fails when using a laptop, look for a function key or physical button or slider-switch to take the laptop out of airplane mode.
- 8. Step4: Verify wireless For XP, got to Control Panel and then Network Connections. In Windows Vista/7, go to the Control Panel and then the Network and Sharing Center. In 7, click on “change adapter settings.” In Vista, click on “manage network connections“. In all versions of Windows, after you get to the places designated above, right click the device giving you trouble, either the Wireless card or Ethernet card. Then select “Properties.”
- 9. Step-5 Verify AP and router settings
- 10. Step-5 Verify AP and router settings Sometimes what seems like a network outage is actually a problem on a specific website’s end. If you can’t get on Twitter, check another few websites to make sure that it’s not just them. You can use Is Up. me to check if a website is down for everyone or just you. Go ahead and reboot your PC, as well as your modem and router. To clear the modem and router caches, wait 60 seconds before you turn them back on again. Turning everything off and back on first ensures that it isn’t a temporary problem. It’s better to reboot now than to waste 30 minutes continuing on when you don’t need to.
- 12. router settings Identify the IP subnet [and, if applicable, virtual LAN (VLAN) ID] assigned to that SSID. Upon successful connection, your Wi-Fi client should receive a local IP address from this subnet. Identify the router or AP's own local IP address that should be reachable through this subnet (and, if applicable, VLAN). Check your router's events log or status GUI to verify that an IP address from this subnet is indeed assigned to your Wi-Fi client when it connects.
- 14. Verify TCP/IP settings While attempting to connect, status may change briefly to Authenticating or Acquiring Network Address, then Connected. At that point, use Status/Support to determine the client's assigned IP address. If the client's IP is 0.0.0.0 or 169.254.x.x, click Diagnose. If that persists, go to step 8. Otherwise, if the Wi-Fi client's IP address is not in your AP or router's subnet, use the Properties/Internet (TCP/IP) panel to reconfigure the connection to get an address automatically and repeat step 4.
- 15. Connect your computer to the server
- 16. Connect your computer to the server Once your wireless client has a valid IP address, use ping to verify network connectivity. Run a Command Prompt window from the wireless client's Start menu and use it to ping your AP or router's IP address with the Internet Control Message Protocol as shown in Figure 5. If pinging your AP or router repeatedly fails, skip to step 6. If pinging your AP or router is successful, then ping any other wired or wireless LAN client that you wish to share files or printers with. If that ping fails, then the destination may be using a firewall to block incoming messages.