Pages: [1] 2 3 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Chaaraa
|
Posted - 2006.11.30 01:53:00 -
[1]
Edited by: Chaaraa on 30/11/2006 02:00:29 Canadian Rogers ISP customers seem to be unable to find routes to the Eve-Online website or the Tranquility server. Bell Sympatico ISP has the routes, Rogers does not.
A number of my Eve friends in real life who are also Rogers customers all have the same problem.
|
Fred FourTwenty
|
Posted - 2006.11.30 02:11:00 -
[2]
I was hoping this wasn't limited to rogers customers :( this is my problem too. *Hates in the direction of Rogers so hard*
|
ShadowandLightsMojo
|
Posted - 2006.11.30 02:27:00 -
[3]
Thought it might have something to do with DNS, i'm on rogers too. Anybody got a solution? CAlling rogers or waiting it out?
|
Fred FourTwenty
|
Posted - 2006.11.30 02:30:00 -
[4]
Originally by: ShadowandLightsMojo Thought it might have something to do with DNS, i'm on rogers too. Anybody got a solution? CAlling rogers or waiting it out?
Doing both If enough people call they might actually get it fixed.
|
ShadowandLightsMojo
|
Posted - 2006.11.30 02:36:00 -
[5]
Gotta tell them something. My EVE isnt working is not gonna do much.
Anybody know the Tranquility server address?
|
Fred FourTwenty
|
Posted - 2006.11.30 03:13:00 -
[6]
The knowledge base yielded this to help,
tracert 87.237.38.200
Tell them their network is dropping packets, tell them where the packets stop.
|
ShadowandLightsMojo
|
Posted - 2006.11.30 03:15:00 -
[7]
For those on the Rogers network i got a bit more info. Tranquility server address is 87.237.38.200 Problem begings to happen after it leaves the rogers network (odd my traceroute showed something else)
Rogers said that there is nothing they can do about it as the issue is not on their network and suggested i talk with CCP.
|
Fred FourTwenty
|
Posted - 2006.11.30 03:25:00 -
[8]
Thats a negative, they are lying to you out of training and cause they don't know the problem. You got the script, you need to be elevated. The problem can be proven to be either their network or their upstream, either way their problem. my tracrt shows, dying on or at the end of the rogers network Tracing route to 87.237.38.200 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms rogers.com [192.168.2.1] 2 9 ms 14 ms 8 ms 10.105.58.1 3 * 8 ms * gw03.ym.phub.net.cable.rogers.com [66.185.90.17]
4 8 ms 8 ms 7 ms gw01.ym.phub.net.cable.rogers.com [66.185.93.33]
5 8 ms 7 ms 8 ms gw02.ym.phub.net.cable.rogers.com [66.185.80.210 ] 6 48 ms 50 ms 49 ms igw01.chfdrl.phub.net.cable.rogers.com [66.185.8 1.1] 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out.
|
Dailey
|
Posted - 2006.11.30 03:38:00 -
[9]
I'm in the US and having similar problems. I seriously doubt it's your ISP. There are all kind of Domain name server problems that I've become aware of. I'm using comcast, and their DNS servers went down. I've changed to new DNS servers, but still can't access Eve and a bunch of other servers. Which leads me to thing there are other resolve problems between my ISP and Eve (and other locations). Please don't tell other people what's going on when you don't have a clue.
|
Fred FourTwenty
|
Posted - 2006.11.30 03:53:00 -
[10]
Hi, see that trace route. Thats the packet stopping right at the end of rogers network, if i can't reach it and tranquility's IP has nto changed that makes it A) rogers, or B) their upstream provider. It may not be rogers, but it **** well looks like it from where i'm sitting, the fact that you have a similar problem in the states suggest its a rogers upstream provider.
K Thanks
|
|
ShadowandLightsMojo
|
Posted - 2006.11.30 03:53:00 -
[11]
All a DNS does is resolve an IP address. Since the connection to Tranquility is done directly by the IP what is the purpose of changing the DNS server?
|
ShadowandLightsMojo
|
Posted - 2006.11.30 03:56:00 -
[12]
Yes Fred it does appear that way. I got the same results with my traceroute.
Rogers said that the servers starting with 66.xx are not part of their network. Well something is not right as the first server after my router is a 66.xx which is always some kind of a gateway system at your ISP. I think Rogers is not telling the truth, but there could be something else in the works aswell as other people outside of Rogers netowrk have had the same problem.
|
Dailey
|
Posted - 2006.11.30 04:09:00 -
[13]
Whoopie, you know how to use tracert, but do you understand it? Maybe it's stopping as it leaves your ISP's routers? Maybe it's getting stopped somewhere other then you ISP? Geez. I kind of figured it was a waste of time to post that. Let's just point out finger at our isp because we have no understanding of the internets.
I'm just saying that there are a lot of routers/whatever that aren't resolving correctly, thus - most likely it isn't your ISP. Seeing as how just changing my DNS server (which was down) only fixed some websites means there are bigger problems than just comcast's local DNS server. Eg, other routers that handle various taffic, specifically the ones between you and Eve may be experiencing problems. I'm sorry if you dont understand what I'm saying, but I work in IT, and I have a vague understanding how it works. I may be wrong in some details, but it's not just your ISP.
I'm also drunks, so I may not be making sense, but I do understand what it going on... vaguely.lol
|
Fred FourTwenty
|
Posted - 2006.11.30 04:14:00 -
[14]
Edited by: Fred FourTwenty on 30/11/2006 04:14:52 Edited by: Fred FourTwenty on 30/11/2006 04:14:26 :D I'm glad you get whats going on, cause you got it across there :P Thats what I'm saying, and based on the information i have am saying it is a router inbetween me and eve. Infact I'm saying it's a router the is upstream of my provider, i have no idea who it is, but they do telling a trained tech(not call center tech) will let them figgure out who, and then get them to fix it.
Just in short again, I'm not saying it IS my isp, i'm saying its their problem. They can talk to the router owner it IS, I can not.
|
Dailey
|
Posted - 2006.11.30 04:20:00 -
[15]
Edited by: Dailey on 30/11/2006 04:21:01 Ok, well.. that's where I was misunderstanding you. It's not you ISP's problem. They may be big, but they can't tell other companies how to conduct business. They have about as much say-so as we end users do. They can tell the company they have a problem, but they probably already knew, and are working on it.
|
Water Star
|
Posted - 2006.11.30 04:20:00 -
[16]
SAME PROBLEM, Can not logon EVE and CCP's web site. :(, Rogers user. Now I am using proxy to view this forum.
|
Fred FourTwenty
|
Posted - 2006.11.30 04:24:00 -
[17]
They purchase the upstream bandwidth, it's not about them being big, one of their links is down, this costs them money, they will see it fixed asap. Now its how fast asap is that is related to how big they are
|
HankMurphy
Pelennor Swarm Eternal Rangers of Terror
|
Posted - 2006.11.30 04:26:00 -
[18]
Edited by: HankMurphy on 30/11/2006 04:27:20 can you ping the server? (forget the damm traceroutes)
i would start w/ your ISP as opposed to what anyone else here may suggest. you only need to get a few hops out before you are on unrestricted core links through the major providers (level3, att, sprint, etc). this Canadian Rogers may be blocking the traffic and not even know it.
if not, then any one of the providers (often many and may change as route paths constantly change based on usage etc) between you and ccp could either need to flush the routes out of their core routers or there may be a more complicated issue w/ some kind of asynchronous route. This is not your issue however. If your ISP demands they aren't blocking anything and cant explain why you cant resolve a ping to the server, it should be your local ISP's responsibility to open a ticket w/ whatever provider is causing the issue.
|
Fred FourTwenty
|
Posted - 2006.11.30 04:29:00 -
[19]
Edited by: Fred FourTwenty on 30/11/2006 04:29:12 usually if you can't trace to something theres no way to ping it, but yes i did try pinging, all dropped, like the trace route would suggest.
I have had this issue with other sites and games with rogers before, it was resolved by telling(with trace info ect.) them and waiting for it to be fixed.
|
Fred FourTwenty
|
Posted - 2006.11.30 04:30:00 -
[20]
Edited by: Fred FourTwenty on 30/11/2006 04:30:22 .. doh double ...
|
|
Dailey
|
Posted - 2006.11.30 04:36:00 -
[21]
geez, I wasn't refuting that you start with you isp. Just saying it's out of their hands. I only take that stance because I've been in the position where our ISP or whatever was down, and our clients where blaming us. We notified the responsible parties, but that's as far as we could go. Same for the ISP. Plus, I'm also saying it's not just one friggin' router. There are a lot of resolution problems tonight. I'm in the US, I have access to two totally different broadband lines, one is in NJ, and one in TN, neither resolve to Eve's server. So maybe, just maybe, it's on a much larger scale then your ISP can be concerned with.
|
Fred FourTwenty
|
Posted - 2006.11.30 04:39:00 -
[22]
The more people concerned with it the better, why shouldn't I concern them because I can, and if, just IF there may be something wrong they can fix or get fixed, job well done. If it is no help, oh well i made a call center employees night one call more interesting.
|
Dailey
|
Posted - 2006.11.30 04:42:00 -
[23]
You're right. I've had far to much scotch. I dunno why I'm defending some friggin' ISP. lol
Whatever the problem is, I wish someone would friggin' fix it. I just wanna play some eve before sayin' g'night. seesh. *cries into my drink*
|
Fred FourTwenty
|
Posted - 2006.11.30 04:45:00 -
[24]
Originally by: Dailey
Whatever the problem is, I wish someone would friggin' fix it. I just wanna play some eve before sayin' g'night. seesh. *cries into my drink*
I'll drink to that, *cheers*
|
Pinpisa Jormao
|
Posted - 2006.11.30 05:03:00 -
[25]
(Taken at 0440 evetime Nov 30)
Working from non-cogent: #1
13 114 ms 115 ms 115 ms so-0-0-0-dcr1.nyk.cw.net [195.2.10.109] 14 115 ms 115 ms 114 ms 66.185.92.25 15 135 ms 136 ms 137 ms gw02.bloor.phub.net.cable.rogers.com [66.185.81.14] 16 136 ms 137 ms 137 ms gw02.ym.phub.net.cable.rogers.com [66.185.80.186] 17 137 ms 137 ms 137 ms gw01.ym.phub.net.cable.rogers.com [66.185.80.209] 18 137 ms 137 ms 136 ms gw03.ym.phub.net.cable.rogers.com [66.185.94.56]
#2 13 114 ms 115 ms 115 ms so-0-0-0-dcr1.nyk.cw.net [195.2.10.109] 14 115 ms 115 ms 114 ms 66.185.92.25 15 135 ms 136 ms 137 ms gw02.bloor.phub.net.cable.rogers.com [66.185.81.14] 16 136 ms 137 ms 137 ms gw02.ym.phub.net.cable.rogers.com [66.185.80.186] 17 137 ms 137 ms 139 ms gw01.ym.phub.net.cable.rogers.com [66.185.80.213] 18 137 ms 137 ms 137 ms gw03.ym.phub.net.cable.rogers.com [66.185.90.17]
From CCP's ISP: http://lg.level3.net/traceroute/traceroute.cgi?site=lon1&target=66.185.94.56
Show Level 3 (London, England) Traceroute to 66.185.94.56 (gw03.ym.phub.net.cable.rogers.com)
1 ae-29-56.ebr2.London1.Level3.net (4.68.116.190) 0 msec ae-19-55.ebr1.London1.Level3.net (4.68.116.158) 8 msec ae-19-53.ebr1.London1.Level3.net (4.68.116.94) 4 msec 2 * * ae-1-100.ebr2.London1.Level3.net (4.69.132.118) 4 msec 3 ae-11-53.car1.NewYork1.Level3.net (4.68.97.84) 184 msec * ae-4.ebr1.NewYork1.Level3.net (4.69.132.109) 72 msec 4 cogent-level3-ge.NewYork1.Level3.net (4.68.111.46) 68 msec cogent-level3-ge.NewYork1.Level3.net (4.68.111.42) 68 msec ae-11-55.car1.NewYork1.Level3.net (4.68.97.148) 68 msec 5 p15-0.core02.jfk02.atlas.cogentco.com (66.28.4.14) [AS174 {COGENT}] 68 msec cogent-level3-ge.NewYork1.Level3.net (4.68.111.46) 68 msec cogent-level3-ge.NewYork1.Level3.net (4.68.111.42) 340 msec 6 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) [AS174 {COGENT}] 92 msec 128 msec p15-0.core02.jfk02.atlas.cogentco.com (66.28.4.14) [AS174 {COGENT}] 68 msec 7 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) [AS174 {COGENT}] 92 msec p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) [AS174 {COGENT}] 92 msec 92 msec 8 * * p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) [AS174 {COGENT}] 92 msec 9 * * * ...
From Cogent router using http://ops.rogerstelecom.net/
Tracing the route to gw03.ym.phub.net.cable.ROGERS.com (66.185.94.56)
1 38.112.10.213 [AS 174] 0 msec 0 msec 0 msec 2 g0-7.core01.dca01.atlas.cogentco.com (66.28.6.189) [AS 174] 4 msec 0 msec 4 msec 3 p6-0.core01.jfk02.atlas.cogentco.com (66.28.4.82) [AS 174] 8 msec 8 msec 4 msec 4 p15-0.core02.jfk02.atlas.cogentco.com (66.28.4.14) [AS 174] 4 msec 4 msec 8 msec 5 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) [AS 174] 36 msec 32 msec 32 msec 6 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) [AS 174] 36 msec 32 msec 32 msec 7 * * * ...
If their sht worked it'd failover to another route but in this case there seems to be problem with that as some of the routers are accessible from cogent and some not while all of them are accessible from my location. |
Aceonfire's Prostitute
|
Posted - 2006.11.30 05:19:00 -
[26]
I am replying on behalf of severel other Rogers customers, none of whome can connect to the forums, or TQ server. I'm sure there are many more, but since they can't access the website, they can't complain about their problem.
It has only happened since the patch / extra nodes/hardware was added, so if CCP would please look into it, there are quite a few people still unable to play.
|
Water Star
|
Posted - 2006.11.30 05:35:00 -
[27]
yes, finding a proper, working proxy server is not easy for a lot people...
|
Fred FourTwenty
|
Posted - 2006.11.30 05:46:00 -
[28]
Originally by: Water Star yes, finding a proper, working proxy server is not easy for a lot people...
Finding a working unsecured and 'pirating'(er) it or slow and public proxy server and lagging, sounds fun, i'll just settle for that.
|
McLearen
|
Posted - 2006.11.30 06:01:00 -
[29]
I am using secureIX proxy to view this and it works well, i am not lagging to bad and my speeds are maybe 20% slower than norm. But I really shouldnt have to do this. Rogers or CCP needs to sort this out. I ll try a Bell sympatico connection.
|
Simoyd
|
Posted - 2006.11.30 07:53:00 -
[30]
Edited by: Simoyd on 30/11/2006 07:57:13 I called up rogers and the dude said he's recieved a couple calls about the problem. He understands the fact that the service (eve) is up and the fact that rogers users cannot connect. He made a support ticket (as he did with the other callers).
Basically the more people that call rogers and tell them that they want the problem fixed, the faster the problem will be fixed. The more tickets means that the people who actually fix things will see a trend and get it fixed. The more information for different people, the faster the problem get's fixed.
I asked him if it was a good idea to tell people on this forum to call in if it's happening to them and he said it was probably a good idea. SO, if you are on rogers, and are unable to connect to this website (LOL), then please call rogers and inform them (politely) that eve-online doesn't work for you.
the more the marrier. tell your friends to do the same (the ones on rogers).
edit: the number is: 1-888-ROGERS1 (1-888-764-3771)
|
|
|
|
|
Pages: [1] 2 3 :: one page |
First page | Previous page | Next page | Last page |