problem solving network issues

• Documentation
• Screenshots
• Try for Free

The Monitoring Agent

4 types of Agents to help you measure network and application performance.

Network Device Monitoring

Monitor the health of devices like Firewalls, Routers, Switches, Wifi APs and more.

• Network Performance Monitoring

Monitor network performance to find and fix issues before they affect users.

Public Monitoring Agents Directory

Proactively Monitor network performance with these service providers.

16 Most Common Network Problems: How to Find & Fix Them

Table of contents.

Intermittent network problems frustrate users, affect productivity levels, overwhelm your IT team, and are a pain for network administrators to solve. There are many problems that can affect network performance, and some of them are very complex to identify and understand.

To address these challenges, we've tailored this article specifically towards business networks, focusing on the most common issues that can plague them. Our aim is to help you proactively identify network problems, allowing you to take prompt action to resolve them. By equipping you with valuable insights and troubleshooting techniques, we intend to minimize network downtime and improve overall network performance.

In addition to our comprehensive guide on network problem identification, we understand the significance of real-time monitoring in maintaining a healthy network. With the combined knowledge of identifying network problems proactively and implementing efficient monitoring measures, you'll be empowered to create a robust and reliable network infrastructure.

To help you proactively identify network problems that may be plaguing your network, we’re running you through some of the most common network problems, including how to monitor and troubleshoot them!

What are Network Problems

Laggy video calls, slow application or network speed , buffering downloads, choppy VoIP Quality , and no Internet connection are examples of network problem symptoms. If you're struggling to perform everyday tasks over the Internet, or unable to use important apps, there's a good chance your network is to blame.

Network problems impact things like, VoIP calls, ERP applications (Netsuite or SAP performance issues ), files downloads, and more. Anytime a bad network disconnection or network connection issues prevents you from accessing something outside your computer, you're likely dealing with a network problem.

There are many different network problems that can affect network performance.

Some network problems can arise from faulty hardware, such as routers, switches, firewalls, and even from unexpected usage patterns, like network bandwidth spikes, changes in app configuration, or security breaches.

Network problems are frustrating, and left unattended, they can have disastrous consequences for your business network. That’s why it’s important to understand what can go wrong with your network and to continuously monitor network performance to quickly identify and fix network problems even before they affect your end-users.

Why Network Problems Are Inevitable For Businesses

Modern technology and the increasing use of hosted services has brought major changes to network and application infrastructures. While these changes have equipped users with more functionality than ever before, they have also greatly increased our dependence on a high functioning network to help us ensure the maintenance of these critical applications.

This means that when a network problem or network error occurs, it can be even more disastrous and difficult to solve.Despite our best efforts, these pesky issues tend to sneak their way in and wreak havoc on our connectivity. Here are some of the main reasons why network problems are bound to happen:

• Complexity : Business networks are intricate beasts, with numerous devices, servers, and software working in tandem. The more complex the network, the higher the likelihood of something going awry. Managing all these interconnected components can be challenging, and even the tiniest misconfiguration can lead to network hiccups.
• Human Error : We're all human, and mistakes happen. Whether it's a misconfiguration, a typo in a command, or accidental unplugging of cables, human error is a significant factor behind network problems. No matter how skilled and experienced the IT team is, the occasional oopsie is part of being human.
• Constant Changes : Business networks are dynamic environments, constantly evolving to accommodate new devices, software updates, and expanding user needs. Each change introduces the potential for compatibility issues, security vulnerabilities, and other problems that need to be addressed.
• External Factors : The network's performance can be impacted by external factors like internet service provider (ISP) outages, weather-related disruptions, or even cyberattacks. These external influences are often beyond the control of the business and can cause unexpected network troubles. Increased Network Traffic: As a business grows and gains more users, the network faces increased traffic demands. This surge in activity can strain the network infrastructure, leading to slowdowns and bottlenecks.
• Aging Hardware : Network equipment, like any technology, has a finite lifespan. As hardware ages, it becomes more prone to failures and performance issues. Regular maintenance and upgrades can help mitigate this, but eventually, replacement is inevitable.
• Security Threats : Cyberattacks and security breaches pose a constant threat to business networks. From malware infiltrations to DDoS attacks, these security issues can disrupt network operations and cause considerable downtime.

While network problems are inevitable, they are not insurmountable. With proactive and active network monitoring , regular maintenance, and a skilled IT team, businesses can minimize the impact of these issues and keep their networks running smoothly most of the time.

And knowing which network problems can affect your network the most can help you understand how to identify network issues fast.

How to Identify the Most Common Network Problems With Network Monitoring

When it comes to identifying and troubleshoot the most common network problems bound to pop up in your business' network - you're not alone! The best tool at your disposal is a Network Monitoring software.

A Network Monitoring tool (or Network Performance Monitoring) monitors end-to-end network performance to identify network issues affecting your end-users, whether the problems occur in your local network infrastructure, over the Internet, or even in a service provider's network.

We recommend a software like Obkio Network Performance Monitoring Software because it does the work for you.

Here's a quick overview about how to Use Obkio to identify and troubleshoot the network problems in this article:

Step 1: Set Up Network Monitoring

Obkio is an end-to-end Network Monitoring tool built to monitor and troubleshoot network problems related to connectivity, performance, VoIP, UC, Internet, network devices and more - for all network types!

Step 2: Monitor All Network Locations

Obkio identifies network problems using Monitoring Agents , which are deployed at key network locations and continuously exchange synthetic traffic for synthetic testing . Install Obkio's agents on strategic points within your network, such as routers, switches, or end-user devices. These agents will collect data on various network metrics like latency, packet loss, and bandwidth.

The Agents are deployed in locations like head offices, branch offices, and data centers for end-user experience monitoring , Internet performance, VoIP applications, UC apps, and more. They can also be installed in the Cloud for Cloud Network Monitoring (this can include Microsoft network monitoring , Zoom monitoring , AWS network monitoring , etc.).

Step 3: Measure Network Metrics:

Install Obkio's agents on strategic points within your network, such as routers, switches, or end-user devices. These agents will continuously measure and collect data on various network metrics like latency, packet loss, bandwidth usage, DNS response times, and other crucial performance indicators.

Step 4: Establish Baselines:

Monitor your network's performance under normal conditions to establish baseline metrics. This data will serve as a reference point for identifying deviations from normal behavior.

Step 5: Configure Alerts

Define specific thresholds for each metric, and set up alerts to notify you when a metric exceeds its defined limit. This will enable you to detect anomalies and potential issues in real-time.

Step 6: Investigate Alerts

When an alert is triggered, investigate the issue promptly. Use Obkio's real-time data and historical analysis to pinpoint the problematic area or device.

Step 7: Path Analysis

Utilize Obkio's path analysis feature to assess the performance of different routes taken by network traffic. This helps you identify congested paths and optimize routing.

Step 8: Trend Analysis

Regularly review historical data and performance trends to spot patterns or recurring problems. This analysis can reveal issues that might not be immediately apparent from real-time network monitoring .

Step 9: Collaborate and Resolve

Involve your IT team in the troubleshooting process, using Obkio's visualizations and data to facilitate collaboration. Work together to resolve network problems efficiently.

The Most Common Network Problems

Now let’s run through some of the most common network problems (or network errors) that have left many users and network administrators pulling out their hair!

But worry not, brave troubleshooters, we're not leaving you to wrestle with these issues alone. In addition to discussing each type of network problem, we'll equip you with valuable tips and techniques to identify and troubleshoot them like seasoned network warriors. So for each network problem we'll discuss:

• What the network problem is
• The consequences of that network problem
• The causes of the network problem
• How to identify & troubleshoot the network problem

Network Problem #1. Intermittent Network Problems

Intermittent network problems are a frustrating and common network issue characterized by sporadic disruptions in network connectivity and performance . Unlike consistent or continuous problems, intermittent issues occur irregularly, making them challenging to diagnose and troubleshoot.

These problems can manifest in various ways, including intermittent connection drops, slow data transfer, or periods of complete network unavailability.

I. The Consequences of Intermittent Network Problems:

• Unpredictable Performance : Intermittent issues make network performance unpredictable, leading to inconsistent user experiences.
• Unreliable Connectivity : Users may experience unreliable connectivity, with connections dropping unexpectedly or becoming temporarily unresponsive.
• Productivity Loss : Intermittent network problems can disrupt workflow and lead to productivity losses.
• Difficult Troubleshooting : Diagnosing intermittent issues can be challenging and time-consuming, delaying the resolution process.

II. The Causes of Intermittent Network Problems

• Loose or Damaged Cables : Interference from loose, damaged, or improperly connected network cables can result in intermittent connectivity issues.
• Wireless Interference : Radio frequency interference or signal blockage can lead to intermittent disruptions in Wi-Fi networks.
• Hardware Malfunctions : Intermittent network issues may arise from faulty network devices, such as routers, switches, or network interface cards (NICs).
• Software Conflicts : Software conflicts, outdated drivers, or firmware bugs can cause intermittent disruptions in network communication.
• Overheating : Network devices can experience intermittent issues when they overheat due to inadequate cooling or poor ventilation.
• IP Address Conflicts : Conflicting IP addresses assigned to devices can lead to intermittent connectivity problems.

III. How to Identify and Troubleshoot Intermittent Network Problems

• Network Monitoring : Utilize network monitoring tools like Obkio to continuously track network performance, diagnose network issues , and identify patterns of intermittent issues.
• Log Analysis : Examine network device logs to identify any recurring error messages or patterns during periods of intermittent disruptions.
• Cable and Connection Checks : Physically inspect network cables and connections to ensure they are secure and undamaged.
• Device Testing : Test network performance and network devices under different conditions to identify any intermittent hardware malfunctions.
• Software Updates : Ensure that network devices have the latest firmware, drivers, and software updates to fix known bugs and compatibility issues.
• Environmental Assessment : Evaluate the environmental conditions of network devices and ensure they are adequately cooled and placed in suitable locations.
• IP Address Management: Implement IP address management practices to prevent conflicts and ensure proper assignment of IP addresses.

By diligently identifying and addressing intermittent network problems, businesses can create a more stable and reliable network environment, minimizing disruptions and ensuring a consistent user experience. Network monitoring and thorough troubleshooting play a crucial role in detecting and resolving intermittent issues promptly.

Learn how to detect intermittent network problems to troubleshoot performance issues that are hard to catch with Obkio Network Monitoring software.

IV. Network Troubleshooting Scenarios for Intermittent Network Problems

Intermittent network problems can be frustrating and challenging to troubleshoot because they occur sporadically and may not be immediately apparent. Here are some network troubleshooting scenarios to consider when dealing with intermittent network problems:

• Loose or Damaged Cables : Physical issues with network cables, such as loose connections or damaged cables, can lead to intermittent connectivity problems. Inspect cables and connectors for any visible damage or loose connections.
• Wireless Interference : In a wireless network, interference from other wireless devices, neighboring networks, or electronic devices can cause intermittent connectivity issues. Conduct a wireless site survey and identify potential sources of interference.
• DHCP Issues : Problems with the DHCP (Dynamic Host Configuration Protocol) server can result in intermittent IP address assignment, leading to connectivity problems. Check DHCP logs and ensure the DHCP server is properly configured and responsive.
• DNS Problems : DNS (Domain Name System) issues can cause intermittent access to websites and services. Verify DNS settings and check for any DNS-related errors in the logs.
• Misconfigured Firewall or Security Software : Overly aggressive firewall rules or misconfigured security software can block legitimate traffic and cause intermittent connectivity problems. Review firewall and security software settings for potential issues.
• Bandwidth Saturation : Periodic spikes in network traffic can saturate the available bandwidth and cause intermittent connectivity problems. Monitor network traffic patterns to identify potential bandwidth saturation points.
• Network Device Overheating : Overheating of network devices, such as routers or switches, can lead to intermittent network outages or services outages (ex. Microsoft Teams outages ). Ensure that network equipment is properly ventilated and not subjected to excessive heat.
• Firmware or Software Bugs : Firmware or software bugs in network devices can cause intermittent problems. Check for firmware updates and apply the latest patches from the manufacturer.
• Duplicate IP Addresses : Duplicate IP addresses on the network can result in intermittent connectivity issues. Use network scanning tools to check for duplicate IP addresses.
• Routing Issues : Incorrect or unstable routing configurations can lead to intermittent connectivity problems. Review routing tables and ensure they are correctly configured.
• Power Fluctuations : Power fluctuations or intermittent power supply issues can cause network devices to reboot or lose connectivity. Use uninterrupted power supply (UPS) units to provide stable power to critical network equipment.
• Network Congestion : During periods of high network usage , congestion can cause intermittent performance issues. Monitor network traffic during peak hours and consider implementing Quality of Service (QoS) policies.
• Malware or Security Breaches : Malware infections or security breaches can cause intermittent network disruptions. Regularly scan for malware and implement robust security measures.

Network Problem #2. High Bandwidth Usage

Bandwidth is the maximum amount of data transmitted over an Internet connection in a given amount of time.

It refers to a network’s capacity to transfer data between devices or the Internet within a given span of time. Bandwidth is often mistaken for Internet speed when it's actually the volume of information that can be sent over a connection in a measured amount of time – calculated in megabits per second (Mbps).

Higher bandwidth allows data to be transferred across your network at a faster rate and can sustain a larger number of connected devices all at once - but it can significantly impact network performance and user experience.

It occurs when a considerable amount of data is being transmitted over the network, leading to increased congestion and potential bottlenecks . When someone or something, like a large application, on your network is monopolizing your bandwidth by downloading gigabytes worth of data, it creates a congestion in your network.

This excessive data transfer can result from various factors, both legitimate and non-legitimate, and it's essential to identify and address the root cause to maintain a smoothly functioning network.

I. The Consequences of High Bandwidth Usage:

• Network Congestion : Network congestion caused by high bandwidth usage, also runs the risk of leaving insufficient amounts of bandwidth for other parts of your network that need it. When this happens, you may start experiencing problems like slow download speed over the Internet.
• Slow Network Performance : High bandwidth consumption can lead to slower network speeds, causing delays in accessing resources and data.
• Latency and Packet Loss : As network resources become saturated, latency (delay) and packet loss may increase, affecting real-time applications like VoIP or video conferencing.
• Reduced Productivity : Sluggish network performance can hamper productivity, as users may experience delays in performing critical tasks.
• Increased Costs : Excessive bandwidth usage can lead to overage charges from internet service providers (ISPs) if they exceed the Internet SLA , or the need to upgrade to higher-tier plans, resulting in higher operational costs. Network Downtime: In extreme cases, high bandwidth usage can lead to network outages if the infrastructure is not equipped to handle the traffic load.

II. The Causes of High Bandwidth

• Large Downloads : Downloads consisting of large files that are being placed on your computer's harddrive from the Internet, like file transfers or backups, can drastically increase bandwidth usage. The more bytes the file contains, the higher your bandwidth usage.
• Latency : Latency refers to the time it takes for a data packet to reach its destination in a network, can. Consistent delays or odd spikes in delay time are signs of major performance issues and can affect bandwidth time.
• Packet Loss : Packet Loss occurs when a data packet is dropped during its journey across a network and never makes it to its final destination and back. It can cause a great deal of problems depending on how much of the packet does not go through and how often it occurs.
• Video Streaming : Streaming videos from the Internet is a more common cause of high bandwidth usage. Streaming video in 7k can take up to 200 times more bandwidth than audio streaming.
• Large Applications : Different applications have different requirements. Applications that require Internet connection, like programs for web development, email, computer games, etc. require a lot of bandwidth to function and can therefore increase your bandwidth usage.
• File Sharing : There are programs that allow users to share files from computer-to-computer connection over the Internet. These programs can result in high bandwidth usage as they require you to download and transfer large files, with large amounts of data, over the Internet.
• Legitimate Traffic : Legitimate high-bandwidth activities, such as large file transfers, video conferencing, cloud backups, and software updates, can consume significant network resources. While these activities are essential for business operations, they can lead to congestion during peak usage times.
• Malware and Unauthorized Activities : Malicious software or unauthorized users can exploit network resources, leading to unanticipated spikes in bandwidth usage. Botnets, malware downloads, or unauthorized file sharing can cause significant disruptions.
• Background Updates : Automatic updates for operating systems, applications, and antivirus software can utilize bandwidth without user intervention. These updates can coincide and cause temporary surges in bandwidth usage.
• P2P File Sharing : Peer-to-peer (P2P) file-sharing applications can lead to high bandwidth usage as users upload and download files directly from each other.

How to measure bandwidth, identify issues & optimize network performance. Use Obkio's Network Performance Monitoring tool for easy bandwidth monitoring.

III. How to Identify & Troubleshoot High Bandwidth Usage

• Network Monitoring : Use a network monitoring tool like Obkio to measure bandwidth and track bandwidth usage in real-time. Observe usage patterns and identify any unusual spikes or sustained high traffic.
• Application Analysis : Analyze the bandwidth consumption of various applications to identify resource-intensive processes. This will help you pinpoint which applications are contributing the most to high usage.
• Quality of Service (QoS) Policies : Implement QoS policies to prioritize critical applications and services over less important ones. This ensures that essential operations receive sufficient bandwidth even during peak usage.
• Bandwidth Optimization : Utilize bandwidth optimization techniques such as compression, caching, or content filtering to reduce overall data transfer.
• Traffic Shaping : Employ traffic shaping mechanisms to control and limit bandwidth usage for specific applications or users.
• Identify Malware or Unauthorized Activity : Regularly scan for malware and unauthorized users on the network, and implement security measures to prevent exploitation.

By proactively identifying and addressing high bandwidth usage, businesses can maintain a responsive and efficient network, enhancing overall productivity and user satisfaction.

IV. Network Troubleshooting Scenarios for High Bandwidth Usage

High bandwidth usage can lead to various network performance issues and can be caused by several factors. Here are some network troubleshooting scenarios to investigate when experiencing high bandwidth usage:

• Malware or Botnet Activity : Malware-infected devices or botnet activity can consume significant bandwidth as they may be involved in malicious activities such as sending spam emails or participating in Distributed Denial of Service (DDoS) attacks. Use network monitoring tools to identify suspicious traffic patterns and isolate infected devices.
• Streaming and Video Content : High-quality video streaming or large file downloads can consume substantial bandwidth. Check for excessive video streaming or downloads that might be impacting the network, especially during peak hours.
• Cloud Services or Backups : Cloud services and data backups can utilize substantial bandwidth, especially if they are scheduled to occur during business hours. Check the bandwidth consumption of cloud services (with Microsoft Cloud Monitoring for example) and backup applications to see if adjustments can be made to their schedules.
• Peer-to-Peer (P2P) File Sharing : P2P file sharing applications can consume a significant amount of bandwidth, especially if multiple users are involved. Identify and control P2P traffic on the network.
• Software Updates : Automatic software updates from operating systems and applications can lead to sudden spikes in bandwidth usage. Ensure that updates are scheduled during off-peak hours.
• Network Misconfiguration : Misconfigured network devices, such as routers or switches, can lead to unnecessary broadcast/multicast traffic or loops that cause high bandwidth usage. Verify the network configuration for any issues.
• Bandwidth-Intensive Applications : Some applications inherently consume more bandwidth than others. Identify and analyze bandwidth usage by specific applications and determine if any optimization or restriction is required.
• Virtual Local Area Networks (VLANs) : Improperly configured VLANs can lead to unnecessary traffic and high bandwidth usage. Review VLAN configurations to ensure they are set up correctly.
• Wireless Network Interference : In a wireless network, interference from other devices, neighboring networks, or non-Wi-Fi devices operating in the same frequency range can cause high bandwidth utilization. Perform a wireless site survey and optimize Wi-Fi settings.
• Data Backups and Replication : Data backup and replication processes between geographically dispersed sites can consume significant bandwidth. Review backup and replication schedules and consider using deduplication and compression techniques.
• Denial of Service (DoS) Attacks : DoS attacks can overwhelm a network with an excessive amount of traffic, leading to high bandwidth usage. Implement DoS protection mechanisms and analyze traffic patterns for signs of an ongoing attack.
• Internet of Things (IoT) Devices : The proliferation of IoT devices can contribute to increased bandwidth consumption if they are transmitting large amounts of data. Monitor IoT device traffic and assess their impact on overall bandwidth.

To troubleshoot high bandwidth usage, it is essential to use network monitoring tools that provide insights into traffic patterns, application usage, and device behaviour, like we mentioned in the last point. With this information, you can identify the root cause of the problem and take appropriate measures to optimize network performance.

Network Problem #3. High CPU Usage

CPU, or “ Central Processing Unit ”, is the primary component of a computer that receives and processes instructions for operating systems and applications.

High CPU usage is another common network problem that can significantly impact the performance and stability of a network. It occurs when the central processing unit (CPU) of a network device, such as a router, switch, firewall, or server, is operating at or near its maximum capacity . This can lead to various issues that affect the overall network functionality and user experience.

With such a big job on its shoulders, the signs of high CPU usage on a network device are a very troubling sign for many of us. As your network devices continue to work harder to perform an increasing amount of tasks, it increases the chance that things can go wrong.

I. The Consequences of High CPU Usage

• Sluggish Network Performance : High CPU usage can lead to delays in processing network traffic, causing slow response times and increased latency.
• Packet Loss : When the CPU is overloaded, it may drop packets, resulting in packet loss, which can degrade the quality of real-time applications like VoIP or video conferencing.
• Network Downtime : In extreme cases, when the CPU is overwhelmed, the device may become unresponsive, leading to network outages and disruptions.
• Security Vulnerabilities : High CPU usage can leave network devices more vulnerable to security threats as their ability to handle security tasks is compromised.

II. The Causes of High CPU Usage

The most common reason for high CPU usage occurs when your network becomes bogged down by enormous amounts of traffic. CPU usage can increase drastically when processes require more time to execute or when a larger number of network packets are sent and received throughout your network.

There are a number of network devices such as switches that have hardware components (ASICs or NPUs) that take charge and process packets super quickly. For this equipment, the CPU usage is not linked to the amount of traffic.

For equipment that analyzes or manipulates traffic, like firewalls, that's a whole different story. Depending on the features that you’ve enabled on your devices, the CPU may be in the critical path of packet routing or forwarding. If overused, network metrics like latency , jitter , and packet loss will increase, which will lead to significant levels of network performance degradation.

In summary, some common causes include:

• Network Traffic Overload : A sudden surge in network traffic or sustained high levels of data transfer can overwhelm the CPU, especially on devices handling routing, switching, or security tasks.
• Network Security Operations : CPU usage may spike during security-related activities such as deep packet inspection, intrusion detection, or denial-of-service attack mitigation.
• Resource-Intensive Applications : CPU usage can be driven up by resource-intensive applications running on servers or other network devices.
• Firmware/Software Bugs : Firmware or software bugs can cause abnormal CPU usage, leading to unexpected behavior and degraded performance.

III. How to Identify & Troubleshoot High CPU Usage

It can sometimes be difficult to gather the right information about the actual use of CPU. Several monitoring tools such as those included in the equipment's GUI or a poorly configured monitoring tool can report an average value on the use of 8 cores or over too long periods, such as every 5, 15 or 60 minutes. Which isn't enough - so to identify and troubleshoot - you need to go further!

• Network Monitoring : Employ a network monitoring tool like Obkio to track CPU utilization on network devices. Monitor CPU usage in real-time and set up alerts for abnormally high CPU levels.
• Identify Resource-Intensive Processes : Use monitoring tools and device logs to identify resource-intensive processes or applications causing high CPU usage.
• Adjust Network Traffic : Implement traffic shaping or quality of service (QoS) policies to prioritize critical traffic and prevent CPU overload during periods of heavy network usage.
• Software/Firmware Updates : Regularly update device firmware and software to patch bugs and optimize performance.
• Optimize Applications : Consider optimizing resource-intensive applications or distributing their load across multiple devices to reduce CPU burden.
• Security Measures : Ensure that security policies and mechanisms are properly configured to manage security-related CPU tasks effectively.
• Device Upgrades : If network devices are consistently experiencing high CPU usage, consider upgrading to more powerful hardware that can better handle the network load.

By promptly identifying and resolving high CPU usage issues, businesses can maintain a stable and responsive network environment, ensuring smooth operations and enhanced user satisfaction.

IV. Network Troubleshooting Scenarios for High CPU Usage

High CPU usage in a network can impact the performance of network devices, leading to sluggish response times, increased latency, and potential service disruptions. Here are some network troubleshooting scenarios to consider when dealing with high CPU usage on network devices:

• Traffic Spikes : Monitor network traffic patterns to identify if there are sudden spikes in data volume that could be causing high CPU usage. Investigate the source of the increased traffic and determine if it is legitimate or if it indicates a potential DDoS (Distributed Denial of Service) attack.
• Packet Storms or Broadcast Storms : Excessive packet storms or broadcast storms can overload the CPU of network devices. Use packet capture tools to analyze the traffic and identify any sources of storms.
• Malware or Botnet Activity : Malware infections on network devices can cause high CPU utilization as they might be involved in malicious activities. Use security monitoring tools to detect and remove malware from affected devices.
• Routing or Switching Loops : Misconfigured or redundant routing or switching paths can cause loops, leading to a significant increase in CPU usage. Review the device configurations to ensure there are no loop-causing issues.
• Software Bugs or Memory Leaks : Software bugs or memory leaks within the operating system or network device firmware can cause CPU usage to spike over time. Ensure that the network devices have the latest firmware updates and patches.
• Network Device Overloading : If a network device is overloaded with traffic due to the number of connected devices or the volume of data being processed, the CPU usage can increase. Consider load balancing or upgrading the device to handle higher traffic volumes.
• Large Scale Routing Updates : In networks with dynamic routing protocols, large-scale routing updates can cause CPU spikes on routers. Analyze routing update events and fine-tune the routing protocols to minimize the impact.
• Monitoring or Debugging Tools : Certain monitoring or debugging tools running on network devices might consume a significant amount of CPU resources. Evaluate the impact of such tools and adjust their configurations if necessary.
• Quality of Service (QoS) Misconfiguration : Improperly configured QoS policies can lead to unnecessary CPU usage as the devices attempt to classify and prioritize traffic. Review and optimize QoS policies.
• Hardware Issues : Faulty hardware components, such as failing CPUs or inadequate cooling systems, can lead to high CPU usage. Perform hardware diagnostics and replace any faulty components.
• Intrusion Detection/Prevention Systems (IDS/IPS) : IDS/IPS systems can be CPU-intensive, especially when handling a large number of network packets. Fine-tune the IDS/IPS settings and consider distributing the load across multiple devices if applicable.
• Virtualization Overhead : In virtualized environments, the hypervisor's CPU overhead can impact network device performance. Adjust virtualization settings and resource allocations as needed.

Network Problem #4. Physical Connectivity Issues

It may seem obvious, but some network issues may occur with the hardware outside of the network.

When the time comes to troubleshoot network issues , our instinct is often to think about the most complex situations, when sometimes the problem is actually very simple and right in front of us.

Hardware problems like defective cables or connectors can generate network errors on the network equipment to which it is connected . You may think that this problem is due to a network outage or network failure , or Internet connection problem, but it’s actually because you have a broken or malfunctioning cable.

This can also occur outside of the LAN network . If a copper cable, or fiber-optic cable is damaged, it will likely reduce the amount of data that can go through it without any packet loss.

I. The Consequences of Physical Connectivity Issues

Physical connectivity problems can manifest in various ways, leading to network outages, slow data transfer, or intermittent connectivity.

• Network Outages : A complete loss of physical connectivity can lead to network outages, preventing users from accessing network resources.
• Intermittent Connectivity : Loose or damaged cables may cause intermittent connectivity issues, resulting in unreliable network access.
• Slow Data Transfer : Poor physical connections can lead to data transmission errors and retransmissions, slowing down data transfer rates.
• Increased Downtime* : The time spent identifying and resolving physical connectivity issues can lead to increased network downtime and reduced productivity.

II. The Causes of Physical Connectivity Issues

• Loose or Damaged Cables : Loose, damaged, or improperly connected cables can lead to signal loss and intermittent connectivity. Cables that are bent, frayed, or crushed may not transmit data effectively.
• Faulty Connectors : Connectors that are not securely attached or have bent pins can result in poor connections between devices, leading to data transmission issues.
• Cable Length : Using cables that exceed their maximum recommended length can lead to signal degradation and data loss.
• Poorly Crimped or Terminated Cables : Improperly crimped or terminated cables may cause signal interference and connectivity problems.
• Network Device Issues : Faulty network interface cards (NICs) or malfunctioning ports on switches or routers can cause physical connectivity problems.
• Environmental Factors : External factors such as water damage, extreme temperatures, or physical disturbances can impact network cables and connectors.

III. How to Identify & Troubleshoot Physical Connectivity Issues

• Network Monitoring : Checking every cable one by one can be repetitive, and can take a large amount of time out of your day. A simple way to monitor cables on a defective connector is to have a network performance monitoring software , like Obkio, that will measure network errors on all network interfaces and warn you if any problems arise.
• Visual Inspection : Perform a physical inspection of cables, connectors, and network devices to identify any visible signs of damage or loose connections.
• Cable Testing : Use cable testers to check for continuity and proper termination of network cables. Swap Cables and Connectors: If possible, try replacing suspect cables and connectors with known-good ones to determine if the issue persists.
• Check Device Indicators : Examine network device indicators, such as LED lights, to see if they indicate any connectivity or link issues.
• Environmental Assessment : Ensure that network equipment is kept in suitable environmental conditions, free from water damage, extreme temperatures, and physical obstructions.
• Label and Organize Cables : Properly label and organize network cables to prevent accidental disconnections and make troubleshooting easier.
• Update Firmware and Drivers : Ensure that network devices have up-to-date firmware and drivers to minimize the risk of hardware-related issues.

Learn how to troubleshoot network issues by identifying where, what, why network problems occur with Network Troubleshooting tools.

IV. Network Troubleshooting Scenarios for Physical Connectivity Issues

Physical connectivity issues can disrupt network communication and lead to various network problems. Troubleshooting physical connectivity issues requires a systematic approach and attention to detail. Here are some network troubleshooting scenarios to consider when dealing with physical connectivity issues:

