PDA

View Full Version : JP PSO2 Request from connected player... (NON VPN / PZ)



Azazel7108
Jul 10, 2014, 07:23 PM
First off I you Cox IP.

Ok I was asked from my ISP lv2 tech to request if anyone from an IP that can connect to pso2.jp (with out the use of a VPN or PingZapper) would be willing to run a trace in your command prompt showing that you can connect. Its a long shot but I am willing to try this to get this blacklist unblocked.

If your not willing to help understand but plz do not bring ill posts. We have had enough drama due to this in the past. I'm just trying to fix this problems.

ArcaneTechs
Jul 10, 2014, 07:29 PM
comcast asked something similar as well for this, reverse tracert

Noc Codez
Jul 10, 2014, 07:40 PM
Sure thing give me a min and i'll post my route.. Anything to help I warn you it's going to be long.. BTW ISP Verizon



Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 5 ms lo0-100.NYCMNY-VFTTP-312.verizon-gni.net [173.56
.244.1]
3 10 ms 6 ms 8 ms T2-0-0-0.NYCMNY-LCR-21.verizon-gni.net [100.41.1
94.114]
4 8 ms 6 ms 6 ms ae3-0.NY325-BB-RTR1.verizon-gni.net [130.81.199.
162]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 92 ms 100 ms 114 ms 0.ae2.XL3.LAX15.ALTER.NET [140.222.227.19]
10 85 ms 84 ms 82 ms TenGigE0-6-0-10.GW5.LAX15.ALTER.NET [152.63.112.
97]
11 72 ms 73 ms 72 ms kddia-gw.customer.alter.net [152.179.21.114]
12 71 ms 72 ms 72 ms lajbb002.int-gw.kddi.ne.jp [59.128.2.29]
13 172 ms 172 ms 173 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.45]
14 175 ms 175 ms 174 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
15 165 ms 166 ms 165 ms 125.29.25.94
16 168 ms 167 ms 170 ms 203.141.47.218
17 178 ms 178 ms 178 ms ae1.tnhcr02.idc.jp [158.205.134.10]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 172 ms 172 ms 172 ms 158.205.188.253
22 178 ms 187 ms 177 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
23 169 ms 165 ms 165 ms 158.205.104.60
24 167 ms 168 ms 168 ms 210.189.209.8
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Dragonlily
Jul 10, 2014, 08:03 PM
My tech asked me to give a tracert for a Working connection to pso2.jp or the servers too. I asked in my Cox Users thread but I don't think ppl that can connect read that one lol. So for those who can connect, give us a couple different tracerts proving you can connect!!! Tyvm <3

Gardios
Jul 10, 2014, 08:09 PM
Getting a tracert from a European player would be swell as well.

Azazel7108
Jul 11, 2014, 12:29 AM
thx for the help. I'm great full. if anyone else would be willing to do this to assist others that need this for Comcast & other ISPs.

Again thank you.

landman
Jul 11, 2014, 02:54 AM
I know of another user of the same ISP as me that can connect, this is a trace from Spain:



Traza a la direcci¢n pso2.jp [210.189.209.8]
sobre un m ximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 31 ms 29 ms 31 ms 1.64.17.95.dynamic.jazztel.es [95.17.64.1]
3 30 ms 31 ms 31 ms 10.255.129.254
4 30 ms 34 ms 30 ms 121.217.106.212.static.jazztel.es [212.106.217.121]
5 31 ms 31 ms 31 ms 118.217.106.212.static.jazztel.es [212.106.217.118]
6 30 ms 32 ms 32 ms 193.159.167.209
7 341 ms 341 ms 341 ms tyo-sa3-i.TYO.JP.NET.DTAG.DE [62.154.5.210]
8 317 ms 345 ms 508 ms as4725.ix.jpix.ad.jp [210.171.224.48]
9 302 ms 301 ms 302 ms STOrc-01Te0-4-0-2.nw.odn.ad.jp [143.90.149.45]
10 317 ms 317 ms 316 ms STOrs-01Te0-1-0-0.nw.odn.ad.jp [143.90.47.6]
11 312 ms 309 ms 308 ms 146.143090232.odn.ne.jp [143.90.232.146]
12 * * * Tiempo de espera agotado para esta solicitud.
13 * 305 ms 303 ms softbank221111068022.bbtec.net [221.111.68.22]
14 302 ms 302 ms 303 ms 203.141.47.218
15 302 ms 301 ms 302 ms ae1.tnhcr02.idc.jp [158.205.134.10]
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * 309 ms 309 ms 158.205.188.253
20 301 ms 301 ms 302 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
21 315 ms 316 ms 320 ms 158.205.104.60
22 314 ms 314 ms 313 ms 210.189.209.8
23 * * * Tiempo de espera agotado para esta solicitud.
24 * * * Tiempo de espera agotado para esta solicitud.
25 * * * Tiempo de espera agotado para esta solicitud.
26 * * * Tiempo de espera agotado para esta solicitud.
27 * * * Tiempo de espera agotado para esta solicitud.
28 * * * Tiempo de espera agotado para esta solicitud.
29 * * * Tiempo de espera agotado para esta solicitud.
30 * * * Tiempo de espera agotado para esta solicitud.

