Pol-1558 >_>

Not a clue but most people who have the problem mentioned that their provider is Shaw.
 
I'm on shaw and can't get on
 
Still nothing after all these hours. I did manage to log on by using HTTP-Tunneling, however, the speed was very slow. Searches took a long time, and zoning took so long I thought I disconnected. I would presume it close to dial-up.

Grumble Grumble

Shaw Edmonton
 
Cohen said:
Is the problem SHAW specific?
Click to expand...

No, the problem is not Shaw specific. Using chello from sweden, same problem.

Could anyone that is on Shaw do a traceroute to wh000.pol.com and post what it looks like after the trace leaves the shaw network?

It could help in finding out exactly where the problem is, if for example both shaw and chello go through the same network to reach Square Enix.
 
God damnit, I still can't get on
 
This is really starting to piss me off.... i want to play damn it!!!!
 
How do you tunnel a fucking connection, cause I am desperate

so fucking tired of all the outages I have experienced in the last month or 2 (A lot of the them have been because of my school's internet not being able to resolve DNS names)
 
from shaw vancouver...

traceroute to wh000.pol.com (202.67.56.55), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 0.260 ms 0.154 ms 0.113 ms
2 * * *
3 rd1bb-ge5-0-0-18.vc.shawcable.net (64.59.159.226) 18.838 ms 8.203 ms 6.544 ms
4 rc1bb-pos15-0.vc.shawcable.net (66.163.69.70) 9.060 ms 20.952 ms 7.896 ms
5 rc1wt-pos3-0.wa.shawcable.net (66.163.76.37) 12.853 ms 13.306 ms 14.034 ms
6 rc2wt-ge3-0-0.wa.shawcable.net (66.163.68.5) 13.308 ms 11.522 ms 12.255 ms
7 rx0wt-abovenet.wa.shawcable.net (66.163.68.22) 40.952 ms 12.870 ms 25.430 ms
8 so-6-3-0.mpr4.sjc2.us.above.net (64.125.28.21) 30.021 ms 30.860 ms 39.075 ms
9 so-3-1-3.mpr2.nrt3.jp.above.net (64.125.30.25) 161.835 ms 163.963 ms 158.377 ms
10 router-squareenix.nrt3.above.net (209.249.200.22) 170.307 ms 145.840 ms 143.653 ms
11 61.195.56.26 (61.195.56.26) 162.753 ms 158.592 ms 169.261 ms
12 202.67.63.45 (202.67.63.45) 161.504 ms 150.357 ms 163.214 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * 202.67.63.122 (202.67.63.122) 146.122 ms !A
22 * * *
23 * * *
24 * * *
25 * * *
26 202.67.63.122 (202.67.63.122) 158.323 ms !A * *
27 * * 202.67.63.122 (202.67.63.122) 160.375 ms !A
28 * * 202.67.63.122 (202.67.63.122) 143.960 ms !A
29 * * 202.67.63.122 (202.67.63.122) 164.406 ms !A
30 * * *
 
Tracing route to wh000.pol.com [202.67.56.55]
over a maximum of 30 hops:

2 4 ms 3 ms 5 ms c213-89-208-1.cm-upc.chello.se [213.89.208.1]
3 4 ms 4 ms 3 ms c213-200-188-13.cm-upc.chello.se [213.200.188.13]
4 5 ms 10 ms 12 ms c213-200-188-1.cm-upc.chello.se [213.200.188.1]
5 4 ms 5 ms 6 ms se-sto01a-ra2-ge-1-0-0.aorta.net [213.46.176.89]
6 29 ms 27 ms 27 ms de-fra01a-rd1-pos-14-0.aorta.net [213.46.160.161]
7 30 ms 25 ms 26 ms de-fra01a-rd2-pos-5-0.aorta.net [213.46.179.6]
8 120 ms 120 ms 121 ms us-ewr01a-rd1-pos-4-0.aorta.net [213.46.160.146]
9 196 ms 197 ms 197 ms us-sjo01a-ri1-so-1-0-0.aorta.net [213.46.190.46]
10 197 ms 200 ms 196 ms ge-2-0-0.r00.snjsca04.us.bb.verio.net [206.223.116.12]
11 202 ms 197 ms 197 ms xe-0-1-0.r20.mlpsca01.us.bb.verio.net [129.250.5.61]
12 305 ms 305 ms 311 ms p64-1-3-0.r20.tokyjp01.jp.bb.verio.net [129.250.4.42]
13 307 ms 306 ms 313 ms xe-2-0-0.a20.tokyjp01.jp.ra.verio.net [61.213.162.110]
14 299 ms 299 ms 299 ms ge-2-2-5.a20.tokyjp01.jp.ra.verio.net [61.120.145.110]
15 328 ms 439 ms 314 ms 202.67.63.45
16 306 ms 303 ms 303 ms 202.67.63.122
17 315 ms 317 ms 315 ms 202.67.56.32
18 299 ms 299 ms 303 ms 202.67.56.55

Trace complete.

No problems between for me, yet still can't get on... Not sure if the data that is sent back from the login server takes the reverse path or some other path though...
The PlayOnline client connects fine to the server, sends a normal HTTP/1.1 GET to the server, and then nothing more happens. I'm decently certain that the server actually receives the request, but what happens to the response I have no idea.
 
For those of you wanting to try HTTP Tunneling, just do what I did:
http://www.http-tunnel.com/html/

No way am I going into details, I found FAQs and How to's which were easy enough to follow. If you're desperate enough, this will work at low speeds, unless you pay for the service. That'll get you high speed through their proxy. I noted in their forums people had problems with FFXI, since they can't trace the specific TCP and UDP ports FFXI and SE use. It gets any more complicated than that, I'm out of my depth. Network specialist, I'm not.
 
Sort of update: Talked to Shaw Tech support, they're getting quite a few calls about this. They seem to think that SE or POL made a change to a DNS server (perhaps in prep for the expansion release) which will take 24-48 hours for the changes to propagate through the Internet. Every 12 hours "All" DNS information is supposedly fired around the world, and your ISPs update their DNS (Domain Name) servers when they get these packets.

I read on Alla that people were using wireless cards to try and find unsecured access points near them to log on and check their plants. How desperate are you? :p

Long story short: Wait another day, it should clear up.
 
GET /pml/main/index.pml HTTP/1.1
Host: wh000.pol.com
User-Agent: PlayOnline-PML-Viewer/1.00 [en] (Windows XP)
X-POL-VIEWER-VERSION: Ver.1.16.05
Accept: text/x-playonline-pml, image/x-playonline-ang, image/png, image/jpeg, */*
Accept-Language: en-GB
Connection: Keep-Alive
If-Modified-Since: Thu, 19 Jul 2005 07:25:43 GMT
X-PlayOnline-Want-Hello: ***********

Is the HTTP request sent by the viewer to wh000.pol.com (202.67.56.55 as reported by their own dns, and by players that CAN connect no problem).

On my connection I get zilch respone, and scanning the traffic with ethereal and checking the data afterwards indicate that the server did send a response but it never got through.

On another connection (that I can't play from unfortunately), the response gets through no problem. Same ip, same domain name.

Saying that it is DNS problems is bullshit they pull off just to get rid of people that want to know what is wrong.

If you just want to check if it's working yet or not, you can browse in to
http://wh000.pol.com:53104/pml/main/index.pml

If nothing happens, probably still problems.
If you get a message about authorization required, you might as well try with the POL viewer and see if you can get on.
 
mine is up and running
finaly~_~
 
You must log in or register to reply here.
Back
Top