Connection Lost: Client unable to connect

36008456 · October 23, 2015, 5:25pm

Charactername:- Mentalmanja

What did you expect to see:- Get connected to a battle

What happened:- Battle starts, but I cannot connect. “Connection Lost: Client unable to connect” is shown. My ships are then stuck in a battle in which I can’t participate.

What was your last action:- Had clicked connect to a PvE battle

Internet connection:- Cable internet 10kbps connection

I have been having this connection since a week. Tried everything from checking MTU to trying opening ports, disabling firewall/antivirus/windows update everything. This happened suddenly. I played a match, quit to go eat my lunch, and came back to the connection issue.

Nothing else is affected. Everything else works. I login, I get rewards, I can send my ships away on missions, I can chat - everything except getting connected to a battle. I click “Launch”>“PvE Battles” - I wait for sometime, then that “connected” sound plays, after a few seconds “Connection Lost: Client unable to connect”. I then try that try to connect ‘Triangulation’, that too fails and leads to the same message.

[conntest.log](< base_url >/applications/core/interface/file/attachment.php?id=10051)

[game.log](< base_url >/applications/core/interface/file/attachment.php?id=10052)

[game.net.log](< base_url >/applications/core/interface/file/attachment.php?id=10053)

1914000 · October 26, 2015, 6:37am

In your log:

MasterServerEndpoint: Successfully login to masterServer 91.230.61.67:3802, uid 001ED538, nick mentalmanja, spaceStationZoneId 3

I don’t see “Client unable to connect”

36008456 · October 26, 2015, 10:33am

In your log:

MasterServerEndpoint: Successfully login to masterServer 91.230.61.67:3802, uid 001ED538, nick mentalmanja, spaceStationZoneId 3

I don’t see “Client unable to connect”

I did say everything works perfectly until I try entering a battle. I can’t enter any battles - rest else works.

I can join battles, my ship enters the battle and gets stuck in battle, but I can’t enter the battle, it gives me that “client can’t connect” error.

From my log -

Conntest

22:49:01.450 | ConnectionTester: new state 'CTS_PINGING'
22:49:01.450 ERROR| Pinger: Failed to create ICPM socket (err: 10013)
22:49:01.450 ERROR| Pinger: Failed to create ICPM socket (err: 10013)
22:49:04.332 | Caught application terminal signal 21
22:49:04.338 | ConnectionTester::Shutdown

Game.log

22:04:50.814 WARNING| client: couldn't connect by timeout (frameTimeReal = 0.043837)
22:04:50.814 | client: connection closed. DR_CLIENT_COULD_NOT_CONNECT
22:04:50.814 | Network stats (bytes per second): avg pushed 0, max pushed 0, avg sent 0, max sent 0, avg received 0, max received 0

Game

1914000 · October 27, 2015, 6:27am

[Info: connection losses, high ping and related issues](< base_url >/index.php?/topic/25324-info-connection-losses-high-ping-and-related-issues/)

36008456 · October 27, 2015, 7:24am

Okay, I have attached the screenshots and the WinMTR results.

I have checked my MTU, and it is ok - so that is not the problem.

I think it has something to do with UDP. I ran conntest in admin mode, here is the result -

--- Date: 2015-10-27 (Tue Oct 2015) India Standard Time UTC+05:30