Traza completa.

FireswordRus
Jul 11, 2014, 03:46 AM
Russia, Murmansk.
ISP Rostelecom
http://www.rostelecom.ru/en/about/net/magistr/

Трассировка маршрута к pso2.jp [210.189.209.8]
с максимальным числом прыжков 30:

1 2 ms 1 ms 1 ms 10.17.255.253
2 2 ms 1 ms 1 ms se100.kolatelecom.ru [94.100.192.1]
3 3 ms 2 ms 2 ms peer-KolaTelecom [77.73.136.89]
4 2 ms 2 ms 2 ms 188.128.3.89
5 133 ms 137 ms 133 ms 95.167.91.155
6 170 ms 161 ms 164 ms 188.254.55.226
7 160 ms 160 ms 160 ms otejbb206.int-gw.kddi.ne.jp [106.187.6.165]
8 152 ms 156 ms 152 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
9 153 ms 153 ms 153 ms 125.29.25.94
10 157 ms 162 ms 157 ms 203.141.47.218
11 160 ms 156 ms 160 ms ae1.tnhcr02.idc.jp [158.205.134.10]
12 * * * Превышен интервал ожидания для запроса.
13 * * * Превышен интервал ожидания для запроса.
14 * * * Превышен интервал ожидания для запроса.
15 165 ms 161 ms 161 ms 158.205.188.253
16 157 ms 160 ms 157 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
17 162 ms 157 ms 157 ms 158.205.104.60
18 162 ms 161 ms 165 ms 210.189.209.8
19 * * * Превышен интервал ожидания для запроса.
20 * * * Превышен интервал ожидания для запроса.
21 * * * Превышен интервал ожидания для запроса.
22 * * * Превышен интервал ожидания для запроса.
23 * * * Превышен интервал ожидания для запроса.
24 * * * Превышен интервал ожидания для запроса.
25 * * * Превышен интервал ожидания для запроса.
26 * * * Превышен интервал ожидания для запроса.
27 * * * Превышен интервал ожидания для запроса.
28 * * * Превышен интервал ожидания для запроса.
29 * * * Превышен интервал ожидания для запроса.
30 * * * Превышен интервал ожидания для запроса.

Трассировка завершена.

Aslani
Jul 11, 2014, 06:55 AM
been able to connect for about a week now through brighthouse in alabama.

Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 8 ms 7 ms ten7-0-0.bham15-ser2.bhn.net [72.31.207.44]
4 9 ms 9 ms 11 ms ten9-0-0.bham01-ser4.bhn.net [72.31.206.148]
5 23 ms 25 ms 26 ms 72-31-206-218.net.bhntampa.com [72.31.206.218]
6 22 ms 23 ms 26 ms 72-31-237-200.net.bhntampa.com [72.31.237.200]
7 26 ms 27 ms 28 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66
.109.6.96]
8 80 ms 87 ms 83 ms ae-0-0.a1.pit75.tbone.rr.com [66.109.1.70]
9 86 ms 85 ms 83 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
10 84 ms 84 ms 87 ms ae-3-0.cr0.lax30.tbone.rr.com [66.109.6.0]
11 81 ms 82 ms 82 ms ae3.pr1.lax10.tbone.rr.com [107.14.19.56]
12 82 ms 81 ms 84 ms unk-426d075a.adelphiacom.net [66.109.7.90]
13 83 ms 82 ms 83 ms lajbb001.kddnet.ad.jp [59.128.2.173]
14 191 ms 189 ms 190 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.13]
15 216 ms 183 ms 182 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
16 186 ms 187 ms 194 ms 125.29.25.94
17 202 ms 180 ms 181 ms 203.141.47.218
18 185 ms 189 ms 185 ms ae1.tnhcr02.idc.jp [158.205.134.10]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 189 ms 189 ms 191 ms 158.205.188.253
23 199 ms 195 ms 199 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
24 184 ms 184 ms 187 ms 158.205.104.60
25 191 ms 191 ms 191 ms 210.189.209.8
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Azazel7108
Jul 11, 2014, 05:53 PM
Thx guys.

