Unable to Log in - Major Lag when finally ingame

Here is my log (sorry, I dont know how to post the whole file)

 

23:57:25.062 | GameApp shutdown

 

From what we can see (again, not a full log!) this is your networking problem - somehow your system is unable to allow access to socket 10057. Have you tried adding the game to your firewall exceptions? Does your router use NAT and UPnP?

Heres my Log Antibus - I have been playing today with no issue’s what so ever

 

Around 17.30 GMT I am struggling to log in, and if I get in and get to play a game on a RU server it is unplayable (Same fault)

 

Just for info here is a speed test I have just ran to check my own internet

 

3081095207.png

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

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

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

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

Im not very technical - Maybe you can explain what this means as well :lol:

 

ls4bhuJ.jpg

Your ISP’s link to Real Time Network’s router is absolute xxxx xxxx.  Contact your ISP and hope to find someone technical enough to understand.  Either your ISP or RTN is responsible, but by the looks of my traceroute the devs are using RTN to host.  If it’s your ISP, they’ll work to fix it.  If it’s RTN, your ISP should work to help RTN fix it.

 

Edit: I should also note that for me, from 195.219.50.38 to ae0-8.RT.BM.SPB.RU.retn.net which is one hop, the ping time spikes 47ms.  I’m going to blame RTN on this one.

No response from any of the admins etc ?

Right, couldn’t access the forum yesterday evening because it was so slow. Firstly, my suggestion to star conflict would be to put the forum on a different server to the game itself, because it’s annoying having the game go down and not being able to access the forum to post logs!

 

Anyways, now I can access it, I’ll upload my logs. Also, here’s the Contester thing which I guess it more important for network issues. This was ran immediately after finding I couldn’t connect to SC (I closed SC then ran contester).

 

— Date: 2013-11-06 (Wed Nov 2013) GMT Standard Time

