GameTracker > Forum > General Help > DayZ Standalone - Server scan fails - old server still appears in GT list
Vultr.com - Instant Cloud Server Deployment
GAMETRACKER FORUMS
Forum Home > General Help > DayZ Standalone - Server scan fails - old server still appears in GT list
electrobug85PM
#1
DayZ Standalone - Server scan fails - old server still appears in GT list
Jan 12, 2015 4:51 PM
Joined: May 14, 2014
Posts: 2
I have purchased a new DayZ Standalone server from ViLayer. The server is set to track, but it shows the information for the server's previous incarnation as an ARMA3 server.

Please see:
http://www.gametracker.com/server_info/142.111.2.222:2502/

It currently shows the following server information:
Server Summary
Name: |eG| Ethix Gaming Altis Life Server
Game: ARMA 3 Browse: ARMA 3 Servers
Address: 142.111.2.222 Port: 2502 Status: Dead
Server Manager: None - Claim Now!

I have attempted to set the following scanning parameters:
Query Port: 2502
Game Type: DayZ

This server is currently online and running. Myself and others are able to connect to it without issue. Thanks for any help you can provide!
burnPM
#2
Jan 12, 2015 6:29 PM
Joined: Sep 27, 2006
Posts: 10924
When you turn this server back online you can update it via http://www.gametracker.com/server_info/142.111.2.222:2502/manage/
I am retired from GameTracker after 11 years and will not be responsive for support requests.

electrobug85PM
#3
Jan 12, 2015 6:31 PM
Joined: May 14, 2014
Posts: 2
Yes, thank you i have done that. It returns error "Could not scan server". I included the parameters in my original post. And as I mentioned in my earlier post, I have confirmed that the server is in fact online.
burnPM
#4
Jan 12, 2015 8:43 PM
Joined: Sep 27, 2006
Posts: 10924
Having difficultly locating any server at that address. Your host will need to properly configure their firewall to allow traffic on that port. Their welcome to use a tool like HLSW to test if it can scan as they try to resolve it.
I am retired from GameTracker after 11 years and will not be responsive for support requests.