I am trying to get into Champion's Dawn (as are my friends and wife) and the first few times it just hung and I was able to reconnect. Now, it says I am in Champion's Dawn, but I cannot login and it times out.
Anyone else?
-DR
d
Zones down?
1 pages • Page 1
d
d
After trying a few different zones, it seems that they are all on server 216.107.245.90:6112 that I cannot connect to. Can the other people who are having problems verify that their places are on that IP or not?
Thanks
-DR
P.S. - The server's IP is both in the error as well as in the upper left hand corner when switching districts or zones.
Thanks
-DR
P.S. - The server's IP is both in the error as well as in the upper left hand corner when switching districts or zones.
I still haven't been able to connect in Kodonur Crossroads. Which is really bad, because I can not play that char at all now. Also can't connect to Guild Wars support. 2 days now. Has anyone else been able to let them know of this problem? And yes that is the same server I am having problems on.
E
Which ISPs are you guys coming from?
I have had a problem for the last 2 days playing either GW or L2 (both NCsoft games). In fact, I can't even reach www.guildwars.com (206.127.153.163) or www.lineage2.com (206.127.153.147). Both sites are not reachable to me. But funny thing is I can reach two of their other web servers: www.cityofheroes.com (206.127.153.137) and www.plaync.com (206.127.153.160). All of these are on the same subnet so WTF? Rest of the sites I visit are fine.
Even funnier is that if I go in through another ISP I have no issues. Just have the issue via AT&T. I have had limited contact (via email) from NC's support but they are VERY slow and told me its a browser cache problem.. LAME. AT&T has been actively looking into it but they can't figure it out.
I have had a problem for the last 2 days playing either GW or L2 (both NCsoft games). In fact, I can't even reach www.guildwars.com (206.127.153.163) or www.lineage2.com (206.127.153.147). Both sites are not reachable to me. But funny thing is I can reach two of their other web servers: www.cityofheroes.com (206.127.153.137) and www.plaync.com (206.127.153.160). All of these are on the same subnet so WTF? Rest of the sites I visit are fine.
Even funnier is that if I go in through another ISP I have no issues. Just have the issue via AT&T. I have had limited contact (via email) from NC's support but they are VERY slow and told me its a browser cache problem.. LAME. AT&T has been actively looking into it but they can't figure it out.
d
d
So, more interesting info for you all...
I talked with AT&T and they are pretty much convinced that it is not in their network. In all fairness, I sorta believe them. The guy didn't jerk me around and went out of his way to help me diagnose the issue.
Here is some interesting info though:
This is a trace on my home network out to the server I cannot reach. As you can see, I make it out of AT&T just fine, but when I hit the last reachable IP, it stops. Now...
This is a trace to a server I can reach. It looks like I reach it just fine and they stop returning hops after some point. Understandable, I guess. The interesting thing to note is that both these traces hit 151.164.189.12, but after that it does not work and they try to hit different IPs.
AT&T said these IPs are not theirs, so they really can't help me. I have forwarded this info to NCSoft, but they haven't responded to my ticket in over 48 hours.
Here is another monkey wrench. I can connect fine at my friend's comcast account and through my work VPN. That makes me think it is AT&T, but they claim these are not their IPs.
Anyway... just wanted to share.
-DR
I talked with AT&T and they are pretty much convinced that it is not in their network. In all fairness, I sorta believe them. The guy didn't jerk me around and went out of his way to help me diagnose the issue.
Here is some interesting info though:
Code:
Tracing route to 216-107-245-90.plaync.com [216.107.245.90] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.0.1 2 7 ms 7 ms 7 ms adsl-75-10-111-254.dsl.frs2ca.sbcglobal.net [75. 10.111.254] 3 7 ms 9 ms 7 ms dist1-vlan60.frsn02.pbi.net [66.122.172.66] 4 7 ms 6 ms 6 ms 151.164.189.12 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * 151.164.190.68 reports: Destination host unreachable. Trace complete.
Code:
Tracing route to 216-107-245-74.plaync.com [216.107.245.74] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.0.1 2 7 ms 7 ms 7 ms adsl-75-10-111-254.dsl.frs2ca.sbcglobal.net [75. 10.111.254] 3 7 ms 7 ms 7 ms dist1-vlan60.frsn02.pbi.net [66.122.172.66] 4 7 ms 6 ms 7 ms 151.164.189.12 5 16 ms 16 ms 16 ms 151.164.95.218 6 24 ms 23 ms 24 ms tge8-4.fr3.sjc.llnw.net [208.111.152.69] 7 26 ms 25 ms 25 ms tge1-1.fr4.lax.llnw.net [69.28.171.117] 8 35 ms 24 ms 24 ms ve6.fr3.lax.llnw.net [69.28.171.205] 9 * * * Request timed out. 10 * * * Request timed out.
AT&T said these IPs are not theirs, so they really can't help me. I have forwarded this info to NCSoft, but they haven't responded to my ticket in over 48 hours.
Here is another monkey wrench. I can connect fine at my friend's comcast account and through my work VPN. That makes me think it is AT&T, but they claim these are not their IPs.
Anyway... just wanted to share.
-DR
E
My trace is similar...
Good (www.cityofheroes.com at 206.127.153.137):
Bad (www.lineage2.com at 206.127.153.147 or www.guildwars.com at 206.127.153.151):
Reverse lookups of the IPs *suggest* that the 71.145.*.* subnets are owned by Alcatel but I think it's really AT&T... the 151.164.*.* subnets are said to be owned by AT&T.
From your trace and mine, it looks like something is going haywire between the 151.164.*.* subnet which is AT&T and LLNW which is Limelight Networks.
The interesting thing again is that some sites at NC work fine and some do not which means that the problematic hop in the middle is dropping only certain packet paths.
Good (www.cityofheroes.com at 206.127.153.137):
Code:
... 2 22 ms 21 ms 21 ms 76-247-188-2.lightspeed.sntcca.sbcglobal.net [76.247.188.2] 3 31 ms 22 ms 22 ms 71.145.12.194 4 22 ms 25 ms 21 ms 71.145.0.12 5 22 ms 22 ms 23 ms 71.145.0.4 6 21 ms 21 ms 21 ms 151.164.43.214 7 22 ms 22 ms 22 ms 151.164.95.218 8 27 ms 24 ms 25 ms tge8-4.fr3.sjc.llnw.net [208.111.152.69] 9 23 ms 23 ms 23 ms ve5.fr4.sjc.llnw.net [69.28.171.210] 10 71 ms 71 ms 74 ms tge1-1.fr3.ord.llnw.net [69.28.171.65] 11 70 ms 71 ms 71 ms ve6.fr4.ord.llnw.net [69.28.172.42] 12 101 ms 101 ms 101 ms tge11-3.fr3.lga.llnw.net [69.28.171.194] 13 108 ms 101 ms 101 ms tge2-4.fr3.iad.llnw.net [69.28.171.157]
Code:
... 2 22 ms 21 ms 21 ms 76-247-188-2.lightspeed.sntcca.sbcglobal.net [76.247.188.2] 3 22 ms 22 ms 22 ms 71.145.12.194 4 23 ms 22 ms 22 ms 71.145.0.12 5 23 ms 22 ms 23 ms 71.145.0.4 6 21 ms 22 ms 21 ms 151.164.43.214 7 * * * Request timed out. 8 151.164.95.220 reports: Destination host unreachable.
From your trace and mine, it looks like something is going haywire between the 151.164.*.* subnet which is AT&T and LLNW which is Limelight Networks.
The interesting thing again is that some sites at NC work fine and some do not which means that the problematic hop in the middle is dropping only certain packet paths.
d
E
I'm using http://www.ip2location.com/free.asp.
Hopefully that resolution clears it up for me as well although it's 12:50pm right now and it's still not working yet...
Hopefully that resolution clears it up for me as well although it's 12:50pm right now and it's still not working yet...
E
d
Okay! I got it to work after forcing the issue with AT&T. I made it up to Tier 2 support and the technician eventually had to "Build me out and Build me in" to their system. After that, I appear to be connecting fine.
Funny enough, the trace is totally different too. o_O
Hope you all can get resolved too.
-DR
Funny enough, the trace is totally different too. o_O
Code:
Tracing route to 216-107-245-90.plaync.com [216.107.245.90] over a maximum of 30 hops: 1 2 ms 3 ms 1 ms pettingzoo [192.168.1.1] 2 3 ms 3 ms 3 ms 192.168.0.1 3 9 ms 9 ms 9 ms adsl-67-114-109-254.dsl.frsn02.pacbell.net [67.1 14.109.254] 4 8 ms 9 ms 10 ms dist2-vlan50.frsn02.pbi.net [66.122.172.3] 5 8 ms 9 ms 10 ms bb1-p12-0.irvnca.sbcglobal.net [151.164.189.14] 6 12 ms 13 ms 13 ms 151.164.95.198 7 15 ms 23 ms 15 ms ve318.fr4.sjc.llnw.net [208.111.152.117] 8 16 ms 16 ms 24 ms ve5.fr3.sjc.llnw.net [69.28.171.209] 9 37 ms 28 ms 26 ms tge1-1.fr4.lax.llnw.net [69.28.171.117] 10 24 ms 24 ms 25 ms ve6.fr3.lax.llnw.net [69.28.171.205] 11 * * * Request timed out.
-DR
d
Aaaannnd.... back to the drawing board...
It is that same damn server.
-DR
Code:
Tracing route to 216-107-245-54.plaync.com [216.107.245.54] over a maximum of 30 hops: 1 4 ms 2 ms 2 ms pettingzoo [192.168.1.1] 2 3 ms 2 ms 2 ms 192.168.0.1 3 9 ms 8 ms 8 ms adsl-67-114-109-254.dsl.frsn02.pacbell.net [67.1 14.109.254] 4 8 ms 8 ms 8 ms dist1-vlan60.frsn02.pbi.net [66.122.172.66] 5 8 ms 9 ms 8 ms 151.164.189.12 6 * * * Request timed out. 7 * * * Request timed out. 8 * * 151.164.95.218 reports: Destination host unreachable. Trace complete.
-DR
E
d
d
I just spent an hour and a half on the phone with AT&T. They say that Lime Light is refusing some of their IPs to be routed through them. They say that the traffic is successfully leaving their network, hitting Lime Light, and dying.
It would seem that everytime they "rebuilt" my connection I got a new IP and with it a random chance that the connection to certain servers would work, and then others that were once working stopped. -_-'
I contacted Lime Light and they had me open a trouble ticket VIA e-mail. The tech wans't helping me over the phone. I guess I will wait and see.
-DR
It would seem that everytime they "rebuilt" my connection I got a new IP and with it a random chance that the connection to certain servers would work, and then others that were once working stopped. -_-'
I contacted Lime Light and they had me open a trouble ticket VIA e-mail. The tech wans't helping me over the phone. I guess I will wait and see.
-DR
E
