Wi-Fi Troubleshooting

Wi-Fi Troubleshooting

Wi-Fi Troubleshooting

Below are the steps that needs to be followed for troubleshooting a Wi-Fi network-

  • The first step would be check the LAN and WAN connections

Usually it happens that the physical connections become weak so it is important to check the wireless AP or the router ports. The LED light should be green on both the ends. If the LED lights are not green then-

  • We need to check if both ends of the devices have the power status on.
  • Ethernet cables can be swapped to check any damage.
  • Make sure that the cable used for the router or AP is of the right type.
  • We can also check the connection by the AP or router to some other device like laptop.
  • The next step is the verification of the wireless adaptor

It is important that we check if the Wi-Fi adaptor of the respective client is enabled for troubleshooting of the network

  • If we are using Windows as a client then we should check if it has the status as Enabled and if not then get your connection enabled. If the issue is with USB adaptor then we should insert it again.
  • When the client is Apple iOS then we need to check if we have not put them on airplane mode and the Wi-Fi connection is enabled.
  • If the client is Android even then we need to check for airplane mode settings and the Wi-Fi connection is enabled.
  • The third step is to verify the settings of the router and AP

We need to use the AP or administrative GUI of the router to network settings.

  • We need to locate the SSID that needs troubleshooting.
  • Then its IP subnet needs to be identified that is assigned to the SSID. When the connection is done we receive one local IP address by the Wi-Fi client.
  • Then we need to identify the local IP address of the AP or router that is to be reached from this subnet.
  • Check AP’s or router’s events log to verify if an IP address is assigned to the user of Wi-Fi.
  • The next step is to check any wireless specific issues

If you are unable to connect to the wireless still then you should consider checking the problems specific to wireless.

  • One needs to enable SSID broadcasts on the router or AP if the SSID is unable to appear in the available network’s list.
  • We should look for a mismatch in the security

If the router or AP are matched but are unable to still connect with each other or exchange traffic then we should investigate for mismatch of security.

It is important that the security mode of the router or AP matches with the client’s support. We should compare the security settings of the router WLAN or AP to the wireless connection properties of the client.

  • If WEP is used for the router or AP then the encryption of the client should be set to WEP and their authentication type should be matched.
  • If WPA-Personal is used in the router or AP then the authentication of client authentication should be set to WPA-PSK and their encryption types should be matched.
  • If WPA2-Personal is used in the router or APr then the authentication of client should be set to WPA2-PSK and their encryption types should be matched.
  • If WPA or WPA2-Enterprise is used in the router or AP then the authentication of client should be set to WPA or WPA2 respectively and their encryption types should be matched.
  • The next step is to make sure that the radius is in working condition

If you have a RADIUS server try the following:

  • We must reconfigure the AP and its server to a similar matching RADIUS server. We also reconfigure the RADIUS server so that it accepts requests from AP.
  • Verify router or AP with RADIUS server network reach ability.
  • Keep a watch on LAN packet counters so as to verify that we can send RADIUS.
  • The last step is to check connectivity and intermittent network issue

And lastly, if the wireless network client gets connected and pings successfully; however, it still encounters some network connectivity problems like some of the pings work and some of them fail then it might happen that you are experiencing a poor signal, or disconnection which is caused by AP roaming.