13:13:56.028 | //////////////////////////////////////////////////////////
13:13:56.028 | //
13:13:56.028 | // Connection Tester 1.2.1.76749 (Oct 7 2015 17:13:51)
13:13:56.028 | //
13:13:56.028 | //////////////////////////////////////////////////////////
13:13:56.028 | 
13:13:56.028 CONSOLE| executing 'connection_tester.cfg'
13:13:56.028 | There are total of 2 hosts to check
13:13:56.028 | ConnectionTester: new state 'CTS_INITIALIZED'
13:13:56.028 | ConnectionTester: new state 'CTS_RESOLVING'
13:13:56.044 | Resolving 'google.com' ...
13:13:56.050 | 'google.com' is 173.194.45.35
13:13:56.051 | Resolving 'node10av-ru.star-conflict.com' ...
13:13:56.052 | 'node10av-ru.star-conflict.com' is 91.230.61.97
13:13:56.052 | ConnectionTester: new state 'CTS_PINGING'
13:13:57.120 | 512 bytes from 91.230.61.97 ( icmpseq=0, triptime=210ms, TTL=49 )
13:13:57.300 | 512 bytes from 173.194.45.35 ( icmpseq=0, triptime=391ms, TTL=48 )
13:13:58.120 | 512 bytes from 91.230.61.97 ( icmpseq=1, triptime=210ms, TTL=49 )
13:13:58.301 | 512 bytes from 173.194.45.35 ( icmpseq=1, triptime=390ms, TTL=48 )
13:13:59.122 | 512 bytes from 91.230.61.97 ( icmpseq=2, triptime=210ms, TTL=49 )
13:13:59.301 | 512 bytes from 173.194.45.35 ( icmpseq=2, triptime=388ms, TTL=48 )
13:14:00.128 | 512 bytes from 91.230.61.97 ( icmpseq=3, triptime=213ms, TTL=49 )
13:14:00.305 | 512 bytes from 173.194.45.35 ( icmpseq=3, triptime=391ms, TTL=48 )
13:14:01.126 | 512 bytes from 91.230.61.97 ( icmpseq=4, triptime=210ms, TTL=49 )
13:14:01.306 | 512 bytes from 173.194.45.35 ( icmpseq=4, triptime=390ms, TTL=48 )
13:14:02.125 | 512 bytes from 91.230.61.97 ( icmpseq=5, triptime=207ms, TTL=49 )
13:14:02.305 | 512 bytes from 173.194.45.35 ( icmpseq=5, triptime=387ms, TTL=48 )
13:14:03.131 | 512 bytes from 91.230.61.97 ( icmpseq=6, triptime=213ms, TTL=49 )
13:14:03.311 | 512 bytes from 173.194.45.35 ( icmpseq=6, triptime=393ms, TTL=48 )
13:14:04.129 | 512 bytes from 91.230.61.97 ( icmpseq=7, triptime=210ms, TTL=49 )
13:14:04.310 | 512 bytes from 173.194.45.35 ( icmpseq=7, triptime=390ms, TTL=48 )
13:14:05.133 | 512 bytes from 91.230.61.97 ( icmpseq=8, triptime=214ms, TTL=49 )
13:14:05.313 | 512 bytes from 173.194.45.35 ( icmpseq=8, triptime=394ms, TTL=48 )
13:14:06.133 | 512 bytes from 91.230.61.97 ( icmpseq=9, triptime=210ms, TTL=49 )
13:14:06.313 | 512 bytes from 173.194.45.35 ( icmpseq=9, triptime=390ms, TTL=48 )
13:14:07.139 | 512 bytes from 91.230.61.97 ( icmpseq=10, triptime=213ms, TTL=49 )
13:14:07.319 | 512 bytes from 173.194.45.35 ( icmpseq=10, triptime=393ms, TTL=48 )
13:14:08.142 | 512 bytes from 91.230.61.97 ( icmpseq=11, triptime=215ms, TTL=49 )
13:14:08.319 | 512 bytes from 173.194.45.35 ( icmpseq=11, triptime=392ms, TTL=48 )
13:14:09.140 | 512 bytes from 91.230.61.97 ( icmpseq=12, triptime=210ms, TTL=49 )
13:14:09.320 | 512 bytes from 173.194.45.35 ( icmpseq=12, triptime=391ms, TTL=48 )
13:14:10.146 | 512 bytes from 91.230.61.97 ( icmpseq=13, triptime=213ms, TTL=49 )
13:14:10.326 | 512 bytes from 173.194.45.35 ( icmpseq=13, triptime=394ms, TTL=48 )
13:14:11.146 | 512 bytes from 91.230.61.97 ( icmpseq=14, triptime=214ms, TTL=49 )
13:14:11.323 | 512 bytes from 173.194.45.35 ( icmpseq=14, triptime=391ms, TTL=48 )
13:14:12.146 | 512 bytes from 91.230.61.97 ( icmpseq=15, triptime=211ms, TTL=49 )
13:14:12.326 | 512 bytes from 173.194.45.35 ( icmpseq=15, triptime=391ms, TTL=48 )
13:14:13.146 | 512 bytes from 91.230.61.97 ( icmpseq=16, triptime=210ms, TTL=49 )
13:14:13.326 | 512 bytes from 173.194.45.35 ( icmpseq=16, triptime=390ms, TTL=48 )
13:14:14.146 | 512 bytes from 91.230.61.97 ( icmpseq=17, triptime=210ms, TTL=49 )
13:14:14.327 | 512 bytes from 173.194.45.35 ( icmpseq=17, triptime=390ms, TTL=48 )
13:14:15.147 | 512 bytes from 91.230.61.97 ( icmpseq=18, triptime=210ms, TTL=49 )
13:14:15.327 | 512 bytes from 173.194.45.35 ( icmpseq=18, triptime=390ms, TTL=48 )
13:14:16.046 | Pinged for 20.0 seconds
13:14:16.047 | google.com: packets: 20/19 ( 5% loss), avg: 391ms, min: 387ms, max: 394ms
13:14:16.048 | node10av-ru.star-conflict.com: packets: 20/19 ( 5% loss), avg: 211ms, min: 207ms, max: 215ms
13:14:16.048 | ConnectionTester: new state 'CTS_UDP_TESTING'
13:14:29.003 | UdpTester(91.230.61.97|35900): Failed to connect
13:14:29.004 | UDP tester work time: 20.0 seconds
13:14:29.005 | UdpTester(91.230.61.97|35900): MTU size: 576
13:14:29.005 | UdpTester(91.230.61.97|35900): Ping: avg: -1ms, min: -1ms
13:14:29.006 | UdpTester(91.230.61.97|35900): Packets received by server: 0/0
13:14:29.007 | UdpTester(91.230.61.97|35900): Sizes of packets received from server (0): 
13:14:29.008 | ConnectionTester: new state 'CTS_FINNISHED'
13:14:29.015 | ConnectionTester::Shutdown

