If you can join the others servers, then it's probably a problem on server's side. At 1st I was thinking about an InSim bug, but it couldn't show up error before he would join the server.
The problem is from players who'r unable to connect to my server with their connection. This player fail one time and then repeat, repeat, repeat (most of time during more than 10min) and then, all players who wanna to connect are blocked.
They wait the information of the player who crash at the connection and LFs refuse the connection.
The problem si that when you try to connect after this player, you will be able to retry a few seconde after that he will retry. (you need to wait the timeout about the "player info") so you'r on,e more time unable to connect because he crashed
I never got this problem before and my dedicated host didn't change. I use a Z3 lfsdedi actually but i know that this problem was worse with Z10.
Yep like for all server. all people can't have a good ping. That depend where is located the server.
For example, the first server that i used worked nicely for all Europe & Asia but US country was unable to join or got a 300+ ping.
Now i've got this problem with Est-Europe country with my french dedicated server.
People have to wait or try the second server instead of repeat the connection if they fail.
lfsdedi had much less problem without the waiting list for the connection. If just one person fails the connection, following players also fails now. :S
For the moment, i can't change it. To host all my stuff, I need a full-acess computer not just a lfs server. I will check later if i can get a better offer elsewhere but i can't do any promess
Ah, you misundertund me about Lc1 & 2. Sry i'm not good at english.
the Lc1 & Lc2 servers are on the same host. I just recommand to people who get trouble with Lc1 to try the connection on Lc2 (where there is less people than Lc1 most of time).
If the problem persist, i can't help them.
I try to found a better offer for my dedicataed computer but withoiut success. Anyway, i never get this problem last year, i can try to correct that but something is wrong with lfsdedi.
With lfs updates, I see more and more problems with lfsdedi