![]() There is nothing more, that we or you can do here. Send your update and location to grab and use their updates, when we release a new server version. If the latest server did not solve your problem.ģ. Open command prompt and type in tracert then type in the website for example tracert without these things. Here is the way to solve this problem for a future server release. So always use the latest server to ensure it's the latest DB, before reporting here. We put the update of the flag database into the server, when a new server was released. It's hardcoded and can not be replaced/updated from you. This service needs a database, which is included in the server. We use an external service to resolve the country for users. IP2Location geolocation data helps users to detect the location of persons by their IP addresses. They update the data when they release new versions so the data used depends on which version of TeamSpeak the server is running. Pros and cons of IP2Location IP geolocation database vs. However, you can type any IP Address to see its location and other geodata. This service is 100 free and provided by third-party sites in the form of Geo-Location databases and APIs. TeamSpeak embed the geolocation db from into the server. Our tools include checking your public IP as well as checking the physical location of IP owner. This is what they had to say when I last reached out to them. That's still an issue for the server admin to resolve unless every Teamspeak server somehow speaks to a geo-location database administered by Teamspeak (which looks unlikely, based on the fact I get different flags for different servers whilst assigned the same IP address). The server you're connecting to is incorrectly identifying the first subnet as being geo-located in the USA. Your connection drops, you reconnect to the same server, you're assigned an IP in a different subnet and your flag switches to UK. ![]() You probably had a USA flag whilst assigned an IP from the 146.198.0.0/16, 146.199.0.0/16 or 146.200.0.0/16 subnets (these are the ones we know cause some issues). ![]() I don't understand how that points to it being a Teamspeak issue? Looks like it's a job for the server admin, rather than Teamspeak themselves?Ĭompletely disagree, because I was on a server a few nights ago and my flag was USA, my connection dropped and my flag changed to UK. I seem to get both UK and US flags depending on the server I'm connecting to: In fact, thinking about this one, the geo-location is probably dependent on the server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |