If you are facing trouble in connecting your smartphone, laptop, tablet or any other Wi-Fi enabled device with your office wireless LAN, then these 10 troubleshooting tips are here to help you out. Let’s have a look:-

Step 1: Check Your LAN and WAN connections

Many times the loose connection is the main culprit in these cases. Therefore it is suggestive to check all wireless router ports or access ports to ensure that the Ethernet cables are inserted properly. Further link status LEDs must be green at both ends. However if it is not:-

  • Verify clients at both ends of Ethernet cable are enabled or not.
  • Try Ethernet cable switching to determine damaged cable.
  • Check router manually to ensure that right cable is used
  • Try to connect another Ethernet capable client to your Wi-Fi like a laptop to the router port or AP.

If the LED status turn green then this is an indication that you have to replace your device as it is failing in auto-negotiation. In this case, check the port configuration at both ends and reconfigure it as required to match duplex mode and speed.

Step 2: Verification of wireless adapters

It seems to be quite obvious but it is really important to make sure that the Wi-Fi adapter used for the network troubleshooting is properly enabled and ready for the connection.

Step 3: Verification of Access Point and Router Settings

Use the Wireless access point or router’s administered Graphical User Interface to verify network setting for the SSID to which Wi-Fi client is trying to connect.

  • Locate SSID for the troubleshooting
  • Identify IP subnet assigned to SSID. On the successful connection, Wi-Fi client receives a local IP address from this subnet.
  • Identify AP’s or Router’s own local IP address that is reachable through this subnet.
  • Check router’s event log or GUI status to verify the IP address from this subnet.

Step 4: Verification of TCP/IP Settings

Although we have described how to manage wireless connection using windows, troubleshooting is conceptually similar if we are using with other types of Wi-Fi clients.

  • For this open, the network connection from the control panel, select the wireless network adapter. If the status is still disabled then return to step number 2.
  • Status is not connected- select wireless network’s SSID and clicks connect. But if your network SSID doesn’t appear in the list, then you can’t connect to the network, you have to debug the wireless settings.
  • While making an attempt of establishing a connection, the status changes briefly to Acquiring network address then connect. At this time, you can determine the client’s assigned IP address. For instance, if the IP of the client is 0.0.0.0 then click Diagnose. If that persists then move to the last step.
  • However, if the client’s Wi-Fi IP address is not in your routers or AP subnet then use internet/properties panel to reconfigure the connection to fetch the address automatically, repeat this step again.

Step 5: Verify the connection with Ping

Once Wireless client attains a valid IP address, then is time to verify network connectivity.

  • Run Command Prompt window from the client’s start menu and ping your router’s IP address with ICMP.
  • If pinging your router or AP fails repeatedly then skip to the next step.
  • If Pinging your router or AP is successful then ping any other wireless LAN or wired client that you want to share printer or files with. If this ping fails then it means that the destination is currently using a firewall to block the incoming messages.
  • Disable the destination’s firewall and then ping again.
  • Now if ping is successful then firewall you have disabled may be blocking windows network protocols. Reconfigure the firewall to permit the traffic you want to exchange amid LAN clients.

Step 6: Determine wireless-specific issues

Even after making so many changes in the configuration your wireless client is still can’t connect then it is time to consider wireless-specific problems

  • The wireless router or AP and client must use compatible 802.11 standards and the same SSID. Use your routers or AP admin GUI to view the WLAN setting and compare them with your client’s wireless connection parameters.
  • If your SSID doesn’t appear in current client’s available list then enable SSID broadcasts on your router or AP. Further add SSID to your client’s wireless network list, as it allows the device to connect even if SSID is hidden. But make sure you match SSID exactly including the capitalization.

Step 7: Determine Security mismatch

If a matched wireless client or router can hear each other but still can’t exchange traffic then certainly there is a security mismatch.
In this case, the client must support security mode. The router or AP requires WEP, open, WPA2 or WPA. Unless WLAN is unsecured, the router or AP and the client must have the same key to encrypt the traffic between them. Before, taking any step ahead compare your router or AP’s WLAN security settings to the client’s wireless connection properties to match them.

Step 8: Ensure proper working of Radius

WPA2-Enterprise and WPA log the client into the network and deliver encryption keys using 802.1X- capable RADIUS server. Further, if you don’t have a RADIUS server, the following tips are worth discussing:-

    • Reconfigure your router or AP and server with matching radius
    • Reconfigure your radius server to accept the request from your router or AP.
    • Ping to verify router or AP to radius server network reachability
    • Observe LAN packet counter to ensure radius is sent.

Step 9: Check user and 802.1X EAP login

If RADIUS is working properly still client’s access request is rejected then look for 802.1X EAP or user login problem. Further, ensure that your client at least supports one of EAP types your server requires. Supply valid login and password, certificate, token or another kind of credential.

Step 10: Intermitted Network Connectivity issues

Finally, your wireless client is connected and pings successfully, however, encounter intermitted network connectivity issues then it may be due to poor signal strength, disconnection by AP roaming or RF interference.

Leave a Reply

Your email address will not be published. Required fields are marked *