constant patch failed to connect
#1
Posted 19 November 2012 - 11:54 AM
sup with that? pretty sure i'm not the only one getting these.
#2
Posted 19 November 2012 - 12:15 PM
Their DNS is intermittently failing to resolve some gravity related addresses. Google for "google public DNS" and follow those instructions to configure your computer to use Google's DNS servers (which are faster, and considerably more reliable than Comcast's)
Tech support question -> Tech support.
#3
Posted 19 November 2012 - 07:18 PM
and yes i'm on comcast
Edited by jake0619, 19 November 2012 - 07:26 PM.
#4
Posted 20 November 2012 - 04:09 AM
If you want a permanent fix you're gonna have to change your Comcast DNS server.
#5
Posted 20 November 2012 - 07:39 AM
#6
Posted 20 November 2012 - 11:46 AM
#7
Posted 20 November 2012 - 11:59 AM
does this cause my lag too? i used to never have lag but now it's unbearable to play without lowerping the past 3~ months or so
This is an easy question to answer - it's quite possible. I haven't been able to play on Comcast w/out lowerping, but Comcast + LP is still way cheaper than competing ISPs around me (though, I haven't paid for LP since I started running drazzy.com, because I proxy through that instead)
Start->Run (or start-> type in search box if there's no run), type 'cmd' (without the 's). At the command window, type 'tracert iro.ragnarokonline.com' (again without the 's). Let it run to completion.
Then copy/paste it in here. Copy/paste doesn't work the way you're used to in command windows. Rightclick and choose mark, and then use the mouse to select the trace results, then press enter to copy them. Paste the results here.
#8
Posted 20 November 2012 - 01:31 PM
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms 10.0.0.1
2 42 ms 29 ms 29 ms 71.58.232.1
3 16 ms 14 ms 15 ms 68.85.45.69
4 18 ms 18 ms 15 ms te-0-3-0-3-ar03.lancaster.pa.pitt.comcast.net [6
8.85.52.193]
5 26 ms 23 ms 27 ms pos-0-2-0-0-ar03.mckeesport.pa.pitt.comcast.net
[68.85.52.154]
6 51 ms 35 ms 59 ms he-4-4-0-0-cr01.ashburn.va.ibone.comcast.net [68
.86.94.161]
7 32 ms 33 ms 30 ms pos-0-1-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.30]
8 29 ms 30 ms 30 ms as6453.ashburn.va.ibone.comcast.net [66.208.233.
46]
9 29 ms 29 ms 29 ms 206.82.139.46
10 33 ms 34 ms 35 ms ae-6.r20.asbnva02.us.bb.gin.ntt.net [129.250.3.1
09]
11 112 ms 105 ms 133 ms ae-2.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.5
5]
12 109 ms 111 ms 116 ms ae-2.r05.lsanca03.us.bb.gin.ntt.net [129.250.5.8
6]
13 110 ms 112 ms 109 ms xe-0-0-0-15.r05.lsanca03.us.ce.gin.ntt.net [198.
172.90.170]
14 113 ms 114 ms 112 ms portal.demarcation.gravityus.com [204.2.170.50]
15 121 ms 105 ms 107 ms www.playragnarok.com [128.241.93.60]
Trace complete.
#9
Posted 20 November 2012 - 02:01 PM
If you run the trace a few times, do you ever get *'s where numbers should be, or numbers much larger than the others showing up in the trace? (that indicates packet loss happening by a low rate, which causes lag spikes, but often won't show up in a trace unless a packet happens to get dropped during the trace).
#10
Posted 20 November 2012 - 02:15 PM
The jump here
10 33 ms 34 ms 35 ms ae-6.r20.asbnva02.us.bb.gin.ntt.net [129.250.3.1
09]
11 112 ms 105 ms 133 ms ae-2.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.5
5]
does look a bit strange to have a ~70 ms jump in latency when it should be nearly at the same server.
#11
Posted 21 November 2012 - 05:57 AM
#12
Posted 21 November 2012 - 12:17 PM
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 3168 ms 17 ms 10 ms 68.85.45.69
4 18 ms 15 ms 20 ms te-0-3-0-3-ar03.lancaster.pa.pitt.comcast.net [6
8.85.52.193]
5 25 ms 26 ms 27 ms pos-0-2-0-0-ar03.mckeesport.pa.pitt.comcast.net
[68.85.52.154]
6 31 ms 35 ms 35 ms he-4-4-0-0-cr01.ashburn.va.ibone.comcast.net [68
.86.94.161]
7 31 ms 29 ms 28 ms pos-0-1-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.30]
8 30 ms 28 ms 29 ms as6453.ashburn.va.ibone.comcast.net [66.208.233.
46]
9 29 ms 31 ms 46 ms 206.82.139.46
10 34 ms 34 ms 33 ms ae-6.r20.asbnva02.us.bb.gin.ntt.net [129.250.3.1
09]
11 115 ms 108 ms 104 ms ae-2.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.5
5]
12 112 ms 107 ms 103 ms ae-2.r05.lsanca03.us.bb.gin.ntt.net [129.250.5.8
6]
13 112 ms 105 ms 101 ms xe-0-0-0-15.r05.lsanca03.us.ce.gin.ntt.net [198.
172.90.170]
14 115 ms 113 ms 113 ms portal.demarcation.gravityus.com [204.2.170.50]
15 112 ms 107 ms 161 ms www.playragnarok.com [128.241.93.60]
Trace complete.
tried to run a tracert during the laggier moments throughout the day. note that i didnt' dc off of ro, just lagged.
#13
Posted 21 November 2012 - 06:03 PM
#14
Posted 21 November 2012 - 08:21 PM
i have had to tether to mobile to get past the patch >>
#15
Posted 22 November 2012 - 09:08 AM
Can you access the IRO update repository using a web browser other than Internet Explorer?
uhh i clicked that link and had to refresh 8 times to get it to work if thats what you mean, on google chrome.
#16
Posted 28 November 2012 - 01:22 PM
i just recently got the same problem and i use comcast as well but its never done this before. not even once in the past until recently-these past 3 days and ive been using comcast for a loong time. are you guys sure its not a server side problem?Yeah just give comcast a call and ask for a manual reset or something. It doesn't seem to work if you just reset your modem on your side. It has to be theirs.
#17
Posted 28 November 2012 - 01:33 PM
I'm also having this problem on multiple comcast networks.
i have had to tether to mobile to get past the patch >>
uhh i clicked that link and had to refresh 8 times to get it to work if thats what you mean, on google chrome.
i just recently got the same problem and i use comcast as well but its never done this before. not even once in the past until recently-these past 3 days and ive been using comcast for a loong time. are you guys sure its not a server side problem?
All of these sound like the problem with Comcast failing to reliably resolve certain DNS entries. I had no problems with comcast recently (but a few years back, I had this problem for a short time, but it just went away after trying a few times), but then it suddenly happened out of the blue. It happens near central square in Cambridge MA, but works a 15 minute drive away in Newtonville MA. It's clearly a Comcast issue.
My suggested fix is to switch to using the Google Public DNS servers (google for Google Public DNS for instructions) - I haven't had problems since I did that (plus, they don't have the near-monthly total DNS failures that comcast does).
Another person had success by calling comcast support and "having Comcast reset his connection from their end"
#18
Posted 28 November 2012 - 01:54 PM
lol it works! i changed my dns number thingy but i wonder if its actually secure? my ignorance leave me to believe that some how people are able to screw me over because im using a public dns? im not savy with computers and i did read a little bit.. lolAll of these sound like the problem with Comcast failing to reliably resolve certain DNS entries. I had no problems with comcast recently (but a few years back, I had this problem for a short time, but it just went away after trying a few times), but then it suddenly happened out of the blue. It happens near central square in Cambridge MA, but works a 15 minute drive away in Newtonville MA. It's clearly a Comcast issue.
My suggested fix is to switch to using the Google Public DNS servers (google for Google Public DNS for instructions) - I haven't had problems since I did that (plus, they don't have the near-monthly total DNS failures that comcast does).
Another person had success by calling comcast support and "having Comcast reset his connection from their end"
#19
Posted 29 November 2012 - 04:59 AM
lol it works! i changed my dns number thingy but i wonder if its actually secure? my ignorance leave me to believe that some how people are able to screw me over because im using a public dns? im not savy with computers and i did read a little bit.. lol
Google commit an enormous amount of resources to ensuring their products and services are secure — probably far more than any ISP. Their DNS servers are publicly-accessible, but only Google has control over them.
#20
Posted 29 November 2012 - 08:25 AM
Google commit an enormous amount of resources to ensuring their products and services are secure — probably far more than any ISP. Their DNS servers are publicly-accessible, but only Google has control over them.
This. I trust Google a lot more than I trust comcast.
If you're wondering why Google does this for free - it's the same reason (or one of them) that they developed Chrome and gave it away - anything that makes people use the internet more benefits Google, because Google is by far the largest online advertising broker. The faster pages load, the more of them you're likely to view. Hence, they run faster (and more reliable) DNS servers than most ISPs, wrote a faster browser, etc.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users