help - strange hiccups

Toggle sidebar Toggle sidebar
N

NikGorn

Junior Member
Jun 28, 2017
6
1
36
my mother rcn.net in NYC

when I connect PC directly to the modem - 100% steady connection - no problems

BUT when I use a NETGEAR WGR614V09 - https://www.netgear.com/support/product/WGR614v9.aspx

both LAN and WiFi PCs get this sporadic connection - hiccup - lasts for a few moments - every now and then

(please see the ping bellow)

hmmm might be some settings?

hmm what could it be?


===========================
might be some settings - hmmm

please see https://imgur.com/a/GkhmTaz

what else to show from here?

===========================
I went the brute force way and ordered

TP-Link N450 Wi-Fi Router - Wireless Internet Router for Home(TL-WR940N)
https://www.amazon.com/gp/product/B003Y5RYNY/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1\\

===========================

ping log bellow:

Code: 
Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=18ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=50ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=13ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=62ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=13ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=59ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=116ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=114ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=24ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=13ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=13ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=8ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=19ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=12ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=21ms TTL=122
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=11ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
Reply from 8.8.8.8: bytes=32 time=9ms TTL=122
 
VirtualLarry

VirtualLarry

No Lifer
Aug 25, 2001
56,570
10,196
126
NikGorn said:
BUT when I use a NETGEAR WGR614V09
Click to expand...
Old garbage router. Give it to Goodwill.
NikGorn said:
I went the brute force way and ordered
TP-Link N450 Wi-Fi Router - Wireless Internet Router for Home(TL-WR940N)
Click to expand...
Better, but still low-end. No IPv6 support == already obsolete, in this day and age.

https://www.tp-link.com/us/products/details/TL-WR940N.html#specifications

Should have spent $40 and gone with an Asus AC1200G or something.

That being said, ping and replies are sometimes rate-limited by routers, so seeing "request timed out" is not unusual.

Do you have any issues with http or https connectivity? If you listed to streaming radio over the internet, does it sound fine, and not drop out? Or does it skip, or disconnect suddenly?

I'm not entirely convinced that you even have a problem, from the data presented.

Also, try a fresh set of pre-made Cat5e cables, or even Cat6, from Newegg or Monoprice, or heck, even maybe from Walmart or Staples if you would prefer to shop in a B&M store. It could be that your cables are older and worn a bit (chair rolled over them once too many times? Cat tripped on them? Ok, unlikely, but still... you get the picture.)
 
N

NikGorn

Junior Member
Jun 28, 2017
6
1
36
VirtualLarry said:
Old garbage router. Give it to Goodwill.

Better, but still low-end. No IPv6 support == already obsolete, in this day and age.

https://www.tp-link.com/us/products/details/TL-WR940N.html#specifications

Should have spent $40 and gone with an Asus AC1200G or something.

That being said, ping and replies are sometimes rate-limited by routers, so seeing "request timed out" is not unusual.

Do you have any issues with http or https connectivity? If you listed to streaming radio over the internet, does it sound fine, and not drop out? Or does it skip, or disconnect suddenly?

I'm not entirely convinced that you even have a problem, from the data presented.

Also, try a fresh set of pre-made Cat5e cables, or even Cat6, from Newegg or Monoprice, or heck, even maybe from Walmart or Staples if you would prefer to shop in a B&M store. It could be that your cables are older and worn a bit (chair rolled over them once too many times? Cat tripped on them? Ok, unlikely, but still... you get the picture.)
Click to expand...

thank you so much

#1 is that YES all devices will a "no internet" page / message at times - as you can imagine - so annoying - so it's not just a ping issue (although from my experience - ping is rather reliable indication of general view)

#2
thank you for confirming that the Netgear router at hand is old and bad - BUT one day it was state of the art - why can't it keep up now

there is no heavy traffic over it

although what is connected is:

* LAN - my moms PC (Win 7)
* LAN - my Server PC (win 10) hmmm yes I need to check if it is seeding anything ...
* WiFi - my laptop
* WiFi - my sisters laptop - rarely
* WiFi - and about 7 android devices - with very little activity

hmmm that's a total of 11 devices - but some with virtually no activity

yea might be too much for that baby
with one antenna

