site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
718
Share Topic
Posting?
Post a:
Post a:
Links: ·Rogers HiSpeed FAQ ·Cable Modem FAQ ·RWIN Calculator ·Distributed Computing Clubs ·Rogers-Yahoo! Help Site
AuthorAll Replies


notme1987

@rogers.com

[Extreme] Just signed up.. really?

Wow I cant play my games.. I keep getting the "disconnect sign", where when you try to move and nothing happens. So wtf??

»www.dropbox.com/s/v5ojaxv8hfj25a4/r.png

I still have Teksavvy. When I switch back and do the same test in cmd and in game it's completely perfect and smooth, no disconnect sign or sort of lag at all.

»www.dropbox.com/s/3si0weftjwu1kig/t.png

This is not what I signed up for

Mindman

join:2012-12-10
Merritt, BC

I would have stuck with techsavvy.. rather than robbers. anyway PLAY DOTA 2 100% betta!



c2roth
Premium
join:2006-04-26
Kitchener, ON
kudos:2
Reviews:
·TekSavvy Cable

reply to notme1987
Does look like you are getting some packet loss which will make just about anything really difficult and gaming would be especially affected.

Could you please run a longer window of pings by running this cmd and posting the results:

ping masterserver.hon.s2games.com -n 200 -l 1024



notme1987

@rogers.com

C:\Users\pku>ping masterserver.hon.s2games.com -n 200 -l 1024

Pinging masterserver.hon.s2games.com [174.37.182.122] with 1024 bytes of data:
Reply from 174.37.182.122: bytes=1024 time=99ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=88ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=88ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=75ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=102ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=86ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=88ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=81ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=96ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=81ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=75ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=82ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=75ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=75ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=85ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=76ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=76ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=95ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=82ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=86ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=78ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=76ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=75ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=92ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=80ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=87ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=74ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=80ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=77ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=79ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=82ms TTL=53
Request timed out.
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=73ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=75ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=76ms TTL=53
Reply from 174.37.182.122: bytes=1024 time=76ms TTL=53
Request timed out.
Reply from 174.37.182.122: bytes=1024 time=72ms TTL=53

Ping statistics for 174.37.182.122:
Packets: Sent = 199, Received = 132, Lost = 67 (33% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 102ms, Average = 75ms
Control-C
^C
C:\Users\pku>



notme1987

@teksavvy.com

Just did the same test with Teksavvy.

C:\Users\pku>ping masterserver.hon.s2games.com -n 50 -l 1024

Pinging masterserver.hon.s2games.com [174.37.182.120] with 1024 bytes of data:
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=91ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=121ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=131ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=85ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=136ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=140ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=93ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=153ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=159ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=85ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=99ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=113ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=89ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=85ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=92ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=98ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=91ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=99ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=84ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=87ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=83ms TTL=52
Reply from 174.37.182.120: bytes=1024 time=86ms TTL=52

Ping statistics for 174.37.182.120:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 159ms, Average = 93ms

---

I'm so mad right now.. Even browsing the web like Facebook and Google on Rogers lags.


bt

join:2009-02-26
canada
kudos:1

reply to notme1987
Your Teksavvy connection is DSL?



notme1987

@rogers.com

Nope. It's Cable.



notme1987

@rogers.com

So..how do I fix this?


technocar2

join:2009-05-29
Brampton, ON
kudos:2
Reviews:
·TekSavvy Cable

1 edit

said by notme1987 :

So..how do I fix this?

One of the 69.63.x.x routers is having problems and they are within rogers network, so best thing you can do is contact tech support and let them know that there is an issue with a main router.

Here is my tracert, as you can see the 69.63.x.x are not dropping packets, but in your case it is (in your tracert the last ping on hop 5 was dropped), so its something only rogers can fix once they know which router is the culprit.

Tracing route to 174.37.182.122-static.reverse.softlayer.com [174.37.182.122]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  main_host_150mbps_link.ca [192.168.0.1]
  2     9 ms    11 ms     8 ms  7.2.120.1
  3    10 ms    11 ms    12 ms  69.63.254.65
  4    10 ms    11 ms    11 ms  69.63.250.86
  5    11 ms    11 ms    11 ms  69.63.249.193
  6    24 ms    24 ms    26 ms  69.63.249.26
  7     *        *        *     Request timed out.
  8    25 ms    25 ms    25 ms  ae7.bbr02.eq01.wdc02.networklayer.com [173.192.1
8.195]
  9    32 ms    36 ms    34 ms  ae1.bbr02.eq01.chi01.networklayer.com [173.192.1
8.155]
 10    57 ms    73 ms    58 ms  ae1.bbr02.cs01.den01.networklayer.com [173.192.1
8.131]
 11    57 ms    57 ms    57 ms  ae7.bbr01.cs01.den01.networklayer.com [173.192.1
8.168]
 12    84 ms    81 ms    87 ms  ae0.bbr01.wb01.sea02.networklayer.com [173.192.1
8.144]
 13    84 ms    83 ms    84 ms  ae0.dar01.sr01.sea01.networklayer.com [173.192.1
8.199]
 14    83 ms    83 ms    83 ms  po1.fcr02.sr03.sea01.networklayer.com [67.228.11
8.225]
 15    82 ms    83 ms    89 ms  174.37.182.122-static.reverse.softlayer.com [174
.37.182.122]
 
Trace complete.
 


c2roth
Premium
join:2006-04-26
Kitchener, ON
kudos:2
Reviews:
·TekSavvy Cable

I have to agree with your assessment. It appears that something isn't quite right with the hop before the SoftLayer network takes over which is Rogers.

OP: Your best bet is to contact Rogers Technical Support and hope that you don't get a really dumb tech.


Wednesday, 19-Jun 20:39:42 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics