cant connect

anyone else haveing this problem??

was online and it kicked me off

connecting to guildwars??

i had that problem a few times but i know wat my problem was.
the internet provider was doing some maintainance work, i kept connecting and disconnecting and everytime i wanted to reconnect quickly it just froze at connecting to guildwars. so maybe its ur internet

hmm
my internet is up

hasnt gone down

you conected to gw?

yeh im connected to gw but when i get that problem u get its from my internet

Proto Local Address Foreign Address State PID
TCP xp333:2631 206-127-148-45.plaync.com:http SYN_SENT 2872
[Gw.exe]

TCP xp333:2620 209-0-90-137.plaync.com:http ESTABLISHED 2872
[Gw.exe]

TCP xp333:2621 222.231.12.56:http ESTABLISHED 2872
[Gw.exe]

TCP xp333:2622 206-127-145-17.plaync.com:http ESTABLISHED 2872
[Gw.exe]

whats yours netstat-b look like

ok u just lost me right there.
how do i get those stats

open command prompt from run in start menu
and typ

netstat -b

oh type cmd from run

any stats?

this sucks

i was ingame

bout to sell my grognars sword for 70k

and i got kicked out of game and cant reconnect

it seeam i cant ping any of the us servers

east us
Pinging 209.0.88.72 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

west us
Pinging 206.127.149.36 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 206.127.149.36:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


i can ping the eu server though
eu
Pinging 206.127.145.228 with 32 bytes of data:

Reply from 206.127.145.228: bytes=32 time=130ms TTL=244
Reply from 206.127.145.228: bytes=32 time=130ms TTL=244
Reply from 206.127.145.228: bytes=32 time=131ms TTL=244
Reply from 206.127.145.228: bytes=32 time=128ms TTL=244


anyone from the midwest online?

west server
Tracing route to 206-127-149-36.plaync.com [206.127.149.36]
over a maximum of 30 hops:

1 6 ms 7 ms 6 ms 10.61.160.1
2 7 ms 6 ms 6 ms gig4-0.kscymonort-rtr1.kc.rr.com [24.94.161.169]
3 8 ms 9 ms 7 ms srp14-0.kscymordc-rtr1.kc.rr.com [24.31.239.1]
4 16 ms 7 ms 8 ms srp14-0.kscymordc-rtr4.kc.rr.com [24.94.160.194]
5 16 ms 9 ms 9 ms so0-0-0.kscymoL3-rtr1.kc.rr.com [24.94.160.1]
6 20 ms 7 ms 11 ms pop1-kcy-P6-0.atdn.net [66.185.142.25]
7 8 ms 7 ms 8 ms bb2-kcy-P0-0.atdn.net [66.185.137.226]
8 20 ms 20 ms 19 ms bb2-dls-P6-0.atdn.net [66.185.152.128]
9 20 ms 19 ms 20 ms pop2-dls-P1-0.atdn.net [66.185.133.99]
10 28 ms 35 ms 28 ms so-2-1-0.edge1.Dallas1.Level3.net [66.185.133.190]
11 29 ms 28 ms 28 ms so-1-2-0.bbr2.Dallas1.Level3.net [209.244.15.165]
12 68 ms 58 ms 81 ms as-1-0.bbr2.LosAngeles1.Level3.net [64.159.0.246]
13 61 ms 59 ms 60 ms ae-13-55.car3.LosAngeles1.Level3.net [4.68.102.142]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

east server
Tracing route to 209-0-88-72.plaync.com [209.0.88.72]
over a maximum of 30 hops:

1 6 ms 6 ms 7 ms 10.61.160.1
2 8 ms 7 ms 5 ms gig4-0.kscymonort-rtr1.kc.rr.com [24.94.161.169]
3 9 ms 7 ms 8 ms srp14-0.kscymordc-rtr1.kc.rr.com [24.31.239.1]
4 7 ms 7 ms 7 ms srp14-0.kscymordc-rtr3.kc.rr.com [24.94.160.193]
5 19 ms 18 ms 17 ms so0-0-0.chcgilL3-rtr1.kc.rr.com [24.94.160.5]
6 17 ms 18 ms 18 ms pop1-chi-P7-0.atdn.net [66.185.136.109]
7 18 ms 19 ms 17 ms Limelight.atdn.net [66.185.150.222]
8 67 ms 77 ms 57 ms agg1-6-1.ar1.ord.llnw.net [68.142.72.206]
9 87 ms 87 ms 86 ms so1-5-2.ar1.lga.llnw.net [69.28.172.238]
10 88 ms 97 ms 85 ms so1-5-1.ar1.iad.llnw.net [69.28.172.169]
11 60 ms 49 ms 49 ms ag1-21.fr1.iad.llnw.net [69.28.156.161]
12 * * * Request timed out.
13 *

can you tell me if those are the correct ip's for the servers
you can find this out easily by running netstat-b while your connected to the game

You are not alone.

I'm getting the exact same tracert results. Playing from the midwest, also using Road Runner.



And you might want to have a look at this here thread.



Final edit: And then for some reason, the connection worked after a reboot.

whoooo im back in

i can ping west coast server cant ping east coast server still

west coast
Tracing route to 206-127-149-36.plaync.com [206.127.149.36]
over a maximum of 30 hops:

1 24 ms 35 ms 40 ms 10.61.160.1
2 43 ms 55 ms 52 ms gig4-0.kscymonort-rtr1.kc.rr.com [24.94.161.169]
3 52 ms 59 ms 54 ms srp14-0.kscymordc-rtr1.kc.rr.com [24.31.239.1]
4 26 ms 28 ms 24 ms srp14-0.kscymordc-rtr4.kc.rr.com [24.94.160.194]
5 28 ms 39 ms 39 ms so0-0-0.kscymoL3-rtr1.kc.rr.com [24.94.160.1]
6 8 ms 8 ms 17 ms pop1-kcy-P6-0.atdn.net [66.185.142.25]
7 21 ms 18 ms 19 ms bb2-kcy-P0-0.atdn.net [66.185.137.226]
8 55 ms 49 ms 54 ms bb2-dls-P6-0.atdn.net [66.185.152.128]
9 36 ms 59 ms 55 ms pop2-dls-P1-0.atdn.net [66.185.133.99]
10 34 ms 38 ms 29 ms so-2-1-0.edge1.Dallas1.Level3.net [66.185.133.190]
11 63 ms 41 ms 59 ms so-1-2-0.bbr2.Dallas1.Level3.net [209.244.15.165]
12 78 ms 95 ms 79 ms ae-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.125]
13 69 ms 64 ms 59 ms ae-23-54.car3.LosAngeles1.Level3.net [4.68.102.110]
14 81 ms 85 ms 86 ms 206-127-157-1.plaync.com [206.127.157.1]
15 78 ms 106 ms 71 ms 206-127-157-82.plaync.com [206.127.157.82]
16 62 ms 54 ms 55 ms 206-127-149-36.plaync.com [206.127.149.36]

east coastTracing route to 209-0-88-72.plaync.com [209.0.88.72]
over a maximum of 30 hops:

1 22 ms 29 ms 14 ms 10.61.160.1
2 30 ms 36 ms 39 ms gig4-0.kscymonort-rtr1.kc.rr.com [24.94.161.169]
3 50 ms 43 ms 52 ms srp14-0.kscymordc-rtr1.kc.rr.com [24.31.239.1]
4 49 ms 52 ms 67 ms srp14-0.kscymordc-rtr3.kc.rr.com [24.94.160.193]
5 77 ms 80 ms 74 ms so0-0-0.chcgilL3-rtr1.kc.rr.com [24.94.160.5]
6 22 ms 34 ms 29 ms pop1-chi-P7-0.atdn.net [66.185.136.109]
7 66 ms 46 ms 47 ms Limelight.atdn.net [66.185.150.222]
8 99 ms 91 ms 100 ms agg1-6-1.ar1.ord.llnw.net [68.142.72.206]
9 142 ms 167 ms 115 ms so1-5-2.ar1.lga.llnw.net [69.28.172.238]
10 86 ms 86 ms 91 ms so1-5-1.ar1.iad.llnw.net [69.28.172.169]
11 54 ms 48 ms 55 ms ag1-21.fr1.iad.llnw.net [69.28.156.161]
12 * * * Request timed out.
13