Jump to content

Frontlines Help with server browser


xpservers

Recommended Posts

Im hoping someone can help out. Ive run out of ideas and frontlines forum is not helping either.

 

I rented out my first frontlines server and the user is complaining they cannot see the server in the server browser in game. The ping shows xxx however you CAN connect to the server via IP address. I have removed the firewall so all ports are open. netstat -a displays ports are listening properly.

 

Also when the user tries to connect with server remote it says

 

...no connection could be made cause the target machine openly refused it 67.213.79.51:14507

 

Some of my configs:

 

[Configuration]

BasedOn=..\Engine\Config\BaseGame.ini

 

[Engine.GameInfo]

DefaultGame=GCGame.GCDefaultGame

DefaultServerGame=GCGame.GCDefaultGame

MaxPlayers=26

ArbitrationHandshakeTimeout=10.000000

InactivePRINum=16

InactivePRILifeSpan=300

 

[GCBaseGame.GCBGame]

;time between rounds before resetting level

ResetTimeDelay=20

;time between maps rotate in on a dedicated server

RestartWait=30

bGameRulesDictateEjectRules=False

 

[Engine.AccessControl]

AdminPassword=Blitzer

;GamePassword=game

 

[Engine.RemoteConsole]

;Admin username

AdminName=admin

;Admin Password (blank for disable remote console)

AdminPassword=

;ListenPort 14507 is default

ListenPort=14507

;ListenBindIP 0.0.0.0 is default

ListenBindIP=67.213.79.51

;MaxClients that can connect via remote console at the same time

MaxClients=7

;Time in seconds after initial connection to wait for username/password response

LoginTimeout=7

;Prevent an individual IP address from taking up all remote console slots

MaxConnectionsPerIP=2

 

 

Generated Command Line:

C:\UserFiles\chris\GameServers\TC35474000873010220854031\Binaries\FFOW-Dedicated-Logging.exe server FL-Roundabout -online -unattended -seekfreeloading -ServerPerfStats matchmakingport=9103 CustomPublicIP=67.213.79.51 MultiHome=67.213.79.51 Port=5476 QueryPort=5478

Link to comment
Share on other sites

I had to remove the matchmakingport on one server to get it to work properly. Remove that from the command line and try again.

 

Also make sure you configured the

 

GCGame/Config/DefaultGame.ini

 

properly.

 

I removed the matchmaking port setting and still having problems.

 

I attached a copy of defaultgame.ini for your viewing

DefaultGame.txt

Link to comment
Share on other sites

%primaryip% doesent work,, I have to manually override it. Does it work for you

 

Here is my command line now. User says the server shows up in the browser but again ping says xxx and they cannot connect via browser only directly from IP

 

FFOW-Dedicated-Logging.exe server FL-Roundabout -online -unattended -seekfreeloading -ServerPerfStats matchmakingport=9103 CustomPublicIP=67.213.68.10 MultiHome=67.213.68.10 Port=5476 QueryPort=5478 PingRedirectIP=67.213.68.2

Link to comment
Share on other sites

Thanks HIS

 

does your command line look like mine ?

 

FFOW-Dedicated-Logging.exe server FL-Roundabout -online -unattended -seekfreeloading -ServerPerfStats matchmakingport=9103 CustomPublicIP=67.213.68.10 MultiHome=67.213.68.10 Port=5476 QueryPort=5478 PingRedirectIP=67.213.68.2

Link to comment
Share on other sites

Thanks HIS

 

does your command line look like mine ?

 

FFOW-Dedicated-Logging.exe server FL-Roundabout -online -unattended -seekfreeloading -ServerPerfStats matchmakingport=9103 CustomPublicIP=67.213.68.10 MultiHome=67.213.68.10 Port=5476 QueryPort=5478 PingRedirectIP=67.213.68.2

 

looks right if .2 is your primary

Link to comment
Share on other sites

This is what your command line should look like:

 

FFOW-Dedicated-Logging.exe server FL-Roundabout -online -unattended -seekfreeloading -ServerPerfStats matchmakingport=9103 CustomPublicIP=67.213.68.10 MultiHome=67.213.68.10

 

Also set it to unranked

 

This game is a P.O.S.

Link to comment
Share on other sites

CustomPublicIP=67.213.68.10 MultiHome=67.213.68.10

 

If these two IP's are not your primary then the server will show xxx ping in the lobby and return unreachable when trying to enter it. CustomPingIP needs to be set. I tested it last night.

Link to comment
Share on other sites

Custom Ping Ip being my primary box ip right ? my primary box ip is 67.213.68.2

 

So would this be correct:

 

FFOW-Dedicated-Logging.exe server FL-Roundabout -online -unattended -seekfreeloading -ServerPerfStats matchmakingport=9103 CustomPingIP=67.213.68.2 CustomPublicIP=67.213.68.10 MultiHome=67.213.68.10 Port=5476 QueryPort=5478 PingRedirectIP=67.213.68.2

 

I also ran the FFOW_QueryProtocolTest.bat in the tools folder and got this output. Not sure if this is of any importance.

 

Frontlines: Fuel of War server query v1.1

CreateSocket() 0.0.0.0:23808 Socket:00000328 Fam:2 Type:2 Prot:0

 

QueryServer() 127.0.0.1:5478 Retries:2 TimeoutSecs:3.000000 HrzOutput:1

... wait for response, BytesSent: 8 AttemptNum: 0/3

Error RecvFrom()! Value: -1 LastErrorCode:10054

WSAECONNRESET

--Finished--

Link to comment
Share on other sites

Well i FINALLY figured it out. Something really stupid and I feel like an ass lol.

 

It was more than one thing I think. When my user submitted a ticket I tried with some test servers and it still didnt work thinking an issue with a TCADMIn config or global config.

 

After adding pingredirect I only tested the users server and not my test servers. If i would of tested my test servers I would of noticed that this was the initial issue which resolved the problem

 

Anyway it still didnt work for my user so i looked into the .ini file and noticed this user put servername==TRB=

 

You cant have 2 equal signs in a row lol

changed it to servername= =TRB= and it worked

 

Thanks again guys !!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Who's Online   0 Members, 0 Anonymous, 5 Guests (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use