• Check Physical Connections : Verify that all network cables, connectors, and ports are properly connected and securely seated. Ensure that Ethernet cables are not damaged and have all pins intact.
• Swap Cables and Ports : If possible, swap suspect cables with known-working ones and test different network ports on the devices to rule out faulty cables or ports.
• Check Link Lights : Observe the link lights on network devices (routers, switches, and network interface cards) to determine if the devices are detecting link signals. If link lights are not active, it could indicate a physical connectivity problem.
• Inspect Patch Panels and Wall Outlets : In structured cabling systems, examine patch panels and wall outlets to ensure cables are correctly terminated and properly labeled.
• Use Cable Testers : Cable testers can help identify faulty cables, open circuits, or short circuits. Use a cable tester to check the integrity of network cables.
• Check Power Over Ethernet (PoE) : For PoE devices, ensure that power is being supplied correctly over the Ethernet cables.
• Verify Power Status : Check the power status of network devices to ensure they are powered on and functioning correctly.
• Check Physical Damage or Environmental Factors : Look for physical damage to network cables caused by bending, crushing, or exposure to environmental elements. Address any environmental factors that might be affecting the cables, such as excessive heat or moisture.
• Review Network Topology : Review the network topology to ensure that cables are appropriately connected between devices and network segments.
• Test Connectivity with Known Devices : Test connectivity with known working devices to isolate the issue to specific network segments or components.
• Check Wiring Standards : Ensure that network cabling adheres to appropriate wiring standards (e.g., TIA/EIA 568) and that cables are of the correct category (e.g., Cat 5e, Cat 6, etc.) for the required network speeds.
• Check Cable Lengths : Verify that the cable lengths do not exceed the maximum allowed length for the chosen cable category and network technology (e.g., Ethernet has specific cable length limits).
• Inspect Network Devices' LEDs : Network devices like switches and routers often have LEDs that indicate port activity and speed. Observe these LEDs to identify any abnormal behavior.
• Check Physical Security : Ensure that physical access to network devices and cables is restricted to authorized personnel to prevent accidental or intentional disconnections.
• Consider EMI/RFI Interference : Electromagnetic Interference (EMI) or Radio-Frequency Interference (RFI) from nearby electrical devices can affect network connectivity . Isolate network devices from potential sources of interference.
• Inspect Fiber Optic Connections : If your network uses fiber optic cables, check the connectors and fiber ends for any dirt, damage, or misalignment.

Network Problem #5. Malfunctioning Devices or Equipment

Sometimes, network issues occur within network equipment or devices like Firewalls, Routers, Switches, Wifi APs.

Malfunctioning devices or equipment are a common network problem that can disrupt network operations and lead to various connectivity issues. This category encompasses hardware failures or malfunctions within network devices, such as routers, switches, firewalls, servers, or network interface cards (NICs) . When devices malfunction, they may experience performance degradation or cease to function altogether, impacting the overall network performance and user experience.

You need to ensure that all the devices on your network are configured correctly in order for your network to work properly. Whenever you install or reconfigure a device, or upgrade equipment firmware on your network, you need to test that device to ensure that it’s been configured correctly.

Many network performance issues are caused by device misconfigurations that can affect different parts of your network and turn into major problems down the line. That’s why you need to pay attention to all the switches and devices on your network to ensure that they’re always working as they should be, and react quickly if they aren’t.

I. The Consequences of Malfunctioning Devices or Equipment

• Network Downtime : When crucial network devices fail, it can result in network outages and disrupt communication and data transfer.
• Slow Performance : Malfunctioning devices may struggle to process network traffic efficiently, leading to slow data transfer and increased latency.
• Data Loss : Hardware failures can cause data loss, especially if the malfunctioning device is responsible for data storage or backups.
• Reduced Reliability : Frequent device malfunctions erode the network's reliability, causing frustration for users and hindering business operations.

II. The Causes of Malfunctioning Devices or Equipment

• Hardware Failure : Components within network devices can fail due to wear and tear, manufacturing defects, or age. Common hardware failures include power supply issues, memory failures, or fan malfunctions.
• Overheating : Network devices that are not adequately cooled or positioned in poorly ventilated areas can overheat, leading to malfunctions and performance degradation.
• Software Bugs : Firmware or software bugs within network devices can cause erratic behavior or crashes, impacting their ability to function correctly.
• Power Surges or Electrical Issues : Power surges or electrical problems can damage network devices and render them inoperable.
• Environmental Factors : Adverse environmental conditions, such as exposure to moisture, dust, or extreme temperatures, can contribute to device malfunction.

III. How to Identify & Troubleshoot Malfunctioning Devices or Equipment

• Network Device Monitoring : Use network monitoring tools like Obkio to track device performance metrics, such as CPU usage, memory utilization, and temperature readings. Abnormal values may indicate potential device malfunctions. Obkio’s network device monitoring solution is a simple and easy solution that offers advanced polling for SNMP Monitoring for all SNMP-enabled devices along your network to ensure they’re all performing as they should be.
• Device Logs : Review device logs and error messages to identify any hardware or software-related issues reported by the device.
• Hardware Diagnostics : Many network devices come with built-in diagnostic tools that can identify hardware failures or malfunctions.
• Hardware Replacement : If a device is suspected to be malfunctioning, consider replacing it with a known-working spare or a new device to confirm if the issue is resolved.
• Firmware/Software Updates : Ensure that devices have the latest firmware and software updates to fix known bugs and optimize performance.
• Temperature Management : Check the environmental conditions of network devices and ensure they are adequately cooled and placed in suitable locations.
• Power Protection : Implement surge protectors and uninterruptible power supply (UPS) systems to safeguard devices against electrical issues.

By proactively identifying and addressing malfunctioning devices or equipment, businesses can reduce network downtime, maintain reliable operations, and ensure an efficient and responsive network infrastructure.

Learn how to identify network issues by looking at common problems, causes, consequences and solutions.

IV. Network Troubleshooting Scenarios for Malfunctioning Devices or Equipment

When dealing with malfunctioning network devices or equipment, prompt troubleshooting is essential to identify and resolve the issues efficiently. Here are some network troubleshooting scenarios to consider when facing malfunctioning devices or equipment:

• Device Power Status : Check if the malfunctioning device is powered on and receiving adequate power. Verify power connections and consider testing the device with a different power source or power cable.
• Device Reset or Reboot : Perform a controlled restart or reboot of the malfunctioning device. Sometimes, a simple restart can resolve temporary issues.
• Check Device Status Lights : Observe the status lights or LEDs on the malfunctioning device to identify any error codes or abnormal behavior. Refer to the device's documentation for guidance.
• Verify Firmware/Software Versions : Ensure that the device's firmware or software is up to date. If available, apply the latest firmware updates or patches from the manufacturer's website.
• Inspect Device Logs : Review the device logs to identify any error messages or alerts that might indicate the cause of the malfunction.
• Device Configuration : Verify the device configuration to ensure it aligns with the network's requirements and network monitoring best practices . Look for misconfigurations or conflicting settings.
• Isolate Device from the Network : Temporarily disconnect the malfunctioning device from the network to determine if it is the cause of broader network issues.
• Test Connectivity and Cable : Check the connectivity of the malfunctioning device by testing it with a known-working cable and connecting it to a different network port.
• Temperature and Ventilation : Overheating can cause devices to malfunction. Ensure that the device has adequate ventilation and is not exposed to excessive heat.
• Test with Different Ports : If the device has multiple ports, test with different ports to check for faulty hardware on specific interfaces.
• Check for Hardware Faults : Examine the device's physical components for any signs of damage or hardware faults.
• Reinstall or Reset Device : If appropriate, consider reinstalling or performing a factory reset on the malfunctioning device to rule out software-related issues.
• Device Interoperability : Verify if the malfunctioning device is compatible with other devices on the network. Ensure that it supports required protocols and standards.
• Replace or Repair Faulty Components : If hardware components are found to be faulty, consider replacing or repairing them.
• Check for Environmental Factors : Determine if the malfunction could be caused by environmental factors such as electromagnetic interference or power fluctuations.
• Update Drivers : For network interface cards and other peripheral devices, update drivers to the latest versions to address potential compatibility issues.
• Verify Network Connectivity : Confirm that the malfunctioning device is connected to the correct network and VLAN (if applicable).
• Seek Vendor Support : If the issue persists or is beyond your troubleshooting capabilities, contact the vendor's technical support for further assistance.

Always document the troubleshooting steps and any changes made to the device or network during the process. Thorough documentation helps in future reference and sharing information with others who might be assisting with the troubleshooting process.

Network Problem #6. DNS Issues

DNS or Domain Name System, controls how visitors find your website over the Internet.

It is essentially a directory for the Internet (and every Internet-connected device) that matches domain names with IP addresses. Every single website has its own IP address on the web, and computers can connect to other computers via the Internet and look up websites using their IP address. When you type in a domain name in your Internet browser, DNS works to find the information connected to that domain.

DNS issues are very common network problems that many people tend to overlook. DNS issues occur when you are unable to connect to an IP address, signalling that you may have lost network or Internet access . For example, your site can simultaneously appear online for you, but looks to be offline to your visitors.

When DNS issues arise, users may experience difficulties accessing websites, sending emails, or connecting to network resources.

I. The Consequences of DNS Issues

The inability to access the Internet or particular sites can have a very immediate and negative impact on your business - especially if it means that users cannot access your site. Just a few hours offline can cost your company in more ways than one, which is why it’s important to find and fix DNS problems as soon as possible.

• Website Inaccessibility : Users may be unable to access websites or services due to failed DNS resolutions.
• Email Delivery Issues : DNS problems can affect email delivery, causing delays or preventing emails from being sent or received.
• Slow Internet Browsing : DNS lookup delays can result in sluggish website loading times and overall slow internet browsing experiences.
• Security Risks : DNS hijacking or cache poisoning can lead to security vulnerabilities, exposing users to phishing attacks or other malicious activities

II. The Causes of DNS Issues

• Bad Configurations: You may experience issues due to improper configuration of DNS records .
• High DNS Latency: High Latency, which is the measure of time it takes for data to reach its destination across a network, can cause slow and abnormally long loading times.
• High TTL Values: High “time to live” values on your records, will lead to high propagation wait times. Traceroute tools, like Obkio’s Live Traceroutes feature and Obkio Vision Visual Traceroue tool , actually track and monitor TTL values.
• Hardware/Network Failures: DNS problems can be caused by hardware failures on the host machine or network failures. Troubleshoot network/ hardware configuration settings using a network performance monitoring tool to identify the source of the problem.
• DNS Server Outages : If the DNS server responsible for resolving domain names becomes unavailable or experiences downtime, users will be unable to access websites or services.
• Misconfigured DNS Settings : Incorrectly configured DNS settings on network devices or client systems can lead to failed DNS lookups.
• DNS Cache Poisoning : Malicious actors can compromise DNS caches, leading to incorrect or spoofed DNS records being served, redirecting users to malicious websites.
• Network Connectivity Issues : Internet connectivity issues or problems or routing can prevent DNS queries from reaching DNS servers or receiving responses and lead to network connectivity issues
• DNS Propagation Delays : After making changes to DNS records, it can take time for the changes to propagate across the internet. During this period, users may experience inconsistent DNS resolution.
• DNS Hijacking : Cyber attackers may hijack DNS queries to redirect users to fraudulent websites or phishing pages.

III. How to Identify & Troubleshoot DNS Issues

• DNS Monitoring : Utilize network monitoring tools like Obkio to track DNS queries and response times. Monitor DNS servers' performance and ensure they are resolving queries promptly.
• DNS Testing Tools : Use DNS testing tools to check the network response time and accuracy of DNS queries from different locations.
• Flush DNS Cache : On client systems, flush the DNS cache to clear any outdated or corrupted entries that may be causing issues.
• Check DNS Server Status : Verify the status of DNS servers to ensure they are operational and responsive.
• Review DNS Settings : Check DNS settings on network devices, routers, and client systems for any misconfigurations.
• DNSSEC Implementation : Consider implementing DNSSEC (DNS Security Extensions) to prevent DNS cache poisoning and improve DNS security.
• Monitor DNS Logs : Review DNS server logs for any unusual activities or error messages that may indicate issues.
• Update DNS Records : Ensure that DNS records are correctly updated and propagated across authoritative DNS servers.

By proactively identifying and resolving DNS issues, businesses can ensure smooth and reliable access to online resources, improve internet browsing experiences, and enhance overall network security.

Learn how to troubleshoot intermittent Internet connection issues with Network Monitoring. Find & fix the cause of intermittent Internet issues.

IV. Network Troubleshooting Scenarios for DNS Issues

DNS (Domain Name System) issues can cause various network problems, including the inability to access websites, email services, or other network resources. Here are some network troubleshooting scenarios to consider when dealing with DNS issues:

• Ping and Traceroute : Use the ping and traceroute commands to verify DNS resolution. If you can ping IP addresses but not domain names, it indicates a DNS resolution problem.
• Check DNS Server Settings : Verify that the DNS server settings on the client devices are correct. Ensure that they are pointing to the appropriate DNS servers, such as those provided by the ISP or internal DNS servers.
• DNS Server Reachability : Check if the DNS servers are reachable from the client devices. Use ping to confirm if the DNS servers respond to requests.
• Flush DNS Cache : Clear the DNS cache on the client devices to ensure they fetch fresh DNS records from the DNS servers.
• DNS Server Logs : Analyze the DNS server logs for errors or issues. Look for failed DNS requests or unusual patterns.
• DNS Forwarding and Recursion : Ensure that DNS servers are properly configured for forwarding and recursion. Misconfigured forwarding can lead to failed DNS resolution.
• DNSSEC Validation : If DNSSEC (Domain Name System Security Extensions) is enabled, check for DNSSEC validation issues that might prevent resolution for some domains.
• Check DNS Records : Verify the DNS records for the domain in question (A, CNAME, MX, etc.) to ensure they are correctly configured.
• Firewall and Filtering : Review firewall rules and content filtering settings that might block DNS traffic or DNS resolution.
• ISP DNS Issues : Contact the Internet Service Provider (ISP) to check if there are any DNS issues or outages in their DNS infrastructure.
• DNS Load Balancing : If using DNS-based load balancing, ensure that it is working correctly and directing traffic to the appropriate servers.
• DNS Round Robin : If DNS round-robin is used, verify that all the IP addresses in the DNS response are functional.
• Reverse DNS Lookup : Check reverse DNS lookup (PTR) records to ensure they match the corresponding forward (A) records.
• DNS Timeouts : Monitor for DNS timeouts in application logs or network captures, which may indicate DNS server unresponsiveness.
• DNS Hijacking or Spoofing : Investigate for any signs of DNS hijacking or spoofing, which could redirect users to malicious websites.
• DNS Over HTTPS (DoH) or DNS Over TLS (DoT) : If DoH or DoT is implemented, verify the configuration and connectivity to the chosen secure DNS resolver.
• IPv6 DNS Configuration : Ensure that DNS resolution works correctly for both IPv4 and IPv6 addresses.
• Third-Party DNS Services : If using third-party DNS services, verify their service status and reachability.
• DNS Health Check Tools : Utilize DNS health check tools or online DNS diagnostics to assess DNS configuration and performance.

By systematically troubleshooting DNS issues, you can identify and resolve the root cause of the problem, ensuring smooth DNS resolution and proper network connectivity. If the issue persists or is beyond your expertise, don't hesitate to seek assistance from qualified network administrators or DNS experts.

Network Problem #7. Interference in the Wireless Network

WiFi problems are one of the most common complaints surrounding modern day connectivity.

Interference in the wireless network is a common and frustrating network problem that can significantly impact Wi-Fi performance and reliability. Wireless networks, such as Wi-Fi, rely on radio frequencies to transmit data between devices. Interference occurs when other devices or signals disrupt this communication, leading to slow or unreliable wireless connections .

Several factors contribute to wireless interference, and identifying and mitigating these issues is crucial for maintaining a stable wireless network.

Signs of wireless interference include:

• Low signal strength even when close to a WiFi broadcast device
• Slower Internet connection when using connected over WiFi
• Slow file transfers between computers over WiFi
• Inability to pair WiFi or Bluetooth devices even when in proximity to the receiver
• Intermittently dropping of WiFi connection

I. The Consequences of Interference in the Wireless Network

• Slow Data Transfer : Interference can lead to a variety of Internet problems like slow data transfer rates and reduced Internet speeds, affecting productivity and user experience.
• Connection Drops : Wireless interference can cause frequent disconnections or dropped connections, disrupting ongoing tasks and communication.
• Unreliable Connectivity : Users may experience intermittent connectivity issues, making it challenging to access network resources consistently.
• Reduced Coverage : Interference can result in reduced Wi-Fi coverage, creating dead spots where wireless signals are weak or nonexistent.

II. The Causes of Interference in the Wireless Network

Very common household items, like microwave ovens or cordless phones, can slow down your home Wi-Fi network performance. If you live in a densely populated area, your neighbors’ Wi-Fi networks could actually be interfering with your own. This is particularly true if you’re using a 2.4GHz wireless router.

Seeing as a failure can occur at any time, the first challenge for network administrators is to quickly identify what can cause interference as well as the precise time they occurred.

• Overlapping Wi-Fi Channels : In environments with multiple Wi-Fi networks, overlapping channels can lead to interference as signals interfere with each other.
• Physical Obstructions : Physical obstacles like walls, floors, and large objects can attenuate Wi-Fi signals, reducing signal strength and causing interference.
• Electronic Devices : Other electronic devices operating on similar frequencies, such as cordless phones, Bluetooth devices, and microwaves, can cause interference.
• Nearby Access Points : When multiple access points are in close proximity, they can interfere with each other's signals, especially if they are on the same or overlapping channels.
• Signal Reflection and Refraction : Wi-Fi signals can reflect off surfaces or refract through materials, creating signal interference and dead zones.

III. How to Identify and Troubleshoot Interference in the Wireless Network

While users are usually quick enough to report problems, it’s ideal to identify and solve the problem before it affects users.

• Real-Time Network Monitoring : Utilize network monitoring tool, like Obkio for real-time network monitoring to track Wi-Fi performance in real-time and detect sudden drops in signal strength or connectivity issues that may indicate interference.
• Wi-Fi Site Surveys : Conduct site surveys using Wi-Fi analysis tools within the network monitoring platform to identify signal strength, coverage areas, and potential interference sources.
• Channel Analysis : Utilize network monitoring tools to analyze Wi-Fi channel utilization and identify crowded or overlapping channels that may be contributing to interference.
• Signal Strength Testing : Measure Wi-Fi signal strength across different areas of the workspace using network monitoring tools to identify weak or strong signal zones.
• Device Interference Check : Identify and isolate devices or equipment that may be causing wireless interference, using network monitoring to detect their presence and impact on Wi-Fi performance.
• Automated Alerts : Set up automated alerts within the network monitoring tool to be notified immediately when Wi-Fi interference is detected, allowing for quick investigation and resolution.
• Historical Analysis : Utilize historical data provided by the network monitoring platform to identify patterns of interference and assess the effectiveness of previous troubleshooting efforts.
• Network Topology Mapping : Use network monitoring tools or network observability tools to create visual representations of the network topology, helping identify potential physical obstructions or sources of interference.

By leveraging network monitoring alongside these troubleshooting approaches, businesses can proactively identify and address wireless interference, ensuring a more reliable and efficient Wi-Fi network. Network monitoring provides real-time insights, historical data, and automated alerts, empowering IT teams to promptly resolve interference issues and optimize wireless performance for enhanced user satisfaction.

IV. Network Troubleshooting Scenarios for Interference in the Wireless Network

Interference in a wireless network can cause signal degradation, reduced throughput, and disconnections. Troubleshooting wireless interference requires careful analysis and mitigation strategies. Here are some network troubleshooting scenarios to consider when dealing with interference in a wireless network:

• Physical Obstructions: Identify and remove or reposition physical obstructions such as walls, furniture, metal objects, or large appliances that may block or attenuate the Wi-Fi signal.
• Neighboring Wi-Fi Networks : Use a Wi-Fi analyzer tool to identify nearby Wi-Fi networks and the channels they are operating on. Choose a less congested channel for your wireless network to reduce interference.
• Microwave Ovens and Cordless Phones : Microwave ovens and some cordless phones operate in the same frequency range as Wi-Fi networks (2.4 GHz). Keep Wi-Fi access points away from these devices to minimize interference.
• Bluetooth Devices : Bluetooth devices can cause interference with Wi-Fi networks, especially in the 2.4 GHz frequency band. Separate Bluetooth devices from Wi-Fi access points or use Wi-Fi channels that are far from Bluetooth frequencies.
• Electronic Devices : Identify and relocate electronic devices that emit electromagnetic interference (EMI) or radio-frequency interference (RFI), such as baby monitors, wireless cameras, or wireless speakers.
• Dual-Band Wi-Fi Devices : If possible, use dual-band Wi-Fi devices that can operate in both 2.4 GHz and 5 GHz frequency bands. The 5 GHz band is typically less congested and offers better performance.
• Wi-Fi Signal Strength : Check the Wi-Fi signal strength at different locations within the coverage area to identify areas with weak signals that might be susceptible to interference.
• Wi-Fi Access Point Placement : Optimize the placement of Wi-Fi access points to achieve better coverage and reduce dead zones. Consider using Wi-Fi range extenders or mesh systems for larger areas.
• Wi-Fi Signal Overlapping : Avoid overlapping Wi-Fi signal coverage from multiple access points, as it can lead to interference. Adjust access point transmit power or channel settings to minimize overlap.
• Rogue Wi-Fi Devices : Look for rogue Wi-Fi access points or devices that might be interfering with your network. Use wireless intrusion detection systems (WIDS) to identify unauthorized devices.
• DFS Channels (5 GHz) : In the 5 GHz band, some channels require Dynamic Frequency Selection (DFS) due to radar detection requirements. Ensure your devices support DFS and are using appropriate DFS channels.
• WLAN Optimization : Use Wi-Fi optimization techniques such as band steering and airtime fairness to balance client connections and reduce interference.
• Wireless Site Survey : Perform a wireless site survey to assess the overall wireless environment and identify potential sources of interference.
• Quality of Service (QoS) : Implement QoS policies to prioritize critical Wi-Fi traffic and minimize the impact of non-essential traffic on network performance.
• Regular Monitoring : Continuously monitor Wi-Fi performance, interference levels, and client connectivity to detect and address issues proactively.
• Firmware Updates : Keep Wi-Fi access points and wireless devices' firmware up to date to take advantage of performance improvements and bug fixes.

By systematically troubleshooting wireless interference, you can optimize your Wi-Fi network's performance and deliver a more reliable wireless experience to users. Use appropriate network monitoring and diagnostic tools, like we mentioned in the section above, to analyze Wi-Fi performance and make informed decisions during the troubleshooting process.

Network Problem #8. Network Congestion

Network congestion is a prevalent network problem that occurs when there is an excessive amount of data traffic on the network, leading to congestion or bottlenecking . It can happen at various points in the network, such as routers, switches, or network links, where the capacity to handle data becomes overwhelmed by the volume of incoming traffic.

Network congestion can result from increased data demands, inefficient network configurations, or inadequate bandwidth allocation, and it can significantly impact the overall network performance and user experience.

I. The Consequences of Network Congestion

Network congestion can have severe ramifications on network performance and user experience. Let's go over the impact of congestion, including:

• Slow Data Transfer : Network congestion can result in slower data transfer rates, leading to delays in accessing resources and data.
• Latency and Packet Loss : Congestion can cause increased latency (delays) and packet loss, affecting real-time applications such as video conferencing or online gaming.
• Dropped Connections : Congestion can cause connections to drop or time out, resulting in failed file transfers or disrupted communication.
• Reduced Productivity : Sluggish network performance can hinder productivity, as users may experience delays in performing critical tasks.
• User Frustration : Network congestion can lead to frustration among users due to the inability to access resources or slow response times.

II. The Causes of Network Congestion

Understanding the root causes of network congestion is vital for devising appropriate solutions. Let’s go over the most common causes of network congestion in more detail:

• Increased Data Traffic : As the number of connected devices and users on the network grows, the demand for data transfer increases, leading to congestion.
• Bandwidth Limitations : Insufficient available bandwidth can cause congestion, especially in networks with limited capacity or where data-intensive applications dominate.
• Network Misconfigurations : Inefficient network configurations, such as incorrect Quality of Service (QoS) settings or improper routing, can lead to inefficient data flow and congestion.
• DDoS Attacks : Distributed Denial of Service (DDoS) attacks involve overwhelming a network with an enormous amount of traffic, causing congestion and rendering services unavailable.
• Software and Firmware Bugs : Network devices with software or firmware bugs can behave unpredictably, potentially contributing to network congestion.

III. How to Identify and Address Network Congestion

To mitigate network congestion, early detection and appropriate measures are essential.

• Network Monitoring : Use network monitoring tools like Obkio to track network performance metrics, including bandwidth utilization and traffic patterns. Identify periods of high traffic and potential congestion.
• Traffic Analysis : Analyze the type of data traffic and its volume to identify bandwidth-intensive applications or devices causing congestion.
• Quality of Service (QoS) Implementation : Implement QoS policies to prioritize critical applications and services over less essential ones during periods of congestion.
• Bandwidth Upgrades : Consider upgrading network bandwidth to accommodate increasing data demands and alleviate congestion.
• Load Balancing : Utilize network load balancing techniques to distribute network traffic across multiple routes or devices, preventing bottlenecks in specific areas.
• Traffic Shaping : Implement traffic shaping to control the flow of data, ensuring fair distribution of bandwidth among different applications or users.
• Network Optimization : Regularly review network configurations and performance to identify areas for network optimization and improvement.

By proactively identifying and addressing network congestion, businesses can ensure a smoother and more responsive network, enhancing productivity and user satisfaction. Network congestion management plays a crucial role in maintaining a reliable and efficient network infrastructure that meets the growing demands of modern businesses.

Learn how to detect network congestion & perform a network congestion test inside & outside your network with Network Monitoring & Network Device Monitoring.

IV. Network Troubleshooting Scenarios for Network Congestion

Network congestion occurs when the network experiences high levels of traffic, causing slow data transmission, increased latency, and potential service disruptions. Here are some network troubleshooting scenarios to consider when dealing with network congestion:

• Identify Peak Usage Hours : Monitor network traffic to identify peak usage hours when congestion is most likely to occur. Plan for additional resources during these periods.
• Bandwidth Monitoring : Use network monitoring tools with SNMP Network Monitoring to track bandwidth usage and identify which applications or devices are consuming the most bandwidth.
• Quality of Service (QoS) : Implement QoS policies to prioritize critical traffic, such as VoIP or video conferencing, over non-essential traffic during periods of congestion. Qos for VoIP is essential for mitigation congestion.
• Malware or Botnet Activity : Malware-infected devices or botnet activity can cause excessive traffic and contribute to network congestion. Use security tools to detect and isolate infected devices.
• Cloud Services and Backups : Cloud services and data backups can consume significant bandwidth. Schedule backups during off-peak hours to avoid congestion.
• Check Network Switches and Routers : Check network devices for errors or signs of packet drops. Upgrade hardware if required to handle increased traffic.
• Analyze Network Topology : Review the network topology to identify potential bottlenecks or areas of contention.
• Segment Network Traffic : Separate different types of traffic, such as voice, data, and video, into separate VLANs to reduce contention.
• Update Firmware and Drivers : Keep network devices' firmware and drivers up to date to ensure optimal performance.
• Optimize Protocols : Fine-tune network protocols to reduce overhead and improve efficiency.
• Load Balancing : Distribute traffic across multiple links or paths using load balancing techniques.
• Consider Network Upgrades : If congestion is chronic and impacting productivity, consider upgrading network infrastructure, such as increasing bandwidth or using faster network technologies.
• Monitor Network Flow : Use flow analysis tools to understand traffic patterns and identify potential sources of congestion.
• Implement Caching : Use caching solutions for frequently accessed content to reduce the need for repetitive data transfers.
• Throttle Bandwidth-Intensive Applications : Limit the bandwidth usage of certain applications or devices that are causing congestion.
• Review ISP Performance : If the congestion is beyond your local network, contact your Internet Service Provider (ISP) to assess the overall network performance.
• Peer-to-Peer (P2P) Traffic Control : Implement policies to control and prioritize P2P traffic, which can consume a significant amount of bandwidth.
• Educate Users : Educate users about responsible internet usage and the impact of excessive data consumption on network performance.

By thoroughly troubleshooting network congestion, you can identify the root causes and implement appropriate solutions to improve overall network performance and user experience. Regular monitoring and analysis of network traffic patterns will help you proactively address congestion issues before they become significant problems.

Network Problem #9. Packet Loss

Packet loss is a prevalent network problem characterized by the failure of data packets to reach their intended destination within a network . It occurs when one or more packets of data are lost or discarded during transmission, leading to incomplete or corrupted data delivery.

Packet loss can happen due to various factors, such as network congestion, hardware issues, or data transmission errors, and it can significantly impact network performance and user experience.

In the same family of network issues, you may also encounter:

• Packet Reordering : When network packets arrive at their destination out of sequence
• Packet Duplication : The unintended replication of data packets during transmission. When packets are duplicated, multiple identical copies of the same packet are delivered to the destination.

I. The Consequences of Packet Loss

• Data Corruption : Packet loss can lead to incomplete or corrupted data transmissions, affecting the accuracy and integrity of transmitted information.
• Slow Data Transfer : Retransmitting lost packets can slow down data transfer rates, leading to increased latency.
• Degraded Voice and Video Quality : In real-time communication applications like VoIP and video conferencing, packet loss can result in choppy audio or pixelated video.
• Reduced Throughput : The loss of packets in data streams can reduce the overall throughput and efficiency of data delivery.
• Impact on Applications : Packet loss can negatively affect the performance of applications, leading to slower response times and disrupted services.

II. The Causes of Packet Loss

• Network Congestion : High levels of data traffic or network congestion can result in packets being dropped to alleviate the strain on the network.
• Network Jitter : Variations in packet delay, known as jitter, can lead to packet loss when packets arrive out of order or too late to be processed.
• Buffer Overflow : When network devices' buffers become overwhelmed due to high data rates, excess packets can be discarded.
• Data Transmission Errors : Errors during data transmission can cause packets to be corrupted or lost, especially in unreliable transmission mediums.
• Wireless Interference : Interference from other wireless signals or physical obstacles can lead to packet loss in Wi-Fi networks.
• Network Hardware Issues : Faulty network switches, routers, or other hardware can cause packet loss as packets fail to traverse the network correctly.