thank you - I will see how the router I ordered for $29 will perform if not well I will order what u suggested - thank you !! (as I think it's a problem of Netgear router - not scale issue ... meaning I do not think I need a huge big powerful expensive router - please correct me if I am wrong
 
mxnerd

mxnerd

Diamond Member
Jul 6, 2007
6,799
1,102
126
802.11g 54Mbps WiFi router is definitely old. Even 802.11n router is considered old technology now. (though I'm still using 802.11n :))

Any computer devices older than 5 years almost always start to degrade in some way.
 
N

NikGorn

Junior Member
Jun 28, 2017
6
1
36
so I am using the new router that I got from amazon

and I am still having issues - BUT ONLY ON MY WIFI laptop - hmmm what could it be? how can I diagnose?

I got
TP-Link N450 Wi-Fi Router - Wireless Internet Router for Home(TL-WR940N)
https://www.amazon.com/gp/product/B003Y5RYNY/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

===========================
SYMPTOMS

* So the pages will fail to load - imagine submitting a long and important form - only to discover all entered info is gone ...

* Skype calls will drop - imagine being on a 30 minute call with a bank - and pooooof gone

* and ping - see it bellow

===========================
WHAT CAN I DO?

how can I diagnose?

should I order yet another router?

thank you

===========================

here is my ping
NOTE - SEE ENTIRE PING LOG HERE - https://codeshare.io/5z9MY4

Code: 
Reply from 8.8.8.8: bytes=32 time=22ms TTL=122
Reply from 8.8.8.8: bytes=32 time=22ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=20ms TTL=122
Reply from 8.8.8.8: bytes=32 time=21ms TTL=122
Reply from 8.8.8.8: bytes=32 time=29ms TTL=122
Reply from 8.8.8.8: bytes=32 time=1773ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=21ms TTL=122
Reply from 8.8.8.8: bytes=32 time=21ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Reply from 8.8.8.8: bytes=32 time=19ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Reply from 8.8.8.8: bytes=32 time=17ms TTL=122
Reply from 8.8.8.8: bytes=32 time=1991ms TTL=122
Reply from 8.8.8.8: bytes=32 time=35ms TTL=122
Reply from 8.8.8.8: bytes=32 time=348ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=23ms TTL=122
Reply from 8.8.8.8: bytes=32 time=18ms TTL=122
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Reply from 8.8.8.8: bytes=32 time=23ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=13ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=15ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Reply from 8.8.8.8: bytes=32 time=20ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=44ms TTL=122
Reply from 8.8.8.8: bytes=32 time=18ms TTL=122
Reply from 8.8.8.8: bytes=32 time=14ms TTL=122
Reply from 8.8.8.8: bytes=32 time=31ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122=
Reply from 8.8.8.8: bytes=32 time=673ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=231ms TTL=122
Reply from 8.8.8.8: bytes=32 time=1186ms TTL=122
Reply from 8.8.8.8: bytes=32 time=105ms TTL=122
Reply from 8.8.8.8: bytes=32 time=64ms TTL=122
Reply from 8.8.8.8: bytes=32 time=19ms TTL=122
Request timed out.
Reply from 8.8.8.8: bytes=32 time=44ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=200ms TTL=122
Reply from 8.8.8.8: bytes=32 time=16ms TTL=122
Reply from 8.8.8.8: bytes=32 time=90ms TTL=122
 
VirtualLarry

VirtualLarry

No Lifer
Aug 25, 2001
56,570
10,196
126
Could it be your physical line from your ISP? Who is your ISP, and what kind of service do you have? Have you called your ISP tech-support yet?

Wait, when you say, "only on my wifi laptop", do you have other wired PCs that DON'T have problems, and do you have other WIFI devices, that likewise DON'T have problems?

In that case, it would be down to your laptop. It could be overheating (or maybe just the wifi card, they get pretty warm under continuous usage, and they can drop out or otherwise lose signal).

Edit: You know, this might be happening to me. I recently switched over from my Comcast connection to my FIOS connection for my LAN, and now, my mining program is showing "Socket Error!" every once in a while, and browsing Newegg, an old tab that had to re-load, some of the images didn't show up, had to manually re-load.

Strange.

It could have something to do with dual routers, or Tomato firmware, or hardware NAT. Or maybe it's just my FIOS, maybe my fiber is nicked somewhere.

I'll commiserate with you, it's not fun having a not-perfect connection.

At least, I don't have too many problems, though. Just some occasional closed sockets.
 
Last edited:
mxnerd

mxnerd

Diamond Member
Jul 6, 2007
6,799
1,102
126
Too many things can happen on the route from OP's home to server destination, simple ping results really can't tell anything.

Like VL has said, has OP tried wired ethernet connection?
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom