You can research the model of router or WiFi access point you have, and search for “channels”.
Make sure that it is away from metal (including electrical conduit), and is away from televisions, microwaves, and Bluetooth devices like speakers. If the above isn’t possible, you may want to look at where you put your router or WiFi access point.Most WiFi access points these days have dual-band try to hop onto the other band temporarily. You can try a router or WiFi access point reboot right off the bat.This is normally caused by poor WiFi access point placement or by too many networks broadcasting nearby (apartment complexes are notorious for this). With this, we’ll see some red beginning at the start of the route similar to what we saw with a device being down, but more sporadic. Here are some of the most common: Device completely "down" There are many issues that could be affecting your Teams call quality. Once you have your PingPlotter results, use the information below to narrow down your issue. We recommend collecting 10 minutes of data at a minimum for the most accurate results. You can also have your colleague trace to you in reverse by sending them your IP and having them trace in the same way indicated above. See if you can find any issues below that appear prior to the final hop. If you see 100% packet loss at the final destination, their edge device likely isn’t configured to respond to ICMP (which is common). This should start up a trace to their location.
Enter the address they gave you into the Trace Bar and hit Enter.
Then, have them give you that IP address and open up PingPlotter. If you believe you’re in a peer-to-peer call, have the person on the other end of the call find out their IP address. If you experience any issues (such as stuttering or freezes), check PingPlotter to see if you see any sudden spike in latency or packet loss. While the trace runs in PingPlotter, start a call in Teams. Using the target above, start tracing to a Teams server. Check your connection to Office 365's servers See our guide on solving common network problems to identify what might be the culprit. If you see high latency or packet loss, your network issue may be broader than just Teams. Enter “” Into PingPlotter’s Target Bar and click the green Start button, or use the link below to start tracing automatically. You can quickly identify basic network issues by starting a PingPlotter trace to a reliable target (such as ). If so, this is most likely the cause of your issue. If you have not already, check Office 365’s service status Twitter (or have your Admin check out their status page) to see if they are currently experiencing any known downtime. Check the status of the Office 365 service
You can click on the link below to automatically launch a PingPlotter trace to an Office 365 server used for Teams (if the link does not open PingPlotter, you can also enter the IP address of the server into PingPlotter's Target Bar). Simply trace to a DNS address, and it should resolve to a viable server. The cool thing is that they’re using DNS - you don’t necessarily need to look through giant lists of IP addresses. Microsoft has a list of servers and their IP addresses used for Office 365 services. Other communications may use peer-to-peer connections for things like calls between two people, meaning that the data is going straight from you to your colleague without hitting an intermediary server. What to targetįor conferences, Microsoft uses a server of theirs, which is chosen based on proximity to the conference creator, as a relay.
A 14-day free trial is always available to help you get started.įor troubleshooting Teams, you can use PingPlotter’s default settings.
To troubleshoot your network connection to Office 365 using this guide, you will need to download and install the latest version of PingPlotter.