Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

can't connect to other players in Kanes Wrath online

Started by fatihd, Jan 23 2018 07:31 PM

Best Answer fatihd, 27 January 2018 - 04:50 PM

I tried vpn again today. and its working now. In game, network option, i selected vpn ip then connect online then problem solved.

I have my own vpn server located germany. if any user have connection problem, i can give free openvpn account.

Go to the full post

Please log in to reply

13 replies to this topic

#1 fatihd

Members
10 posts

Posted 23 January 2018 - 07:31 PM

I can connect only too less players. Here is my connection test.

Using server nntest.cnc-online.net:30000

Bound to local port 62007

Bound to local alternate port 62008

Resolving hostname 'nntest.cnc-online.net'...

Resolved server host to be '37.247.49.213'

Sending client INIT from port 62007 to nntest.cnc-online.net:30000

Received server INIT [652262]

Our public address is 95.70.214.84:30107

Sending client INIT2 [652262] from port 62008 to nntest.cnc-online.net:30000

Received server INIT2 [652262]

Our alternate public address is 95.70.214.84:28828

Sending cient START [652262] from port 62008 to nntest.cnc-online.net:30000

Received server START [652262]

Server extra port is 40000

Sending client PING [652262] from port 62007 to nntest.cnc-online.net:40000

Received server PING(2) [652262]

Received server PING(3) [652262]

Received server PING(4) [652262]

===========

SUCCESS

===========

Received 3 pings from nntest.cnc-online.net:40000.

NAT negotiation works with your router and connection.

==> You do not have to use port forwarding.

Press any key to continue . . .

C:\WINDOWS\system32>ping 37.247.49.213

Pinging 37.247.49.213 with 32 bytes of data:

Reply from 37.247.49.213: bytes=32 time=55ms TTL=49

Reply from 37.247.49.213: bytes=32 time=86ms TTL=49

Reply from 37.247.49.213: bytes=32 time=84ms TTL=49

Reply from 37.247.49.213: bytes=32 time=138ms TTL=49

Ping statistics for 37.247.49.213:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 55ms, Maximum = 138ms, Average = 90ms

C:\WINDOWS\system32>ping 37.247.49.213

Pinging 37.247.49.213 with 32 bytes of data:

Reply from 37.247.49.213: bytes=32 time=79ms TTL=49

Reply from 37.247.49.213: bytes=32 time=50ms TTL=49

Reply from 37.247.49.213: bytes=32 time=49ms TTL=49

Reply from 37.247.49.213: bytes=32 time=56ms TTL=49

Ping statistics for 37.247.49.213:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 49ms, Maximum = 79ms, Average = 58ms

C:\WINDOWS\system32>

Back to top

#2 Guest_protoman1008_*

Guests

Posted 23 January 2018 - 08:09 PM

The 4th ping request does look a little high in comparison to the 1st ping request in the first test.
Using WiFi? Or a Shared internet connection?

Edited by protoman1008, 23 January 2018 - 08:11 PM.

Back to top

#3 fatihd

Members
10 posts

Posted 24 January 2018 - 08:00 AM

wifi without shared connection.

Back to top

#4 Guest_protoman1008_*

Guests

Posted 24 January 2018 - 08:52 AM

WiFi isn’t that reliable, honestly.
If you can, you could try cable instead, should give way better results and is a lot more stable in comparison to WiFi.

Back to top

#5 fatihd

Members
10 posts

Posted 24 January 2018 - 11:47 AM

cable connection is same.

Back to top

#6 Guest_protoman1008_*

Guests

Posted 24 January 2018 - 12:42 PM

Hm... I just did multiple Ping requests, all replied around the same ping results.

You can do this by typing: ping 37.247.49.213 -t

PS C:\WINDOWS\System32> ping 37.247.49.213 -t

Pinging 37.247.49.213 with 32 bytes of data:

Reply from 37.247.49.213: bytes=32 time=63ms TTL=53

Reply from 37.247.49.213: bytes=32 time=59ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=59ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=56ms TTL=53

Reply from 37.247.49.213: bytes=32 time=59ms TTL=53

Reply from 37.247.49.213: bytes=32 time=61ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=55ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=56ms TTL=53

Reply from 37.247.49.213: bytes=32 time=61ms TTL=53

Reply from 37.247.49.213: bytes=32 time=59ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=59ms TTL=53

