Wireless Network Troubleshooting

Overview

The process of troubleshooting the network if they have wireless components, is more complex than wired infrastructure. In reality it is necessary to solve the wired and wireless infrastructure to determine the problem. The methodology starting from the customer and work through the OSI model application layer is effective with the wiring. The wireless client traffic does not see any wiring until it has been the association withAccess Point. In essence, there is a wireless data connection between client and access point. This established relationship of traffic data between access points and switches wired network.

The customer has a wired Cat-5 cable inserted into the wired switch that ends in a desktop. All customers associate with a specific access point now share a single CAT 5 cable between the 'switch of the access point. This makes it easier to troubleshoot, as the wiring is the source of manyNetwork problems, problems with that cable, however, apply to all customers. It 'important to minimize the performance by the number of access points for customers the best. implementations of the network average 10-24 clients to the access point.

The key to troubleshooting is to determine what has changed. Sometimes it's the hardware that does not work or made some changes, such as new equipment or software configured additional staff stressed the network. Could bea particular problem or several problems. Start with the client adapter to determine the specific symptoms and go from there.

What follows is a series of questions that can be used as a guide for troubleshooting:

1. If the client to connect to any wireless access point?

2. You can ping the IP address change?

3. Can you ping the router?

4. Can you ping the DHCP server?

5. If the client has an IP address?

6. Youthe WAN connection available?

7. It is a software client installed on the new?

8. Not all customers experience the problem?

9. It 's a coincidence or a pattern?

10. Is there any server or application-specific details?

11. If the IP address of the DNS server is set up correctly?

12. There is a firewall to filter traffic?

TOOLS:

a) Wireless Client software displays status information such as Access Point Association, DHCP enabled, the IP address, default gateway, DNS server address.

b) Control Panel displays the settings of your wireless network adapter, the configuration of the firewall, etc.

c) Check to see if the ping network routing.

information packet of study) packet network sniffer, such as protocols, programs or filtered error with applications.

e) recognize high frequency spectrum disorders and possible sources.

COMMON PROBLEMS Wireless

Wireless> Client Settings

• Update the client adapter driver manufacturer.

• Implement the pack of the Windows operating system service.

• Check client data rates, transmission power, preamble, the decision to roaming, WPA settings.

• Confirm that the application of shared keys do not match between client and AP.

• You can check the IP address. DHCP client-specific settings for each. These clients withoutDHCP to configure the IP address, subnet mask, default gateway and DNS server IP address.

• The client SSID configured, the AP configured with.

• Confirm the AP have the recommended IOS version with the specific functions.

• Check the mounting AP change and, if necessary, with installation instructions.

• Delete all configured loopback addresses.

• Configuring power Setting up and down when there is interference between channels.

• Configuration mixed 802.11b / g environments, each with 802.11b AP rates database.

• Configuration of data transmission speed and duplex settings to switch between AP and the same thing.

Design

• Configuration data set and the match between duplex wireless bridges.

• standard Cat 5 UTP cable should not exceed 328 feet between AP and switches.

• Distance from the wireless> Client-to-access point must be within the specified area.

• Maximum number of clients per access point should be no more than 17-24