- The user interface thread appears to be frozen pingplotter Patch#
- The user interface thread appears to be frozen pingplotter full#
I don't know if that will have an affect.
I haven't reset the router by using the WPS button to fully clear it and start fresh again. I spent over 325.00 for this router a couple of years ago. wouldn't do any testing and/ or checking logs, even waiving my credit card didn't do anything. I believe the airprotect is o, so I don't know what you mean by thatĪsus support is non existent. You mentioned "Pure router mode", the router is not setup as AIMesh crap. all cat6 for direct connection to the router.
The user interface thread appears to be frozen pingplotter Patch#
i could replace the patch cable from the modem to the router., but it's new cat6. my 5ghz channel was on auto, and i tested all channels and chose the best one.Īll cables(incl outside lines) were tested. Start pointed out there maybe be issues with the router. We came back with a 2 to 3 high latency per tests. believe me, 1hr and 25 mins of pur testing. We have tested direct connection to the modem (PC booted in safe mode with no firewal, tons of pings and trace tests. The CMTS should be the preferred target for this as the results you see won't be mixed up with any potential network issues beyond the CMTS. If the CMTS doesn't respond, due to the fact that your with a TPIA, ping the Start DNS. The purpose of the ping test is to look for latency in the return and look for packet loss.
The user interface thread appears to be frozen pingplotter full#
a modem (pure modem) followed by a router in full router mode. a gateway modem in Bridge mode followed by a router in full router mode Ģ. That can be confirmed by pinging the CMTS, which is the 2nd IP address in a trace to anywhere if you have:ġ. Those problem are due to the (modem and firmware) design.īeyond that, you could have an external cable and/or connector issue. Modem stats have nothing to do with this. In addition, you will have packet loss for UDP packets, which are used for web address lookups, gaming, VPNs and backups, if configured for UDP.
If you have an Intel Puma 6 modem which does not have updates to correct latency and packet loss thru the modem, then you will see latency for all IPV4 and IPV6 protocols, ICMP, TCP/IP and UDP. This problem is not detectable by most users since the line stat, speed test and actual download/ upload is what model of modem do you have? Thats important. Sounds like you are on Cable, is it possible that Start changed something?! I've been with Start for few years and this just started few months ago!
My main issue that is pushing me to change ISP's (Bell states nothing wrong with my line, Start.ca at least pushed them to send a tech once but always after my picture evidence of the damaged line) is me connecting to my server in France, I rent a Kimsufi/ OVH server and run 4 game servers for the past decade (or longer) while connecting to either of my servers and others, every few seconds I get the Network Icon meaning lost connection to the server so I am frozen and can't move, this happens every few seconds and lasts for a few second (till I re-boot) Even Putty hangs! I asked for my profile to be put back to what it was before but same issue.Īt least now it takes about 4 days for the problem to come back, so I re-boot my gateway (SR505n) every day. May be Start changed WAN, PTM or profile settings?! So, I ended up thinking it is either the PED feeding me or Bell has changed something higher up. I tested with 3 different computers, one of them I built new just to do this test! If I took my Notebook out and connect to my friends, there are no issues. Now it is a lot better with all my changes but pinging the gateway itself (50 packets) using the command prompt, PingPlotter and WINMTR, could show 1ms for 15 packets then jump to 3000ms then back to 1ms. I am on FTTN 50/10 and have been experiencing same.Īfter replacing Gateway once then purchasing my own, running CAT5e from the NID to a new jack and re doing the burial myself(I am a Rogers tech but couldn't get Bell burial cable yet so I replaced with one that was not being used but still have a splice, better than 4 splices before my fix, next I'll try a temp direct to the NID), I still experience the Jitter!
0 kommentar(er)