Reply from 37.247.49.213: bytes=32 time=59ms TTL=53

Reply from 37.247.49.213: bytes=32 time=56ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=60ms TTL=53

Reply from 37.247.49.213: bytes=32 time=64ms TTL=53

Reply from 37.247.49.213: bytes=32 time=61ms TTL=53

Reply from 37.247.49.213: bytes=32 time=56ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=57ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Reply from 37.247.49.213: bytes=32 time=62ms TTL=53

Reply from 37.247.49.213: bytes=32 time=58ms TTL=53

Ping statistics for 37.247.49.213:

Packets: Sent = 43, Received = 43, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 55ms, Maximum = 64ms, Average = 58ms

My guess is or the Internet Connection may be unstable or some settings may be a bit too strict such as firewalls as example.

You can check your Internet Connection speed at http://www.speedtest.net.

Can you double check if the speedtest result is around the internet speed you're paying monthly for. (Again, WiFi may give incorrect values due to other nearby routers being in the same Frequency as yours. For an accurate test, roll with both WiFi and Cable. What also helps for the best test result is to close as many apps as possible that's making use of your internet connection. Such as Discord, Skype, Steam and so forth)

Sometimes pulling the power cord out of the router for at least 5 seconds or so could solve issues as well.

If it is, double check firewalls.

Some routers has a feature called SPI-Firewall, it's a try worth to see if this solves the issue.

Perhaps enable UPnP on your router if still no change after checking the firewall.

If you're in a full lobby as example, are you getting Connection Error 1-2 Connection in Progress or Connection Error 1-2 Connection Failed by any chance the moment the lobby leader wants to start the match?

Back to top

#7 fatihd

Members
10 posts

Posted 24 January 2018 - 03:18 PM

Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=54ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=48ms TTL=49
Reply from 37.247.49.213: bytes=32 time=54ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=54ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=72ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=143ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=65ms TTL=49
Reply from 37.247.49.213: bytes=32 time=53ms TTL=49
Reply from 37.247.49.213: bytes=32 time=78ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=50ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=57ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=52ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=53ms TTL=49
Reply from 37.247.49.213: bytes=32 time=52ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=52ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=93ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=53ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=48ms TTL=49
Reply from 37.247.49.213: bytes=32 time=54ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=51ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49
Reply from 37.247.49.213: bytes=32 time=49ms TTL=49

my con speed is 50/4 mbit d/u

speedtest result is 35-40 mbit.

other online games working good.

Back to top

#8 ToxicShock

Gamereplays.org Staff

Division Leaders
9,685 posts

Location:London, England
Projects:Shatabrick C&C Player Database
I have blue text?
Division:C&C:Online
Job:C&C:Online Leader

Posted 24 January 2018 - 06:26 PM

OK, you often get this from providers in your geographic location. Could you try using a VPN and see if that helps? You can google for a free one.

Gamereplays.org staff - Shatabrick admin.

Back to top

#9 fatihd

Members
10 posts

Posted 24 January 2018 - 07:53 PM

i think this not related to ping . because 50 ms ping time is enough for online gaming. but i dont know what the problem.

i tried with wtfast program and vpn program but nothing changed.

Edited by fatihd, 25 January 2018 - 06:32 AM.

Back to top

#10 fatihd

Members
10 posts

Posted 25 January 2018 - 03:33 PM

i checked server location. it is located to australia. is it true ? i think best location is europa. aruba servers from 1 euro/month may you know ?

this ip hops is problematic. 37.247.50.19

inetnum: 37.247.50.16 - 37.247.50.31
netname: VPS-50-16-31
descr: VPS block 1 for VLAN 98

Edited by fatihd, 25 January 2018 - 03:44 PM.

Back to top

#11 fatihd

Members
10 posts

Posted 25 January 2018 - 04:51 PM

i tried www.tunngle.net over network game. its working good. pls help for this problem.

Back to top

#12 ToxicShock

Gamereplays.org Staff

Division Leaders
9,685 posts

Location:London, England
Projects:Shatabrick C&C Player Database
I have blue text?
Division:C&C:Online
Job:C&C:Online Leader

Posted 26 January 2018 - 11:10 AM

As I say, you need to use a VPN because (like a number of providers in your area) it looks like your provider does not support arbitrary UDP. Tungle is a network game (like gameranger) and does not work the same way.

Gamereplays.org staff - Shatabrick admin.