Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 14, 2015 22:13:01 GMT -8
Want to guess what the problem was? I'll give you three guesses...
|
|
|
|
Post by Dan W. on Apr 14, 2015 22:20:10 GMT -8
1.Cat or dog chewed the cable.
2. Someone was downloading porn.
3.your modem was upside down and plugged in backwards.
Did I win!!
As you can see, I don't do guessing games very well. So what was it?
|
|
|
|
Post by Ian on Apr 14, 2015 23:41:08 GMT -8
1) windows updates
2) someone on house watching netflix
3) someone downloading torrents
Sent from Galaxy Note 3
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 15, 2015 7:03:52 GMT -8
Dan, you were closest. My dad had gotten me a Cat 6 Ethernet cable from the Fairfield Radioshack for virtually nothing when they were doing their store-closing sale and I have been using that one for a few months although some of the time there seemed to be ping issues. I plugged the longer Cat 5 one back in which I had gotten from Amazon (need at least a 100 ft cable to go from my mancave upstairs to the downstairs modem - this one is 150 ft  ) and while the speed was hardly different (30 ms of ping on the Cat 5 vs. 26 on the Cat 6 recorded on Speedtest), I went on a different rFactor server and rather than the 300-700 you saw last night, I had a consistent 67 ms showing  . |
|
|
|
Post by Ian on Apr 15, 2015 9:42:59 GMT -8
Awesome Sent from Galaxy Note 3 |
|
) and while the speed was hardly different (30 ms of ping on the Cat 5 vs. 26 on the Cat 6 recorded on Speedtest), I went on a different rFactor server and rather than the 300-700 you saw last night, I had a consistent 67 ms showing 
.