19:05:27.327        | //////////////////////////////////////////////////////////
19:05:27.327        | //
19:05:27.327        | // Connection Tester  0.9.9.40587 (Nov  1 2013 01:58:43)
19:05:27.328        | //
19:05:27.328        | //////////////////////////////////////////////////////////
19:05:27.328        |
19:05:27.328        | Preloaded 1 SStrings
19:05:27.330 CONSOLE| executing ‘connection_tester.cfg’
19:05:27.331        | There are total of 3 hosts to check
19:05:27.332        | ConnectionTester: new state ‘CTS_INITIALIZED’
19:05:27.332        | ConnectionTester: new state ‘CTS_RESOLVING’
19:05:27.336        | Resolving ‘main01av-ru.star-conflict.com’ …
19:05:27.345        | ‘main01av-ru.star-conflict.com’ is 91.230.60.102
19:05:27.345        | Resolving ‘node01av-ru.star-conflict.com’ …
19:05:27.370        | ‘node01av-ru.star-conflict.com’ is 91.230.61.156
19:05:27.370        | Resolving ‘node02av-ru.star-conflict.com’ …
19:05:27.395        | ‘node02av-ru.star-conflict.com’ is 91.230.61.172
19:05:27.395        | ConnectionTester: new state ‘CTS_PINGING’
19:05:30.381        | 512 bytes from 91.230.61.172 ( icmpseq=2, triptime=156ms, TTL=114 )
19:05:30.385        | 512 bytes from 91.230.61.156 ( icmpseq=2, triptime=160ms, TTL=114 )
19:05:31.225 WARNING| 91.230.60.102 response (seq 0) timed out
19:05:31.225 WARNING| 91.230.61.156 response (seq 0) timed out
19:05:31.225 WARNING| 91.230.61.172 response (seq 0) timed out
19:05:32.223 WARNING| 91.230.60.102 response (seq 1) timed out
19:05:32.223 WARNING| 91.230.61.156 response (seq 1) timed out
19:05:32.224 WARNING| 91.230.61.172 response (seq 1) timed out
19:05:33.229 WARNING| 91.230.60.102 response (seq 2) timed out
19:05:34.231 WARNING| 91.230.60.102 response (seq 3) timed out
19:05:34.232 WARNING| 91.230.61.156 response (seq 3) timed out
19:05:34.233 WARNING| 91.230.61.172 response (seq 3) timed out
19:05:34.384        | 512 bytes from 91.230.61.172 ( icmpseq=6, triptime=149ms, TTL=114 )
19:05:35.234 WARNING| 91.230.60.102 response (seq 4) timed out
19:05:35.235 WARNING| 91.230.61.156 response (seq 4) timed out
19:05:35.237 WARNING| 91.230.61.172 response (seq 4) timed out
19:05:36.234 WARNING| 91.230.60.102 response (seq 5) timed out
19:05:36.236 WARNING| 91.230.61.156 response (seq 5) timed out
19:05:36.237 WARNING| 91.230.61.172 response (seq 5) timed out
19:05:37.238 WARNING| 91.230.60.102 response (seq 6) timed out
19:05:37.242 WARNING| 91.230.61.156 response (seq 6) timed out
19:05:37.386        | 512 bytes from 91.230.61.156 ( icmpseq=9, triptime=147ms, TTL=114 )
19:05:37.390        | 512 bytes from 91.230.61.172 ( icmpseq=9, triptime=148ms, TTL=114 )
19:05:38.240 WARNING| 91.230.60.102 response (seq 7) timed out
19:05:38.242 WARNING| 91.230.61.156 response (seq 7) timed out
19:05:38.244 WARNING| 91.230.61.172 response (seq 7) timed out
19:05:39.241 WARNING| 91.230.60.102 response (seq 8) timed out
19:05:39.243 WARNING| 91.230.61.156 response (seq 8) timed out
19:05:39.244 WARNING| 91.230.61.172 response (seq 8) timed out
19:05:40.241 WARNING| 91.230.60.102 response (seq 9) timed out
19:05:40.388        | 512 bytes from 91.230.61.172 ( icmpseq=12, triptime=144ms, TTL=114 )
19:05:41.243 WARNING| 91.230.60.102 response (seq 10) timed out
19:05:41.245 WARNING| 91.230.61.156 response (seq 10) timed out
19:05:41.246 WARNING| 91.230.61.172 response (seq 10) timed out
19:05:41.393        | 512 bytes from 91.230.61.156 ( icmpseq=13, triptime=147ms, TTL=114 )
19:05:42.242 WARNING| 91.230.60.102 response (seq 11) timed out
19:05:42.246 WARNING| 91.230.61.156 response (seq 11) timed out
19:05:42.249 WARNING| 91.230.61.172 response (seq 11) timed out
19:05:42.394        | 512 bytes from 91.230.61.172 ( icmpseq=14, triptime=144ms, TTL=114 )
19:05:43.246 WARNING| 91.230.60.102 response (seq 12) timed out
19:05:43.247 WARNING| 91.230.61.156 response (seq 12) timed out
19:05:43.397        | 512 bytes from 91.230.61.156 ( icmpseq=15, triptime=144ms, TTL=114 )
19:05:44.249 WARNING| 91.230.60.102 response (seq 13) timed out
19:05:44.250 WARNING| 91.230.61.172 response (seq 13) timed out
19:05:45.253 WARNING| 91.230.60.102 response (seq 14) timed out
19:05:45.577 WARNING| 91.230.61.156 response (seq 14) timed out
19:05:45.724        | 512 bytes from 91.230.61.156 ( icmpseq=17, triptime=147ms, TTL=114 )
19:05:46.254 WARNING| 91.230.60.102 response (seq 15) timed out
19:05:46.255 WARNING| 91.230.61.172 response (seq 15) timed out
19:05:46.721        | 512 bytes from 91.230.60.102 ( icmpseq=18, triptime=143ms, TTL=114 )
19:05:46.725        | 512 bytes from 91.230.61.156 ( icmpseq=18, triptime=147ms, TTL=114 )
19:05:47.258 WARNING| 91.230.60.102 response (seq 16) timed out
19:05:47.265 WARNING| 91.230.61.156 response (seq 16) timed out
19:05:47.267 WARNING| 91.230.61.172 response (seq 16) timed out
19:05:47.720        | 512 bytes from 91.230.61.172 ( icmpseq=19, triptime=142ms, TTL=114 )
19:05:48.578 WARNING| 91.230.60.102 response (seq 17) timed out
19:05:48.579 WARNING| 91.230.61.172 response (seq 17) timed out
19:05:48.724        | 512 bytes from 91.230.61.156 ( icmpseq=20, triptime=142ms, TTL=114 )
19:05:49.581 WARNING| 91.230.61.172 response (seq 18) timed out
19:05:49.729        | 512 bytes from 91.230.60.102 ( icmpseq=21, triptime=142ms, TTL=114 )
19:05:50.581 WARNING| 91.230.60.102 response (seq 19) timed out
19:05:50.583 WARNING| 91.230.61.156 response (seq 19) timed out
19:05:51.585 WARNING| 91.230.60.102 response (seq 20) timed out
19:05:51.585 WARNING| 91.230.61.172 response (seq 20) timed out
19:05:52.589 WARNING| 91.230.61.156 response (seq 21) timed out
19:05:52.594 WARNING| 91.230.61.172 response (seq 21) timed out
19:05:52.740        | 512 bytes from 91.230.61.172 ( icmpseq=24, triptime=146ms, TTL=114 )
19:05:53.593 WARNING| 91.230.60.102 response (seq 22) timed out
19:05:53.594 WARNING| 91.230.61.156 response (seq 22) timed out
19:05:53.597 WARNING| 91.230.61.172 response (seq 22) timed out
19:05:54.594 WARNING| 91.230.60.102 response (seq 23) timed out
19:05:54.596 WARNING| 91.230.61.156 response (seq 23) timed out
19:05:54.597 WARNING| 91.230.61.172 response (seq 23) timed out
19:05:54.745        | 512 bytes from 91.230.61.172 ( icmpseq=26, triptime=144ms, TTL=114 )
19:05:55.596 WARNING| 91.230.60.102 response (seq 24) timed out
19:05:55.597 WARNING| 91.230.61.156 response (seq 24) timed out
19:05:55.747        | 512 bytes from 91.230.61.172 ( icmpseq=27, triptime=144ms, TTL=114 )
19:05:56.600 WARNING| 91.230.60.102 response (seq 25) timed out
19:05:56.602 WARNING| 91.230.61.156 response (seq 25) timed out
19:05:56.604 WARNING| 91.230.61.172 response (seq 25) timed out
19:05:56.782        | 512 bytes from 91.230.61.156 ( icmpseq=28, triptime=178ms, TTL=114 )
19:05:57.340        | Pinged for 30.0 seconds
19:05:57.341        | main01av-ru.star-conflict.com: packets: 29/2 ( 93% loss), avg: 143ms, min: 142ms, max: 143ms
19:05:57.342        | node01av-ru.star-conflict.com: packets: 29/8 ( 72% loss), avg: 152ms, min: 142ms, max: 178ms
19:05:57.343        | node02av-ru.star-conflict.com: packets: 29/9 ( 69% loss), avg: 146ms, min: 142ms, max: 156ms
19:05:57.344        | ConnectionTester: new state ‘CTS_UDP_TESTING’
19:06:03.957        | UdpTester(91.230.61.156|36000): Failed to connect
19:06:06.348        | UdpTester(91.230.60.102|36000): Connected. MTU size = 1200
19:06:06.349        | UdpTester(91.230.60.102|36000): Sending request 1
19:06:07.350        | UdpTester(91.230.60.102|36000): Sending request 2
19:06:08.353        | UdpTester(91.230.60.102|36000): Sending request 3
19:06:09.354        | UdpTester(91.230.60.102|36000): Sending request 4
19:06:09.719        | UdpTester(91.230.61.172|36000): Failed to connect
19:06:10.356        | UdpTester(91.230.60.102|36000): Sending request 5
19:06:11.357        | UdpTester(91.230.60.102|36000): Sending request 6
19:06:12.360        | UdpTester(91.230.60.102|36000): Sending request 7
19:06:13.361        | UdpTester(91.230.60.102|36000): Sending request 8
19:06:14.362        | UdpTester(91.230.60.102|36000): Sending request 9
19:06:15.362        | UdpTester(91.230.60.102|36000): Sending request 10
19:06:16.365        | UdpTester(91.230.60.102|36000): Sending request 11
19:06:17.368        | UdpTester(91.230.60.102|36000): Sending request 12
19:06:18.368        | UdpTester(91.230.60.102|36000): Sending request 13
19:06:18.508        | UdpTester(91.230.60.102|36000): Disconnected
19:06:18.509        | UDP tester work time: 30.0 seconds
19:06:18.510        | UdpTester(91.230.60.102|36000): MTU size: 576
19:06:18.511        | UdpTester(91.230.60.102|36000): Ping: avg: -1ms, min: -1ms
19:06:18.512        | UdpTester(91.230.60.102|36000): Packets received by server: 0/13
19:06:18.513        | UdpTester(91.230.60.102|36000): Sizes of packets received from server (0):
19:06:18.514        | UdpTester(91.230.61.156|36000): MTU size: 576
19:06:18.515        | UdpTester(91.230.61.156|36000): Ping: avg: -1ms, min: -1ms
19:06:18.516        | UdpTester(91.230.61.156|36000): Packets received by server: 0/0
19:06:18.516        | UdpTester(91.230.61.156|36000): Sizes of packets received from server (0):
19:06:18.517        | UdpTester(91.230.61.172|36000): MTU size: 576
19:06:18.518        | UdpTester(91.230.61.172|36000): Ping: avg: -1ms, min: -1ms
19:06:18.519        | UdpTester(91.230.61.172|36000): Packets received by server: 0/0
19:06:18.520        | UdpTester(91.230.61.172|36000): Sizes of packets received from server (0):
19:06:18.521        | ConnectionTester: new state ‘CTS_FINNISHED’
19:06:18.528        | ConnectionTester::Shutdown
 

 