moorebounce
Jul 11, 2014, 06:15 PM
Here's mine. I use TWC


Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 18 ms 15 ms 142.254.148.1
3 12 ms 15 ms 12 ms agg25-1306.clmcohib01r.midwest.rr.com [184.59.243.161]
4 32 ms 19 ms 20 ms tge0-4-0-1.clmkohpe07r.midwest.rr.com [65.29.17.136]
5 17 ms 17 ms 13 ms 65.29.1.34
6 41 ms 40 ms 42 ms bu-ether35.cr0.chi30.tbone.rr.com [107.14.19.60]
7 86 ms 92 ms 83 ms bu-ether15.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.227]
8 83 ms 83 ms 87 ms ae-0-0.cr0.lax30.tbone.rr.com [66.109.6.5]
9 80 ms 79 ms 79 ms ae3.pr1.lax10.tbone.rr.com [107.14.19.56]
10 117 ms 86 ms 201 ms unk-426d075a.adelphiacom.net [66.109.7.90]
11 85 ms 88 ms 87 ms lajbb001.kddnet.ad.jp [59.128.2.173]
12 186 ms 182 ms 197 ms otejbb205.int-gw.kddi.ne.jp [203.181.100.9]
13 171 ms 171 ms 202 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.52]
14 181 ms 182 ms 188 ms 125.29.25.94
15 198 ms 199 ms 197 ms 203.141.47.218
16 177 ms 181 ms 179 ms ae1.tnhcr02.idc.jp [158.205.134.10]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 187 ms 173 ms 171 ms 158.205.188.253
21 192 ms 188 ms 190 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
22 177 ms 172 ms 181 ms 158.205.104.60
23 202 ms 192 ms 196 ms 210.189.209.8
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Taskus
Jul 11, 2014, 06:29 PM
^ I also use TWC and have been able to connect without pz since the 7/2 maint


Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 38 ms 28 ms 31 ms cpe-76-171-80-1.socal.res.rr.com [76.171.80.1]
3 10 ms 12 ms 11 ms tge7-1.orngcaho01h.socal.rr.com [76.166.13.141]
4 13 ms 11 ms 15 ms tge0-10-0-1.grgvcabt01r.socal.rr.com [72.129.29.226]
5 19 ms 15 ms 15 ms agg23.lsancarc01r.socal.rr.com [72.129.29.0]
6 15 ms 15 ms 15 ms 107.14.19.32
7 18 ms 15 ms 15 ms ae-0-0.cr0.lax30.tbone.rr.com [66.109.6.5]
8 25 ms 13 ms 15 ms ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
9 14 ms 15 ms 16 ms unk-426d075a.adelphiacom.net [66.109.7.90]
10 52 ms 16 ms 15 ms lajbb002.kddnet.ad.jp [59.128.2.177]
11 129 ms 134 ms 127 ms otejbb206.int-gw.kddi.ne.jp [203.181.100.45]
12 121 ms 118 ms 121 ms cm-ote257.int-gw.kddi.ne.jp [118.155.197.180]
13 118 ms 133 ms 117 ms 125.29.25.94
14 121 ms 121 ms 117 ms 203.141.47.218
15 124 ms 124 ms 126 ms ae1.tnhcr02.idc.jp [158.205.134.10]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 120 ms 120 ms 120 ms 158.205.188.253
20 137 ms 143 ms 137 ms lag3.l303.ta1.eg.idc.jp [158.205.188.250]
21 132 ms 129 ms 145 ms 158.205.104.60
22 121 ms 121 ms 121 ms 210.189.209.8
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Commander A9
Jul 11, 2014, 11:31 PM
Ehh...I can't...but here's my tracenet data anyway...

Comcast out of New Jersey, USA.

C:\Users\Commander A9>tracert pso2.jp

Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 10.0.0.1
2 33 ms 21 ms 28 ms 69.142.80.1
3 9 ms 10 ms 9 ms te-1-2-ur01.brownsmills.nj.panjde.comcast.net [6
8.87.215.149]
4 10 ms 10 ms 10 ms 68.85.192.54
5 11 ms 12 ms 10 ms te-1-3-ur01.medford.nj.panjde.comcast.net [68.85
.35.246]
6 11 ms 12 ms 26 ms xe-18-0-3-0-ar03.audubon.nj.panjde.comcast.net [
68.85.158.13]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * he-3-5-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.97
] reports: Destination net unreachable.

Trace complete.


I'm trying to determine what Comcast's tech support email is so I can inform them of, well, our issues and see what they can do for us.

Strangely enough, this website at least allowed me to access what appears to be Sega's Japanese-based website: http://unblocksit.es/en/2/unblock/sega.jp/

Wonder if there's some kind of way that this could be incorporated into our means...

...I wonder if port-forwarding would work...

Chik'Tikka
Jul 12, 2014, 12:17 AM
Sega.jp, nor cha.isao.jp have ever been inaccessible even during the DDoS+^_^+ SEGA uses a wholly different IP range for their main site [54.178.254.234] which according to Google belongs to Amazon Technologies ISP and not Yahoo+^_^+ either way, global ISPs already have a route to Sega.jp and that hasn't changed since like 2001+^_^+

as for that site, it uses a proxy, you forward info to unblocksit.es, then unblocksit.es forwards your info to that site, that site then sends info to unblocksit.es, then unblocksit.es sends it to you, acting like a middle man+^_^+

tl;dr, that unblock thing is a proxy/VPN for websites+^_^+