traccar 3.10 on windows server not work

olivier8 years ago

Hello

I installed traccar 3.10 on a windows server of AWS. The problem is that my device tk102 does not connect on port 5002 or 5023 or 5013 . as you can see on the detail below, ports 5002 and others are listened by java.exe . Is this normal? I disabled the firwall and opened all tcp ports on EC2 AWS but no result.

Thank you in advance for your answer.

sorry for my bad English . I'm from France

TCP    172.31.23.104:50099    sea15s12-in-f206:https  ESTABLISHED
 [firefox.exe]
  TCP    [::]:135               EC2AMAZ-DT7872G:0      LISTENING
  RpcSs
 [svchost.exe]
  TCP    [::]:445               EC2AMAZ-DT7872G:0      LISTENING
 Can not obtain ownership information
  TCP    [::]:2179              EC2AMAZ-DT7872G:0      LISTENING
 [vmms.exe]
  TCP    [::]:3389              EC2AMAZ-DT7872G:0      LISTENING
  TermService
 [svchost.exe]
  TCP    [::]:5001              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5002              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5003              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5004              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5005              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5006              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5007              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5008              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5009              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5010              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5011              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5012              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5013              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5014              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5015              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5016              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5017              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5018              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5019              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5020              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5022              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5023              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5024              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5025              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5026              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5027              EC2AMAZ-DT7872G:0      LISTENING
 [java.exe]
  TCP    [::]:5028              EC2AMAZ-DT7872G:0      LISTENING
Anton Tananaev8 years ago

Check troubleshooting guide:

https://www.traccar.org/troubleshooting/

olivier8 years ago

hello anton

thanks for your fast replay i have checked the guide. i can connect my phone on the serveur by using port 5055

but tk102 not working on the serveur and nothing about my tk102 in the log file.

thanks you for your help

Anton Tananaev8 years ago

It likely means that your device doesn't send anything, or is configured incorrectly.

olivier8 years ago

Is it possible that these ports are blocked by aws?
Because I installed under linux and it does the same

Anton Tananaev8 years ago

Please carefully read troubleshooting page.

  1. assign the port 5006 initially
    tk102 commands

assign APN
apn123456□cmnet□User name□ password
assign ip
adminip123456□192.168.1.1□5006
note : use your server ipaddress, the above ipaddress is a sample
assign gprs mode 0- TCP 1- UDP
gprsmode123456□0

  1. check /opt/traccar/logs/tracker-server.log
    if you receive some hex codes find the device id and copy that, add the device id to traccar web interface under add device, then you will be able to view the device in map

if not then its problem with your device settings or your device not sending data to server

olivier8 years ago

THANK YOU
I forgot the configuration of the apn :) it works now

thanks

great and happy you have resolved.
if possible please make any amount of donation that you can to Anton @ https://www.traccar.org/donate/
To honor his hard work and effort.
He deserve it

Thanks