Thats that, and the log should be attached below as a zip file.

My network itself is fine, I’m running a lot of internet based apps which run fine, just not SC at the same time each day.

Hope the log etc helps fix it!

 

Anthony :slight_smile:

[2013.11.06 19.02.49.zip](< base_url >/applications/core/interface/file/attachment.php?id=6984)

Im not very technical - Maybe you can explain what this means as well :lol:

 

We have studied your logs and the picture from Ping Plotter. The problem you are experiencing is in your ISP, you are experiencing a massive packet loss on the route to our servers. We recommend you to contact your ISP in order to find a slotion to the problem. 

Right, couldn’t access the forum yesterday evening because it was so slow. Firstly, my suggestion to star conflict would be to put the forum on a different server to the game itself, because it’s annoying having the game go down and not being able to access the forum to post logs!

 

Anyways, now I can access it, I’ll upload my logs. Also, here’s the Contester thing which I guess it more important for network issues. This was ran immediately after finding I couldn’t connect to SC (I closed SC then ran contester).

 

Thats that, and the log should be attached below as a zip file.

My network itself is fine, I’m running a lot of internet based apps which run fine, just not SC at the same time each day.

Hope the log etc helps fix it!

 

Anthony :slight_smile:

 

Same thing here: the main problem lies with your ISP. We recommend you to contact your provider and try to find a solution to this. 

 