[WinMTR Results.txt](< base_url >/applications/core/interface/file/attachment.php?id=10063)

23605300 · October 28, 2015, 5:28am

13:14:29.003 | UdpTester(91.230.61.97|35900): Failed to connect

it still something wrong with UDP packets coming from or to you. Check your network settings, not only firewall/antivirus, but also router and any other intermediate devices firewalls and traffic inspectors.

When you’ll find the filtering point, you see successfull UDP pings in conntester, somethink like this:

INFO   : ConnectionTester: new state 'CTS_UDP_TESTING'
INFO   : UdpTester(91.230.61.97|35900): Connected. MTU size = 1430
INFO   : UdpTester(91.230.61.97|35900): Sending request 1
INFO   : UdpTester(91.230.61.97|35900): Received packet (len=1025)
INFO   : UdpTester(91.230.61.97|35900): Sending request 2
INFO   : UdpTester(91.230.61.97|35900): Sending request 3
INFO   : UdpTester(91.230.61.97|35900): Received packet (len=1537)
INFO   : UdpTester(91.230.61.97|35900): Sending request 4
INFO   : UdpTester(91.230.61.97|35900): Sending request 5
INFO   : UdpTester(91.230.61.97|35900): Received packet (len=2049)
INFO   : UdpTester(91.230.61.97|35900): Sending request 6
INFO   : UdpTester(91.230.61.97|35900): Sending request 7
INFO   : UdpTester(91.230.61.97|35900): Received packet (len=16385)
INFO   : UdpTester(91.230.61.97|35900): Sending request 8
INFO   : UdpTester(91.230.61.97|35900): Sending request 9
INFO   : UdpTester(91.230.61.97|35900): Sending request 10
INFO   : UdpTester(91.230.61.97|35900): Sending request 11
INFO   : UdpTester(91.230.61.97|35900): Sending request 12
INFO   : UdpTester(91.230.61.97|35900): Sending request 13
INFO   : UdpTester(91.230.61.97|35900): Sending request 14
INFO   : UdpTester(91.230.61.97|35900): Sending request 15
INFO   : UdpTester(91.230.61.97|35900): Sending request 16
INFO   : UdpTester(91.230.61.97|35900): Sending request 17
INFO   : UdpTester(91.230.61.97|35900): Sending request 18
INFO   : UdpTester(91.230.61.97|35900): Sending request 19
INFO   : UdpTester(91.230.61.97|35900): Sending request 20
INFO   : Finishing UDP test
INFO   : UDP tester work time: 20.0 seconds
INFO   : UdpTester(91.230.61.97|35900): MTU size: 1430
INFO   : UdpTester(91.230.61.97|35900): Ping: avg: 48ms, min: 43ms
INFO   : UdpTester(91.230.61.97|35900): Packets received by server: 20/20
INFO   : UdpTester(91.230.61.97|35900): Sizes of packets received from server (4):  1025, 1537, 2049, 16385
INFO   : ConnectionTester: new state 'CTS_FINNISHED'INFO   : ConnectionTester::Shutdown