III. How to Identify & Troubleshoot Packet Loss

• Network Monitoring : Utilize network monitoring tools like Obkio to measure packet loss and track packet loss rates and identify periods of increased packet loss.
• Packet Analysis : Conduct packet analysis to identify the root causes of packet loss and determine the affected network segments.
• Bandwidth Optimization : Optimize bandwidth allocation and implement Quality of Service (QoS) to prioritize critical traffic and reduce packet loss.
• Jitter Control : Minimize network jitter through QoS and traffic shaping to prevent packet loss due to variations in packet delay.
• Network Hardware Inspection : Inspect network hardware to identify and replace faulty devices contributing to packet loss.
• Wireless Signal Optimization : Optimize Wi-Fi signals to reduce wireless interference and decrease packet loss in wireless networks.

By proactively identifying and addressing packet loss, businesses can improve network performance , maintain data integrity, and enhance the overall user experience. Network monitoring, packet analysis, and appropriate network optimization techniques play a vital role in detecting and mitigating packet loss issues effectively.

How to measure packet loss with Obkio’s Network & Packet Loss Monitoring tool. Check for packet loss in your network & read packet loss measurements.

IV. Network Troubleshooting Scenarios for Packet Loss

Packet loss can degrade network performance and cause disruptions in data transmission. Troubleshooting packet loss requires identifying the underlying causes and implementing appropriate solutions. Here are some network troubleshooting scenarios to consider when dealing with packet loss:

• Ping and Traceroute : Use ping and traceroute commands to identify packet loss and latency issues between devices. This can help pinpoint the location and severity of packet loss.
• Check Network Cables : Inspect network cables and connectors for damage, loose connections, or faulty wiring that could lead to packet loss.
• Verify Network Interface Cards (NICs) : Test and update network interface card drivers to ensure they are functioning correctly.
• Physical Layer Troubleshooting : Examine physical network components, such as switches and routers, for signs of hardware issues or congestion.
• Bandwidth Saturation : Monitor network traffic to see if bandwidth saturation is causing packet loss. Consider implementing Quality of Service (QoS) policies to prioritize critical traffic.
• Check for Network Congestion : Analyze network traffic patterns to identify areas of congestion that may be causing packet loss.
• Wireless Interference : In wireless networks, interference from neighboring Wi-Fi networks or other devices can lead to packet loss. Use a Wi-Fi analyzer to identify potential sources of interference.
• Reduce MTU Size : If you are experiencing fragmentation-related packet loss, reduce the Maximum Transmission Unit (MTU) size to prevent fragmentation.
• Jitter and Buffering : Examine network devices for excessive jitter or inadequate buffering that can contribute to packet loss.
• Routing Issues : Verify routing configurations to ensure packets are being routed correctly without any loops or misconfigurations.
• Firewall Settings : Check firewall rules to ensure they are not blocking legitimate traffic and causing packet loss.
• Malware and DDoS Attacks : Monitor for signs of malware infections or Distributed Denial of Service (DDoS) attacks, as they can cause packet loss.
• ISP Issues : If the packet loss is beyond your local network, contact your Internet Service Provider (ISP) to investigate potential problems with their network.
• Buffer Bloat : Address buffer bloat issues by configuring QoS and traffic shaping to manage buffer size and prevent excessive queuing delay.
• Ping Flood or DDoS Testing : If you suspect malicious activities, investigate for possible ping flood or DDoS testing targeting your network.
• Update Firmware and Software : Keep network devices' firmware and software up to date to prevent known issues causing packet loss.
• Trunk Port Errors : For VLANs and trunk ports, check for misconfigurations or errors that might cause packet loss.
• Segment and Isolate Network Traffic : Use VLANs and subnetting to isolate different types of network traffic and prevent congestion-related packet loss.

By methodically troubleshooting packet loss, you can identify the root causes and apply appropriate solutions to improve network performance and reliability.

Network Problem #10. Jitter

Jitter is a common network problem that refers to the variation in packet delay experienced during data transmission over a network. It occurs when data packets encounter fluctuations in the time it takes to traverse the network from the source to the destination .

Jitter is particularly relevant in real-time communication applications, such as Voice over Internet Protocol (VoIP) calls and video conferencing, where timing precision is crucial for smooth and seamless communication.

I. The Consequences of Jitter

• Voice and Video Quality Issues : In real-time communication applications like VoIP and video conferencing, excessive jitter can cause choppy audio or video, affecting the overall call quality.
• Delayed Data Transmission : Jitter can lead to variations in data transmission delays, impacting the responsiveness of applications and services.
• Synchronization Problems: For time-sensitive applications, jitter can cause synchronization issues between data packets, leading to data corruption or loss.
• Interference with Real-Time Applications : Jitter can disrupt the flow of real-time data, making it challenging to maintain a smooth user experience.

II. The Causes of Jitter

• Network Congestion : High levels of data traffic or network congestion can lead to varying packet queuing times and result in jitter.
• Packet Routing : Different paths and routing delays taken by packets can cause varying arrival times at the destination.
• Network Jitter : Variations in network jitter itself can compound the issue, leading to additional packet timing discrepancies.
• Network Interference : Physical obstacles, wireless interference, or other external factors can introduce varying transmission delays.
• Buffering : Buffering in network devices can introduce variations in packet arrival times due to the varying lengths of packets.

III. How to Identify & Troubleshoot Jitter

• Network Monitoring : Use network monitoring tools like Obkio to measure jitter levels and identify periods of increased jitter. Obbkio will also help you identify the cause, source and time of jitter spikes in you network so you where where and how to direct your troubleshooting efforts.
• Quality of Service (QoS) Implementation : Implement QoS policies to prioritize real-time traffic, reducing the impact of jitter on critical applications.
• Buffer Management : Optimize buffer settings in network devices to minimize the effects of buffering-induced jitter.
• Traffic Shaping : Use traffic shaping techniques to regulate the flow of data and manage jitter more effectively.
• Path Optimization : Optimize network paths to minimize variations in packet routing and reduce jitter.
• Wireless Signal Optimization : In wireless networks, optimize Wi-Fi signals to reduce interference and decrease jitter.

By proactively identifying and addressing jitter, businesses can improve the performance of real-time communication applications, ensuring smooth voice and video calls, and enhancing the overall user experience. Network monitoring, QoS implementation, and network optimization play a crucial role in detecting and mitigating jitter effectively.

Learn how to measure network jitter using Obkio’s Network Monitoring software to identify network problems & collect data to troubleshoot.

IV. Network Troubleshooting Scenarios for Jitter

Jitter is the variation in the delay of packet delivery in a network, which can lead to inconsistent and unpredictable performance. Troubleshooting jitter involves identifying the causes of delay variations and implementing measures to mitigate its impact. Here are some network troubleshooting scenarios to consider when dealing with jitter:

• Ping and Traceroute : Use ping and traceroute commands to measure latency and identify potential variations in packet delivery times.
• Check Network Utilization : High network utilization can contribute to jitter. Monitor network traffic to identify congestion points and take appropriate actions to alleviate it.
• Quality of Service (QoS) : Implement QoS policies to prioritize real-time traffic, such as VoIP and video conferencing, over non-time-sensitive traffic to reduce jitter.
• Buffer Bloat : Buffer bloat occurs when excessively large buffers cause delays in packet delivery. Adjust buffer sizes on routers and switches to manage latency.
• Packet Loss : Packet loss can exacerbate jitter. Address any packet loss issues, as it may lead to increased jitter levels.
• Wireless Interference : In wireless networks, interference from other devices or neighboring networks can cause jitter. Use a Wi-Fi analyzer to identify sources of interference.
• Network Congestion : Congestion on the network can lead to increased jitter. Identify and resolve congestion points to minimize its impact.
• Physical Layer Issues : Inspect network cables and connectors for damage or faults that may cause delays in packet delivery.
• Network Switches and Routers : Verify the performance of network switches and routers, as hardware issues can contribute to jitter.
• Jitter Buffer : For real-time applications, such as VoIP, ensure that jitter buffer settings are appropriately configured to compensate for jitter.
• Traffic Shaping : Use traffic shaping techniques to control the flow of traffic and prevent sudden bursts of data that may cause jitter.
• Power Management : Disable power-saving features on network devices that may introduce latency variations.
• Proper Synchronization : Ensure that clocks are synchronized across network devices to prevent timing discrepancies that contribute to jitter.
• VoIP Codecs : For VoIP systems, consider using different codecs that are less sensitive to network jitter.
• Update Firmware and Software : Keep network devices' firmware and software up to date to address known issues related to jitter.
• ISP Performance : If jitter is beyond your local network, contact your Internet Service Provider (ISP) to assess and address potential issues on their network.
• Monitor Network Performance : Continuously monitor network performance to identify patterns of jitter and take proactive measures to improve and check network stability .
• Use Network Diagnostic Tools : Employ network diagnostic tools to analyze jitter levels and identify sources of delay variations.

By systematically troubleshooting jitter, you can identify the underlying causes and apply appropriate solutions to improve network performance and deliver a smoother experience for real-time applications.

Network Problem #11. Routing Problems

Routing problems are a common network issue that occurs w hen data packets are unable to reach their intended destination due to incorrect or inefficient routing decisions . Routing is the process of determining the best path for data to travel from the source to the destination across a network.

When routing problems arise, data packets may take suboptimal paths, experience delays, or even get lost, leading to disruptions in network communication and performance.

I. The Consequences of Routing Problems

• Slow Data Transfer : Routing problems can lead to longer data transmission times, causing delays in accessing resources and services.
• Packet Loss : Incorrect routing decisions can cause packets to be lost or dropped during transmission, affecting data integrity.
• Network Inefficiency : Routing problems can lead to inefficient use of network resources, increasing network latency and reducing overall performance.
• Disruptions in Communication : Critical services and applications may become unavailable or experience disruptions due to routing problems.

II. The Causes of Routing Problems

• Misconfigurations : Incorrect configuration of routing protocols or routing tables can lead to suboptimal or incorrect routing decisions.
• Network Congestion : High levels of network congestion can cause routers to make suboptimal routing choices, leading to delays and packet loss.
• Link Failures : When a link between network devices fails, routers may need to reroute traffic, and if this process is not seamless, routing problems can occur.
• BGP (Border Gateway Protocol) Issues : In large-scale networks, BGP misconfigurations or route flapping can cause routing problems and instability.
• Inadequate Bandwidth : Insufficient bandwidth on certain links can cause congestion and result in suboptimal routing decisions.

III. How to Identify & Troubleshoot Routing Problems

• Network Monitoring : Use network monitoring tools like Obkio to track routing metrics and identify anomalies or fluctuations in routing behavior.
• Routing Protocol Analysis : Analyze the configuration of routing protocols and routing tables to identify misconfigurations or inconsistencies.
• Route Flap Damping : In BGP environments, enable route flap damping to mitigate the impact of unstable routes.
• Bandwidth Upgrades : Consider upgrading network links with inadequate bandwidth to alleviate congestion and improve routing efficiency.
• Link Redundancy : Implement link redundancy and dynamic routing protocols to ensure seamless failover in case of link failures.
• Regular Audits : Conduct regular audits of network configurations and routing tables to identify and rectify potential issues.

By proactively identifying and addressing routing problems, businesses can maintain a more efficient and reliable network infrastructure. Network monitoring, analysis of routing protocols, and proper network configuration play a vital role in detecting and resolving routing problems promptly. This ensures smooth and seamless data transmission, optimizing network performance and user experience.

IV. Network Troubleshooting Scenarios for Routing Problems

Routing problems can lead to communication issues between network devices and services. Troubleshooting routing problems requires careful analysis of the routing configuration and associated network components. Here are some network troubleshooting scenarios to consider when dealing with routing problems:

• Ping and Traceroute : Use ping and traceroute commands to verify connectivity between devices and identify potential routing issues.
• Routing Table Verification : Check the routing tables on routers and switches to ensure they are correctly configured and have the appropriate routes.
• Routing Protocol Issues : If dynamic routing protocols are used, verify the protocol configurations and adjacencies between neighboring routers.
• Default Gateway : Confirm that devices have the correct default gateway configured, which is critical for forwarding traffic to external networks.
• Routing Loops : Check for routing loops in the network, which can cause packets to circulate indefinitely. Correct any misconfigurations causing loops.
• Routing Redistribution : If multiple routing protocols are in use, check for proper redistribution to ensure that routes are distributed correctly.
• Static Routes : Verify that any static routes are accurate and up-to-date, especially if they are used to override dynamic routing protocols.
• Routing Metrics : Review routing metrics to ensure they are set appropriately, as improper metrics can lead to suboptimal routing decisions.
• Routing Blackholes : Look for cases where routing paths unexpectedly drop packets (routing blackholes) and investigate the cause.
• Network Topology Changes : If recent network topology changes have occurred, verify that routing configurations were updated accordingly.
• Routing Protocol Authentication : Check if routing protocol authentication is enabled and configured correctly to prevent unauthorized routing updates.
• Split Horizon : For networks using split horizon, ensure that the split horizon rule is properly applied to prevent routing information loops.
• Routing Protocol Timers : Examine routing protocol timers to ensure they are set appropriately for the network environment.
• Network Segmentation : Confirm that network segmentation is accurate and logical, and routes are correctly configured between segments.
• Router Interface Status : Verify that router interfaces are operational and have the correct IP addressing and subnet masks.
• Physical Connectivity : Check for physical connectivity issues that may prevent proper routing information exchange.
• Backup Routes : If using backup or redundant routes, validate their configurations and failover mechanisms.
• Update Firmware and Software : Keep router and switch firmware/software up to date to address known issues related to routing.
• Monitor Routing Changes : Continuously monitor routing tables and log any changes to quickly identify and address unexpected alterations.

By methodically troubleshooting routing problems, you can identify and resolve issues that may be disrupting communication in the network. Regular network monitoring, like we mentioned in the previous section, thorough analysis of routing configurations, and prompt resolution of routing-related errors will help ensure smooth and reliable network operation. If the issue persists or is beyond your expertise, seek assistance from qualified network administrators or engage with vendor support.

Network Problem #12. VoIP Call Quality Issues

VoIP (Voice over Internet Protocol) call quality issues are a common network problem that affects the clarity and reliability of voice communications over the Internet .

VoIP enables real-time voice communication using the internet as the transport medium. However, various factors within the network environment can lead to degraded call quality, causing disruptions, echoes, or delays in voice conversations.

I. The Consequences of VoIP Call Quality Issues

• Poor Call Clarity : VoIP call quality issues can result in poor audio quality, making it challenging to understand and communicate effectively.
• Dropped Calls : Frequent call dropouts or disconnects due to packet loss or network issues can hinder communication.
• Communication Delays : High latency can lead to noticeable delays in conversations, causing awkward pauses and communication difficulties.
• Unreliable Communication : Call quality problems can lead to unreliable communication experiences, affecting business operations and customer service.

II. The Causes of VoIP Call Quality Issues:

• Network Congestion : High data traffic and network congestion can lead to delayed or lost VoIP packets, resulting in poor call quality.
• Jitter : Variations in packet delay, known as jitter, can cause voice packets to arrive out of order, resulting in choppy or distorted audio during calls.
• Packet Loss : Packet loss occurs when VoIP packets fail to reach their destination, leading to gaps or dropouts in the conversation.
• Latency : Latency, the delay between sending and receiving data, can lead to noticeable delays and interruptions in VoIP calls.
• Insufficient Bandwidth : Inadequate bandwidth can restrict the amount of data that can be transmitted, leading to reduced call quality.
• Network Interference : Interference from other devices or signals can impact VoIP calls, especially in wireless environments.

How to Identify & Troubleshoot VoIP Call Quality Issues

• Network Monitoring : Use network monitoring tools like Obkio to measure VoIP quality metrics, such as MOS score, jitter, packet loss, and latency and identify issues affecting VoIP Quality right on the VoIP Quality graph.
• QoS Implementation : Implement Quality of Service (QoS) ) policies to prioritize VoIP traffic and minimize the impact of other data traffic on call quality.
• Bandwidth Allocation : Ensure sufficient bandwidth is allocated to VoIP traffic to avoid congestion and call quality issues.
• Traffic Shaping : Utilize traffic shaping techniques to regulate data flow and prioritize VoIP packets.
• Jitter Buffer Optimization : Optimize jitter buffer settings to compensate for jitter and ensure smoother audio playback.
• Network Upgrades : Consider upgrading network infrastructure to handle increased VoIP traffic and improve call quality.

By proactively identifying and addressing VoIP call quality issues, businesses can ensure clear and reliable voice communication, improving collaboration and customer interactions. Network monitoring, QoS implementation, and network optimization are essential in detecting and mitigating VoIP call quality issues, enhancing overall communication experiences within the organization.

Learn how to measure VoIP Quality using MOS Score (Mean Opinion Score) & Obkio’s VoIP monitoring solution to identify poor VoIP Quality issues & dropped calls.

IV. Network Troubleshooting Scenarios for VoIP Call Quality Issues

VoIP (Voice over Internet Protocol) call quality issues can negatively impact communication and user experience. Troubleshooting VoIP call quality issues requires identifying and resolving factors that affect voice transmission over the network. Here are some network troubleshooting scenarios to consider when dealing with VoIP call quality issues:

• Check Bandwidth and Network Utilization : Insufficient bandwidth or high network utilization can lead to call quality degradation. Monitor network traffic and ensure sufficient bandwidth is available for VoIP traffic.
• Quality of Service (QoS) : Implement QoS policies to prioritize VoIP traffic over other types of data to ensure smooth transmission and reduced latency.
• Ping and Jitter : Measure ping and jitter between endpoints to identify potential latency and jitter issues affecting call quality.
• Packet Loss : Monitor for packet loss, which can significantly impact call quality. Address any packet loss issues on the network.
• Buffer Bloat : Buffer bloat can introduce latency in the network. Optimize buffer sizes to prevent excessive delays in packet transmission.
• Codecs : Check the codecs used for VoIP calls. Some codecs may prioritize bandwidth savings over call quality. Consider using codecs that offer better voice quality.
• Network Congestion : Analyze network congestion points and address them to reduce the impact on VoIP call quality.
• Network Equipment : Verify the performance of network switches and routers, as hardware issues can contribute to call quality problems.
• Wireless Interference : In wireless networks, interference from neighboring Wi-Fi networks or other devices can affect VoIP call quality. Use a Wi-Fi analyzer to identify sources of interference.
• Check for Dropped Packets : Identify and address any dropped packets affecting call quality.
• VoIP Gateway Configuration : Verify the configuration of VoIP gateways and devices to ensure they are set correctly for the network environment.
• Codec Mismatch : Ensure that both ends of the call are using compatible codecs. A codec mismatch can lead to poor call quality.
• Router Configuration : Review router configurations for issues that may affect VoIP call quality, such as Access Control Lists (ACLs) or firewall settings.
• Router Firmware Updates : Keep router firmware up to date to address known issues related to VoIP call quality.
• SIP Trunk and Provider Issues : If using SIP trunks or a VoIP service provider, check for any issues with their service that may be affecting call quality.
• Jitter Buffer Settings : Adjust jitter buffer settings to optimize the handling of packet variations and reduce jitter-related issues.
• Network Monitoring : Continuously monitor network performance to detect any patterns of call quality degradation and identify the causes. Network monitoring tools with VoIP monitoring , like Obkio, are especially important for identifying VoIP Quality issues.
• Network Latency : Address any latency issues in the network that may affect VoIP call quality.
• ISP Performance : If VoIP call quality issues persist, contact your Internet Service Provider (ISP) to assess and address potential network problems.

By methodically troubleshooting VoIP call quality issues, you can identify and resolve factors impacting call quality, leading to improved voice communication over the network. Regular network monitoring and analysis will help you proactively detect and address VoIP call quality issues as they arise.

Network Problem #13. Network Device Failures

Network device failures are a common and potentially disruptive network problem that occurs when essential network devices, such as routers, switches, firewalls, or access points, stop functioning correctly .

Network devices play a crucial role in data transmission, routing, and security within a network infrastructure. When one of these devices fails, it can lead to service disruptions, connectivity issues, and downtime.

I. The Consequences of Network Device Failures

• Network Downtime : When critical network devices fail, it can lead to network downtime and service interruptions.
• Connectivity Issues : Failures in routers, switches, or access points can disrupt network connectivity, affecting communication and data transfer.
• Security Vulnerabilities : Failed security devices like firewalls can expose the network to potential security breaches and unauthorized access. 8 Data Loss : Network device failures can lead to data loss, especially if devices were responsible for data storage or backup.

II. The Causes of Network Device Failures

• Hardware Malfunctions : Network devices can experience hardware failures due to wear and tear, overheating, power surges, or manufacturing defects.
• Firmware or Software Errors : Faulty firmware or software updates can cause network devices to behave unpredictably or fail.
• Configuration Errors : Incorrect or misconfigured settings in network devices can lead to malfunctions or instability.
• Environmental Factors : Environmental conditions, such as exposure to extreme temperatures, humidity, or dust, can impact the reliability of network devices.

III. How to Identify & Troubleshoot Network Device Failures

• Network Monitoring : Use network monitoring tools like Obkio, along with Obkio’s Network Device Monitoring feature to continuously monitor the health and performance of core network devices to identify device availability, resource and performance issues.
• Device Health Checks : Perform regular health checks on network devices to identify early signs of potential failures or abnormalities.
• Firmware and Software Updates : Keep network device firmware and software up to date with the latest stable releases to minimize potential issues.
• Configuration Backups : Regularly back up the configuration settings of network devices to facilitate quick recovery in case of failures.
• Redundancy and Failover : Implement redundancy and failover mechanisms to ensure network continuity in the event of device failures.
• Hardware Maintenance : Regularly inspect and maintain network devices to address any physical issues and ensure proper functioning.

By proactively monitoring and maintaining network devices, businesses can reduce the risk of network disruptions caused by device failures. Quick identification and timely resolution of network device failures play a crucial role in minimizing downtime, improving network reliability , and ensuring seamless communication and data transfer.

Learn about Network Device Monitoring to easily monitor performance of firewalls, routers & switches to identify problems like high CPU & bandwidth usage.

IV. Network Troubleshooting Scenarios for Network Device Failures

Network device failures can disrupt network communication and lead to service outages. Troubleshooting network device failures requires a systematic approach to identify the failing device and address the issue promptly. Here are some network troubleshooting scenarios to consider when dealing with network device failures:

• Physical Inspection : Perform a physical inspection of the device to check for any visible signs of damage, loose connections, or hardware failures.
• Power Cycle : Power cycle the device by turning it off and then back on. Sometimes, a simple reboot can resolve temporary issues.
• Check Power and Power Supply : Verify that the device is receiving power and that the power supply is functioning correctly.
• Check Device LEDs : Observe the status lights or LEDs on the device to identify any error codes or abnormal behavior.
• Device Logs : Analyze the device logs for error messages or alerts that might indicate the cause of the failure.
• Test Connectivity : Test connectivity to and from the device to see if it is responsive or if it is completely unreachable.
• Replace Network Cables : If applicable, try replacing the network cables connecting the device to the network.
• Isolate the Failing Device : If possible, isolate the failing device from the network to prevent it from causing further disruptions.
• Swapping Redundant Components : If the device has redundant components (e.g., power supplies, interface cards), try swapping them with spare parts to see if it resolves the issue.
• Verify Firmware/Software Versions : Ensure that the device's firmware or software is up to date. Apply the latest firmware updates or patches from the manufacturer's website.
• Temperature and Ventilation : Overheating can cause devices to fail. Ensure that the device has adequate ventilation and is not exposed to excessive heat.
• Check for Environmental Factors : Determine if the device failure could be caused by environmental factors such as power fluctuations or temperature variations.
• Backup and Restore Configurations : If the device can be replaced, backup its configuration and restore it on the replacement device to minimize downtime.
• RMA or Warranty : If the device is under warranty or support contract, contact the vendor for a possible replacement or repair.
• Identify the Impact : Assess the impact of the failed device on the network and affected services.
• Redundancy and Failover : Review the network design to ensure proper redundancy and failover mechanisms are in place to handle device failures.
• Replacement and Spare Parts : Keep spare devices or critical components on hand to quickly replace failed devices when needed.
• Document the Failure : Document all the troubleshooting steps, actions taken, and the resolution for future reference.

By following a systematic troubleshooting approach, you can quickly identify the failing device and take appropriate steps to address the issue, minimizing network downtime and ensuring smooth network operation. If the issue is beyond your expertise, seek assistance from qualified network technicians or engage with vendor support for further assistance.

Network Problem #14. VPN Connectivity Problems

VPN (Virtual Private Network) connectivity issues are a common network problem that can hinder remote workers or branch offices from securely accessing the corporate network. VPNs create encrypted tunnels over the public internet, allowing users to access internal resources and services as if they were directly connected to the corporate network.

However, various factors can lead to connectivity problems, preventing users from establishing or maintaining a stable VPN connection .

I. The Consequences of VPN Connectivity Issues

• Limited Remote Access : VPN connectivity issues can restrict remote workers' access to critical resources and data.
• Reduced Productivity : Users may experience delays or interruptions in their work due to VPN connection failures.
• Security Risks : VPN connectivity problems can prompt users to seek alternative and potentially insecure ways to access corporate resources.

II. The Causes of VPN Connectivity Issues

• Network Congestion : High levels of data traffic or network congestion can impact VPN performance and lead to connectivity problems.
• Firewall or Security Settings : Misconfigured firewalls or security settings can block VPN traffic, preventing successful connections.
• VPN Server Overload : An overloaded VPN server can struggle to handle incoming connection requests, leading to connection failures.
• Client Software Conflicts : Interference from other software or settings on the client device can cause VPN connectivity issues.
• Internet Connection Instability : Unstable or unreliable internet connections can disrupt VPN connections.
• VPN Protocol Issues : Compatibility issues between VPN protocols and devices can lead to connection problems.

III. How to Identify & Troubleshoot VPN Connectivity Issues

• Network Monitoring : Use network monitoring tools like Obkio to track VPN connectivity metrics and identify potential issues. Obkio has remote network monitoring features, which is especially important for monitoring remote workers connectivity towards VPNs.
• Firewall and Security Configuration : Review and adjust firewall settings to ensure VPN traffic is permitted and secure.
• VPN Server Load Balancing : Implement load balancing for VPN servers to distribute connection requests evenly and avoid network overload .
• VPN Client Troubleshooting : Troubleshoot VPN client software on user devices to identify and resolve conflicts or configuration issues.
• Internet Connection Stability : Address internet connection problems on user devices to ensure a stable VPN connection.
• VPN Protocol Selection : Choose appropriate VPN protocols based on device compatibility and network requirements.

By proactively monitoring and troubleshooting VPN connectivity issues, businesses can ensure remote workers have reliable access to corporate resources. Network monitoring, VPN server optimization, and client device maintenance play a vital role in identifying and resolving VPN connectivity issues, enhancing productivity, and maintaining a secure remote work environment.

IV. Network Troubleshooting Scenarios for VPN Connectivity Issues

VPN (Virtual Private Network) connectivity issues can prevent users from securely accessing resources on a remote network. Troubleshooting VPN connectivity problems requires a careful examination of both client-side and server-side configurations. Here are some network troubleshooting scenarios to consider when dealing with VPN connectivity issues:

• Check Client Credentials : Verify that the VPN client has the correct username, password, and any necessary authentication tokens or certificates.
• VPN Client Software : Ensure that the VPN client software is installed correctly and up to date.
• VPN Server Status : Check the VPN server's status to ensure it is operational and accepting connections.
• Firewall and Security Software : Temporarily disable any third-party firewalls or security software that might be blocking VPN connections.
• Check VPN Server Logs : Review the VPN server logs for any error messages or connection attempts from the problematic client.
• Network Address Translation (NAT) : If the VPN server is behind a NAT device, ensure that proper NAT traversal (like NAT-T) is configured.
• VPN Protocol : Verify that both the client and server are using the same VPN protocol (e.g., OpenVPN, PPTP, L2TP/IPsec, IKEv2).
• Firewall Rules : Check firewall rules on the VPN server to ensure that incoming VPN traffic is allowed.
• Verify VPN Server and Client IP Addressing : Ensure that there are no IP address conflicts between the client and server networks.
• Internet Connectivity : Verify that both the client and server have a stable internet connection.
• ISP Blocking : Check if the internet service provider (ISP) is blocking VPN traffic. Try connecting from a different ISP to test.
• MTU Settings : Test different Maximum Transmission Unit (MTU) settings on the client and server to avoid potential fragmentation issues.
• VPN Split Tunneling : Confirm that VPN split tunneling is not causing conflicts with local or remote network access.
• Restart VPN Services : Try restarting the VPN server and services.
• VPN Routing : Ensure that VPN routing is correctly configured to allow traffic to flow between client and server.
• VPN Server Certificates : Verify that server-side certificates (if used) are valid and not expired.
• Check VPN Encryption Settings : Ensure that both the client and server agree on encryption and authentication settings.
• Temporary Bypass VPN : Temporarily bypass the VPN and test regular internet connectivity to verify the issue is VPN-specific.
• NAT Traversal : If the VPN client is behind a NAT device, ensure that NAT traversal methods are enabled on both client and server.
• Update VPN Client and Server Software : Keep both the VPN client and server software up to date to address any known issues.
• Client and Server Time Sync : Verify that the client and server clocks are synchronized, as time differences can cause authentication problems.

By systematically troubleshooting VPN connectivity issues, you can identify and resolve the root causes, allowing users to securely access remote resources over the VPN. Documenting the troubleshooting steps and actions taken will aid in future reference and assist others in resolving similar issues. If the issue persists or requires expertise beyond your capabilities, don't hesitate to seek assistance from qualified network administrators or VPN specialists.

Network Problem #15. Load Balancing Configuration Errors

Load balancing configuration errors are a common network problem that occurs when the distribution of network traffic across multiple servers or links is not optimized or balanced correctly .

Load balancing is a technique used to evenly distribute incoming network requests or data traffic among multiple resources, ensuring optimal utilization of resources and preventing overload on individual components. However, misconfigurations or errors in load balancing setups can lead to uneven distribution, causing performance issues and potential service disruptions.