We would like to make it clear: in these two cases, it is not our servers, but ISP of our pilots. 

Antibus, by the looks of Kipps traceroute and my traceroute, we’re both encountering issues once when getting from one of retn.net’s peers and onto retn.net’s own network.  For Kipps it’s packet loss and for me it’s just a higher than expected latency for one hop.  Considering that we’re entering retn.net’s network from different routes it seems as though it could actually be your ISP.  The peering points are adding a lot of latency.  Could you add traceroutes to con_tester to look for noticeable locations that cause trouble?  The ISP’s aren’t being friendly enough with eachother.

Had the same problem with a friend yesterday. Strange thing, the second friend who had another ISP didn’t have the problem.

I hope things will get fixed soon, this is anoying to be disconnected 3 times in a single pve game.

Same thing here: the main problem lies with your ISP. We recommend you to contact your provider and try to find a solution to this. 

 

We would like to make it clear: in these two cases, it is not our servers, but ISP of our pilots. 

Hi,

 

Cool, thanks for letting me know.

Just to clarify though, you say it’s the ISP, do you know exactly what the ISP is doing? Just means I know what to say when I contact them telling them they’re doing something wierd! Also the fact it happens at the same time every day, I take it this is because the ISP block something at certain times due to peak traffic or am I wrong?

 

Thanks!

 

Anthony :slight_smile:

Well it’s happened again tonight <EDIT: I take that back, it started working after a few mins but still>. I honestly can’t just go to BT and say ‘Star conflict isn’t working, help!’ because they won’t have a clue what Star conflict even is.

If perhaps someone could clarify what the issue is with the ISP I might be able to get them to help.

 

Thanks,

 

Anthony

Hi,

 

Cool, thanks for letting me know.

Just to clarify though, you say it’s the ISP, do you know exactly what the ISP is doing? Just means I know what to say when I contact them telling them they’re doing something wierd! Also the fact it happens at the same time every day, I take it this is because the ISP block something at certain times due to peak traffic or am I wrong?

 

Thanks!

 

Anthony :slight_smile:

 

No, unfortunatle we don’t. What we can see from logs is that you are experiencing a massive packet loss en route to our servers, problems like these are usually network-side, we do not know what exactly your provider does to cause this, but we suggest you to use ping plotter and then submit this info to you ISP. 

No, unfortunatle we don’t. What we can see from logs is that you are experiencing a massive packet loss en route to our servers, problems like these are usually network-side, we do not know what exactly your provider does to cause this, but we suggest you to use ping plotter and then submit this info to you ISP. 

Ok, I’ll give that a whirl and send it off, thanks :slight_smile:

 

Anthony

The issue still persists for me, and it seems to have just started again but the afternoon in the weekend. Did anyone ever get through to their ISP about how to fix this? BT support seems to be pretty useless so I couldn’t get a solution from them :stuck_out_tongue:

 

Anthony