the user interface thread appears to be frozen pingplotter

The user interface thread appears to be frozen pingplotter manual#

The only thing that hasn't been replaced/ tested so far is the RJ11 cable to the telephone socket - Is it worth doing this anyway or is it likely the issue resides on the WAN/ ISP infrastructure after hop 2? When we originally raised our concerns with the ISP (before we did any detailed testing using Pingplotter), they actually replaced the router for a new unit, this was around 3 weeks ago. The tablets that we run this app on do not lose WiFi connectivity and when the issue occurs I am still able to successfully load a webpage to prove the internet connectivity has not dropped out. However we don't tend to see any other issues if using other internet based apps such as streaming Youtube/ Spotify, or loading web pages etc.

Every day we get intermittent freezing of the app, which we believe is due to internet connectivity issues. The reason we are using Pingplotter - We are a bar/ restaurant and use a cloud-based app for taking orders + payments/ printing receipts etc. The service is FTTC and we receive good speeds of 60-80Mb down/ 20Mb up. It is worth reiterating again that my laptop was the only device on the network at the time - I would have thought that the router would drop less ICMP packets in this case as there is nothing else on the network for it to prioritise? I am now starting to believe the packet loss from Hop 1 could be a false-positive and the root cause may reside further up the route. At this point I increased the Interval from 2.5s to 5s, and even 10s but the same level of packet loss remained after collecting 30-60mins of data. I have also tried another laptop of different (and equally high) spec, with a different (new) ethernet cable, yet the same issue and results persist.Īt first I thought the router hardware was at fault, as the PL was originating at Hop 1 - However after doing some reading I learned that many routers de-prioritise ICMP traffic, therefore resulting in PL.

In my testing I have disconnected all clients and network devices from the router, turned off wireless radios, and only connected my laptop (running Pingplotter) directly to the router via gigabit ethernet. Regardless of the destination, we are seeing averages sometimes in excess of 70% packet loss all the way from Hop 1 through to the final hop. I'm still having trouble with pinpointing my issue.

The user interface thread appears to be frozen pingplotter manual#

I'm planning on sending them that screenshot today.Hello all, new to Pingplotter and this forum - Have spent a lot of time reading through the manual and Knowledge Base, really informative content and feel like I've learned lots already. Then on the 28th of march I receivied yet another response from their support team, in that letter they've asked to run traceroutes to capture issues along my route to the server. On march 25th the support asked me to perform a tracert to their game server and send them the file, I did, but they haven't done anything.

On march 22nd I wrote the support again and they've responded with these fixes:įollowed this guide, also this guide on configuring firewalls, and this guide, then I flushed dns and restarted my pc. On march 17th I received a mail from valorant support to disable IPv6 on all tunnel interfaces and to also flush dns, did all that, the problem continued. The worst problem is that the game recognizes me as being afk and punishes me for it. During the time that I spend waiting to get back into the game I can talk my teammates and hear them, but not get into the game. Soon after I get kicked out of the game into the loading screen. I can see bullet tracers and hear shots being fired and I can also hear my teammates, but I cannot help or assist them. Weapon pull out animation cuts out, players stop moving or they just walk straight forward, I can't reload my weapon nor use my abilities. Network problem icon appears in the top right corner.ĭuring the period of time that it is there my game stops working normally.