I. Consequences of Load Balancing Configuration Errors

• Overloaded Servers : Misconfigurations can lead to uneven distribution of traffic, overburdening certain servers while leaving others underutilized.
• Service Degradation : Load balancing errors can cause performance issues, leading to slow response times and reduced service availability.
• User Experience Issues : Users may experience inconsistent service quality or disruptions due to load balancing problems.
• Increased Downtime Risk : Load balancing configuration errors can increase the risk of service outages or downtime during peak traffic periods.

II. Causes of Load Balancing Configuration Errors

• Incorrect Weighting : Assigning improper weights to servers or links in the load balancing setup can result in disproportionate traffic distribution.
• Inadequate Health Checks : Inaccurate or inadequate health checks on servers can lead to the inclusion of faulty or overloaded servers in the load balancing pool.
• Session Persistence Misconfiguration : Misconfiguring session persistence can cause users to lose their session data when redirected to different servers.
• Improper Load Balancer Placement : Placing the load balancer in an inefficient location within the network can lead to suboptimal traffic routing.

III. How to Identify & Troubleshoot Load Balancing Configuration Errors

• Network Monitoring : Utilize network monitoring tools like Obkio to track server performance and identify any imbalanced traffic patterns.
• Load Balancer Configuration Review : Regularly review load balancer settings and verify proper weightings and health checks.
• Testing and Validation : Conduct network load testing and validation to ensure load balancing configurations work as intended under different traffic conditions.
• Session Persistence Testing : Verify session persistence settings to ensure smooth user experience during server changes.
• Load Balancer Placement : Review the placement of load balancers in the network to optimize traffic routing.

By proactively identifying and addressing load balancing configuration errors, businesses can ensure efficient resource utilization, enhance service performance, and reduce the risk of downtime. Network monitoring, load balancer configuration reviews, and rigorous testing play a crucial role in detecting and resolving load balancing configuration errors, improving the overall reliability and network availability of network services.

IV. Network Troubleshooting Scenarios for Load Balancing Configuration Errors

Load balancing configuration errors can lead to uneven distribution of traffic, service disruptions, and degraded performance. Troubleshooting load balancing issues requires careful analysis of the load balancer's configuration and associated network components. Here are some network troubleshooting scenarios to consider when dealing with load balancing configuration errors:

• Check Load Balancer Configuration : Review the load balancer's configuration to ensure it is set up correctly, including virtual server settings, server pools, and load balancing algorithms.
• Monitor Server Health : Monitor the health and status of the backend servers to ensure they are properly configured and responsive to requests.
• Verify Server Pool Membership : Check that all the intended backend servers are added to the appropriate server pools and that no servers are mistakenly excluded.
• Check Load Balancer Status : Verify that the load balancer is operational and not experiencing any issues.
• Load Balancer Firmware and Software Updates : Keep the load balancer's firmware and software up to date to address known issues and security vulnerabilities.
• Algorithm Selection : Ensure the appropriate load balancing algorithm (e.g., round-robin, least connections, weighted) is selected based on the specific application and server requirements.
• Monitor Traffic Distribution : Observe the traffic distribution among backend servers to identify any imbalances.
• Session Persistence : Check session persistence settings to ensure that client requests are directed to the same backend server for the duration of a session, if required.
• Health Checks and Monitors : Review health check settings to ensure they accurately monitor backend server availability and health.
• Virtual IP Address and Network Configuration : Verify that the virtual IP address and network configuration are properly set up and accessible.
• Firewall Rules and Security Groups : Check that firewall rules or security groups are not blocking the load balancer's traffic.
• Service Ports and Protocols : Confirm that the load balancer is configured to forward traffic to the correct service ports and protocols on the backend servers.
• Log Analysis : Analyze load balancer logs for any error messages or indications of misconfiguration.
• Service Check : Use network monitoring tools to perform service checks on the backend servers to identify any issues.
• Load Test and Simulation : Conduct load testing or simulate traffic to observe how the load balancer handles various loads and conditions.
• SSL Certificates : If using SSL termination, verify that the SSL certificates on the load balancer are valid and not expired.
• Application-Specific Configuration : For certain applications, ensure that any application-specific configurations or settings are correctly configured in the load balancer.
• Backup and Restore Configurations : Keep backups of load balancer configurations and restore them in case of accidental changes or misconfigurations.
• Rollback Changes : If you recently made changes to the load balancer configuration, consider rolling back the changes to a known working state.

By systematically troubleshooting load balancing configuration errors, you can identify and resolve issues that affect traffic distribution and optimize the performance and reliability of the load balancer. Regular monitoring and analysis of traffic patterns will help you proactively detect and address load balancing issues as they arise. If the issue persists or is beyond your expertise, seek assistance from qualified network administrators or load balancing specialists.

Network Problem #16. Link Flapping

Link flapping is a common network problem characterized by the frequent and rapid oscillation of a network link between the up and down states .

When a link flaps, it continuously alternates between being connected (up) and disconnected (down). This rapid and inconsistent behavior can disrupt network communication, cause service interruptions, and lead to instability within the network infrastructure.

I. The Consequences of Link Flapping

• Network Instability : Frequent link flapping can destabilize the network, leading to poor performance and service disruptions.
• Packet Loss : During link flapping, data packets may be lost or delayed, affecting data integrity and delivery.
• Connectivity Issues : Devices connected to the flapping link may experience intermittent connectivity or disconnections.
• Spanning Tree Protocol (STP) Recalculation Delays : STP recalculations during link flapping can result in temporary network outages or increased convergence times.

II. The Causes of Link Flapping

• Physical Connectivity Issues : Loose or damaged cables, connectors, or network ports can cause link flapping when there are intermittent connections.
• Network Device Errors : Malfunctioning network switches, routers, or network interface cards (NICs) can lead to unstable link states.
• Spanning Tree Protocol (STP) Misconfigurations: Incorrect STP configurations can create network loops, resulting in link flapping as STP tries to block or unblock redundant paths.
• Ethernet Auto-Negotiation Problems : Inconsistent auto-negotiation settings between devices can cause link flapping due to mismatched speeds or duplex modes.

III. How to Identify & Troubleshoot Link Flapping

• Network Monitoring : Use network monitoring tools like Obkio to track link status and identify instances of link flapping.
• Physical Inspection : Physically inspect network cables and connectors to ensure they are properly connected and not damaged.
• Interface Errors : Check for interface errors or error counters on network devices to identify potential issues.
• STP Configuration Review : Review and verify STP configurations to prevent network loops and link flapping.
• Speed and Duplex Settings : Ensure consistent speed and duplex settings between connected devices to avoid negotiation issues.
• Link Redundancy : Evaluate link redundancy and adjust configurations to avoid unintended loops.

By proactively identifying and addressing link flapping, businesses can maintain a stable and reliable network infrastructure. Network monitoring, physical inspections, and STP configuration reviews are essential in detecting and mitigating link flapping issues, ensuring smooth communication and data transfer within the network.

IV. Network Troubleshooting Scenarios for Link Flapping

Link flapping occurs when a network link experiences frequent up and down transitions, causing instability and disruptions in communication. Troubleshooting link flapping requires identifying the underlying causes and implementing solutions to stabilize the link. Here are some network troubleshooting scenarios to consider when dealing with link flapping:

• Physical Inspection : Inspect the physical connections of the link for loose cables, damaged connectors, or faulty network equipment.
• Cable Quality : Check the quality of the network cables. Use certified and properly shielded cables to reduce interference.
• Link Speed and Duplex Settings : Verify that both ends of the link are set to the same speed and duplex settings (e.g., 1 Gbps, full duplex) to avoid negotiation issues.
• Auto-Negotiation : Test the link with auto-negotiation enabled and disabled to see if it stabilizes the connection.
• Check Network Equipment : Review the logs and statistics of the network switches or routers connected to the link for any errors or alerts related to the flapping link.
• Firmware and Software Updates : Ensure that the firmware and software of network devices are up to date to address known issues.
• STP (Spanning Tree Protocol) Issues : Check if the link is part of a spanning tree loop or blocked by Spanning Tree Protocol (STP) due to redundancy misconfigurations.
• STP PortFast and BPDU Guard : If using STP, ensure that PortFast and BPDU Guard are configured correctly to prevent accidental loops.
• Link Aggregation (EtherChannel/LACP) : If the link is part of a link aggregation group, verify the configuration of the aggregation protocol (e.g., EtherChannel, LACP).
• Power Fluctuations : Verify that the devices connected to the link have stable power sources to prevent link flapping due to power issues.
• Update NIC Drivers : Keep network interface card (NIC) drivers up to date on connected devices to prevent compatibility issues.
• Interference : Check for sources of electromagnetic interference or signal degradation that might affect the link stability.
• Port Statistics : Monitor port statistics to check for excessive error counters, collisions, or other anomalies.
• MTU Size : Test different Maximum Transmission Unit (MTU) sizes to avoid potential fragmentation issues.
• Bypass Network Equipment : Temporarily bypass any intermediate network equipment (e.g., switches, routers) to determine if the issue is specific to a particular device.
• Check Other Network Links : Investigate if any other links or devices in the network are causing network congestion or instability.
• Isolate Devices : Isolate devices connected to the link to test if the problem lies with one of the connected devices.
• Network Capture : Use network capture tools to analyze network traffic and look for patterns or events leading to link flapping.

By systematically troubleshooting link flapping, you can identify the root causes and implement appropriate solutions to stabilize the link and ensure reliable network communication. Regular monitoring and analysis of network performance will help you proactively detect and address link flapping issues as they arise. If the issue persists or requires expertise beyond your capabilities, seek assistance from qualified network administrators or network equipment vendors.

How to Troubleshoot the Most Common Network Problems: Steps & Tips

Now that we've gone over some of the most common network problems that businesses encounter in enterprise networks, it's essential to equip ourselves with effective troubleshooting steps. When network issues arise, swift and systematic troubleshooting is crucial to minimize downtime, ensure smooth operations, and maintain a reliable network infrastructure.

Identifying network issues is the first step to solving them - and it all comes down to pinpointing who , what , where , and when .

Step 1: Network Assessment

The first step when it comes to identifying network problems, with your Network Monitoring tool in hand, is performing a network assessment to collect some key information about your network. Obkio's Network Monitoring tool , which we helped you deploy earlier in this blog post, plays a vital role in this process.

By conducting a thorough network assessment, you can gain valuable insights into your network's health, performance, and potential bottlenecks. This information serves as a solid foundation for efficient troubleshooting and enables you to pinpoint the root causes of network issues more effectively. Now, let's delve into the general troubleshooting steps to address common network problems and make the most out of your network monitoring capabilities

• What actions to take: After you’ve collected all the information you need to identify the network issue, can then start network troubleshooting . That could include reaching out to your ISP or MSP, or bringing the problem to your network administrator to fix it internally.

For all the details about identifying network issues, check out our article on how to identify network issues!

Troubleshooting common network problems involves identifying the "what" issue is occurring, determining "where" the problem is located in the network, understanding "when" the issue is happening, identifying "who" is affected, and then taking appropriate actions to resolve the problem. Here are some steps to help troubleshoot common network problems:

Step 2: Identify the Issue (What)

To know how to solve these problems, you need to actually understand what they are. A network performance monitoring software will measure network metrics and report back if it finds any issues, with details about what the issue is, and what caused it.

• Gather information from users or monitoring tools to determine the symptoms and specific problem experienced.
• Clearly define the issue, such as slow internet speed, intermittent connectivity, or VoIP call quality problems.

Step 3: Locate the Problem (Where)

It’s important to identify where exactly in your network an issue has occurred. Using Monitoring Agents , Obkio allows you to deploy Agents in key network locations for end-to-end visibility over your network to provide you with details about where problems have occurred. This end-to-end network monitoring approach gives you visiblity of every end of your network, from your LAN to your WAN .

• Determine which part of the network is affected, such as a specific network segment, device, or service.
• Use network monitoring tools and analysis to identify potential network bottlenecks , high utilization areas, or devices showing errors.

Step 4: Determine the Timeframe (When)

Identifying the specific timeframe in which a network problem occurs is essential for effective troubleshooting. Pinpointing when the issue started and its recurrence patterns using historical data from Obkio's NPM tool can help correlate the problem with network changes or events, streamlining the resolution process.

• Find out when the problem started occurring to correlate with any changes in the network or configurations.
• Analyze network logs and timestamps to pinpoint when the issue typically happens, if it's intermittent.

Step 5. Identify Affected Users (Who)

Understanding which users or devices are experiencing network issues is crucial in troubleshooting. By pinpointing the affected users, network administrators can focus their efforts, assess the scope of the problem, and provide targeted support, ensuring a prompt resolution and improved user experience."

• Determine which users or devices are experiencing the problem to understand the scope of the issue.
• If the problem is widespread, identify common factors among affected users.

Step 6. Who is Responsible For the Network Segment

Once you know where a network problem is located, and what exactly it is, you can then easily decide who in your business is responsible for that network segment.

• Identifying the responsible party helps streamline communication and coordination, ensuring a more effective and targeted approach to resolving the issue.
• By involving the right stakeholders, you can facilitate a faster resolution and prevent delays in troubleshooting efforts.

Step 7. Take Initial Actions (What Actions to Take)

When network issues arise, it's essential to swiftly address the problem with initial actions. This step focuses on quick checks and basic troubleshooting to resolve common issues that might be causing the network problem. By taking these immediate actions, you can potentially resolve the problem right away or narrow down the root cause, setting the stage for further targeted troubleshooting.

• Perform basic checks, such as verifying cable connections, power cycling affected devices, or checking for software updates.
• Review network configuration changes or recent updates that might have contributed to the problem.

Step 8. Isolate the Issue

To efficiently troubleshoot network problems, isolating the issue is crucial. This step involves narrowing down the problematic area or component in the network. By systematically eliminating potential causes, you can pinpoint the specific source of the problem, leading to a more precise and effective resolution.

• Monitor network devices, like switches or routers, using Obkio's Network Device Monitoring feature, to identify if they are causing the problem or experiencing resource issues.
• Divide the network into segments and test each segment independently to narrow down the location of the problem.
• Use Visual Traceroutes to determine if the problem is in your local network or ISP network.

Step 9. Implement Solutions

After identifying the root cause of the network problem, it's time to implement targeted solutions. This step focuses on making necessary adjustments, configurations, or replacements to address the issue directly. By applying the appropriate solutions, you can effectively restore network functionality and prevent the problem from recurring

• Based on the gathered information, apply appropriate solutions, such as adjusting configurations, updating firmware, or replacing faulty hardware.
• If the network problem is beyond your organization's control and is related to the Internet Service Provider (ISP) or Managed Service Provider (MSP) infrastructure, promptly reach out to them for assistance.
• Collaborating with your ISP or MSP can expedite the resolution process for issues that lie outside your network's scope.
• Document the changes made during troubleshooting for future reference.

Step 10. Test, Verify & Continuously Monitor Network Performance

Culminating the troubleshooting process, this section outlines the essential steps to verify the effectiveness of the implemented solutions and ensure a stable network environment. From thorough network testing to continuous monitoring, these practices ensure that network issues are promptly resolved and potential future problems are proactively addressed.

• After implementing solutions, thoroughly test and continuously monitor network performance with your Network Monitoring tool to ensure the problem is resolved.
• Verify that the network is functioning as expected and the previously identified issues are no longer present. Monitor the network post-resolution to verify the stability and effectiveness of the applied changes.
• Continuously monitor network performance using tools like Obkio to ensure the problem does not reoccur and to detect any new issues that may arise.
• By ongoing monitoring, you can proactively address potential problems before they impact the network's stability and user experience.

Why Should Businesses Find & Fix Network Problems Anyways?

In this section, we'll delve into why finding and troubleshooting network problems is a critical mission for businesses. From bolstering productivity and enhancing customer experience to safeguarding data and gaining a competitive edge, we'll explore the myriad reasons why proactive network monitoring is an indispensable investment.

• Maintaining Productivity : A smooth and reliable network is the backbone of business productivity. When network problems occur, they disrupt communication, data access, and collaborative efforts, leading to downtime and decreased efficiency. By identifying and resolving these issues promptly, businesses can minimize disruptions and keep productivity levels at their peak.
• Enhancing Customer Experience : In a digitally interconnected world, customer satisfaction hinges on swift and seamless interactions. Network problems can affect customer-facing services, leading to slow response times, website downtime, and impaired online transactions. By proactively addressing network issues, businesses can provide a positive customer experience, which can bolster loyalty and brand reputation.
• Cost Savings : Network problems can be costly in terms of both time and resources. Extended downtime can result in revenue losses, missed opportunities, and increased operational expenses as IT teams rush to troubleshoot and fix issues. By resolving problems swiftly, businesses can mitigate these financial impacts and avoid potential long-term consequences.
• Security and Data Protection : Network problems, especially those related to security breaches, can expose sensitive data and compromise the overall integrity of the business. Troubleshooting network vulnerabilities and promptly addressing security threats is essential for safeguarding valuable information and maintaining regulatory compliance.
• IT Team Efficiency : Persistent network issues can place an immense burden on IT teams, overwhelming them with repetitive troubleshooting tasks. By proactively identifying and resolving problems, IT teams can focus on strategic initiatives and improvements, ultimately making the best use of their expertise and time.
• Business Continuity : In today's digital-dependent landscape, uninterrupted business operations are crucial for survival and growth. Network problems, if left unchecked, can lead to extended outages and interruptions, threatening business continuity. By troubleshooting and resolving issues, businesses can ensure a more robust and resilient infrastructure.
• Competitive Advantage : In a competitive market, businesses must deliver a seamless user experience to stand out from their rivals. A well-maintained and efficient network allows companies to differentiate themselves by providing reliable services and smooth interactions, ultimately gaining a competitive edge.
• Employee Satisfaction : A functional network translates to a smoother work experience for employees. When network problems are addressed promptly, employees can focus on their tasks without the frustration and stress caused by technology-related hurdles.

In conclusion, finding and troubleshooting network problems is crucial for businesses to maintain productivity, enhance customer experience, save costs, protect data, streamline IT operations, ensure business continuity, gain a competitive advantage, and foster employee satisfaction. It's an essential investment in the overall success and growth of any modern business.

In Conclusion

There are a variety of network problems that could take over your network at any given moment. With the growing complexity and size of modern network infrastructures, network problems can be more frustrating than ever.

Businesses can’t afford to waste time and money dealing with network problems that effect:

• Productivity
• IT resources

Knowing about some of the most common network problems helps you prepare for what your network may encounter in the future.

Network performance monitoring using a network performance monitor tool is your key to identifying network problems, because it pinpoints intermittent network slowness issues that are difficult to troubleshoot otherwise! A distributed network monitoring solution like Obkio's offers visibility that traditional systems are unable to offer.

Obkio is a simple Network Performance Monitoring SaaS solution for IT pros to help you continuously monitor the health of their network and core business applications to improve the end-user experience!

Put It to the Test: Trying Is the Ultimate Way to Learn!

Networks may be complex. But Obkio makes network monitoring easy. Monitor, measure, pinpoint, troubleshoot, and solve network problems.

• 14-day free trial of all premium features
• Deploy in just 10 minutes
• Monitor performance in all key network locations
• Measure real-time network metrics
• Identify and troubleshoot live network problems

You can rest assured that we're not like those pushy Sellsy people - there's no catch here. We firmly believe in the excellence of our product, but if it's not the right fit for you, we understand and want what's best for you.

Monitor mutliple network types, apps and services with features for:

• Network Audits
• Cloud Network Monitoring
• VoIP Monitoring
• Remote Network Monitoring
• UC Monitoring
• SD-WAN Monitoring
• SD-WAN Migration Monitoring
• MPLS Network Monitoring
• Internet Monitoring
• Firewall Monitoring
• SASE Monitoring

These might interest you

Don't let network issues slow you down - learn how obkio can help, see how obkio finds & fixes network problems - watch now, say goodbye to network headaches..

Get a live demo of Obkio now!

Did you know?

How to Troubleshoot Windows Network Connections

Get your Wi-Fi or Ethernet connection up and running.

Without a working Internet connection, most Windows devices really can’t work the way they should, nor allow users to function completely or well. That makes fixing network issues extremely important. Here’s how to get that done.

Arguably, Windows without a working network connection isn’t really worth much. That’s because access to email, social  media, the Web – and even Windows updates and apps – doesn’t work without network (and Internet) access. That’s probably why Microsoft has put a lot of time and effort into making networking issues easy to recognize, diagnose and fix as part and parcel of how Windows works.

Getting Network Troubleshooting Started

The views from the more recent Windows 11 and Windows 10 builds appear in Figures 1 and 2 following. What they show is that by right-clicking on the network symbol in the notification area of the Task Bar (right-hand side, by default) you can jump straight into troubleshooting your Windows network connection.

Figure 1: Right-click on the Wi-Fi (or Ethernet) symbol (bottom center) and “Diagnose network problems” pops right up in Windows 11 Insider Preview 

Figure 2: In all current Windows 10 versions, right-click on the active network symbol to get “Troubleshoot problems” instead.

Either way, it’s a one-click maneuver to start the network troubleshooting process in Windows 10 and in Windows 11 recent builds. Older Windows 11 versions aren’t quite as accommodating, as shown in Figure 3.

In older versions of Windows 11, however, network troubleshooting is never too far away. Click on Start 🡪 Settings, then enter “Trouble” into the Settings search box. As you can see in Figure 4, a number of options pop up in response, click the “Troubleshoot Other problems” item to continue.

When you follow that “Other problems” entry, the “Network and Internet” item finally appears. That’s what you want (and that’s where the other Windows versions take you more directly). Click the “Run” button at the right to proceed from here.

This approach works for all Windows 10 and 11 versions, actually (with some minor differences in Windows 10 for wording, but the pathway is pretty much identical).

The Windows Network Troubleshooters

Because Windows networking mostly revolves around two kinds of networks, there are two kinds of troubleshooters to match: one for wired Ethernet, the other for wireless Wi-Fi, in all its many forms. Figure 6 shows the results of running the Wired Ethernet troubleshooter, with all options expanded in a “no trouble” situation:

Figure 7 shows the same troubleshooter when run on a Wi-Fi attached system instead. Iconography and minor terminology changes aside, it’s identical to the version shown in Figure 6.

The various actions suggested in the troubleshooters cover a wide array of possible problem sources. Let’s walk through those items to discuss what the troubleshooters look for, what they might find, and related fixes.

Try a different website : Any given website is, of course, somewhere on the Internet. 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. 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:

1. Ping loopback (this checks that TCP/IP is working, and looks for a response from a synthetic address that’s always available).

2. Ping localhost (this checks that the current network interface device is up and running)

3. 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)

4. Ping a known working Internet address ; for whatever reason MS often uses ping Microsoft.com as its check). See this sequence in Figure 8.

Restart the network adapte r (Wi-Fi or wired Ethernet, depending…): this basically turns off the network interface and then turns it back on. In some situations, signaling or traffic issues can cause the network interface to stop working temporarily. Turning it off, then back on, will usually clear such temporary glitches. 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).

Restart your modem, router, or access point (all three apply to Wi-Fi, and the first two to wired Ethernet). 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. I’ve seen power glitches, signaling issues, and even service outages show up as a boundary device issue. In many cases (except when a service outage persists) restarting the boundary device will set things back to rights. 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).

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. Nowadays, if you use that same key combo, you’ll get the logout screen, from which you can indeed get to the restart button. But sometimes, Windows gets itself into a state where some things don’t work – including networking, in this context. 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.

Other Sources of Network Difficulty

There are three basic ways in which networking can go wrong. This applies equally to Windows PCs and other devices, but the details will differ. 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). 

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. 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).

The Windows network troubleshooter does a pretty thorough job of checking all of these things as it runs through its various tests. 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:

