Page 1 of 1
I can't connect
PostPosted:Sat Mar 16, 2019 3:14 pm
by Jack Skywalker
There's already some time I can't connect to KR server. The first time it happened I thought the server was down so I didn't come here, but now I see the server is up and it still just displays "Awaiting connection..." message forever when I try to connect. And it's not my internet cause I can play on other servers normally.
Re: I can't connect
PostPosted:Sun Mar 17, 2019 4:55 pm
by Elsecaller
D: I Hope We Can Get That Fixed Soon. We Need A Skywalker!
Re: I can't connect
PostPosted:Mon Mar 18, 2019 4:03 am
by jawfin
Try again now. I white-listed your IP so if it now works we'll know your game client behaves like a software attack - for whatever reason!
Re: I can't connect
PostPosted:Sat Mar 23, 2019 8:03 pm
by Jack Skywalker
I'll only have the opportunity to test my connection from my home IP one or two weeks from now, but I've just tried connecting from the dorm's internet (the one I'm using at this moment) and it happens the same thing. I can play on other servers but not KR.
Re: I can't connect
PostPosted:Sun Mar 24, 2019 7:00 am
by jawfin
Try again from that connection.
Re: I can't connect
PostPosted:Sat Mar 30, 2019 2:07 pm
by Jack Skywalker
I'm already home again and I tried connecting from here, but I still get the "Awaiting connection..." message. Also both KR1 and KR2 IP's are saved on my favorites list, but the server names don't appear, the list only shows their IP's like if the servers were down (Idk if that means anything).
Re: I can't connect
PostPosted:Sat Mar 30, 2019 2:26 pm
by John
Might try running command prompt and do: ping 192.223.29.244
Also might be firewall(but you said you could connect to other servers so probably not), press the windows key and type firewall and click the "Allow programs/apps through windows firewall" option and make sure jedi academy multiplayer if allowed through.
Re: I can't connect
PostPosted:Sat Mar 30, 2019 11:07 pm
by jawfin
Your home IP is definitely white-listed, the KR firewall isn't touching you. And, it never occurred to me that you'd just be trying to connect to a non-existent server, so like John said, also try connecting directly to KR via "/connect 192.223.29.244" in the JKA console.
Re: I can't connect
PostPosted:Fri Apr 05, 2019 4:01 pm
by MadonLightstorm
I just had same thing happen to me, jack skywalker, at first KR server was in my favorites and then it diseapered and I tried connecting to it said "waiting connection 1..2..3..4..5' it was if I was connecting to a server that never existed, then suddenly master server list went down, so I wanted to find KR discord or any kind, to see if this has happened to anyone, try to see what's going on around here, I sure hope jka didn't die or anything that'd be sad entirely and I hope they didn't shut off sorten things also in process.
I wanted to see who was all effected by this, was hoping someone was still left alive at kr, then I found kr's discord, login'd into it, I hope they didn't limit NA to US servers or put limitations on stuff, that'd be even more sad, cause that mean, we'd be cut off from one other, unable to see each other or friends, or old collegues , now servers that survived my favorites are JOF and JAWA and Hidden Spy's server, but KR server went blank and diseapered from list .
I must've tried like 3-5 times to add KR to my favorites it won't let me do it.
Re: I can't connect
PostPosted:Sat Apr 06, 2019 12:29 pm
by Jack Skywalker
John wrote: Might try running command prompt and do: ping 192.223.29.244
Now this is a weird result... all the packets were lost.
Re: I can't connect
PostPosted:Sun Apr 07, 2019 6:49 am
by jawfin
You could try a tracert to see how far through the hops its progressing. Here's what mine looks like from Brisbane, Australia: -
Code: Select allC:\WINDOWS\System32>tracert 192.223.29.244
Tracing route to v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 4 ms 3 ms rdl1-l101.bng.optusnet.com.au [106.70.0.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 19 ms 18 ms 19 ms 211.29.126.226
7 18 ms 18 ms 17 ms 198.142.139.112
8 175 ms 180 ms 189 ms 203.208.177.125
9 178 ms 178 ms 178 ms 203.208.172.234
10 181 ms 182 ms 181 ms te-0-2-0-0-pe02.529bryant.ca.ibone.comcast.net [75.149.231.241]
11 179 ms 180 ms 180 ms be-11083-cr02.sunnyvale.ca.ibone.comcast.net [68.86.84.13]
12 177 ms 178 ms 178 ms be-11015-cr02.losangeles.ca.ibone.comcast.net [68.86.86.98]
13 210 ms 225 ms 217 ms be-11523-cr01.houston.tx.ibone.comcast.net [68.86.87.174]
14 209 ms 220 ms 238 ms be-12324-cr02.dallas.tx.ibone.comcast.net [68.86.84.110]
15 205 ms 205 ms 320 ms be-12441-pe01.1950stemmons.tx.ibone.comcast.net [68.86.89.206]
16 208 ms 208 ms 207 ms 96-87-8-78-static.hfc.comcastbusiness.net [96.87.8.78]
17 214 ms 215 ms 215 ms border5.ae2-bbnet1.dal006.pnap.net [216.52.191.109]
18 217 ms 216 ms 221 ms inap-b2.e5.router.dallas.nfoservers.com [74.91.120.254]
19 223 ms 222 ms 222 ms v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
Trace complete.
Re: I can't connect
PostPosted:Sun Apr 07, 2019 4:37 pm
by Jack Skywalker
Mine looks like this:
Code: Select allC:\Windows\system32>tracert 192.223.29.244
Rastreando a rota para v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
com no máximo 30 saltos:
1 1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms 10.10.5.234
3 2 ms 3 ms 2 ms 10.10.5.233
4 36 ms 2 ms 2 ms 10.10.8.249
5 5 ms 7 ms 4 ms 205.22.125.189.static.impsat.net.br [189.125.22.205]
6 113 ms 112 ms 113 ms ae1-300G.ar5.MIA1.gblx.net [67.17.94.249]
7 * * * Esgotado o tempo limite do pedido.
8 * * * Esgotado o tempo limite do pedido.
9 113 ms 113 ms 113 ms mai-b1-link.telia.net [213.248.84.80]
10 127 ms 126 ms 126 ms atl-b24-link.telia.net [62.115.113.48]
11 127 ms 127 ms 130 ms atl-b22-link.telia.net [62.115.113.24]
12 143 ms 142 ms 144 ms dls-b21-link.telia.net [80.91.246.75]
13 144 ms 143 ms 143 ms internap-ic-140173-dls-bb1.c.telia.net [213.248.73.194]
14 144 ms 144 ms 144 ms border5.ae1-bbnet1.dal006.pnap.net [216.52.191.44]
15 * * * Esgotado o tempo limite do pedido.
16 * * * Esgotado o tempo limite do pedido.
17 * * * Esgotado o tempo limite do pedido.
18 * * * Esgotado o tempo limite do pedido.
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
29 * * * Esgotado o tempo limite do pedido.
30 * * * Esgotado o tempo limite do pedido.
Rastreamento concluído.
When I did the command again, the same thing happened, I got "request timed out" messages after the line with "border5.ae1-bbnet1.dal006.pnap.net [216.52.191.44]" IP.
Re: I can't connect
PostPosted:Sun Apr 07, 2019 11:21 pm
by jawfin
Some hops won't respond to a ping, they are not public facing machines, i.e. not website hosts; they are just there as Internet nodes, so won't respond to ICMP requests, thus, timeout. But, as you get closer to the server you starting to get closer to a public zone and they should be responding.
(Fun fact: did you know that *any* device online which does not treat ICMP packets correctly are not technically considered part of the Internet? Go figure.)
So it looks like your problem is upstream. As a test you could try to wifi-hotspot your phone, or USB modem it (any smart phone should be able to do either of those things these days) and see if you can connect with that. At least we will confirm whether the problem is in your PC, the Internet, or the server.
Failing all that you may just have to swing a golf ball retriever around in a garage to keep your sabering skills up!
Re: I can't connect
PostPosted:Sat Apr 13, 2019 12:46 pm
by Jack Skywalker
This is the tracert from the dorm's internet:
Code: Select allC:\WINDOWS\system32>tracert 192.223.29.244
Rastreando a rota para v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
com no máximo 30 saltos:
1 3 ms 1 ms 1 ms 192.168.0.1
2 3 ms 1 ms 1 ms 192.168.10.1
3 7 ms 7 ms 5 ms 10.10.5.42
4 3 ms 5 ms 6 ms 10.10.5.41
5 6 ms 6 ms 3 ms user.1-239-236-186.users.net-rosas.com.br [186.236.239.1]
6 9 ms 10 ms 9 ms 205.22.125.189.static.impsat.net.br [189.125.22.205]
7 115 ms 117 ms 115 ms ae1-300G.ar5.MIA1.gblx.net [67.17.94.249]
8 * * * Esgotado o tempo limite do pedido.
9 * * * Esgotado o tempo limite do pedido.
10 118 ms 116 ms 117 ms mai-b1-link.telia.net [213.248.84.80]
11 134 ms 132 ms 134 ms atl-b24-link.telia.net [62.115.114.218]
12 133 ms 178 ms 228 ms atl-b22-link.telia.net [62.115.113.24]
13 150 ms 149 ms 147 ms dls-b21-link.telia.net [80.91.246.75]
14 149 ms 147 ms 151 ms internap-ic-140173-dls-bb1.c.telia.net [213.248.73.194]
15 150 ms 147 ms 151 ms border6.ae1-bbnet1.dal006.pnap.net [216.52.191.45]
16 * * * Esgotado o tempo limite do pedido.
17 * * * Esgotado o tempo limite do pedido.
18 * * * Esgotado o tempo limite do pedido.
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
29 * * * Esgotado o tempo limite do pedido.
30 * * * Esgotado o tempo limite do pedido.
Rastreamento concluído.
This ones are using my phone's 4G internet:
Code: Select allC:\WINDOWS\system32>tracert 192.223.29.244
Rastreando a rota para v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
com no máximo 30 saltos:
1 3 ms 4 ms 2 ms 172.20.10.1
2 * * * Esgotado o tempo limite do pedido.
3 * * * Esgotado o tempo limite do pedido.
4 * * * Esgotado o tempo limite do pedido.
5 * * * Esgotado o tempo limite do pedido.
6 * * * Esgotado o tempo limite do pedido.
7 * * * Esgotado o tempo limite do pedido.
8 207 ms 100 ms 98 ms et2-0-0.rio6.rio.seabone.net [213.144.160.113]
9 147 ms 135 ms 101 ms et4-1-0.sanpaolo8.spa.seabone.net [195.22.219.75]
10 110 ms 70 ms 82 ms ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.65]
11 198 ms 214 ms 270 ms unknown.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.196]
12 226 ms 236 ms 239 ms ae-2.r21.miamfl02.us.bb.gin.ntt.net [129.250.3.134]
13 744 ms 282 ms 840 ms ae-4.r22.dllstx09.us.bb.gin.ntt.net [129.250.2.219]
14 208 ms 517 ms 246 ms ae-2.r11.dllstx09.us.bb.gin.ntt.net [129.250.5.14]
15 * 205 ms 215 ms ae-1.a01.dllstx09.us.bb.gin.ntt.net [129.250.3.30]
16 213 ms 214 ms 203 ms ae-0.internap.dllstx09.us.bb.gin.ntt.net [130.94.195.2]
17 223 ms 212 ms 207 ms border5.ae1-bbnet1.dal006.pnap.net [216.52.191.44]
18 286 ms 274 ms 306 ms inap-b2.e5.router.dallas.nfoservers.com [74.91.120.254]
19 309 ms 283 ms 292 ms v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
Rastreamento concluído.
Code: Select allC:\WINDOWS\system32>tracert 192.223.29.244
Rastreando a rota para v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
com no máximo 30 saltos:
1 3 ms 1 ms 1 ms 172.20.10.1
2 * 380 ms 327 ms 209.95.50.2.static.midphase.com [209.95.50.2]
3 240 ms 299 ms * 185.7.225.178.static.100tb.com [185.7.225.178]
4 195 ms 205 ms 262 ms be4450.rcr21.b007023-2.jfk05.atlas.cogentco.com [38.104.74.45]
5 198 ms 172 ms 191 ms be2809.ccr31.jfk05.atlas.cogentco.com [154.54.81.201]
6 178 ms 172 ms 193 ms be3294.ccr41.jfk02.atlas.cogentco.com [154.54.47.217]
7 199 ms 185 ms 178 ms be2806.ccr41.dca01.atlas.cogentco.com [154.54.40.106]
8 219 ms 217 ms 246 ms be2112.ccr41.atl01.atlas.cogentco.com [154.54.7.158]
9 332 ms 284 ms 227 ms be2687.ccr41.iah01.atlas.cogentco.com [154.54.28.70]
10 292 ms 277 ms 290 ms be2441.ccr31.dfw01.atlas.cogentco.com [154.54.41.66]
11 * 232 ms * be2938.rcr21.dfw04.atlas.cogentco.com [66.28.4.18]
12 238 ms 323 ms 280 ms be3795.nr51.b028597-0.dfw04.atlas.cogentco.com [154.24.61.202]
13 271 ms 277 ms 221 ms 38.140.239.18
14 * * 265 ms border5.ae1-bbnet1.dal006.pnap.net [216.52.191.44]
15 322 ms 388 ms 345 ms inap-b2.e5.router.dallas.nfoservers.com [74.91.120.254]
16 230 ms 227 ms * v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
17 2154 ms 511 ms 300 ms v-192-223-29-244.unman-vds.inap-dallas.nfoservers.com [192.223.29.244]
Rastreamento concluído.
I connected to the server normally using my phone's internet (despite the high ping), but I got kicked right after that... lol
Re: I can't connect
PostPosted:Sat Apr 13, 2019 8:31 pm
by Elsecaller
Have You Tried Reinstalling The Game Completely? I Don't Know If That Will Help But Its Worth A Try.
Re: I can't connect
PostPosted:Sat Apr 13, 2019 9:25 pm
by jawfin
I wasn't sure if that was you, sorry. But you did say " connect server normally" - but here is the connection you used: -
IP : 173.244.217.90
Name : -[KR]-Jack-Skywalker-
Hostname : adf4d95a.setaptr.net
ASN : 32780
ISP : WestHost
Organisation : Hosting Services Inc
Country : United States
State/Region : Kansas
City : Lenexa
That is a proxy, whether you knew it or not (maybe attached to your antivirus).
As Dorothy would say: "Toto, I've a feeling we're not in Kansas anymore".
If that's the only way you can join let me know and I'll bypass the firewall for the proxy you use.
Re: I can't connect
PostPosted:Mon Apr 15, 2019 12:53 am
by Jack Skywalker
Jawfin wrote: That is a proxy, whether you knew it or not (maybe attached to your antivirus).
This happened when I was using my phone's internet, and I don't have a proxy set on my computer (I've already used it to play on KR server before without any problem). The problem is phone 4G internet sucks to play JKA, and I also have a 100 MB use limit on it, so it wouldn't help that much if I could connect with it using the proxy. I'd really need a fix for the "Request timed out" issue to play on KR
Re: I can't connect (solved)
PostPosted:Sat Apr 27, 2019 3:28 pm
by Jack Skywalker
Update: somehow everything is working normally.
