Connection problem, can`t play the game

Hello, i have the problem, that i often can´t connect to the missions or space. i play a mission, it works, and the next 20 tries it wont work and i cant play anymore.

When in open space i cant use the portals cause often it looses connection… 

My provider uses IPV6, so i cant port forward (cause it should work automaticaly).

 

I tried to use the SC_Active_Srv_nettest.cmd  but even if i can connect to a mission, it wont start and is just waiting that i start a mission. so i dont get any information out of it.

Same with PacketLoss_Trapper.cmd.

 

I tried to close firewall etc, but wont work. And since i cant get information cause i dont know server ip etc. dont know what to do. i use Steam version of the game

 

 

5a5ba7b02961f_Error2t.png.8c8f7c97e09115fe806d192eb72bb47d.jpg

— Date: 2018-01-14 (Sun Jan 2018) Mitteleuropäische Zeit UTC+01:00

20:01:35.000         | //////////////////////////////////////////////////////////
20:01:35.001         | //
20:01:35.001         | // Connection Tester  1.5.0b.114911 (Dec 26 2017 19:25:23)
20:01:35.001         | //
20:01:35.002         | //////////////////////////////////////////////////////////
20:01:35.002         | 
20:01:35.018  CONSOLE| executing ‘connection_tester.cfg’
20:01:35.056         | There are total of 2 hosts to check
20:01:35.056         | ConnectionTester: new state ‘CTS_INITIALIZED’
20:01:35.056         | ConnectionTester: new state ‘CTS_RESOLVING’
20:01:35.060         | Resolving ‘google.com’ …
20:01:35.098         | ‘google.com’ is 172.217.18.174
20:01:35.098         | Resolving ‘node09st-ru.star-conflict.com’ …
20:01:35.160         | ‘node09st-ru.star-conflict.com’ is 95.213.156.195
20:01:35.161         | ConnectionTester: new state ‘CTS_PINGING’
20:01:35.898         | 72 bytes from 172.217.18.174 ( icmpseq=0, triptime=39ms, TTL=54 )
20:01:35.920         | 512 bytes from 95.213.156.195 ( icmpseq=0, triptime=61ms, TTL=52 )
20:01:36.896         | 72 bytes from 172.217.18.174 ( icmpseq=1, triptime=36ms, TTL=54 )
20:01:36.920         | 512 bytes from 95.213.156.195 ( icmpseq=1, triptime=60ms, TTL=52 )
20:01:37.900         | 72 bytes from 172.217.18.174 ( icmpseq=2, triptime=39ms, TTL=54 )
20:01:37.921         | 512 bytes from 95.213.156.195 ( icmpseq=2, triptime=60ms, TTL=52 )
20:01:38.940         | 72 bytes from 172.217.18.174 ( icmpseq=3, triptime=78ms, TTL=54 )
20:01:38.943         | 512 bytes from 95.213.156.195 ( icmpseq=3, triptime=81ms, TTL=52 )
20:01:39.060         | Pinged for 4.0 seconds
20:01:39.060         | google.com: packets: 4/4 (  0% loss), avg: 48ms, min: 36ms, max: 78ms
20:01:39.061         | node09st-ru.star-conflict.com: packets: 4/4 (  0% loss), avg: 66ms, min: 60ms, max: 81ms
20:01:39.061         | ConnectionTester: new state ‘CTS_UDP_TESTING’
20:01:41.331         | UdpTester(95.213.156.195|35900): Connected. MTU size = 1200
20:01:41.332         | UdpTester(95.213.156.195|35900): Sending request 1
20:01:41.407         | UdpTester(95.213.156.195|35900): Received packet (len=1025)
20:01:42.332         | UdpTester(95.213.156.195|35900): Sending request 2
20:01:43.335         | UdpTester(95.213.156.195|35900): Sending request 3
20:01:43.416         | UdpTester(95.213.156.195|35900): Received packet (len=1537)
20:01:44.335         | UdpTester(95.213.156.195|35900): Sending request 4
20:01:45.335         | UdpTester(95.213.156.195|35900): Sending request 5
20:01:45.537         | UdpTester(95.213.156.195|35900): Received packet (len=2049)
20:01:46.336         | UdpTester(95.213.156.195|35900): Sending request 6
20:01:47.336         | UdpTester(95.213.156.195|35900): Sending request 7
20:01:47.877         | UdpTester(95.213.156.195|35900): Received packet (len=16385)
20:01:48.337         | UdpTester(95.213.156.195|35900): Sending request 8
20:01:49.337         | UdpTester(95.213.156.195|35900): Sending request 9
20:01:50.338         | UdpTester(95.213.156.195|35900): Sending request 10
20:01:51.338         | UdpTester(95.213.156.195|35900): Sending request 11
20:01:52.339         | UdpTester(95.213.156.195|35900): Sending request 12
20:01:53.339         | UdpTester(95.213.156.195|35900): Sending request 13
20:01:54.340         | UdpTester(95.213.156.195|35900): Sending request 14
20:01:55.340         | UdpTester(95.213.156.195|35900): Sending request 15
20:01:56.340         | UdpTester(95.213.156.195|35900): Sending request 16
20:01:57.340         | UdpTester(95.213.156.195|35900): Sending request 17
20:01:58.341         | UdpTester(95.213.156.195|35900): Sending request 18
20:01:59.061         | Finishing UDP test
20:01:59.140         | UDP tester work time: 20.0 seconds
20:01:59.140         | UdpTester(95.213.156.195|35900): MTU size: 1200
20:01:59.140         | UdpTester(95.213.156.195|35900): Ping: avg: 60ms, min: 56ms
20:01:59.140         | UdpTester(95.213.156.195|35900): Packets received by server: 18/18
20:01:59.140         | UdpTester(95.213.156.195|35900): Sizes of packets received from server (4):  1025, 1537, 2049, 16385
20:01:59.140         | ConnectionTester: new state ‘CTS_FINNISHED’
20:01:59.149         | ConnectionTester::Shutdown
 

 

Unbenannt.png.9b098ffc9dec539a697a388e48bcc8e1.png

On 15.01.2018 at 12:05 AM, TheWeskerLp said:

i often can´t connect to the missions or space

If repeated, please, use WinMTR utility for trace your connrction and post result’s screenshot(s)

 

Thanks. I got a squezzed MTU and now it works with 1460 ![:)](<fileStore.core_Emoticons>/emoticons/001j.png “:)”) Had to find out with the ping command in cmd. Hope it now solved everything ![:)](<fileStore.core_Emoticons>/emoticons/001j.png “:)”)