1. Make sure ipconfig shows a valid network address scheme and configuration.You can check this by entering “ipconfig” at the command line. One sure sign of IP troubles is PCs that present Microsoft Automatic Private IP Addressing (APIPA) addresses. These IPv4 addresses fall in the range from 169.254.0.1 – 169.254.255.254 (basically the tail end of the 169.254 Class B address. They show up automatically when other sources of addressing aren’t working. This usually indicates some kind of trouble with local DHCP services (not working or unavailable). Fixing this often requires restarting (or sometimes, replacing) the local router, gateway or wireless access point.

2. Make sure that DNS is working and points to the correct DNS server . Improper name resolution can cause all kinds of Internet access problems (and may indicate security is compromised). Run ipconfig /all and check DNS information for the network adapter in active use. On my network, for example, the default address comes from Spectrum my ISP and shows up as 1.0.0.1. It’s tied to CloudFlare, which is a well-known, well-respected, and highly secure DNS provider. See LifeWire’s Best Free and Public DNS Servers (June 2023) for a list of reliable public DNS providers.

3. Keep an extra network interface handy. I always have one or two extra hardware devices around, so I can try a different network interface if the one on any particular PC appears to be acting up. On the wired (GbE) Ethernet side, I’ve got an USB 3.0 to GbE adapter ( US$20 -35 ): it plugs into any USB 3.0 (or better) port and provides an RJ-45 from which I can cable into my nearest switch. On the Wi-Fi side, I’ve got a USB 3.0 to 802.11ax adapter ( US$20-60 ). If a PC’s existing adapter stops working, or has trouble, I simply need to plug one or the other in. That’s usually all it takes to get networking back (with an RJ-45 cable into the switch for GbE as well). In a pinch, in fact, I’ve used the USB-to-Wi-Fi device with my iPhone as a hotspot to keep working on the Internet even during ISP outages, some extended for days.

Bottom Line

Should one (or all) of your Windows PCs run into networking difficulty, turn to the Windows Network and Internet Troubleshoot as your first point of action in attempting to diagnose and fix whatever’s wrong. In the vast majority of cases – over 90% in my personal experience – it will also be the last tool you need to use to help figure out what’s wrong and get started on a fix. Indeed, except for situations that require hardware changes, or working with ISP boundary devices, or similar third-party issues, this will probably also be the last tool you need to use to get networking and Internet access working again.

Stay on the Cutting Edge

Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.

Ed Tittel is a long-time IT writer, researcher and consultant, and occasional contributor to Tom’s Hardware. A Windows Insider MVP since 2018, he likes to cover OS-related driver, troubleshooting, and security topics.

Microsoft's 2023 ugly sweater lets you wear the famous Windows XP wallpaper

Super tiny Windows 11 OS that fits inside your 4GB thumb drive gets a big update — Tiny11 2311 shrinks 20% and allows cumulative updates

Alienware's RTX 4090 laptop and desktop deals cost little more than the card itself.

Most Popular

By Sammy Ekaran September 30, 2023

By Sammy Ekaran September 25, 2023

By Sammy Ekaran September 24, 2023

By Paul Alcorn September 12, 2023

By Les Pounder September 11, 2023

By Sammy Ekaran September 04, 2023

By Les Pounder August 27, 2023

By Les Pounder August 21, 2023

By Sammy Ekaran August 20, 2023

By Sammy Ekaran August 19, 2023

By Sydney Butler August 18, 2023

Fix Wi-Fi connection issues in Windows

Troubleshooting network problems in windows.

If you can’t get email, browse the web, or stream music, chances are you’re not connected to your network and can’t get onto the internet. To fix the problem, here are some things you can try.

Things to try first

Try these things first to help you fix or narrow down the connection problem.

Run Get Help to troubleshoot and fix common connection problems. Right click the network icon in the right side of the taskbar and select Diagnose network problems or open  Get Help for Network & Internet

Make sure Wi‑Fi is turned on. Select the No internet icon  on the right side of the taskbar, and make sure Wi-Fi is turned on. If it isn't, select it to turn it on. Also, make sure  Airplane mode  is turned off.

Select Manage Wi-Fi connections ( > ) on the Wi-Fi quick setting, see if a Wi-Fi network you recognize and trust appears in the list of networks. If it does, select the Wi-Fi network, and they try to connect to it. If it says  Connected  underneath the network name, select  Disconnect , wait a moment, and then select  Connect  again.

Try connecting to a network on a different frequency band. Many consumer Wi-Fi routers broadcast at two different network frequency bands: 2.4 GHz and 5 GHz. These will appear as separate networks in the list of available Wi-Fi networks. If your list of available Wi-Fi networks includes both a 2.4 GHz network and a 5 GHz network, try connecting to the other network. To learn more about the differences between 2.4 GHz networks and 5 GHz networks, check out  Wi-Fi problems and your home layout .

Make sure the physical Wi‑Fi switch on your laptop is turned on. (An indicator light usually shows when it's on.)

Restart your modem and wireless router. This helps create a new connection to your internet service provider (ISP). When you do this, everyone that is connected to your Wi-Fi network will be temporarily disconnected. The steps you take to restart your modem and router can vary, but here are the general steps.

Note:  If you have a cable modem/Wi-Fi router combo device, you only need to follow the steps for the single device.

Unplug the power cable for the router from the power source.

Unplug the power cable for the modem from the power source.   Some modems have a backup battery. If you unplug the modem and lights stay on, remove the battery from the modem.

Wait at least 30 seconds or so. If you had to remove the battery from the modem, put it back in.

Plug the modem back into the power source. The lights on the modem will blink. Wait for them to stop blinking.

Plug your router back into the power source. Wait a few minutes for the modem and router to fully power on. You can usually tell when they’re ready by looking at the status lights on the two devices.

On your PC, try to connect again.

Narrow down the source of the problem

Connection problems can be due to a variety of reasons—problems with the website, your device, the Wi-Fi router, modem, or your Internet Service Provider (ISP). Try the following steps to help narrow down the source of the problem.

If the "Wi-Fi connected" icon  appears on the right side of the taskbar, visit a different website. If the website opens, there might be a problem with the specific website. If you can't connect to another website, go to the next step.

On another laptop or phone, try to connect to the same network. If you can connect, the source of the problem is likely due to your device—go to the section  Network troubleshooting on your device . If you can't connect to the network on any device, continue to the next step.

Check to see if there is a problem with the connection to your Wi-Fi router. Do this by using a ping test.

Select Search on the taskbar, and type  command prompt . The  Command Prompt  button will appear. To the right of it, select  Run as administrator  >  Yes .

At the command prompt, type  ipconfig , and then select  Enter . Look for the name of your Wi-Fi network within the results, and then find the IP address listed next to  Default gateway  for that Wi-Fi network.  Write down that address if you need to.  For example:  192.168.1.1

At the prompt, type  ping <DefaultGateway>  and then select  Enter .   For example, type  ping 192.168.1.1  and select  Enter .   The results should be something like this:

Reply from 192.168.1.1: bytes=32 time=5ms TTL=64

Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:  Minimum = 4ms, Maximum = 5ms, Average = 4ms

If you see results like this and are getting a reply, then you have a connection to your Wi-Fi router, so there might be a problem with your modem or ISP. Contact your ISP or check online on another device (if you can) to see if there's a service outage.

If the results of the ping test indicate that you are not getting a reply from the router, try connecting your PC directly to your modem by using an Ethernet cable (if you can). If you can connect to the internet using an Ethernet cable, it confirms the connection problem is due to the Wi-Fi router. Make sure you've installed the latest firmware and see the documentation for your router.

Network troubleshooting on your device

Run network commands

Try running these network commands to manually reset the TCP/IP stack, release and renew the IP address, and flush and reset the DNS client resolver cache:

At the command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem:

Type  netsh winsock reset  and select   Enter .

Type  netsh int ip reset  and select  Enter .

Type  ipconfig /release  and select  Enter .

Type  ipconfig /renew  and select  Enter .

Type  ipconfig /flushdns  and select  Enter .

Uninstall the network adapter driver and restart

If the previous steps didn’t work, try to uninstall the network adapter driver, and then restart your computer. Windows will automatically install the latest driver. Consider this approach if your network connection stopped working properly after a recent update.

Before uninstalling, make sure you have drivers available as a backup. Visit the PC manufacturer’s website and download the latest network adapter driver from there. If your PC can't connect to the internet, you'll need to download a driver on a different PC and save it to a USB flash drive so you can install the driver on your PC. You’ll need to know the PC manufacturer and model name or number.

Select Search on the taskbar, type  device manager , and then select  Device Manager  from the list of results.

Expand  Network adapters , and locate the network adapter for your device.

Select the network adapter, press and hold (or right-click), and then select  Uninstall device  > check the  Attempt to remove the driver for this device  check box >  Uninstall .

After uninstalling the driver, select Start  >  Power  >  Restart .

After your PC restarts, Windows will automatically look for and install the network adapter driver. Check to see if that fixes your connection problem. If Windows doesn't automatically install a driver, try to install the backup driver you saved before uninstalling.

Check if your network adapter is compatible with the latest Windows Update

If you lost your network connection immediately after upgrading to or updating Windows 11, it's possible that the current driver for your network adapter was designed for a previous version of Windows. To check, try temporarily uninstalling the recent Windows Update:

Select Start  >  Settings  >   Windows Update  >  Update history  > Uninstall updates .

Select the most recent update, then select  Uninstall .

If uninstalling the most recent update restores your network connection, check to see if an updated driver is available:

Select the network adapter, press and hold (or right-click), then select  Update driver  > Search automatically for updated driver software , and then follow the instructions.

After installing the updated driver, select Start  >  Power  > Restart  if you're asked to restart, and see if that fixes the connection issue.

If Windows can’t find a new driver for your network adapter, visit the PC manufacturer’s website and download the latest network adapter driver from there. You’ll need to know the PC manufacturer and model name or number.

Do one of the following:

If you couldn’t download and install a newer network adapter driver, hide the update that’s causing you to lose your network connection. To learn how to hide updates, see  Hide Windows Updates or driver updates .

If you could successfully install updated drivers for your network adapter, then reinstall the latest updates. To do this, select Start  >  Settings  >  Windows Update > Check for updates .

Use network reset

Using network reset should be the last step you try. Consider using it if the steps above don’t help to get you connected.

This can help solve connection problems you might have after upgrading from Windows 10 to Windows 11. It can also help to fix the problem where you can connect to the internet, but can't connect to shared network drives. Network reset removes any network adapters you have installed and the settings for them. After your PC restarts, any network adapters are reinstalled, and the settings for them are set to the defaults.

Select Start  >  Settings  >  Network & internet  >  Advanced network settings > Network reset . Open Network & Internet Status settings

On the  Network reset  screen, select  Reset now  >  Yes  to confirm.

Wait for your PC to restart, and see if that fixes the problem.

After using network reset, you might need to reinstall and set up other networking software you might be using, such as VPN client software or virtual switches from Hyper‑V (if you're using that or other network virtualization software).

Network reset might set each one of your known network connections to a public network profile. In a public network profile, your PC is not discoverable to other PCs and devices on the network, which can help make your PC more secure. However, if your PC is used for file or printer sharing, you’ll need to make your PC discoverable again by setting it to use a private network profile. To do this, select Start  >  Settings  >  Network & internet  >  Wi-Fi . On the  Wi-Fi  screen, select  Manage known networks  > the network connection you want to change. Under  Network profile type , select  Private .

Additional troubleshooting steps

Check your Wi-Fi settings

Wi-Fi adapter manufacturers might have different advanced settings you can change based on your network environment or connection preferences.

Check the Wireless Mode setting for your network adapter and make sure it matches the capabilities of the network you’re trying to connect to. If it doesn’t match, you won’t be able to connect, and the network might not appear in the list of available networks. The Wireless Mode will often be set to Auto or something similar by default, which enables connection for every kind of network that’s supported.

To find the wireless mode setting

In Device Manager, select  Network adapters , and then double-click the network adapter name.

Select the  Advanced  tab and look for a  Wireless Mode  setting. Make sure it’s set to the mode your network is using.

Wi-Fi profile settings

Windows uses the Wi-Fi profile to save the settings that are needed to connect to a Wi-Fi network. These settings include the network security type, key, network name (SSID), and so on. If you can’t connect to a Wi-Fi network that you could connect to before, it’s possible that the network settings might have changed or the profile is corrupted.

To fix this, remove (or "forget") the network connection, then reconnect to the network. When you forget a network connection, it removes the Wi-Fi network profile from your PC.

To forget a network

Select Start  > Settings  >  Network & internet .

Select  Wi-Fi , then select  Manage known networks .

Select the network you want to forget, then select  Forget .

Afterwards, select the Wi-Fi icon on the taskbar and try to reconnect to the network to renew the network connection.

Check your home layout

Your Wi-Fi network might be affected by the network's frequency band, channel congestion, and/or signal strength.  For more info, see  Wi-Fi problems and your home layout .

Check for additional symptoms for the "No internet connection" icon.

There may be additional troubleshooting steps you can try, depending on which symptoms you're having. To view these steps, check out  Wi-Fi connection icons and what they mean .

Related topics

Setting up a wireless network

How to find your wireless network password

Analyze the wireless network report

Wi-Fi tools and apps

Make a Wi-Fi network public or private in Windows

Afterwards, see if a Wi-Fi network you recognize and trust appears in the list of networks. If it does, select the Wi-Fi network, and they try to connect to it. If it says Connected underneath the network name, select Disconnect , wait a moment, and then select Connect again.

Try connecting to a network on a different frequency band. Many consumer Wi-Fi routers broadcast at two different network frequency bands:  2.4 GHz and 5 GHz. These will appear as separate networks in the list of available Wi-Fi networks. If your list of available Wi-Fi networks includes both a 2.4 GHz network and a 5 GHz network, try connecting to the other network. To learn more about the differences between 2.4 GHz networks and 5 GHz networks, check out Wi-Fi problems and your home layout .

Run the Network troubleshooter. The Network troubleshooter can help diagnose and fix common connection problems.

To run the Network troubleshooter

Select the Start  button >  Settings > Network & Internet > Status . Open Network & Internet Status settings

Under Change your network settings , select Network troubleshooter .

Follow the steps in the troubleshooter, and see if that fixes the problem.

Restart your modem and wireless router. This helps create a new connection to your internet service provider (ISP).

When you do this, everyone that is connected to your Wi-Fi network will be temporarily disconnected. The steps you take to restart your modem and router can vary, but here are the general steps. ( Note : If you have a cable modem/Wi-Fi router combo device, you only need to follow the steps for the single device.)

If the "Wi-Fi connected" icon  appears on the right side of the taskbar, visit a different website. If the website opens, there might be a problem with the specific website. If you can't connect to another website, go to the next step.

On another laptop or phone, try to connect to the same network. If you can connect, the source of the problem is likely due to your device—go to the section Network troubleshooting on your device . If you can't connect to the network on any device, continue to the next step.

Check to see if there is a problem with the connection to your Wi-Fi router.  Do this by using a ping test.

In the search box on the taskbar, type command prompt . The Command Prompt button will appear. To the right of it, select Run as administrator > Yes .

At the command prompt, type ipconfig , and then select Enter . Look for the name of your Wi-Fi network within the results, and then find the IP address listed next to Default gateway for that Wi-Fi network.  Write down that address if you need to. For example:  192.168.1.1

At the prompt, type ping <DefaultGateway> and then select Enter .  For example, type ping 192.168.1.1 and select Enter .  The results should be something like this:

Type netsh winsock reset and select Enter .

Type netsh int ip reset and select Enter .

Type ipconfig /release and select Enter .

Type ipconfig /renew and select Enter .

Type ipconfig /flushdns and select Enter .

In the search box on the taskbar, type device manager , and then select Device Manager from the list of results.

Expand Network adapters , and locate the network adapter for your device.

Select the network adapter, press and hold (or right-click), and then select  Uninstall device  > check the  Attempt to remove the driver software for this device  check box >  Uninstall .

After uninstalling the driver, select the Start button > Power  > Restart .

If you lost your network connection immediately after upgrading or updating Windows 10, it's possible that the current driver for your network adapter was designed for a previous version of Windows. To check, try temporarily uninstalling the recent Windows Update:

Select the Start  button, then select Settings  > Update & Security   > Windows Update  > View update history > Uninstall updates .

Select the most recent update, then select Uninstall .

Select the network adapter, select Update driver > Search automatically for updated driver software , and then follow the instructions.

After installing the updated driver, select the Start button > Power  > Restart if you're asked to restart, and see if that fixes the connection issue.

If you couldn’t download and install a newer network adapter driver, hide the update that’s causing you to lose your network connection. To learn how to hide updates, see Hide Windows Updates or driver updates .

If you could successfully install updated drivers for your network adapter, then reinstall the latest updates. To do this, select the Start  button, then select Settings  > Update & Security > Windows Update > Check for updates .

This can help solve connection problems you might have after upgrading from a previous version of Windows to Windows 10. It can also help to fix the problem where you can connect to the internet, but can't connect to shared network drives. Network reset removes any network adapters you have installed and the settings for them. After your PC restarts, any network adapters are reinstalled, and the settings for them are set to the defaults.

Note:  To use network reset, your PC must be running Windows 10 Version 1607 or later. To see which version of Windows 10 your device is currently running, select the Start button, then select Settings > System > About .

Select the Start  button, then select Settings  > Network & Internet  > Status > Network reset . Open Network & Internet Status settings

On the Network reset screen, select Reset now > Yes to confirm.

Network reset might set each one of your known network connections to a public network profile. In a public network profile, your PC is not discoverable to other PCs and devices on the network, which can help make your PC more secure. However, if your PC is used for file or printer sharing, you’ll need to make your PC discoverable again by setting it to use a private network profile. To do this, select the Start  button, then select Settings > Network & Internet  > Wi-Fi  . On the Wi-Fi screen, select Manage known networks > the network connection you want to change > Properties . Under Network profile , select  Private .

In Device Manager, select Network adapters , and then double-click the network adapter name.

Select the Advanced tab and look for a Wireless Mode setting. Make sure it’s set to the mode your network is using.

Select the Wi-Fi network  icon on the right side of the taskbar, then select Network & Internet settings .

Select Wi-Fi , then select Manage known networks .

Select the network you want to forget, then select Forget .

Afterwards, select the Wi-Fi icon on the taskbar and try to reconnect to the desired network to renew the network connection.

Your Wi-Fi network might be affected by the network's frequency band, channel congestion, and/or signal strength.  For more info, see Wi-Fi problems and your home layout .

There may be additional troubleshooting steps you can try, depending on which symptoms you're having. To view these steps, check out Wi-Fi connection icons and what they mean .

Make a Wi-Fi network public or private in Windows 10

Check the basics on your PC

Make sure Wi-Fi is turned on.

Swipe in from the right edge of the screen, select  Settings , then select the  Network  icon.

Turn on  Wi-Fi .

Make sure your PC isn’t in airplane mode.

Turn off  Airplane mode .

Move closer to the router or access point if you can.

If you don’t see the network name at all, the router or access point might not be set to broadcast the network name. In this case, you’ll need to connect to it manually.

Swipe in from the right edge of the screen, and then select  Settings .

Select the  Network  icon, and then select  Hidden network .

Type the network name and select  Next .

Type the password and select  Next .

Follow any additional instructions to get connected.

The network will be added to your list of networks and will be available to connect to when your computer is in range of the network. To connect to the network, follow these steps:

Open  Connect to a Network  by selecting the network icon in the notification area.

Select  Unnamed Network , select  Connect , and then type the network information. The network will be added to your list of networks and will be available to connect to in the future when your computer is in range of the network..

Use the Network Troubleshooter

Let Windows try to help you fix the problem. Try running the Network troubleshooter to see if it can diagnose and fix the problem.

Select the  Start   button, start typing  Network problems , and then select  Identify and repair network problems  in the list.

Run network commands after using the Network Troubleshooter

The Network Troubleshooter (mentioned above) can help diagnose and fix common connection problems. After using that, try running the network commands below because the combination of doing these two things can help you get connected.

If your problem isn’t fixed after running the Network troubleshooter, try to:

Reset the TCP/IP stack.

Release the IP address.

Renew the IP address.

Flush and reset the DNS client resolver cache.

Here's how to run networking commands in a command prompt:

Select the Start  button, start typing cmd , right-click Command Prompt in the list, select Run as Administrator , and then select Yes .

At the command prompt, run the following commands in the listed order and then check to see if that fixes your connection problem:

Type netsh winsock reset and press Enter.

Type netsh int ip reset and press Enter.

Type ipconfig /release and press Enter.

Type ipconfig /renew and press Enter.

Type ipconfig /flushdns and press Enter.

Restart your modem and router

This helps create a new connection to your Internet service provider (ISP). When you do this, everyone that is connected to your Wi-Fi network will be temporarily disconnected.

The steps you take to restart your modem and router can vary, but here are the general steps:

Unplug the power cable for the modem from the power source. Some modems have a backup battery. So if you unplug the modem and lights stay on, remove the battery from the modem.

See if it's a problem with your modem or your ISP

Make sure it’s not a problem with your cable modem or Internet service provider (ISP). If it is, contact your ISP.

At the command prompt, type ipconfig . Look for the IP address listed next to Default gateway . Write down that address if you need to. For example, 192.168.1.1.

At the prompt, type ping <Default gateway> and press Enter . For example, type ping 192.168.1.1 and press Enter . The result should be something like this: Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 5ms, Average = 4ms

If the ping is successful and you see results similar to the results above, but you can’t connect to the Internet on your PC, there may be a problem with your modem or Internet service provider (ISP).

Check your network adapter

If you’re still having trouble connecting to a network, it might be related to your network adapter.

Try using the Network Adapter troubleshooter to automatically find and fix some problems. This troubleshooter will disable and re-enable the adapter, and try some other common repairs.  Select the Start  button, start typing Troubleshooting , and then select Troubleshooting in the list. Select View all  >  Network Adapter .

Update the network adapter driver. An outdated or incompatible network adapter driver can cause connection problems. Check to see if an updated driver is available.

Select the Start  button, start typing Device Manager , and then select it in the list.

In Device Manager, select  Network adapters , right-click your adapter, and then select Properties .

Select the Driver tab, and then select Update Driver .

Select Search automatically for updated driver software .

If Windows can’t find a new driver for your network adapter, visit the PC manufacturer’s website and download the latest network adapter driver from there. If your PC can't connect to the Internet, you'll need to download a driver on a different PC and save it to a USB flash drive so you can install the driver on your PC. You’ll need to know the PC manufacturer and model name or number.

Other steps to try on your router

Here are some things to check and try with your router if you’re at home and having trouble getting connected.

If you don't see the network name, sign in to your router and check to see if it’s set to broadcast the network name.

Connect your PC to your router using an Ethernet cable.

Open your web browser and type the IP address for your wireless router. (For example, 192.168.1.1 or 172.16.0.0—check the documentation for your router to find the default IP address.)

Sign in with your user name and password, then make sure an option labeled Enable SSID Broadcast , Wireless SSID broadcast , or something similar is turned on. This setting is often on a Wireless Settings page.

Check to see if your Wi-Fi network uses Media Access Control (MAC) address filtering for security. If it does, you’ll need to add the MAC address for your PC to the access list on your router before you can connect.

Select the Start   button. Start typing cmd  and right-click Command Prompt in the list. Select Run as Administrator , and then select Yes .

At the command prompt, type ipconfig /all . Write down the address that appears next to  Physical Address for your wireless network adapter. This is the address you’ll need to add to the access list on your router.

To add the MAC address to the access list on your router:

Sign in with your user name and password, then look for a setting that says MAC Address Filter or something similar.

Add the MAC address you wrote down for your PC to the access list and save your changes.

On your PC, try to connect to the Wi-Fi network again.

Look in the  Wireless Network  section. If Wi-Fi is on, the button should say  Turn wireless off .

Check and make sure your PC isn’t in airplane mode.

Select  Add , and then select  Manually create a network profile .

Type the network information.

If you want Windows to automatically connect when the network is in range, select the  Start this connection automatically  check box.

Select the  Connect even if the network is not broadcasting  check box, select  Next , and then select  Close .

Open the Network troubleshooter by right-clicking the network icon in the notification area and then selecting  Troubleshoot problems .

Need more help?

Want more options.

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders

Find solutions to common problems or get help from a support agent.

Online support

Was this information helpful?

Thank you for your feedback.

• PRO Courses Guides New Tech Help Pro Expert Videos About wikiHow Pro Upgrade Sign In
• EXPLORE Tech Help Pro About Us Random Article Quizzes Request a New Article Community Dashboard This Or That Game Popular Categories Arts and Entertainment Artwork Books Movies Computers and Electronics Computers Phone Skills Technology Hacks Health Men's Health Mental Health Women's Health Relationships Dating Love Relationship Issues Hobbies and Crafts Crafts Drawing Games Education & Communication Communication Skills Personal Development Studying Personal Care and Style Fashion Hair Care Personal Hygiene Youth Personal Care School Stuff Dating All Categories Arts and Entertainment Finance and Business Home and Garden Relationship Quizzes Cars & Other Vehicles Food and Entertaining Personal Care and Style Sports and Fitness Computers and Electronics Health Pets and Animals Travel Education & Communication Hobbies and Crafts Philosophy and Religion Work World Family Life Holidays and Traditions Relationships Youth
• Browse Articles
• Learn Something New
• Quizzes Hot
• This Or That Game New
• Train Your Brain
• Explore More
• Support wikiHow
• About wikiHow
• Log in / Sign up
• Computers and Electronics
• Computer Networking

How to Fix Common Computer Network Issues

Last Updated: December 30, 2022 References

This article was written by Luigi Oppido and by wikiHow staff writer, Travis Boylls . Luigi Oppido is the Owner and Operator of Pleasure Point Computers in Santa Cruz, California. Luigi has over 25 years of experience in general computer repair, data recovery, virus removal, and upgrades. He is also the host of the Computer Man Show! broadcasted on KSQD covering central California for over two years. This article has been viewed 339,167 times.

Computer networks equip computers and other electronic devices to exchange data. These networks allow you to connect to the internet, send emails, print wirelessly, and share files. If you are experiencing problems connecting to a computer network, you can try to fix, bypass, or troubleshoot common issues yourself before consulting a tech expert. This wikiHow teaches you how to diagnose basic network issues.

General Troubleshooting

• Windows: In the task bar in the lower-left corner.
• Mac . In the menu bar in the upper-right corner.
• Smartphones and Tablets: In the upper-right corner of the screen.

• The lights on your router may be different from one router make and model to the next. If you are confused as to what the lights mean, check your user's manual or manufacturer's web page for more information.

• If the range or your wireless internet is a problem, you can expand your network using a second wireless router or you can purchase a wireless mesh system to expand the range of your wireless network.

• One last simple fix can be reverting your router back to factory settings.

• Click the Windows Start menu.
• Click the Settings menu/Gear icon.
• Click Network and Internet .
• Click Change adapter options .
• Click your internet connection.
• Click Diagnose this connection .

• Click Network and Internet
• Right-click on the connection and then select Properties .
• Locate the Networking tab and click Configure .
• Click the Power Management tab.
• Uncheck the box next to “Allow the computer to turn off this device to save power.”

• Type "Device Manager" and click the Device Manager icon.
• Double-click Network Adapters .
• Right-click a network adapter.
• Click Update Driver .
• Click Search automatically for updated driver software .

• Click the Windows Start icon
• Type “cmd” into the search box.
• Right-click on the Command Prompt icon and click Run as Administrator .
• Type the following into the text box: "netsh interface TCP set global autotuninglevel=disabled".
• Hit the Enter key.
• Restart your computer. [2] X Research source

• Click the Windows Start icon.
• Click Network and Sharing Center .
• Click Change Advanced Sharing settings:
• Click Turn on Network Discovery .
• Click Turn on file and printer sharing .
• Click Save changes .

• Scroll down and click All Networks .
• Click Turn off password protected sharing .

• Click Windows Start"
• Right-click on the Command Prompt icon and select Run as Administrator .
• Type “ipconfig/flushdns” in the command prompt.
• Press Enter .

• Click on the WiFi icon in the top left corner of your screen.
• Click on Open Network Preferences .
• Click Advanced .
• Check the box next to “Remember networks this computer has joined."

• Click on the Apple icon in the upper-left corner.
• Click System Preferences .
• Click on the Network icon that resembles a globe.
• Scroll through your list of Networks until you find your 5 GHz network.
• Click on this network and drag it to the top of the list.

• Click Advanced . def
• Select your network from the list and then open the “DNS” tab.
• Click on the “+” icon under the “DNS Servers” column.
• OpenDNS: 208.67.222.222 or 208.67.220.220.
• Google DNS: 8.8.8.8 or 8.8.4.4.
• Click Apply .

• Click the Apple icon .
• Click System Preferences
• Click Sharing
• Check Media Sharing .
• Enter your Apple ID password.
• Launch iTunes .
• Enter your Apple ID and password.
• Click Home Sharing .
• Turn on Home Sharing .

Community Q&A

• Always start troubleshooting with simple things. Almost 50% of connection issues are due to loose cable or router needing a hard boot or few setting changes Thanks Helpful 0 Not Helpful 0
• Always make sure your router is on and connected properly. Thanks Helpful 0 Not Helpful 0
• Always call your ISP before going to any advanced stuff, if you forgot to pay the bill or your ISP has some connection issues, you won't be able to fix the issue in ways mentioned in this guide. Thanks Helpful 0 Not Helpful 0

• The solutions presented in this article will not work for all issues, and when in doubt do not be afraid to ask. Thanks Helpful 0 Not Helpful 0

You Might Also Like

• ↑ http://windows.microsoft.com/en-us/windows-vista/troubleshoot-network-connection-problems
• ↑ http://www.speedguide.net/faq/how-to-disable-windows-vista-tcpip-auto-tuning-247
• ↑ https://support.apple.com/en-us/HT201735
• ↑ http://www.macworld.com/article/2824564/slow-internet-edit-your-dns-settings.html
• ↑ https://support.apple.com/en-us/HT202190

About This Article

1. Make sure Wi-Fi is turned on on your devices. 2. Make sure you have a strong Wi-Fi connection. 3. Check multiple websites and apps to make sure none of them are connecting. 4. Make sure the Internet light on your modem or router is glowing solid white or green. 5. Make sure your internet cable is firmly attached to your modem or router. 6. Restart your modem and/or router by unplugging them and then plugging them back in. 7. Restart all your internet-connected devices. 8. Use a wired connection. 9. Try again later. 10. Contact your internet service provider. Did this summary help you? Yes No

• Send fan mail to authors

Reader Success Stories

Rajendra Mundkur

Aug 6, 2016

Is this article up to date?

Featured Articles

Trending Articles

Watch Articles

• Terms of Use
• Privacy Policy
• Do Not Sell or Share My Info
• Not Selling Info

Keep up with tech in just 5 minutes a week!

Basic Network Troubleshooting: A Complete Guide

The basics of network troubleshooting have not changed much over the years. When you’re network troubleshooting, a lot can be required to solve the problem. You could be solving many different issues across several different systems on your complex, hybrid network infrastructure. A network observability solution can help speed up and simplify the process.

The Network is the Key

“The network is down!” — I’m sure you heard that before.

Despite your best efforts as a network engineer, network failures happen, and you have to fix them. Hopefully, you’ve implemented a network observability platform in advance, so you should be collecting a wealth of information about your network, making troubleshooting easier.

But what happens when it’s time to activate troubleshooting mode?

In this post, I’m going to talk about the steps to troubleshoot your network. And then I’ll provide some best practices, as well as provide examples of troubleshooting with Kentik’s network observability solutions.

What is Network Troubleshooting?

Network troubleshooting is the process of solving problems that are occurring on your network, using a methodical approach. A simple definition for what can often be a hard task!

When users complain, whether they’re internal or external to your organization — or ideally, before they do — you need to figure out what the cause of their problem is. The goal is to troubleshoot and fix whatever issue underlies the problems.

Troubleshooting requires taking a methodical approach to resolving the issue as quickly as possible. Unfortunately for you, the user doesn’t care what your service-level objective for fixing the problem is. In today’s “gotta have it fast” culture, more often than not, you need to fix it now — or revenue is affected.

Let’s get into some ways you can troubleshoot your network and reduce your mean time to repair (MTTR).

Basic Network Troubleshooting Processes

Identify the problem.

When you’re troubleshooting network issues , complexity and interdependency make it complex to track down the problem. You could be solving many different issues across several different networks and planes (underlay and overlay) in a complex, hybrid network infrastructure.

The first thing you want to do is identify the problem you’re dealing with. Here are some typical network-related problems:

• A configuration change broke something . On a network, configuration settings are constantly changing. Unfortunately, configuration change accidents can happen that bring down parts of the network.
• Interface dropping packets . Interface issues caused by misconfigurations, errors, or queue limits lead to network traffic failing to reach its destination. Packets simply get dropped.
• Physics limitations on connectivity . Sometimes, your connections don’t have enough bandwidth. Or the latency is too much between source and destination. These lead to network congestion, slowness, or timeouts.
• Problems in the cloud . Intra- or inter-cloud connectivity problems can have their own unique set of causes and challenges. Often driven by someone else’s congestion, oversubscription, or software failures.

Find Your Network Troubleshooting Tools

Fixing these kinds of troubleshooting problems needs more than identification. To paraphrase French biologist Louis Pasteur — where observation is concerned, chance favors only the prepared mind.

No network engineer can troubleshoot without being prepared with their tools and telemetry. So once you’ve identified that there is a problem, it’s time to use your network troubleshooting tools.

Ideally, you have tools and telemetry in advance, so your network observability toolchain is using AI to automatically identify problems and linking you to a jumping off point so you can drive down both MTTK (Mean Time to Know) and either MTTR (Mean Time to Repair) or MTTI (Mean Time to Innocence).

Here are a few examples of basic network troubleshooting tools:

• Tracert/ Trace Route
• Ipconfig/ ifconfig
• Pathping/MTR

The First Step — Ping Affected Systems

When your network is down, slow, or suffers from some other problem, your first job is to send packets across the network to validate the complaint. Send these pings using the Internet Control Message Protocol (ICMP) or TCP to one or any of the network devices you believe to be involved.

The ping tool is a utility that’s available on practically every system, be it a desktop, server, router, or switch.

There’s a sports analogy that says “the most important ability is availability” for systems. If you can’t reach it, it’s not available to your users.

Sending some ICMP packets across the network, especially from your users’ side, will help answer that question, if your platform isn’t presenting the path to you automatically. In some cases if ICMP is filtered, you can usually switch to TCP (Transmission Control Protocol) and use tcping, telnet, or another TCP-based method to check for reachability.

Get the Path with Traceroute

If you’re not getting any ping responses, you need to find out where the ping is stopping. You can use another ICMP-based tool to help, and that’s traceroute.

Your ping could be getting stopped because ICMP isn’t allowed on your network or by a specific device. If that’s the case, you should consider TCP Traceroute on Linux, which switches to TCP packets.

From traceroute, since you will see the path of IP-enabled devices your packets take, you will also see where the packets stop and get dropped. Once you have that, you can further investigate why this packet loss is happening. Could it be a misconfiguration issue such as a misconfiguration of IP addresses or subnet mask? A misapplied access list?

Test Your Network with Synthetic Monitoring

Tool such as Kentik Synthetic Monitoring enable you to continuously test network performance (via ICMP, TCP, HTTP, and other tests) so you can uncover and solve network issues before they impact customer experience. Ping and traceroute tests performed continuously with public and/or private agents generate key metrics (latency, jitter, and loss) that are evaluated for network health and performance.

To get ahead of the game, Kentik also allows you to set up autonomous tests, so there’s already test history to your top services and destinations. You can also run these continuously (every second, like the ping command default) for high resolution.

Device Commands and Database Logs

Now that you’ve identified the network device or group of devices that could be the culprit, log into those devices and take a look. Run commands based on your device’s network operating system to see some of the configuration.

Take a look at the running configuration to see what interfaces are configured to get to the destination. You can take a look at system logs that the device has kept for any routing or forwarding errors. You can also look at antivirus logs on the destination systems that could be blocking access.

At this point, you may find yourself unable to get enough detail about the problem. Command line tools are telling you how things should work. What if everything’s working the way it should? What now? Or you might be getting overwhelmed by the amount of log data.

Device Configuration Changes

Many network outages relate to changes that humans made! Another key step on the troubleshooting path is to see if anything changed at about the same time as issues started.

This information can be found in logs of AAA (Authentication, Authorization, and Accounting) events from your devices. Ideally stored centrally, but often also visible by examining the on-device event log history.

Packets and Flows

The old saying about packet captures is that packets don’t lie! That’s also true for flow data, which summarizes packets.

Both packets and flows provide information about the source and destination IP addresses, ports, and protocols.

When getting flow data, you’re not as in the weeds as during a packet capture, but it’s good enough for most operational troubleshooting. Whether it’s with NetFlow, sFlow, or IPFIX , you’ll be able to see who’s talking to whom and how with flow data going to a flow collector for analysis.

Capturing packet data is truly getting into the weeds of troubleshooting your network. If it’s unclear from flow, and often if it’s a router or other system bug, you may need to go to the packets.

Unless you have expensive collection infrastructure, it’s also often more time consuming for you than any of the other tools above. Whether it’s tcpdump, Wireshark, or SPAN port, you’ll be able to get needle-in-the-haystack data with packet captures.

One great middle ground is augmented flow data, which captures many of the elements of packets. This can be great if you can get performance data, but not all network devices can watch performance and embed in flow — in fact, the higher speed the device, the less likely it is to support this kind of enhancement.

Collecting and analyzing packets and flows is where you start to venture into the next step. You’re using a mix of utility tools (tcpdump) and software (Wireshark, flow collector). If you’re expecting to keep a low MTTR, you need to move up the stack to software systems.

Up the Stack

If you can’t find issues using these tools and techniques at the network level, you may need to peek up the stack because it could be an application, compute, or storage issue. We’ll cover more on this cross-stack debugging in a future troubleshooting overview.

Kentik Network Observability

Of course, network performance monitoring (NPM) and network observability solutions such as Kentik can greatly help avoid network downtime, detect network performance issues before they critically impact end-users, and track down the root cause of network problems

In today’s complex and rapidly changing network environments, it’s essential to go beyond reactive troubleshooting and embrace a proactive approach to maintaining your network. Network monitoring and proactive troubleshooting can help identify potential issues early on and prevent them from escalating into more severe problems that impact end users or cause downtime.

Kentik’s Network Observability solutions, including the Network Explorer and Data Explorer, can be invaluable tools in implementing proactive troubleshooting strategies. By providing real-time and historical network telemetry data and easy-to-use visualization and analysis tools, Kentik enables you to stay ahead of potential network issues and maintain high-performing, reliable, and secure network infrastructure.

Network Explorer Solution

Kentik Network Explorer provides an overview of the network with organized, pre-built views of activity and utilization, a Network Map, and other ways to browse your network, including the devices, peers, and interesting patterns that Kentik finds in the traffic.

To make NetOps teams more efficient, Kentik provides troubleshooting and capacity management workflows. These are some of the most basic tasks required to operate today’s complex networks, which span data center, WAN, LAN, hybrid and multi-cloud infrastructures.

The Network Explorer combines flow, routing, performance, and device metrics to build the map and let you easily navigate. And everything is linked to Data Explorer if you need to really turn the query knobs to zoom way in.

Data Explorer Solution

If you can’t find the obvious issue with something unreachable or down, it’s key to look beyond the high level and into the details of your network.

Kentik Data Explorer provides a fast, network-centric, easy-to-use interface to query real-time and historic network telemetry data. Select from dozens of dimensions or metrics, 13 different visualizations and any data sources. Set time ranges and search 45 days or more of retained data. Query results within seconds for most searches.

This lets you see traffic, routing, performance, and device metrics in total, by device, region, customer, application, or any combination of dimensions and filters that you need to zoom in and find underlying issues.

Kentik’s Data Explorer provides graphs or table views of network telemetry useful for all types of troubleshooting tasks.

Software Tools Help Facilitate Network Troubleshooting

Marc Andreessen of Netscape fame once said that, “software is eating the world.” But software has made things a lot easier when it comes to network troubleshooting. It has taken over from the manual tools run from a terminal or network device.

There are software tools that ping not just to one device but multiple devices simultaneously for availability and path. Many are flow and packet data stores with software agents sending network data. All this is done and put on a nice dashboard for you. Network troubleshooting is still hard, but software makes it easier.

However, in this cloud-native and multi-cloud infrastructure era, some software makes it easier than others. For that, you need to move beyond traditional monitoring software because it’s not enough anymore. You need to move to observability software.

With software tools like products from Kentik, you can use the devices to send data to observe the state of your network instead of pulling it from the network.

Network Troubleshooting Best Practices

Whether you’re using network observability tools, or have a network small enough where the other tools are sufficient, here are some best practices you should consider.

Develop a Checklist

You should develop a checklist of steps like what I’ve outlined above when troubleshooting.

In his book The Checklist Manifesto , Dr. Atul Gawande discusses how checklists are used by surgeons, pilots, and other high-stress professionals to help them avoid mistakes. Having a checklist to ensure that you go through your troubleshooting steps promptly and correctly can save your users big headaches. And save you some aggravation.

Over time, this checklist will likely become second nature, and having and following it ensures you’re always on top of your game.

Ready Your Software Tools

You want to have already picked the network troubleshooting tools you need to troubleshoot a network problem before you get an emergency call. That isn’t the time to research the best software tool to use. By then, it’s too late.

If you run into a network troubleshooting problem that took longer than you hoped with one tool, research other tools for the next time. But do this before the next big problem comes along.

Get Documentation

It’s tough to jump on a network troubleshooting call and not know much about the network you’re going to, well, troubleshoot. IT organizations are notorious for not having enough documentation. At times, you know it’s because there aren’t enough of you to go around.

But you have to do what you can. Over time, you should compile what you learn about the network. Document it yourself if you have to, but have some information. Identify who owns what and what is where. Otherwise, you could spend lots of troubleshooting time asking basic questions.

Prepare Your Telemetry

In addition to having the software to move with speed, you’ll need to be already sending, saving, and ideally detecting anomalies over your network telemetry. For more details on network telemetry, see our blog posts “The Network Also Needs to be Observable” and “Part 2: Network Telemetry Sources” .

Follow the OSI

If you closely follow the toolset above, you may have noticed that I’m moving up the stack with each tool.

In some ways, I’m following the Open Systems Interconnection (OSI) stack. When troubleshooting, you want to start at the physical layer and work your way up. If you start by looking at the application, you’ll be masking potential physical connection problems such as interface errors or routing issues happening at layer 3. Or any forwarding problems at layer 2.

So follow the stack, and it won’t steer you wrong.

Preparedness and Network Troubleshooting

And there it is. When the network is down, troubleshooting can be a daunting task, especially in today’s hybrid infrastructure environments .

But if you follow the steps I’ve outlined, you can make things easier on yourself. Create your network troubleshooting checklist, decide on your toolset, and get ready. If it’s not down now, the network will likely be down later today.

Now that you know this about network troubleshooting, you’ll be ready when the network issues affect traffic in the middle of the night. You won’t like it; nobody likes those 1:00 A.M. calls. But you’ll be prepared.

Explore more from Kentik

• Multi-Cloud Observability
• SD-WAN Monitoring
• Network Performance Monitoring
• Network Security and Compliance
• Synthetic Monitoring
• Peering and Interconnection
• Subscriber Intelligence
• AI-Driven Insights
• Network Telemetry
• Universal Data Explorer
• Observability Data Pipeline
• Integrations
• Kentik Data Engine
• Reduce Cloud Spend
• Migrate To and From Any Cloud
• Improve Cloud Performance
• Optimize Enterprise WAN
• Improve Infrastructure Reliability
• Deliver Exceptional Digital Experiences
• Detect and Mitigate DDoS
• Harden Zero-Trust Cloud Network Policy
• Investigate Security Incidents
• Visualize All Cloud and Network Traffic
• Troubleshoot Any Network
• Understand Internet Performance
• Consolidate Legacy Tools
• Optimize Peering and Transit
• Plan Network Capacity
• Google Cloud

New and Notable

• Introducing Kentik Kube: Revolutionizing Kubernetes Network Observability
• The Ultimate Guide to Network Observability
• Box Achieves Google Cloud Migration Success with Kentik
• Case Studies
• Resource Library
• Telemetry Now Podcast
• Kentik Network Analysis Center
• Product Updates
• Documentation
• Plans and Pricing
• Kentik Slack Community
• Privacy Policy
• Terms of Use

The Complete Windows Network Troubleshooting Guide

Got an internet or network issues? We'll guide you through your network setup and show you simple troubleshooting techniques to find and fix the problem.

When you have internet or network issues, it may feel like a regression back to the stone age. Let's try and understand networks and look at some troubleshooting techniques to bring you back into the world of the living.

In this guide: An Introduction to Networks | Network Troubleshooting

An Introduction to Networks

In this section: Network Diagrams | Internet Protocol Address and Hostname | DHCP | Domain Name System | Mbps vs. MBps | Wired Networks | Wireless Networks | Wireless Settings for Best Results | Guest Network | Consolidation | Drawing Your Own Network

Network Diagrams

Here's what your network setup may look like.

The above diagrams are basic representations of what a typical home network consists of. There are typically two cases. The first case is a central device acting as the modem, router, switch and wireless access point. The second diagram shows another case, where the roles are split into multiple devices.

Each method has pros and cons. Having a single device is much easier to set up, but there is a single point of failure. Having different devices is the method most larger companies choose. While setup can get extremely complicated, it's far more scalable. Let's take a look at some of the services that a network requires to function.

Internet Protocol (IP) Address and Hostname

An IP address is an identifying number for a piece of network hardware. Having an IP address allows a device to communicate with other devices over an IP-based network like the internet. Each device on a network must have a unique IP.

The most common form of IP we see today is IP version 4 (IPv4). IPv4 is comprised of four sets of numbers, between 0 and 255, separated by a decimal point. Example IPv4 addresses looks like:

• 192.168.0.254
• 172.16.254.6

A hostname should be more human readable. All devices on your network should also have a unique hostname. Having multiples devices on your network with the same hostname can cause a network malfunction. You can view your computer's hostname by right-clicking on My Computer / This PC > Properties .

Clicking on the Change Settings link, will allow you to set a custom name for your PC.

Just ensure all devices on your home network have a unique name and IP address and you should be golden.

The Dynamic Host Configuration Protocol (DHCP) is a protocol where some network information is exchanged between a client and a server. In a home network, this is a role that is covered by the router.

In a home network always ensure that there is only one DHCP server. DHCP provides information such as IP address, Subnet Mask, Gateway and Domain Name Service (DNS).

The DHCP server keeps a list of which device is leasing which IP address. This ensures that no two devices will get assigned the same IP. Having two devices on your network with the same IP can cause one or both of them to malfunction. To view your current network settings go to Control Panel > Network And Sharing Centre > [Connection] > Details . A shortcut to getting to the control panel:

• WinKey + R on your keyboard. Or you could open the start menu and type Run .
• Now enter control in the Run Command box followed by the Return key .

The relevant information here is:

• DHCP enabled: should be Yes
• Address: this device's IP
• Subnet Mask: this devices subnet mask
• Default Gateway: should be your router's address
• DHCP Server: should be your router's address
• DNS Servers: should be your router's address

The numbers that you will see will be slightly different. Generally speaking, routers default to one of the following addresses:

• 192.168.0.1
• 192.168.1.1

All other devices on your network will only have the last number incremented. Our example diagram has the router at the address 10.0.0.1 and the other devices starting at 10.0.0.20. It is a good idea to reserve a few IP addresses for devices you would like to assign static IPs to. These can include the router, some servers, or even certain workstations.

Domain Name System (DNS)

If everything was addressed by their IP address, life would be challenging. Is it easier to remember 216.58.212.78 or Google.com? A DNS server is the device that translates the www.google.com you type in your browser to the 216.58.212.78 IP address that it really is. You can try this by typing the IP address in your browser window, and Google should pop up!

In a home network, your router acts as a DNS server, translating hostnames to IP addresses. If you need to access another device on your network, your router has a database of everyone that is on the network and will translate a computer's hostname to an IP. If you need to access a device on the internet, your router will forward the request to another DNS server on the internet and send the reply to the device that requested it.

In most cases, two DNS servers, a primary and a secondary server, are automatically configured on your router and/or computer when connecting to your Internet Service Provider (ISP) via DHCP. You can configure two DNS servers in case one of them happens to fail, after which the device will resort to using the secondary server.

While many DNS servers are operated by ISPs and intended to be used only by their customers, several public-access ones are also available. Generally speaking, your primary DNS server should be your router.

Mbps vs. MBps

Megabits Per Second (Mbps) is not the same as Megabytes Per Second (MBps). It takes 8 Megabits to equal 1 Megabyte. You will generally see Mbps when network speed is being referenced, and MBps indicates the amount of file data transferred per second. When an ISP advertises network speed , it's always in Megabits. This might be slightly confusing so let's take an example.

If you want to download a short video, and the file size is 10 MB (Megabytes). Your internet connection gives you download speeds up to 16 Mbps. First, convert your Mbps into MBps by dividing 16 by 8 which equals 2MBps. Now divide the file size (10MB) by your MBps (2) to get the amount of time it will take to download the file. 10MB / 2MBps = 5 seconds. It will take approximately 5 seconds to download your 10MB file with an internet connection of 16Mbps.

Wired Networks

Wired networks have been around since the 1980s. They are currently faster, more stable and less susceptible to attacks compared to wireless networks. Some notation for wired networks you will come across are 10/100/1000, and 10 GbE.

10/100/1000 means that device can support 10Mbps, 100Mbps or 1,000Mbps. 10 GbE just means 10 Gigabit Ethernet. The vast majority of consumer devices will come standard with 1 GbE . For now, this is sufficient as 10 GbE is relatively much more expensive. This is guaranteed to change shortly as our data demands and internet speeds increase over time. As technology is adopted by the wider market, it also becomes cheaper to manufacture.

You can view what network adapter your computer has from the Windows Device Manager window. In the Run Command dialog box type devmgmt.msc followed by the return key.

If you expand the Network adapters, you should see what Network Interface Card (NIC) your computer is sporting. To see what your network speed is you can go to Control Panel > Network And Sharing Centre > [Connection] . The best practice in a home network setup is to have all your wired devices connected to the same network switch to avoid any bottlenecks when communicating with each other.

Wireless Networks

Wireless networks are the most convenient but are slightly more complex to configure and manage. They are also susceptible to interference from other wireless radios and other electrical and electronic hardware. Wireless networking can be a little tricky to understand, but we can try to demystify it's terrible naming conventions.

Wireless Fidelity (Wi-Fi) is governed by a set of standards which you will commonly see as 802.11g, 802.11n, and 802.11ac or something similar. The character on the end will indicate the theoretical max speed. The problem is is that these theoretical speeds are nonsense, and in real-world scenarios, you never get close to the theoretical speeds.

One of the contributing factors in never reaching the theoretical speeds is the antennas. 802.11ac can support up to eight antennas each running at over 400Mbps each. You may have seen some of these routers that resemble Lord Sauron himself such as the ASUS ROG GT-AC5300. While such devices adorn eight antennas, the device being used to connect to them will almost certainly not have that many. Your typical smart device may only have two or three antennas which makes it a bottleneck for the theoretical speed.

802.11ac only works on the 5GHz frequency while 802.11n supports both 5GHz and 2.4GHz. The key difference between the two frequencies is coverage versus bandwidth. 2.4GHz is much more capable at long range but cannot compete with the speed of the 5GHz network.

Wireless Settings for Best Results

When you first received your wireless router, chances have you probably changed the administrator login password and chose a cool name for your Wi-Fi . The other settings may have been ignored in the overly complicated dashboard. It's probably best not to try and tweak every little setting like a mad scientist, but there are a few settings that could enhance your Wi-Fi experience.

Regarding security, I strongly recommend using the WPA2/PSK mode and choosing AES as the encryption. Other options are just less secure. Under no circumstances should WEP be used as it can be easily hacked by a malintentioned individual armed with a laptop lurking outside your house.

Next, you should choose a channel. A channel is simply a slice of the 2.4GHz or 5GHz band that your router is broadcasting on. Most modern day routers will choose a channel automatically. If you are getting slower than expected speeds, a congested channel may be the culprit, especially if you live in an apartment complex with lots of other Wi-Fi routers in the area.

You can grab the WiFi Analyzer app from the Microsoft Store, which will turn your PC into a wireless scanner. It will show you which channels are congested and even make a recommendation on which one to choose for best performance.

Lastly, ensure that the correct Wi-Fi standard is chosen. Most modern-day devices support 802.11n and 802.11ac, so ensure those are selected. If however, you have a legacy device, such as a Nintendo 3Ds that is not detecting your Wi-Fi, you may have to enable 802.11g.

Guest Network

If your router supports an option for a guest Wi-Fi network, it would be a great idea to enable it. Guest Wi-Fi networks can have different passwords, so you don't have to share your main Wi-Fi network password. The best part is that any device connected to the guest network will not have access to local computers or files on the main network.

Your router treats the guest network as a completely different LAN. You may even have options for throttling or setting limits on clients connected to the guest network, to ensure your friends are not hogging your lovely internet.

At a glance, these are some of the settings you could tweak. Overall, it would be a good idea to make a small change, then run a speed test to see how that has affected your Wi-Fi. Then try the same speed test in a different part of your house. If you're unsatisfied, make another single change, then run your speed tests again. Making too many changes at once may lead to being unable to isolate the problem area.

Consolidation

There is a lot going on when it comes to networking. The above is by no means exhaustive, but it should be enough to give you an understanding of what's happening under the hood.

The above diagram shows a flow example of how some of these services fit together.

• Your computer gets a network connection and starts looking for a device that is a DHCP server.
• The DHCP server will check that it has a free IP address and lease one to the client.
• A user will type in a web address like Google.com in a browser window.
• This address needs to be converted into an IP address that computers can understand; this is done via a DNS server.
• Once the DNS is resolved, the web page can be found, and a connection is opened up between the user's computer and the web server hosting the web page.

Drawing Your Own Network

If your network is quite complex, it may be a good idea to have it drawn out, to help troubleshoot any issues. There's a great tool over at draw.io that makes drawing anything technical super simple. It's also completely free!

Everything is entirely drag-and-drop, and the user interface is about as simple as it gets. Enter something you'd like in the search box and hit return. Once, you've found an item that you like, just drag and drop it onto the canvas. From there you can join items and just double-click either on them or on the canvas to name them.

Our diagrams in this article were done entirely on draw.io and can be very helpful even when planning out a new network or finding potential problems in an existing one.

Troubleshooting Your Network

In this section: Troubleshooting Methodology | Basic Diagnosis | Browser Issues | Area Outages | Intermediate Diagnosis | DNS | Advanced Diagnosis | Firewalls and Anti-Malware | Uninstalling the Network Adapter | Network Reset | Wired Ethernet Problems | Wired Hardware Faults | Resetting Your Router | Wi-Fi Problems

Troubleshooting Methodology

Have you come across the principle of Occam's Razor? In a nutshell, it states that the simplest answer, or the one with the least assumptions, is usually the correct one. This is often the case when looking at problems, especially when it comes to technology.

When diagnosing network issues, it is extremely rare for the problem to be a hardware one. It's not unheard of, but NICs, switches, and routers are much less likely to be the problem relative to some silly software setting.

Once you've drawn out your network, and applied some of the recommendations above, it will be easy to get to the bottom of any network issues you may have. The best way of going about networking issues is using the process of elimination. As mentioned above, making too many changes at once can make diagnosing a problem much more difficult.

You can use this guide as a top-down approach. The guide starts with suggestions on what to try first before moving to the next step. If at some point you notice the behavior is unexpected, there is a possibility that your problem is at that point. Bearing these principles in mind let's get to the bottom of it!

Basic Diagnosis

Oh no! That fateful day where you open a browser window and nothing loads. If you're the IT person in the family, this is sometimes followed by "Sam! The Wi-Fi isn't working!" or some similar bellowing. Now, before things begin to get a little heated, there is a good chance you can solve this in a few seconds.

Our basic flow goes like this:

• Restart the device.
• Restart the router and or modem.
• Disable and enable the network adapter.
• Try a different browser. If you're using Google Chrome, try Microsoft Edge.
• Try a different website.
• Try a different device that is on the same network. So if your device that can't connect is wired, try another device that is on the wired network.
• Check your area's network status.
• Try using a device that is on a different network. So if your device that can't connect is wired, try using a device that is on the wireless network.

To disable and enable an adapter go to Control Panel > Network and Sharing Center > Change adapter settings . Right-click on your network connection and select Disable . The adapter will turn grey, and after a few seconds, you can right-click on the device and select Enable .

As you can see, using the process of elimination, you can quickly get to the bottom of where the problem may lie. Restarting your devices will in most cases solve the issues.

Browser Issues

If a different website works, the website you initially tried to load may be down. If a different browser works, your initial browser may need its cache and residual files to be cleared .

This can be done in Chrome by going to Settings > More Tools > Clear browsing data . In the dialog box that pops us, select All time from the Time range selection. Under the Advanced tab select Hosted app data , and finally, click the Clear Data button.

This will require you to sign in to any websites you were previously signed into and clear your browsing history. Ensure that any sites you need to refer back to are bookmarked.

Area Outages

Depending on where you live and who your ISP is this is generally uncommon but not unheard of. There is a website which has an awesome community that reports if there is a fault with common internet services, namely Downdetector .

Using Downdetector, you can check the status of your ISP network according to what other people are reporting. If you see that many people are reporting an issue, there might be a problem with your ISP.

You can also use the Live Outage Map to make sure whether or not your specific area is affected. If you still suspect an area outage, you could check with your neighbors and finally call your ISP to make sure everything is dandy in your area.

Intermediate Diagnosis

If all of the above hasn't worked, it will now require further diagnosis. Our flow goes like this:

• Check IP Settings.
• Can you ping your router?
• Can you ping a website?

You can check your IP settings, as shown above by going to Control Panel > Network And Sharing Centre > [Connection] > Details . Alternatively, open a command prompt by typing cmd into the run dialog box, and type this command:

If you notice that the IP address looks like the image above, your device is having a problem getting its IP settings from the DHCP server. If your IP settings look fine, you should try a ping. A ping is a utility used to check the reachability of a device via its IP address or hostname. It can also provide insight as to whether DNS is working and how long it is taking for a device to respond. Our flow shows trying to ping the router first, so in your command prompt type:

If you see a constant response, like the one above, your connection between your device and your router is perfect. If your ping looks something similar to this:

In the above case, there is a problem between your device and the router. If your local ping is fine, try pinging a website on the internet. There are two things that happen with a ping to a website on the internet. Our sequence diagram above shows that a DNS server first has to resolve the hostname into an IP address. Once the name is resolved, the ping will begin. A healthy ping will show the IP address next to the website you're trying to ping like this:

A ping result like this might indicate that there is a DNS problem:

By default, your ISP will assign you a primary and a secondary DNS server. Your computer or smart device may only show the router being the primary device, but your router is just acting as an intermediary or a forwarder.

Changing the default assignment actually might have some benefits. These benefits may include better security and a faster browsing experience. Google's public DNS servers can be a viable option on which DNS server you should use.

Your router's DNS options are generally found under the DHCP settings, and you could set it to the Google public DNS as follows:

• Primary: 8.8.8.8
• Secondary: 8.8.4.4

Once these are set and saved on your router, you can refresh your device's IP settings for good measure. An easy way to do this without restarting is by running the following in a command prompt:

The above will first clear your cached DNS entries, then release and renew your IP settings.

Advanced Diagnosis

• Update the adapter driver.
• Roll back the network adapter driver.
• Temporarily turn off firewalls.
• Temporarily turn off anti-virus or anti-malware software.
• Uninstall the network adapter driver.
• Perform a network reset.

An outdated or incompatible network adapter driver can cause connection problems. If you recently upgraded to Windows 10, it's possible that the current driver was designed for a previous version of Windows. You can find all your PC components drivers under the Device Manager . There's a shortcut on how to get there in the Wired section above .

Right-click on the network adapter and select Update driver and select Search automatically for updated driver software .

While you may not have an internet connection, Windows may have a local updated driver. Restart your PC and check your network.

You can also go to your PC or motherboard manufacturers website and get the latest version of the driver. You will need another computer to do so and a USB drive to transfer the driver to your problem PC for installation.

It's possible a newly installed network driver is causing an issue, so you can roll the driver back .

In Device Manager, right-click the adapter and click on Properties . Under the Driver tab, look for the Roll Back Driver button. If the button is greyed out, there is no driver to roll back to. If you can click it, follow the steps and restart your PC, then check your network connection.

Firewalls and Anti-Malware

Sometimes, firewall software might prevent you from getting connected. You can see if the connection issue is caused by a firewall by turning it off temporarily and then trying to visit a website you trust.

The steps to turn off a firewall depend on the firewall software you're using. Check the documentation for your firewall software to learn how to turn it off. While disabling your firewall makes your PC vulnerable, doing it temporarily and visiting a site you trust should be okay. Make sure you turn it back on as soon as possible.

To turn the windows firewall off, search for Command prompt in the Start Menu , right-click it and select Run as administrator followed by Yes .

At the command prompt type:

Open a browser and visit a website you trust to see if your network is working. If it doesn't then your firewall is not causing the issue. To turn it back on, in the same command prompt type:

If you find the firewall software is causing the connection issues, contact the software vendor or visit their website to check and see if updated software is available. You could also check your firewall rules to make sure there is nothing blocking your network connection in there.

It's also possible that antivirus or anti-malware software is the root of your problem. Typically, you could pause protection by right-clicking the icon in the Taskbar and selecting Disable .

In Windows 10, you could check what security software you have installed. Type system and security in the Start Menu and select Review your computer's status and resolve issues.

Under the Security section, look for any third-party security software that's installed.

Uninstalling the Network Adapter

If the previous steps didn't work, try uninstalling the network adapter driver, and then restart your computer and have Windows automatically install the latest driver . Consider this approach if your network connection stopped working properly after a recent update.

To be safe, ensure you have drivers available as a backup. Visit the PC manufacturer's website and download the latest network adapter driver from there. You may have to do this on another PC and copy it to USB drive.

Right-click your adapter in the Device Manager and select Uninstall device . If there is a checkbox which shows Delete the driver software for this device select it and click Uninstall . Now restart your computer.

After your PC restarts, Windows will automatically look for and install the network adapter driver. Check to see if that fixes your connection problem. If Windows doesn't automatically install a driver, try to install the backup driver you saved before uninstalling.

Network Reset (Windows 10)

This option removes any network adapters you have installed and the settings for them. After your PC restarts, any network adapters are reinstalled, and the settings for them are set to the defaults.

Select the Start button, then select Settings > Network & internet > Status > Network reset . On the Network reset screen, select Reset now > Yes to confirm. Wait for your PC to restart and see if that fixes the problem.

Network reset might set each one of your known network connections to a public network profile. In a public network profile, your PC is not discoverable to other PCs and devices on the network. However, if your PC is part of a homegroup or used for file or printer sharing, you'll need to make your PC discoverable again by setting it to use a private network profile.

This can be done from the same menu. Depending on the type of network connection that you use. Ethernet will show you your current network connection which can be either your LAN cable connection or your Wi-Fi connection. Click on the connection name on the right under Ethernet. It should be the name of your LAN or Wi-Fi network. Check the switch Find devices and content .

Wired Ethernet Problems

If your problem device is on a wired ethernet connection and another device that is also on a wired connection works, you've narrowed it down to the wired connection being a problem.

Always start with the simplest solution first. After going through the basic, intermediate and advanced diagnosis above, start by eliminating possibilities. If your device is connected first to a switch, which is in turn connected to the router, try connecting your problem device directly to the router.

You should now have the shortest path between your problem device and the internet. Device > Router / Modem > Internet .

The last few troubleshooting steps you could try now is:

• Set a static IP.
• Use a different ethernet cable that you know is working.
• Try a USB to ethernet adapter.
• Try a different ethernet port on your router.
• Reset your router to factory settings.
• Try a different modem/router that you know is working.

To set a static IP, go to Control Panel > Network and Sharing Center > Change adapter settings . Right-click on your adapter and select Properties . Highlight the item which shows (TCP/IPv4) and click on Properties . Set the following items according to your network:

• IP address: an IP with the same first three numbers as your router, followed by an arbitrarily number that is unlikely to be used by another device on your network. This must be between 0 and 255.
• Subnet mask: this is typically 255.255.255.0
• Default gateway: IP address of your router, typically ends in .1
• Preferred DNS server: IP address of your router
• Alternate DNS server: a public DNS server like 8.8.8.8

If at this point your internet starts working there may be an issue with your DHCP server as it is not issuing the correct IP settings.

Wired Hardware Faults

The final steps will be testing the hardware to find the fault. You can grab a USB to ethernet adapter which is relatively inexpensive. If that works, your PC's ethernet adapter may be faulty. If your PC's ethernet adapter is onboard, that might raise concerns for the health of your motherboard.

Getting your hands on another modem/router might be slightly tricky. Your ISP may require a specific modem, but you will be spoilt for choice when it comes to a router. Try and borrow one temporarily and swap yours out to see if it makes a difference.

Resetting Your Router

Resetting your router to its factory settings needs some consideration. Note that your Wi-Fi, DHCP, and other settings will all be back to their default settings. This might be a good thing. It's possible one of the settings you've tweaked has caused your network to be malfunctioning.

The method of resetting your router will depend on the model and manufacturer. In general, there will be a little reset button on the back that needs to be pressed using a pin. Refer to your manufacturers manual for further information.

Some routers will allow a backup and restore of settings, but doing so might restore a setting that's causing your network woes!

Wi-Fi Problems

Wi-Fi can be tricky to troubleshoot because of the added variables in the equation. You have to eliminate interference from other devices, and there are more settings to take into account.

After you've configured your Wi-Fi with some of the suggestions above, and gone through the basic, intermediate and advanced diagnosis, we can start our elimination process. To eliminate interference issues sit as close as possible to the access point/router. If your internet works when you're close to your router but doesn't when you're far away, you may want to consider extending your wifi network.

• Forget and reconnect to your network.
• Try a different Wi-Fi network.
• Try a USB Wi-Fi Adapter.

To forget your Wi-Fi network go to Control Panel > Network and Sharing Center and click Manage wireless networks . Right-click the connection you'd like to forget and click Remove network . You can try reconnecting to the removed network as normal.

Setting a static IP is the same as it's done on wired. To quickly try another Wi-Fi network, use your smart device as a hotspot. USB Wi-Fi adapters are also quite inexpensive.

Are Your Network Issues Resolved?

We've summarized all the steps in this interactive checklist which you can use on your PC or print out and step through. Remember our methodology on trying the simplest solutions before moving on to more advanced steps.

What is your ideal network setup? How often do you have troublesome network issues? Let us know in the comments below.

• Skip to content
• Skip to search
• Skip to footer

What Is Network Troubleshooting?

Network troubleshooting is the act of discovering and correcting problems with connectivity, performance, security, and other aspects of networks.

• See how it works (1:14)
• Explore Cisco Catalyst Center

Contact Cisco

• Get a call from Sales

Call Sales:

• 1-800-553-6387
• US/CAN | 5am-5pm PT
• Product / Technical Support
• Training & Certification

What's the value of network troubleshooting?

Fast, effective network troubleshooting is a cornerstone of business resilience. Today's networks perform more mission-critical business tasks than ever. Without robust troubleshooting and speedy resolution of issues, networks can suffer costly downtime.

The cost of downtime includes reduced productivity and the economic impacts of disrupted or underperforming services, data breaches, and malware. These consequences can result in steep costs and cause long-lasting damage to brands.

How do organizations handle troubleshooting?

Of course, troubleshooting isn't just about resetting user passwords or restarting devices. Especially in large organizations, it's about a set of procedures, practices, and tools used to process numerous requests by a complex mix of users and dispersed network assets and infrastructure.

Typically, a large organization has an entire team devoted to network troubleshooting. The team's engineers address problems at various levels: Tier 1 for basic issues such as password resets, Tier 2 for issues that can't be resolved by Tier 1, and Tier 3 for mission-critical issues.

Frequently, Tier 1 troubleshooting is outsourced. An escalation framework is used to route requests efficiently and make sure that upper-level engineers are tasked appropriately.

In recent years, artificial intelligence (AI), machine learning (ML), and automation have been used to bridge skills gaps. These technologies offer guided remediation tools that empower Tier 1 engineers to solve complex network problems more rapidly.

Many organizations have separate network troubleshooting tools, but the addition of these tools may require training and management by IT departments. More commonly, network troubleshooting is embedded in a network management system (NMS).

How do NMSs relate to troubleshooting?

In large organizations, network troubleshooting teams are not simply waiting for users to report issues.

An NMS monitors networks continuously. It sends status updates—and alerts, when needed—on network key performance indicators (KPIs) such as connection speed, bandwidth, latency, users, and access.

The NMS performs monitoring by querying the various parts and nodes of the network to update status, at an interval determined by the IT team. Newer network elements, however, use telemetry to transmit their KPIs automatically.

An essential part of network troubleshooting is tracking and collecting data on network events. A system of IT service management (ITSM) tickets is used for this process. The data aggregated from the tickets can provide insights to identify problem areas and guide network optimization and upgrades.

Network events

An occurrence that triggers a network troubleshooting process is called an event. Some common events are described below.

Connection failures

Such events could be caused by cables and plugs that aren't connected properly.

Security lapses

These events could involve anything from a full-blown malware attack to an unapproved user's being able to connect to Wi-Fi.

KPIs missed

KPIs, when they're well-calibrated, can provide early warnings of network issues before they affect users.

Application failures

For locally hosted applications, a failure could mean an update that wasn't installed or the presence of an obsolete device.

Policy failures

Network performance can suffer when network policies, such as those for security, traffic management, and access control, inadvertently contradict each other.

Endpoint issues

Issues with endpoint connectivity, for example, could be caused by endpoints' lack of proximity to network routers, network interference problems, or issues with a remote worker's local network.

Troubleshooting processes

Once alerts or requests have been received and basic problems such as hardware connections and user connectivity have been ruled out, network troubleshooting typically involves one or more of the following steps.

IP-configuration checks

Problems with IP addresses cause many network issues. Often, assigning a new IP address can resolve an issue if a previous address was incorrect.

Ping and tracert testing

If the IP address is correct, the network issue may be upstream of a modem. To diagnose the problem further, IT teams can use the ping utility or the tracert command to test connections with remote servers and return information about the signal path.

A DNS check will determine whether there's a problem with a server to which networks are trying to connect. When an IT team performs a DNS check and receives results such as "Request timed out" or "No response from server," the problem might originate in the DNS server for the destination.

Service provider checks

Outages do occur, even with major cloud providers and cloud-based services. Providers' status pages report outages that might be affecting network performance.

Virus and malware checks

Viruses and other malware can affect network performance, and often they're not easy to detect. IT teams should use security tools to see whether new attacks have been flagged.

Database logs

Databases that are full or overtaxed can slow performance across the network. A fresh review of database logs will show whether this is the case. 

Command-line tools

The most common command-line tools are ipconfig and nslookup. Numerous others—such as iptables, netstat, tcpdump, route, arp, and dig—can also help identify network issues.

Test environments 

For cases that are especially challenging or that involve sensitive or restricted data, IT teams may need to construct test environments, where they can re-create problems and test solutions.

Troubleshooting software features

Engineers benefit from a network troubleshooting interface that provides a global view of an entire network as well as a view into specific KPIs. As networks become more complex and dispersed, the design and ease of use of this interface become even more important.

Customizable views

The ability to filter network data by location, department, device, or network improves the early stages of diagnosing network problems.

Cross-domain visibility

The idea of viewing the network as a series of interconnected domains is becoming obsolete. The typical enterprise network includes not just local-area networks (LANs) connected to the internet, but also remotely hosted databases, applications, and data processing. Up-to-date troubleshooting tools are designed to manage these new, more complex networks.

Related products and solutions

• Network Analytics
• Evolution of Network Monitoring
• Network monitoring and troubleshooting user guide
• Meraki Insight Introduction
• Cisco Intent Based Networking (IBN)

You may also like…

• What Is AI (Artificial Intelligence) in Networking?
• What Is Endpoint Analytics?
• What Is Network Monitoring?
• What Is Networking Software?
• What Is Zero-Trust Networking?
• What Is AIOps?

Troubleshoot Network Connectivity

Your network could be a blessing that makes life easier and it also becomes a nightmare that turns into hell. And this hell could turn into a headache on a global scale.

There was, for example, the Turkish ISP incident in 2004 where they managed to pull the whole internet and made it past their routers. The ISP (TT) misconfigured its routers which then went online, to announce to the rest of the internet that everything should be routed through them.

Since routers sync with one another and propagate this kind of information, the configuration errors spread and resulted in tens of thousands of networks on the internet sending traffic to the wrong destinations.

This was a great example of how some network connectivity issues – and their resolutions – could have a ripple effect that goes far beyond the networks’ boundaries.

The most common network connectivity issues

Before we start talking about troubleshooting network connectivity issues, let’s have a look at how we can group them into four major groups and come up with a common solution for each of them.

These four major groups of issues that can be encountered in a network are:

• Network connectivity issues
• Bandwidth issues
• Connectivity device configuration issues
• IP and addressing issues

It is with these groups in mind that we will be talking about how to tackle issues and resolve them.

Troubleshooting the issue – the basics

Network connectivity issues can be reported by users or alerts from monitoring tools.

The basic steps that apply to all the issue types mentioned above can be grouped into:

Collect information

Before you can even say you have a network connectivity issue, you need to collect information proving this is indeed true.

Start with complaints from users – both within and beyond the network – and, in the case of alerts from monitoring tools, go ahead and collect analytical data from reports, logs, and audit trails.

You can observe application, operating system, and server response times and compare the collected data to see if there are any changes over time.

Identify the symptoms

Use the analysis to get an idea of the type of problem you are facing, which assets it has affected, and even if you have encountered it in the past. You might even be able to make out who is behind the chaos.

Determine the scope of the issue

If you have good monitoring tools, you will also need to look at the extent – or reach – of the fallout. This could remain contained locally in one subnet or, like the Turkish incident above, could end up having an effect that is felt on a global scale.

Check for changes in the network

This is the first step in taking action towards resolving issues – start tracking any changes that were made on any digital asset. It doesn’t matter if it is a software, operating system, hardware, or connectivity device – it needs to all be audited and checked for any errors.

Questions to be asked here include:

• Were there any upgrades? Were there any updates?
• Were there any new devices added to the network?
• Were any devices configured or reconfigured?
• Were there any new users added? Was anyone given a new role? Were new users added?

Establish the most likely cause of the problem

Once a general idea of what could have been the cause is formed, it is time to start drilling down deeper and try to pinpoint the most likely one among them to have been the actual culprit.

Deploy a solution and test it

With a narrower target, administrators can now start trying different methods to find the most effective fix for the network issue.

Document the problem and solution

Congratulations! Now, it is time to record the issue and its solution. This will serve as a reference and knowledge base for anyone who might need to quickly resolve the same problem in the future.

A few commands that will help with troubleshooting

Here are the three most-used commands used when troubleshooting a network:

A longer list of other commonly used commands and tools can be found here .

How to troubleshoot your network connectivity issues like a pro

Now, let us move on to the actual troubleshooting steps needed to figure out any issues that may occur on your network or the devices on it.

To make it easier, we will break the process into each one of the four scenarios we’ve mentioned above:

1. Troubleshooting network connectivity

Typical symptoms of an issue with network connectivity are:

• Error messages indicating “device not found” or that the connection has timed out.
• Applications slowing down, video and audio communication becoming laggy or even impossible to make.
• Domain syncing or authorization jobs take longer than usual – or fail completely – due to timeouts.
• Inability to communicate with devices located in the cloud (or over the internet), on the same network, and even in the same subnet.

The troubleshooting steps to take to resolve such network connectivity issues include:

• Checking hardware Check all your devices to make sure everything is connected properly, has been switched on, and is working well. Make sure all switches are in the correct positions. Power cycling the device is a good idea. The adage “ Have you tried turning it on and off again?” applies here.

• Test connectivity Ping a remote device to test connectivity.
• Find out your IP address You can find IP details about your device to check for any misconfigurations.
• Reset your IP address You can use the tool to refresh your IP address and get a new one to check for a DHCP error.
• Running tracert This is another basic tool that allows for testing the connectivity of devices, the route data packets take, the distance that is traveled (in seconds), and how healthy the connection is.
• Running nslookup This network administration command-line tool is used to test the DNS to determine whether there’s a problem with a target server. Check out our article nslookup: How to Check DNS Records – Step-by-Step Walkthrough on how to use this tool to get the best out of your testing.

• Perform audit trails and log checks Administrators make it a point to keep an eye on their network’s usage and access history. Logs and audits are always good sources of information about what went wrong and give a clue about what can be done.
• Kill unnecessary applications Some applications can interfere with your network connection. Software solutions like proxies , antiviruses, and anti-malware tend to block packets. Firewalls select traffic that passes through the network and misconfigurations could lead to unintentional disruption of traffic (or even bring to a complete halt).
• Divide and conquer Troubleshooting the network without these applications – the proxies, antiviruses, and anti-malware, i.e. – should be done with care, though. Letting down all defenses isn’t an easy network administration decision to make. All access to the outside world (internet) should first be cut. Also, partial testing should be done to check each subnet for issues – and not the whole network – if possible.

Remedies to take include :

• Rebooting of all affected hardware.
• Reconfiguring settings – or correcting wrong ones.
• In case of continued failure, starting from scratch – building from the ground up by installing all firmware and software, configuring them, and finally monitoring and testing performance.
• Testing connectivity one step at a time – like pinging and tracing devices one hop at a time.
• Blocking of ports and denying access to unauthorized users, applications, and devices – removing unnecessary privileges, roles, and accounts.

2. Troubleshooting bandwidth issues

Typical symptoms of bandwidth issues are:

• Websites take forever to complete loading, return timeout errors, or don’t load at all.
• Apps don’t sync with servers and could even fail after timeouts.
• Client-server corporate solutions fail to update or retrieve data slowly.
• Communications between connected devices, and downloading or uploading normal file sizes, take ages – if it happens at all.

Loss of bandwidth can cause a whole network to come to a slowdown. Therefore, finding and eliminating bottlenecks should also be a part of troubleshooting network connectivity.

• Look for the signs You don’t even need a tool to find issues with your bandwidth. Are your applications too slow? Are your videos suddenly taking longer to buffer? Do you get “connection timed out” error messages from your connectivity devices?
• Slow delivery Another indication would be the slow delivery of packets. These could be emails taking too long to reach recipients or tracert (traceroute) showing long hop times.
• Use monitoring tools If you need a graphical presentation of the bandwidth usage on your network, you can choose one of the tools listed in our post 5 Best Free Bandwidth Monitoring Tools for 2022- Network Traffic Usage .
• Kill or stop bandwidth-hogging applications.
• Schedule resource-intensive jobs – like cloud backups – for after-hours or beyond peak times.
• Implement a Quality of Service ( QoS ) to improve optimal delivery.
• Implement a policy restricting file sizes that can be sent across the network – and implement packet blockers.

Although you can simply pay for more bandwidth, this will be addressing the symptoms and not the root causes.

3. Troubleshooting connectivity device configuration issues

Troubleshooting connectivity devices configuration issues can be divided into two major parts:

Configuration issues with connected devices

Examples of such devices include browsers, applications, laptops, mobile devices, and servers.

Typical symptoms of issues with such connected devices are:

• These devices have trouble connecting – or don’t connect at all – even when the network is working perfectly.
• Someone else on the network, with the same type of connected devices, has no issues while you do.
• The connection issues were first noticed after configuration changes or updates were done on the devices.
• Network configuration – IP address, domain, authentication, privileges – change brings connectivity down.

Every device that is connected to a network needs the correct configuration before it can go online. This, as can be imagined, is a complicated undertaking and a broad topic.

Every device has its required configuration settings for it to connect to the internet correctly. In case of issues with such configurations, the only advice we can give you here is that you will need to get the support for the software or hardware from the products’ makers and proceed accordingly.

After all, browsers, computers, servers, and mobile devices come under this category and all have unique configurations.

Some basic troubleshooting steps that can be taken include:

• Checking browser configuration, clearing the cache, reinstalling the browser, and trying switching to other browsers.
• Devices like laptops and PCs can try to telnet into the nearest router – a successful connection implies there are no hardware issues.

• Rebooting the computer, server, or mobile device – updating all software, uninstalling recently installed applications, updates or upgrades.
• You can also check for hardware conflicts .

A good administrator always has a backup of everything under their control and in case of a failure, they can revert to an older version – back to a restore point, that is.

• Check network connection settings – IP address, subnet masks, DNS addresses, and proxy server settings are good places to start looking into.
• Try copying configurations from other devices that are working well – or you can replicate configurations from devices on other subnets.
• Run antivirus and anti-malware to see if the errors are being caused by viruses or malicious code.
• Revert to previous versions or return to restore points when everything was last working fine.
• If all else fails, perhaps formatting and reinstallation can revert the device to a “ Factory Reset ” status and start building it all up again.

Configuration issues with connectivity devices

Examples of such tools include hubs, routers, switches, gateways, and firewalls.

Typical symptoms of issues with such connectivity devices are:

• The devices have trouble maintaining network connections – or don’t connect them at all – even when the rest of the network is working perfectly.
• The other, similar, connectivity devices have no issues – just one or a few of them.
• The issues were noticed when configuration changes or updates were done on the devices – they stopped working or there was a noticeable latency on the network.
• There were changes made in network configuration – IP address, domain, authentication, privileges – which brought the connectivity down.

Every connectivity device in a work has a specific task to perform. Depending on the location, a failed connectivity device can cause a network to lose packets or even drop connections completely.

The drivers for connection hardware like Wi-Fi adapters, NICs, and serial ports can affect connectivity if the latest versions haven’t been installed. On the other hand, a driver update could bring a previously well-working device down. Administrators should make sure there are no conflicts by testing them before bringing them online.

Some basic troubleshooting steps that can be taken:

• Reboot the router, switch, or modem – these devices normally clear their caches and refresh their configurations which, in turn, could get rid of basic issues.
• Firmware updates can fix issues; therefore, administrators can simply run updates on their devices and see if it fixes the problem.
• Worst case scenario is that they might need to factory-reset the device and restart the configuration from the ground up.
• Study the network architecture to see if there are any gaps, misconfigurations, or collisions – tracert and ping are your friends here.
• Make sure all paths connect from client to destination path – all hops should be completed in a reasonably short time.
• If upgrades or updates have been performed prior to the issues’ arising, it would make sense to revert to the previous statuses.
• Connectivity devices, just like any hardware, have maximum shelf life limits following which their performances deteriorate – perhaps, it is time to have legacy devices replaced.

4. Troubleshooting IP and addressing issues

Typical symptoms of IP and addressing issues are:

• You get an error message about your IP address including one warning you about “… IP address conflict” or, in case of hosted sites, “This site can’t be reached… server IP address could not be found.”

• Specific devices can’t access local shared assets like folders, servers, portals, and printers – even though everyone else does.
• Inability to sign into the domain – even with the right credentials being submitted.
• Your TCP command-line tools – like PING and TRACERT – return errors.

Now, although we have seen how CLI connectivity testing tools like IPCONFIG and tracert can uncover a lot of information about a network it is still a manual task. Also, when we talk about IP and connectivity issues we are talking about the misconfiguration of IP addresses for client devices, as well as connectivity devices – which is a lot of devices when considering the average network size.

All this means that administrators looking to troubleshoot IP and connectivity issues will need to automate pinging and tracing tasks.

Examples that could lead to issues include:

• Assigning the wrong IP address to a device or plugging it into the wrong subnet.
• Collision of IP addresses in the same subnet or on the network.
• The DHCP server is not assigning IP addresses or has run out of them.
• Wrong subnet mask being assigned thus curbing the IP range of a device.
• Using the wrong DNS configuration or assigning the wrong gateway and making it impossible for the device to connect beyond its subnet.
• Misspelling of device or domain names.

Next, there is the issue with accounts, roles, and privileges. Network and system administrators need to keep track of every account that is permitted to access digital assets.

Apart from the users, the assets themselves need to have permission to be on the network. It isn’t uncommon for administrators to block communication between devices or networks. The Marketing group of users might not be allowed to access assets on the IT subnet. Therefore, troubleshooting such issues needs to start with checking permissions as it avoids having to unnecessarily tamper with devices’ configurations.

Let us not forget that there are networks that intentionally block ping and tracert packets to remain hidden. This means that just because you can’t use these tools doesn’t mean there is any connectivity issue.

• Administrators need to keep track of every single IP address assignment of every single device on their network – some tools can help with automating this, and we will soon have a look at a few.
• Antiviruses and anti-malware can be run to make sure there is nothing malicious running on the network (or the devices on it).
• Make sure all involved hardware devices ( cables , RJ45 jack , NIC , routers , etc.) are working and that there are no collisions or driver issues.
• Reset all IP address assignments – renew your IP addresses, flush DNS, and even test connectivity with manually assigned, static IP addresses.

Ultimately, if everything seems fine on your network, but the issue remains unresolved, you may need to contact your ISP to find out if there are any issues on their side, and inform them that everything on your side of the network is working fine and that it is just not connecting with any device beyond your perimeter.

Best defense – monitor your network

You can avoid issues on your network before they even occur. Administrators need to leverage network monitoring and management tools to help them keep an eye on the performance of their network – and resolve issues before they occur using their forecasting features.

Using such tools, they can stay on top of their network’s security and integrity by watching for any changes occurring in real-time. They can also set up alerts to help with sending notifications whenever suspicious activities are spotted. With machine learning and AI playing a major role in network monitoring technology, there is a high chance that they will keep their networks protected at all times.

The best network monitoring tools can be used round the clock and on any network configuration – be it LAN, cloud, or hybrid. It would be wise to take advantage of them.

Three of the Leading Network Monitoring Tools

Here is our list of the leading Network Monitoring Tools:

• Paessler PRTG Network Monitor EDITOR’S CHOICE This on-premises package provides monitoring services for networks, servers, and applications and includes Ping utilities to check on device availability and connectivity. Available for Windows Server or as a SaaS package.
• Nagios XI A package for network, server, and application monitoring that gives access to a large library of free plug-ins and provides connectivity tests with Ping. Runs on Linux or a virtualization.
• Progress WhatsUp Gold A network monitoring system that is based on SNMP for device detection and status checks and also provides connectivity tests with Ping. Runs on Windows Server.

Since we agree that it makes sense to use a network monitoring tool to automate the task we thought you would also like to know what options you had by way of such tools.

Our methodology for selecting network connectivity troubleshooters

We reviewed the market for connectivity testers and troubleshooters and assessed the options based on the following criteria:

• A network monitoring package that identifies all devices
• An automated asset inventory creation process
• Network topology mapping
• A continuous Ping that can be set to raise an alert if connectivity is lost
• A manual Ping option for troubleshooting
• A free trial or a demo service for a no-obligation assessment opportunity
• Value for money from a network monitoring tool that includes automatic alerts for lost connectivity

Let us, therefore, have a look at three of the best network monitoring tools:

1. Paessler PRTG Network Monitor

PRTG Network Monitor is an SNMP-based network monitoring tool that can be expanded by buying add-ons to monitor other infrastructure.

Key Features:

• Device autodiscovery
• Network mapping
• Ping connectivity tests
• SNMP device statuses
• Free version

Why do we recommend it?

Paessler PRTG automatically detects network devices, creates a network inventory, and generates a network topology map. These system documents really help with troubleshooting and the package also includes connection testing tools, such as Ping, and assessment reports, such as a protocol analyzer. The system can test internet connections as well as LANs.

It can be installed on Windows Server that can be used to monitor applications, systems, devices, and traffic on an IT infrastructure.

It is a network monitoring software that uses SNMP, packet sniffing, and Windows Management Instrumentation (WMI) to monitor networks.

This tool has fully customizable dashboards that can help administrators of networks of any size – large or small. It is scalable, powerful, and user-friendly.

Finally, PRTG is extensible to cover the entire network’s digital assets as the company also makes other solutions to cater to them – just have a look at their full catalog.

Who is it recommended for?

This package is suitable for all types and sizes of businesses. The software bundle is customizable because the buyer pays for an allowance of monitors, which are called “sensors,” and then decides which of the services in the package to turn on. The system is available as a SaaS platform or a software download for Windows Server.

• Uses a combination of packet sniffing, WMI, and SNMP to report network performance as well as discover new devices
• Autodiscovery reflects the latest inventory changes almost instantaneously
• Drag and drop editor makes it easy to build custom views and reports
• Supports a wide range of alert mediums such as SMS, email, and third-party integration
• Supports a freeware version
• Is a very comprehensive platform with many features and moving parts that require time to learn

Try PRTG Network Monitor – Free for 30 days.

EDITOR'S CHOICE

Paessler PRTG is our top pick for a network connectivity tester because the high-end monitoring system is free if you only activate 100 sensors. The package includes a large library of monitors and there are one-way and remote response Ping tests in the package. The bundle will automatically discover your local network and all of the devices connected to it. It will also generate an asset inventory and a network topology map. Use the basic free version to keep an eye on device availability or pay for more sensors and get a full stack monitoring package.

OS: Cloud or Windows Server

2. Nagios XI

Nagios XI is a network monitoring tool that offers flexibility and extensibility. It is gentle on the network as it uses an agentless model to cover a large number of assets.

• Monitors networks, servers, and software
• Autodiscovery
• Connectivity tests with Ping

Nagios XI and its free counterpart Nagios Core include a Ping utility that can tell you about device availability and other issues, such as packet loss. The Nagios system also implements an automated network discovery cycle that repeats continuously, creating and updating an asset inventory. Ping plays a part in that process, too.

This tool runs on Linux and is based on their proprietary and free Nagios Core engine which comes with thousands of free plugins.

It is an enterprise server and network monitoring software that helps administrators monitor their applications, services, and network as a whole – from one central solution.

Nagios comes with a large community of users and plugins that are easy to develop which means this tool will continue to get better.

This system has a wide audience because it is available in a free edition for small and cash-strapped businesses and a more sophisticated version for big businesses. The system is very flexible because users and system suppliers provide free plug-ins that extend the monitor’s capabilities.

• Simple, yet informative interface
• Flexible alerting options support SMS and email
• A wide range of community-designed plugins are available for free
• The open-source version lacks the support found in paid products

Try Nagios XI for FREE .

3. Progress WhatsUp Gold

Progress WhatsUp Gold is a network performance monitor that utilizes SNMP to check the health of network devices.

• Network performance monitor
• Device detection
• Automatic network mapping

Progress WhatsUp Gold is a network device monitor that includes network discovery and automatic inventory creation. The interface for the tool shows each of the endpoints and network devices and the details screen for each as a Test button to run a connectivity check to that device.

It is a tool for monitoring the availability and performance of networks, systems, applications – regardless of the architecture which could be LAN, cloud, and hybrid. It also covers wireless networks and internet connections bridging remote sites or cloud resources.

It has an auto-discovery module that populates the assets inventory at startup and then continues to poll for changes that may have occurred in the resources connected by the network. In case of changes, the tool automatically updates the network inventory by adding, moving, or deleting their profiles accordingly.

This inventory is then used to create a map showing the latest network topology that adapts automatically in real-time as the assets change.

This monitoring package is marketed to mid-sized businesses. It is an on-premises package that has a core unit and optional extensions. The core system includes a connectivity test and also has a Ping utility. You can get deeper traffic monitoring services through the Network Traffic Analysis add-on.

• Great interface
• Supports a wide range of flow-enabled devices
• Can support both virtual and physical hardware
• Balances user experience with monitoring features quite well
• Free version can only monitor up to five resources

Try Progress WhatsUp Gold for FREE .

Troubleshoot your network connectivity like a professional

We hope this article has helped you tackle the task of troubleshooting any network connectivity issues that may occur. As you may have realized, this is a huge undertaking that requires patience and technical know-how.

But, we think that the best way to troubleshoot network connectivity is with the help of the monitoring tools that we have seen. We recommend you make use of them to prevent the issues from occurring in the first place.

We would like to hear from you. Leave us a comment below.

Network connectivity FAQs

What are the 3 important parts of network connectivity.

Network connectivity has three points of failure: the endpoint network interface, network devices, or internet connections. Narrowing down the location of connectivity issues should be your first task when troubleshooting connectivity problems. Use Ping to check on connections to different devices, starting with a Ping to a device on the network and then Ping to a remote location. The results of these tests will help you identify the root cause of the connectivity problem.

Where is network connectivity?

The heart of network connectivity on any device lies with its network card. You need to ensure that the computer is physically connected to the network with a cable or can contact a wireless access point (AP) with WiFi.

What are network connectivity problems?

The connectivity problems that you experience will have different causes depending on the type of network that you have. With wireless networks, connectivity issues are usually down to a weak signal in the area where the poorly performing computer is located. With wired networks, the problem will be wither with the addresses allocation procedure,m with network device capacity, or with the computers network interface.

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Everything To Manage & Monitor Your Network In One Simple Bundle

Solarwinds top 5 essential it tools.

• Web Heldesk simplifies support ticketing
• Remote Support - desktop remote control
• FTP Server for internal and external file sharing
• Patch Manager - network wide Windows updates
• Engineers Toolset has 60+ tools for network monitoring, management and security

DOWNLOAD FREE TRIAL

Fully functional for 30 days

8 Easy-to-Do Ways to Troubleshoot Network Connection

You'll be up and running in no time

A faulty Wi-Fi connection doesn’t have to ruin your day. There are plenty of ways you can restore a lost internet connection. Follow these network troubleshooting tips and you’ll be up and running in no time.

1. Check Your Settings

First, check your Wi-Fi settings. Go to Settings > Network & Internet > Wi-Fi . Switch Wi-Fi to the On position.

Phones and tablets also have settings that turn Wi-Fi on and off. Make sure that it is turned on so you can connect to the network.

You also want to check if Airplane Mode is turned on.

2. Check Your Access Points

Check your WAN (wide area network) and LAN (local area network) connections. In layman’s terms, these are the Ethernet cables that go to and from your router.

If you suspect that the cables are the culprit, try swapping them out with new ones.

3. Go Around Obstacles

Walls, furniture, and other obstructions can be the reason why you’re unable to go online. Moving closer to the router can re-establish the connection. If moving closer to the router does not solve the issue, then at least we can remove it from the list of suspects.

4. Restart the Router

Sometimes restarting the router can help fix connectivity issues. This is even truer in cases where the router has not been turned off in a while. A quick restart can jolt the router back into working like it used to.

If that doesn’t work, you might also consider resetting the router. But only do so if you’re okay with it being restored to its factory settings. You will have to reconfigure everything including the SSID and password.

5. Check the Wi-Fi Name and Password

Check the network name (otherwise known as SSID) and password of the network connection. If you’re used to connecting automatically when in range of a router but are no longer able to, changes may have been made to the network while you’re away.

It could be as simple as administrators updating the password or the SSID could have been changed to a different one.

6. Check DHCP Settings

Routers are usually set up as DHCP servers. This setting lets computers join a network automatically. With DHCP turned on, users will no longer have to mess with IP Address and DNS Server settings manually.

To edit your DHCP settings, go to Windows Settings > Network & Internet > Wi-Fi . Under Wi-Fi , click Manage Known Networks . Select a network and click Properties .

Under IP Settings , click Edit . From the drop-down menu, select Automatic (DHCP) .

Note: Selecting Manual will let you set your DNS Server Address and IP Address settings manually.

7. Update Windows

Your network problems could be caused by your system. If that is the case, Windows could have possibly released a fix. Try updating your Windows machine to the latest release.

Go to Windows Settings > Update & Security > Windows Update . Click Check for Updates . If there are updates available, Windows will download and install them.

8. Open Windows Network Diagnostics

Windows has a tool called Windows Network Diagnostics that lets users troubleshoot connection issues.

Go to Windows Settings > Network & Internet > Status . Under Change Your Network Settings , click Network Troubleshooter .

Windows Network Diagnostics will run a couple of tests to see what’s possibly causing your Wi-Fi issues.

Windows will let you know if it does not find any issue. Otherwise, you will be given a list of possible actions to take to resolve the problem.

This tool, or a version of it, should be available in Windows 7 to Windows 10.

Christopher Jan Benitez is a freelance writer for hire who provides actionable and useful web content to small businesses and startups. In his spare time, he religiously watches professional wrestling and finds solace in listening to '80s speed metal. Read Christopher's Full Bio

Read More Posts:

Dominick Fair

Chief Technology Officer

15 Common Network Problems & How To Solve Them

So, your network crashed. It’s a great day.

You just lost an entire morning’s work because your network quit on you- and this is not some college research paper, this is your business .

Life is crazy and busy enough already! You don’t need more network and IT stressors added to it.

The only thing you need is a business network that makes your job and your life fluid.

It doesn’t matter if you live in Frederick, Bethesda , Rockville, McLean or Alexandria- you live in the future tech-hub of the world. Amazon is moving in, and Google has already caught on. You need protected, reliable and progressive IT.

If your business network breaks down, we have you covered.

We know about the uncommon network problems on the backend. But, did you know there are common network problems that can sometimes be prevented with the services of a managed service provider?

Here’s some information that may help you take a positive step towards never having to deal with annoying network issues again:

1. Networking Issues

IT management companies can always help businesses with their networking issues. But not all IT companies which help you with network issues are created equal. 

Some aren’t worth the time to call them. Some have great network solutions for issues but cost too much. What if we were to tell you about a company that can handle your networking issues at an affordable price? 

Maybe you’re skeptical at this point, so we’ll go over 15 of the most common network problems. Then we will tell you why we’re the best IT company in your area.

Here are a few common network problems:

• Your network is too slow. You have rebooted your computer. You have deleted files and folders that take up a lot of memory. But you still have a slow network speed. 
• The Wi-Fi signal is strong in some areas and weak in other areas of the office. It makes no sense. It continues, no matter how you rearrange the furniture.
• The IP addresses have snafus. Sometimes there may be duplicate IP addresses. Sometimes there can be IP address exhaustion. 
• Network path cannot be found. This is also knowns as a DNS problem. If there is a network error message that drives most people to distraction, it is that one. 
• Unable to connect to a printer or file on a network share program. That can put a group meeting in an indefinite hold pattern if not fixed as soon as possible.

We know how aggravating and stressful these network issues can be. As an IT management company with clients from Virginia to DC and Maryland, we also know how important our network solutions are.

They are the reasons our solutions need to work the first time, every time.

2. Network Problems

We are presenting you with common network issues and problems that affect all businesses from time to time. We also have solutions for these problems.

Here’s a small cheat sheet of brief solutions you may try for a couple of these ongoing network problems.

Here are more everyday common network problems;

• Cyber Security or hacking your network . Only about 14 percent of small businesses can mitigate cyber risks and their network’s vulnerability. Of the 14%, 60 percent of them go out of business within six months. 
• Data Back-ups . You have a lot of data that needs to be backed up at the end of each workday. But sometimes that doesn’t happen right, or it doesn’t happen at all. It’s a nightmare to figure out what happened.
• The Cloud and those who don’t understand it, misuse it, keep incorrect data on it or cannot figure it out so they get rid of it on their computer. 
• No IT plan at all? This is when we have our work cut out for us and we love every minute. Because it allows us to help a business develop an IT plan that grows and develops with them.
• Account Privilege Abuse. That’s when someone who shouldn’t be using company networks does. It can be a nightmare because  60% of all security breaches on your network are done from the inside. That means it is someone who works with or for you.

There are solutions to these network problems we work with every day. But the longer the problems go on, the more difficult it is to fix at every level. We get it done, but it is time-intensive. 

3. Common Network Problems

The last five common network problems are some of our unique network problems. But that being said, they are still common enough to include on our the list. They are:

• Misconfigurations cause as much as 80% of all network problems. Setting parameters manually may be something you can do. But when it is done wrong, it can cause untold IT headaches.
• VLAN issues happen when a VLAN is not configured to the correct port, which supports its services. 
• Wireless connections don’t work. There is nothing worse than going to use the wireless connection with your boatload of work only to realize that you cannot get access to the connection.
• Unable to establish a VPN connection. Many people may not know what or how the VPN connects so this can be a real stress-inducer IT problem.
• Ongoing network processes are using up all the memory. This one can be a puzzler without an IT management group which can help you walk through what is going on.

The value of an IT management company cannot be overstated. We say the heartbeat of your business is your network.  There is no substitute you can put in the place of a network that crashed. Because it doesn’t exist.

Reliable networks are a necessity for businesses everywhere. If your network problems cause you to lose business, for a day or even an hour- it is going to make a huge difference in office flow and client relations on your end.

Managed IT can prevent these problems before they happen.

Common Network Problems & Solutions

Some answers to a few of the common network problems we mentioned above you may find surprising. Some will seem too easy to be true but sometimes it works out that way.

But there are other network problems that can take the average IT knowledgeable person, more days than they want to figure it all out. This is often because of all the moving parts in network systems and servers.

The good news is that there isn’t a single network problem or issue we haven’t seen already. When it comes to complicated and in-depth network problems, we know what to do and how to do it almost as soon as we make it.

Here are some short answers to what can be difficult network problems.

• When your network is too slow , it can be the router’s positioning causing wireless interference. We test in all positions when we need to.
• The WiFi signal is strong and weak throughout the building may be because of your network’s administrator interface. It needs to be set to optimum performance.
• Data Back-up issues can be caused by hardware and software problems so all need to be checked out. You can back up directly to an outside server or another outside source as a temporary measure.
• VLAN issues require you to check the cabling and the interface first before doing anything else.
• Continuous loss of memory because your network has a memory hog somewhere. Damaged hardware or a capacity bottleneck can cause this. Either can be fixed in a straight-forward manner.

Network Issues 

There is no network issue you have which does not have a solution or answer. That’s what we will as truth in our industry. We give you the IT management services and answers to meet your network needs.

View pricing on our management plans that vary and are based on your particular needs. We have starter package plans for new businesses. We also have our obsidian package plan for established, larger businesses.

All of our packages can handle any of your current or potential network issues and provide your business with the answers and solutions to get you back on track. Our mission is to create fluidity in the workspace so that you and your business can get back to what it does best in its day-to-day operations.

All technology today evolves at the speed of a week-to-week and sometimes day to day basis. Problems in networking, cloud computing, and remote access are what we fix for our customers every day.

Your business should be able to hop online with the touch of a button and click of a mouse. Many of our calls come when people have tried to fix their network issues themselves but think they may have made things worse. We can fix those network issues too. 

Our IT Service Management Plans

Our IT service management plans allow us to be there for you so you never have to worry about having network problems or issues. 

We offer timely network solutions that give you peace of mind. Also, they get your business back up to speed as quickly as possible.  

Wouldn’t it be great to know that your network protection is just around the corner with 24/7 support?

SADOS offers more than solutions to your network problems. We offer specialized architecture and deployment. SADOS does maintenance and LAN/WAN network monitoring in our managed service packages.

We’re only one call away . Reach out to us before you need us in a network emergency. 

Try our FREE AI-powered  help desk. No login required.

Need a quick fix?

Try our free ai-powered tech support.

Describe the problem you are facing. Be friendly, descriptive. Remember that AI can make mistakes. If you’re having an IT emergency, please contact us .

You may also like...

What Does a Content Delivery Network Do?

If you’re interested in optimizing your company’s website to improve page load speed, boost security, or lower your bandwidth cost, using a content delivery network will help.

6 Steps to Surviving an IT Emergency

When you operate your own business, your IT system is your lifeline. That’s why it’s important to be prepared for an IT emergency.

Is Your Business Protected with a Disaster Recovery Plan?

Disaster recovery plans are necessary to help businesses avoid unrecoverable loss. Here are some disaster recovery plans available.

News to your inbox

Keep tabs on what’s happening in the world of technology. We’ll send you new posts to your inbox

Ready to modernize your IT?

Service Status

• Entertainment

How to Fix Network Connection Issues on Windows 10

Fix Network Connection Issues on Windows 10 (2021)

2. Once the Command Prompt window is open, begin typing in the IPconfig commands. The first command is ipconfig /release and it releases the current IP configuration.

Ping is not a troubleshoot resolver, but it’s a handy command to check the reliability of your network on Windows 10. From the response time, you can gauge if your PC needs network diagnosis or not.

Troubleshoot Network

If the methods above didn’t work, you could try out the built-in Windows troubleshooter to fix the network connection issues on Windows 10. Here is how you use it.

3. Finally, click on “Internet Connections,” and then click on “Run the troubleshooter.” It will detect the problem and will try to fix the issue automatically.

Reset Network Settings

Resolve Internet Connection Issues on Windows 10

Passionate about Windows, ChromeOS, Android, security and privacy issues. Have a penchant to solve everyday computing problems.

None of these actually work… especially with a vpn that may be in use.

Aparently there is a fix for the ICON that says “no connectivity” but you actually are connected…

Thank you for sharing this. Now I can fix my network connection issue easily.

Add new comment

• PingPlotter Professional
• PingPlotter Standard
• Getting Started Guide
• Product Manual
• Compare Products
• PingPlotter Cloud
• PingPlotter for Contact Centers
• Server Status
• Support Center
• Articles & News
• Troubleshooting Guide
• Interpreting PingPlotter
• PingPlotter Cloud Login
• Pingman Tools Login
• License Management

Get a free 7 day trial of PingPlotter Cloud

The Beginner's Guide to Solving Network Problems

If a bad connection is between you and the online content you want, this guide helps diagnose your problem and work toward a solution.

Keep reading to learn how to use PingPlotter to find the source of network problems!

Let PingPlotter do the tedious work

PingPlotter Sidekick automates setup and guides you through troubleshooting.

Network Problems Suck

It's never fun when your connection's on the fritz, but you can do more than reboot your router . Follow this step-by-step guide and we'll show you how to find the source of your problem and start working toward a solution.

This Beginner's Guide to Solving Network Problems is effective whether or not you control the failing part of the network. If your local network is the problem, we'll show you how to diagnose the issue and fix it. If a network outside your control, like an internet provider, is the problem, we'll show you how to build a case and persuade the provider to help fix the problem.

What is a Network Problem?

Lag, buffering, bad call quality, and no internet connection are examples of network problem symptoms. If you're unable to enjoy the online content you want, there's a good chance your network is to blame. Network problems impact things like online games, websites, streaming media, and video calling. The internet doesn't even have to be involved. Any time a bad connection prevents you from accessing something outside your computer you're dealing with a network problem.

Network problems happen when something disrupts the connection between your computer and the content you're trying to access.

How are Network Problems Solved?

The first step to solving a network problem is finding the source. Network problems are caused by a part of the network you control or a part of the network outside your control. We're assuming you control your local network and don't control anything beyond that. If that's not the case, just think of local as in your control and outside as in someone else's control .

Your devices, including your internet modem and wireless router, are usually in your direct control.

External services, like the servers for online games, media, and more, are out of your direct control.

The way you solve the problem depends on whether or not you control the failing part of the network. You can solve local network problems by yourself because you control the network. Outside network problems require help from whoever runs that network. Either way, this guide has the steps you need to move toward a solution.

Why Follow this Guide?

We've been helping people solve network problems for almost twenty years. Our "secret sauce" is a software tool called PingPlotter . It tests your network and makes it easier to find the source of problems. With PingPlotter and this guide by your side, you're well equipped to tackle problems of all shapes and sizes.

PingPlotter makes finding the source of problems easier by graphing network performance. Green is good. Red is bad.

How Does PingPlotter Work?

PingPlotter tests your network with the same tools technicians have been using for years. Those tools are Ping and Traceroute. The difference is PingPlotter visualizes the information in a way that makes finding the source of network problems easier.

To find the source of a problem, look for places on the network where performance goes from good to bad.

What Happens After I Find the Source of the Problem?

Once you have an idea of what's going on, we'll show you how to check your diagnosis and work toward a solution based on the results. If you have a local network problem, we'll provide instructions on how to fix it. If your problem is outside you local network, we'll show you how to effectively connect with the people running the network and persuade them to help you.

So what do you say? Ready to try it out?

• Test the Network
• Diagnose the Problem
• Local Network Problems
• Outside Network Problems

Let PingPlotter help you troubleshoot.

7 Common Network Issues and How to Resolve Them Fast

Networks are networks. Despite best efforts to keep things smooth all the time every day, things happen. Here's a look at some common network issues, some tips for quickly resolving them, and even better, how to prevent them from occurring again.

1. Duplicate IP Addresses

When two devices attempt to share a single IP, you see the dreaded "Address Already in Use" Kill — with no ability to access the network.

The Quick Fix: The blame for this often rests with your router's default DHCP configuration. DHCP is probably trying to assign your new device an address at the beginning of your subnet , and another device may already occupy these low-numbered addresses with static IPs. If you've just introduced a new device or server to your network, it may have its own DHCP server. Simply disable the DHCP server on that device to restore sanity to your network.

The Preventive Measure: You can take one simple step to avoid IP conflicts by modifying your router's configuration to begin assigning DHCP addresses near the top end of your subnet, leaving the lower addresses available for devices that require static IPs.

2. IP Address Exhaustion

To troubleshoot this issue, use the ipconfig command. If the workstation has assigned itself an IP address that begins with 169.x.x.x, it means that no IP address was available from the DHCP server.

The Quick Fix: Some users on cable internet might not have a local router, in which case IP addresses are assigned on a limited basis directly from your ISP. You have probably run out of allowed IP addresses from your ISP. The solution to this is to purchase either a standalone router or WiFi access point with an integrated router. This creates your own local pool of internal addresses, ensuring you won't run out.

If you already have a local router with DHCP, the default address pool might be too small for your network. By accessing the DHCP settings on the router, you can adjust the size of the address pool to meet your network's needs.

The Preventive Measure: It's important that any internet-connected network have a local router in operation with NAT and DHCP, both for security reasons and to prevent IP address exhaustion. The router needs to be the only device connected to the modem, with all other devices connecting through the router.

3. DNS Problems

Errors such as The Network Path Cannot Be Found, IP Address Could Not Be Found, or DNS Name Does Not Exist, can usually be traced to a DNS configuration issue . The command line utility nslookup can be used to quickly show a workstation's DNS settings.

The Quick Fix: Workstations and other network devices can be configured to use their own DNS servers, ignoring the server assigned by DHCP. Checking the 'Internet Protocol Version 4 (TCP/IP)' settings for your adapter will show if an incorrect DNS server is specified, so just select "Obtain DNS server address automatically" instead.

The Prevention Measure: Your local router might be configured to operate as a DNS Server, creating a DNS pass-through to your ISPs servers. On busy networks, this may overload the capabilities of the router. Change your network's DHCP settings to directly access your DNS servers.

4. Single Workstation Unable to Connect to the Network

If only a single workstation is displaying the "No internet" message when opening a web browser, we can usually assume that the rest of the network is healthy and turn our attention to any hardware and software that is particular to this system.

The Quick Fix: To resolve this network issue, start by eliminating the obvious communication barriers such as a bad cable, poor WiFi signal , failing network card or incorrect drivers. Ensure that the workstation's network adapter is configured with the correct IP, subnet, and DNS servers.

If that doesn't solve the problem, check any firewall software on the device to ensure that necessary ports are open to the external network. Common ports include 80 and 443 for web traffic, plus 25, 587, 465, 110, and 995 for email.

The Preventive Measure: It's usually best to leave all workstation TCP/IP settings to "Automatically assigned." Use a DHCP server to hand out a uniform configuration to all devices on the network. If a static IP is needed on a particular workstation or server, most DHCP servers allow the ability to create static IP mappings.

5. Unable to Connect to Local File or Printer Shares

Sharing problems are among the most difficult network problems to solve, due to the number of components that need to be configured properly.

Most commonly, sharing problems arise due to conflicts between mixed security environments. Even different versions of the same operating system sometimes use slightly different security models, which can make interconnection of workstations difficult.

The Quick Fix: We can cure sharing problems most efficiently by drilling down through the possibilities in this order:

Ensure that the required services are running. On Windows systems, the server, TCP/IP NetBIOS Helper, workstation, and computer browser services all need to be running. On Linux machines, Samba is the primary component required to share with Windows systems.

Check your firewall(s) . It's very common for a workstation's firewall to be configured to block file and printer sharing traffic, especially if a new antivirus package is installed that introduces its own firewall. Firewall issues can also exist at the hardware level, so ensure that routers or managed switches are passing share traffic within the subnet. Speaking of subnet….

Ensure all workstations are on the same subnet. This problem typically only appears on complex networks, however, even simple networks sometimes have static-IP equipment with an improperly configured subnet. The result is that external traffic will move about just fine, while internal traffic will hit unexpected roadblocks.

All Windows network adapters will need File and Printer Sharing for Microsoft Networks, Client for Microsoft Networks, and NetBIOS over TCP/IP enabled.

Once the above checks have passed, it's finally time to check the most likely culprit, permissions. There are multiple layers of access required, each with their own interface within the OS. Check for:

        Systems configured with the wrong workgroup or domain.

        Incorrectly configured HomeGroup.

        Network type set to Public.

        Incorrect NTFS permissions.

6. Local Network is Unable to Connect to the internet

This situation can either be intermittent or persistent. Often times, the most difficult aspect of dealing with any external network problem is finding the company responsible. And then tasking them to solve the issue, particularly with intermittent failures that are difficult to trace. It can sometimes be such a problem that organizations will have to switch internet providers in order to solve the issue.

The Quick Fix: A router and modem reboot is the first order of business. The tracert then utility can be used to identify communication breaks. It will clearly hiccup on the particular router hop that is causing the problem. Contact your ISP with your findings, providing screenshots as necessary.

The Preventive Measure: To avoid the finger-pointing that can prevent rapid resolution of external issues, do some research to ensure that you procure connectivity only from local Tier 1 providers. Other ISPs are more than happy to sell you service, however, they are simply piggybacking the Tier 1 connection, since they don't actually own the infrastructure in your area.

The goal is to remove as many middle-men as possible, so that when (not if) you experience a problem, one phone call is all that is required to identify the issue and get technicians to work on it.

7. Slow Internet Performance

Slow performance is typically due to congestion, or sometimes poor quality connections that have corroded or otherwise deteriorated. Congestion may not be directly related to bandwidth exhaustion, as a single overloaded port on a switch or router can diminish network performance.

This can be especially true on leased lines where dedicated bandwidth is to be expected, but speed tests indicate the network is not reaching it's rated potential.

The Quick Fix: Use speed test websites, conducting tests from geographically remote servers. This can pinpoint areas of congestion on the ISP's network. In the case of cable internet, the local network is shared amongst your neighbors, committing your ISP to a costly bandwidth upgrade when saturation occurs. Report your findings to your ISP so that they can take steps to resolve the issue.

DNS servers are an often overlooked aspect of internet performance . Using incorrect DNS servers can result in routing congestion or load balancing problems. While you should typically use your ISP's DNS settings whenever possible, they may actually be routing traffic through overloaded web caches. You can temporarily adjust your DNS settings to use OpenDNS instead.

The Preventive Measure: if internet performance is critical, you'll need to procure adequate connectivity. While cable internet may be inexpensive, you could be setting yourself up for frequent jeers from employees. A local DSL operator may offer improved reliability for a slightly higher cost, but for the most consistent performance, you may find that an expensive leased line is a requirement for your organization.

There's plenty of help out there — use it!

The good news is there are a plethora of resources for troubleshooting and solving network issues, and many of them are free and built into most operating systems. Ping, tracert, ipconfig, nslookup, and speedtest.net should be in the top drawer of every admin's toolkit .

More advanced utilities such as Wireshark provide a detailed analysis of your network's potential stumbling points, while wardriving tools can be called upon to identify WiFi performance or interference issues.

Armed with a deeper knowledge of how your network works, you can be prepared for the inevitable , and can even train end users to troubleshoot simple problems themselves. Your reputation as a network hero lives on!

By submitting this form you agree to receive marketing emails from CBT Nuggets and that you have read, understood and are able to consent to our privacy policy .

Recommended Articles

I have read and understood the privacy policy and am able to consent to it.

• Product Product
• Browse training
• All courses
• Certification training
• New training
• Solutions Solutions
• Resources Resources
• Learner stories
• Why e-learning?
• Customer reviews
• Ultimate Cert Guides
• Company Company
• Become a Trainer
• Transparency in Coverage
• Support Support
• Help Center

Let's chat!

We explain and teach technology, solve tech problems and help you make gadget buying decisions.

9 Fixes for “Can’t Connect to This Network” Error on Windows 11

You can have more than one Wi-Fi connection at your home or workplace. However, you might face the “Can’t connect to this network” error on Windows 11 when establishing a connection. If this has happened to you as well, here are 9 ways to fix it.

Before we get started, try connecting the router with your Windows 11 device using an ethernet cable to ensure the issue is not with your Wi-Fi. Then, disconnect the cable and try connecting wirelessly. If you still get the “Can’t connect to this network” error on Windows 11, continue with the below fixes.

1. Restart Windows and Router

Restarting your Windows 11 device will help fix issues occurring due to any temporary bugs or issues. Additionally, restarting your router will also help in refreshing your Wi-Fi network. This is one of the reasons why it’s mostly recommended as the first troubleshooting fix. For more details, here’s a step-by-step look.

Step 1: Go to the taskbar and click on the Start icon.

Step 2: Then, click on the Power button and select Restart once the options appear.

Simultaneously, remove the power cable from your router or press the power off button. Then, wait a few minutes, and either reconnect the power cable or press the power button again. Wait for your router and PC to reboot. Then, try connecting to the selected Wi-Fi network again. If Windows 11 won’t connect to Wi-Fi, move on to the next fix.

2. Turn Airplane Mode On and Off

Turning on Airplane Mode turns off all wireless communications on your Windows 11 device. Then, once it is disabled, all wireless connections are re-enabled. This can help fix any temporary issues and can be done instead of restarting your device.

For more details, check our guide on turning Airplane Mode on or off on Windows 11 .

3. Forget and Reconnect Network

If you’ve been facing issues connecting to any specific network on your Windows 11 device, forgetting and reconnecting to the network might help resolve it. This will help disconnect the device and establish a fresh pairing connection, resolving any issues that might have occurred during the first pairing attempt.

Follow the below steps to do it.

Step 1: Use the Windows + I key to open Settings. Then, click on ‘Network & internet’ from the menu options.

Step 2: Click on Wi-Fi.

Step 3: Here, click on ‘Manage known networks’.

Step 4: Go to the network you wish to forget and click on Forget.

Step 5: Now, go back to the Wi-Fi page. Here, click on ‘Show available networks’.

Step 6: Go to the network you wish to connect to and click on Connect.

Step 7: When prompted, enter the Wi-Fi password and click on Next.

Wait for Windows 11 to finish connecting to the selected network. If you still see the “Wi-Fi can’t connect to this network” error on Windows 11, move on to the next method.

4. Run Network Troubleshooter

The Windows troubleshooter can scan and detect issues that might be preventing Windows from establishing a connection. Based on that, you might get a list of suggestions that can help rectify it. Here’s how to run it on your Windows 11 device.

Step 1: Using the Windows + I key, open the Settings menu.

Step 2: Then, click on System. Here, click on Troubleshoot.

Step 3: Scroll down and click on Other troubleshooters.

Step 4: In front of ‘Network and Internet’, click on Run.

Wait for the troubleshooter to run. Once the suggestions are visible, use them and try connecting to the selected network again.

5. Disable IPv6

Your Windows device doesn’t always need IPv6 to establish a connection. And while it offers better security, there are still some connections that don’t support it. So, to fix any connection issues, manually disable IPv6 on Windows 11 and check again. Here’s how to do it.

Step 1: Go to Search and type ‘ View network connections ‘. Open the app from the search results.

Step 2: Here, right-click on your connection and select Properties.

Step 3: From the options, uncheck the IPv6 box. Additionally, ensure the IPv4 box is checked.

Step 4: Once done, click on OK.

This will save your settings and close the window.

6. Disable and Enable Wireless Connection

If the network adapter for the selected Wi-Fi network is not working properly on your Windows device, disabling and then re-enabling it can help fix this. Follow the below steps to do it.

Step 1: Click on Search, type ‘ View network connections ‘, and open the app from the search results.

Step 2: Here, right-click on the relevant connection. Click on Disable.

Step 3: Wait a while and right-click on the connection again.

Step 4: Then, click on Enable.

Wait for the connection to enable and reconnect. Then, check and see if the error message is visible or not.

7. Check for Driver Updates

Out-of-date drivers can disrupt the connection, especially if they become incompatible with your device. To ensure this does not happen, you can manually check and install updates for your network driver on your Windows 11 device. Here’s how to do it.

Step 1: Right-click on Start and click on Device Manager.

Step 2: Click on Network adapters. Then, right-click on your Wi-Fi driver.

Step 3: Here, select Update driver.

Step 4: Click on ‘Search automatically for drivers’.

If an update is available, install it and wait for Windows to finish restarting. Then, try connecting again.

8. Flush DNS and Reset TCP/IP

TCP/IP helps establish a connection with other network devices. Once done, it stores information regarding your recently visited websites as a DNS cache. This can aid in establishing a quick connection. However, this can prevent a connection from being established.

In this case, reset TCP/IP and flush the DNS cache to fix network connection issues in Windows 11. Here’s how to do it.

Step 1: Right-click on Start and click on Terminal (Admin). Click on Yes when prompted.

Step 2: Click on the downward arrow and select Command Prompt.

Step 3: Then, type the below command and press enter to execute.

Step 4: Now, type the following command and press enter.

Once done, restart your Windows 11 device and check again.

9. Check for Windows Update

Besides driver and other network issues, software issues can also cause problems when connecting to Wi-Fi. In this case, an update might be available to fix it. You can manually check and install it from Windows Update. Follow the below steps to do it.

Step 1: Go to Search and type Windows Update . Then, open the app from the search results.

Step 2: Here, click on ‘Check for updates’.

Wait for the update to download and install. Then, connect to the selected Wi-Fi network again on your Windows 11 device.

Fix Network Errors on Windows PC

Not being able to connect to your local network can be frustrating. So, we hope this article helped you fix the “Can’t connect to this network” error on Windows 11. Additionally, check our other article if you have trouble seeing Wi-Fi networks on Windows 11 .

Last updated on 29 November, 2023

The above article may contain affiliate links which help support Guiding Tech. However, it does not affect our editorial integrity. The content remains unbiased and authentic.

DID YOU KNOW

Ankita Sharma

A writer at heart, Ankita enjoys exploring and writing about technology, especially Android, Apple, and Windows devices. While she started as a script and copywriter, her keen interest in the digital world pulled her towards technology, and with GT, she has found her passion in writing about and simplifying world of tech for others. On any day, you can catch her chained to her laptop, meeting deadlines, writing scripts and watching shows (any language!).

More in Windows

How to Fix ‘This PC Can’t Run Windows 11’ Error on Windows 10

Top 8 Ways to Fix Can’t Connect to 5GHz Frequency Band of Wi-Fi on Windows 11

Join the newsletter.

Get Guiding Tech articles delivered to your inbox.

• WEATHER ALERT Dense Fog Advisory Full Story

Capital Health officials say network outages may be caused by cybersecurity incident

TRENTON, New Jersey (WPVI) -- Capital Health, with hospitals in Trenton and Hopewell, New Jersey, is the latest medical system to be affected by a cyber security issue that is causing network outages.

The hospital became aware of the problem earlier in the week and notified authorities.

Officials say it's unknown if there's been a breach of patient, employee or financial data.

While the hospitals are admitting and treating patients, there are some disruptions.

Elective surgeries are being prioritized by urgency, and outpatient radiology is not available, along with some cardiology testing.

Capital Health released a statement Wednesday saying:

"We continue to care for patients in both hospitals, including our Emergency Rooms, in our practices, and at all other locations under established protocols for system downtimes where necessary. We are prioritizing safe patient care while working to restore the network and address the impact of this disruption."

Rob D'Ovidio researches and teaches about cybercrime at Drexel University.

"This is purely a financial play here by the criminals. And what we've seen over the past few years with these types of attacks - there's an organized crime group behind it," said D'Ovidio.

He says that based on other recent cyber attacks on healthcare systems, this is likely a ransomware attack - where criminals disable a server or network, demanding payment.

In August, Prospect Medical Holdings was targeted, with four hospitals in Delaware County.

D'Ovidio says the criminals are often overseas, and he's not surprised to see hospitals being compromised now.

"Pretty interesting time of the calendar year where our emergency rooms and doctors offices are filled with flu and other respiratory illnesses that come up," said D'Ovidio.

A hospital spokesperson says primary care doctors' offices are unaffected.

How long that'll last is unknown, but the hospital says they expect to operate with system limitations for at least a week.

• HEALTH & FITNESS
• CYBERATTACK

Top Stories

AccuWeather: Dry, cloudy start to the weekend

• 9 minutes ago

Police ID serial burglar targeting homes while residents are sleeping

Philadelphia-born supermodel was one of first women to die of AIDS

Escaped inmate still on the run in Philadelphia | Here's what we know

Man charged with stabbing Derek Chauvin 22 times in prison: DOJ

Felicity Huffman on college scandal: 'I had to break the law'

Everything you need to know for the 2023 Philly Holiday Parade!

Rain doesn't dampen spirits at West Chester Christmas Parade

Help | Advanced Search

Electrical Engineering and Systems Science > Signal Processing

Title: deep regularized compound gaussian network for solving linear inverse problems.

Abstract: Incorporating prior information into inverse problems, e.g. via maximum-a-posteriori estimation, is an important technique for facilitating robust inverse problem solutions. In this paper, we devise two novel approaches for linear inverse problems that permit problem-specific statistical prior selections within the compound Gaussian (CG) class of distributions. The CG class subsumes many commonly used priors in signal and image reconstruction methods including those of sparsity-based approaches. The first method developed is an iterative algorithm, called generalized compound Gaussian least squares (G-CG-LS), that minimizes a regularized least squares objective function where the regularization enforces a CG prior. G-CG-LS is then unrolled, or unfolded, to furnish our second method, which is a novel deep regularized (DR) neural network, called DR-CG-Net, that learns the prior information. A detailed computational theory on convergence properties of G-CG-LS and thorough numerical experiments for DR-CG-Net are provided. Due to the comprehensive nature of the CG prior, these experiments show that our unrolled DR-CG-Net outperforms competitive prior art methods in tomographic imaging and compressive sensing, especially in challenging low-training scenarios.

Submission history

Access paper:.

• Download PDF
• Other Formats

References & Citations

• Google Scholar
• Semantic Scholar

BibTeX formatted citation

Bibliographic and Citation Tools

Code, data and media associated with this article, recommenders and search tools.

• Institution

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs .