Click for Sun
Back to Board Index

Getting Kicked (FSOpen Server)
Jon Bowles
United States

17th Feb 2012
21:44:25
Hey Dave,

My admin and I (Chicago Flights Server) seem to be getting kicked from the server, quite often lately. This happens when trying to key up, using only the Caps Lock key, to announce positions.

In other words, not trying to make a server announcement on all frequencies, but just regular intention call outs.

Has there been a change? I think I remember you saying that the software won't kick admin, at all, but it now seems to be doing so to everyone, regardless of Admin status... An with just a basic call.

Thanks
Jon Bowles
United States

17th Feb 2012
21:45:08
Sorry this is for Our Server. I realized how the original message might confuse which I am talking about.
Dave Wave
United Kingdom

20th Feb 2012
08:38:06
No changes for a long time Jon.

Perhaps user has changed his key mapping so caps lock is transmitting on all freqs?
Jon Bowles
United States

24th Feb 2012
15:24:41
Sorry for such a late response... Been a bit busy.

Thanks for the reply Dave, but this is happening to me and several other of my Admin. I have Default Key Mappings. I have checked, and we are all on the ADMIN IP list, but not the Gamespy list, as we allow Direct Connect.

It first started with one of our guys, but now has escalated to more than three of us. I have since turned the Broadcast All freqs off, because we can't even announce our positions on UNICOM without getting the boot.

When one of us gets booted, the Chat Window says "Player Sven2157, spawning 127.1.1.1", or something to that effect (That is not the IP output, the BOT uses the actual IP ).

Also, the output window, has a very frequent message about the connection to your server, and Object couldn't be referenced. Sorry I just tried to get into the computer but I think that is down at the moment, or I would have the exact details for you.

If you would like, I could add your IP/Gamespy to the Admin file, and you could try yourself... I know you are a busy man, but I thought I would throw that out there... ;-)

Thanks,

Jon
Jon Bowles
United States

24th Feb 2012
16:00:54
Here, the system came back online. This is the message we get every time the BOT is running for more than 5 minuets: (For privacy reasons, I removed the 2 middle Octets of the IP addresses; the addresses come in fine though)

ReadyListeneningThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out
MaxMud98 is spawning IP=69.168The operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out
[FSX]RDA is spawning IP=201.73The operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out
ANGPilot42 is spawning IP=67.83
ANGPilot42 is spawning IP=67.83The operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out


Generally when it says an ID and their IP address, that is the BOT kicking people from the session. Including Admin.
Dave Wave
United Kingdom

27th Feb 2012
15:56:42
I wonder if you are all using the same add on that might be causing the issue?

The operation timed out means that your server cannot connect to fsopen database within 20 seconds. This can be due to a number of problems but normally due to our database being off line, poor network conditions somewhere between the two on the interweb or possibly you have saturated your upload capacity on your internet connection.

This does not affect anything on the server, it just means the information from your session failed to update to our server and so maps and live stats will be out of date.

If you connect to your session from a clean machine, make the ip an admin, and then xmit on all freqs is that player kicked?
Jon Bowles
United States

28th Feb 2012
18:50:50
With the option on, yes/no. Just single freq transmissions are kicking us, too. It seems as though the commands for the BOT are being ignored.

I also have an issue of friends requests still getting through, and kick the server off the Gamespy network.
Jon Bowles
United States

28th Feb 2012
18:57:26
Oh yeah, and the server, as well as, FSOpen Server is completely open. The firewall is not blocking them from the internet at all.
Grant Farmer
United States

1st Mar 2012
14:53:24
My server seems to work realy well, one minor problem I see on a daily basis is, why does the grid replace a players name with another player and clear all their information on both players when entering a session? example: player 1 enters session, player 2 enters session, player 3 enters session, then player 4 enters session, the grid will sometimes place player 4 as player 2 and all information on both players all cleared from the grid. The grid should read players 1,2,3,4, instead it reads players 1,2,2,3?
Mark Killen
Canada

24th May 2012
22:55:00
I wonder if you are all using the same add on that might be causing the issue?

Dave
What are you meaning by add ons?

Jon
Are you guys still having the same issue? If not what was the rectification
Curley Campbell
United States
25th May 2012
10:50:39
For what it is worth... I have seen the same issues intermittently for at least the past 4 months.
George Newhall
United States
25th May 2012
21:22:16

Same thing with me

ReadyListenening
fAbIaNw234 is spawning IP=188.22.28.110
kevinnico is spawning IP=92.73.72.236
crocker121 is spawning IP=71.91.0.146
kevinnico is spawning IP=92.73.72.236
crocker121 is spawning IP=71.91.0.146
Kristof1000100 is spawning IP=80.171.177.169
TacoLee is spawning IP=24.74.212.183
martin086 is spawning IP=86.19.170.45
martin086 is spawning IP=86.19.170.45
zorro.lizhi is spawning IP=99.241.121.217
willwager1 is spawning IP=78.151.48.80
MATRIX-4701 is spawning IP=94.197.127.244The operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out
jay_328592 is spawning IP=122.149.90.110
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
ccarlyon is spawning IP=94.205.130.180
adam1677 is spawning IP=108.217.204.41The operation has timed outThe operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out
Stealthfighter97 is spawning IP=85.110.2.78
Fireflight195 is spawning IP=65.31.218.102
Fireflight195 is spawning IP=65.31.218.102
delfonexxx is spawning IP=79.1.226.26
Bilal0786 is spawning IP=2.127.83.179
Youldsy is spawning IP=93.109.74.1The operation has timed outThe operation has timed outThe operation has timed outThe operation has timed out
MYBIGJONNY is spawning IP=86.15.94.158
Mark735 is spawning IP=90.193.6.223
kongounyoi is spawning IP=83.152.205.145
kongounyoi is spawning IP=83.152.205.145
kongounyoi is spawning IP=83.152.205.145
kongounyoi is spawning IP=83.152.205.145
MATRIX-4701 is spawning IP=94.197.127.251The operation has timed out
Dave Wave
United Kingdom

26th May 2012
21:44:38
George, I told you I was not going to support you. You know the reason why. I have now removed your account.
Dave Wave
United Kingdom

29th May 2012
15:28:45
Version 44 should fix the kicking problem



You need to Log on to post a reply.
Back to Board Index



Forum help

No politics, just flying
FSopen © 2009 - 2017
Page views: 43491357