Wrong location under Windows 10 running Prey 1.8.2

Hello,

I install Prey on a new laptop and like previous one, they are both located 16 kms far away from my current location shown in Google Maps (and correct).
I try to disable Location Services under WIndows10 settings as mentionned in Help Section but Google Maps become a bit less precise but Prey still show my laptop in a other city always same address 16 kms far away.

Is there any specific option to allow to let Prey have a correct location or rights to access this location ?
Is this wrong location due to free version or paid version will have this same behaviour ?

Thank you for your feedback.
Regards.

Hi there. Is the computer connected to an Ethernet cable or something similar?

No integrated wifi on a Lenovo Yogabook laptop previous same Macbook running bootcamp (same location for both 16 kms far away from real location).
I will make some tests tomorrow ; i’m travelling for two days so I will check the different locations and see with wifi if location and accuracy change.

Alright. Please keep us posted.

Another location wifi connection in railway station : Prey 900m from Google maps location (which was correct).

Could you please paste here the contents of your C:\Windows\Prey\prey.log file?

Here is the last two days :slight_smile:
████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.8.2 spreads its wings!
Current time: Wed Feb 20 2019 16:51:44 GMT+0100 (Paris, Madrid)
Running with PID 6740 as YOGABOOKC930_ over Node.js v4.5.0 on a x64 windows system (10.0.17134)

 info Wed, 20 Feb 2019 15:51:44 GMT Plugin loaded: control-panel
 info Wed, 20 Feb 2019 15:51:44 GMT 1 plugins loaded with 0 errors.
 info Wed, 20 Feb 2019 15:51:44 GMT Initialized.
 info Wed, 20 Feb 2019 15:51:44 GMT [triggers] Watching: connection, control-zones, hostname, location, network, power
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Starting trigger: connection
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Running: connection
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Starting trigger: control-zones
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Running: control-zones
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Starting trigger: hostname
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Starting trigger: location
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Running: location
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Starting trigger: network
 info Wed, 20 Feb 2019 15:51:44 GMT [actions] Starting trigger: power
 warn Wed, 20 Feb 2019 15:51:44 GMT [control-panel] Unable to sync settings.
error Wed, 20 Feb 2019 15:51:44 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
 info Wed, 20 Feb 2019 15:51:45 GMT [actions] Running: hostname
 info Wed, 20 Feb 2019 15:51:45 GMT [actions] Running: network
 info Wed, 20 Feb 2019 15:51:45 GMT [actions] Running: power
error Wed, 20 Feb 2019 15:52:02 GMT [network] Connection error: Error: socket hang up
error Wed, 20 Feb 2019 15:53:49 GMT [network] Connection error: Error: socket hang up
 info Wed, 20 Feb 2019 15:54:51 GMT [reports] Gathering status report.
error Wed, 20 Feb 2019 15:54:57 GMT [reports] Unable to get active_access_point: No access points found.
 info Wed, 20 Feb 2019 15:54:57 GMT [reports] Report gathered: status
 info Wed, 20 Feb 2019 15:54:57 GMT [control-panel] Posting event
 info Wed, 20 Feb 2019 15:54:57 GMT [control-panel] Got error: Network seems to be down. Check your connection and try again.
error Wed, 20 Feb 2019 15:56:38 GMT [network] Connection error: Error: socket hang up
error Wed, 20 Feb 2019 16:12:07 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 20 Feb 2019 16:28:04 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 20 Feb 2019 16:52:11 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Wed, 20 Feb 2019 17:04:12 GMT [network] Connection error: Error: socket hang up
error Wed, 20 Feb 2019 17:08:12 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Wed, 20 Feb 2019 17:13:12 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Wed, 20 Feb 2019 17:19:42 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 20 Feb 2019 17:48:09 GMT [network] Connection error: Error: socket hang up
error Wed, 20 Feb 2019 17:50:43 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 20 Feb 2019 17:50:45 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
 info Wed, 20 Feb 2019 20:12:45 GMT [reports] Gathering status report.
error Wed, 20 Feb 2019 20:12:51 GMT [reports] Unable to get active_access_point: No access points found.
 info Wed, 20 Feb 2019 20:12:51 GMT [reports] Report gathered: status
 info Wed, 20 Feb 2019 20:12:51 GMT [control-panel] Posting event
 info Wed, 20 Feb 2019 20:12:51 GMT [control-panel] Got 200 response: 
 info Thu, 21 Feb 2019 08:46:03 GMT [reports] Gathering status report.
error Thu, 21 Feb 2019 08:46:06 GMT [reports] Unable to get active_access_point: No access points found.
 info Thu, 21 Feb 2019 08:46:06 GMT [reports] Report gathered: status
 info Thu, 21 Feb 2019 08:46:06 GMT [control-panel] Posting event
 info Thu, 21 Feb 2019 08:46:06 GMT [control-panel] Got 200 response: 
error Thu, 21 Feb 2019 08:49:34 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Thu, 21 Feb 2019 08:51:56 GMT [network] Connection error: Error: connect ENETUNREACH 107.178.244.155:443
 info Thu, 21 Feb 2019 09:00:26 GMT [providers] battery_status already in progress.
 info Thu, 21 Feb 2019 09:01:47 GMT [reports] Gathering status report.
error Thu, 21 Feb 2019 09:01:52 GMT [reports] Unable to get active_access_point: No access points found.
 info Thu, 21 Feb 2019 09:01:52 GMT [reports] Report gathered: status
 info Thu, 21 Feb 2019 09:01:52 GMT [control-panel] Posting event
 info Thu, 21 Feb 2019 09:01:52 GMT [control-panel] Got 200 response: 
 info Thu, 21 Feb 2019 15:24:22 GMT [long-polling] Got 1 commands.
 info Thu, 21 Feb 2019 15:24:28 GMT [reports] Gathering status report.
error Thu, 21 Feb 2019 15:24:32 GMT [reports] Unable to get active_access_point: No access points found.
 info Thu, 21 Feb 2019 15:24:32 GMT [reports] Report gathered: status
 info Thu, 21 Feb 2019 15:24:32 GMT [control-panel] Posting data
 info Thu, 21 Feb 2019 15:24:32 GMT [control-panel] Got 200 response: OK

And strange behaviour, the location still indicate position at the office whereas I’m 70 kms far away (perhaps link to the fact that I"m connected to a CISCO Meraki Wifi access point) but Google Maps still my correct position.

Thank you for your help.
Regards

Thank you for the log! The key part is this one:

error Thu, 21 Feb 2019 15:24:32 GMT [reports] Unable to get active_access_point: No access points found.

Prey can’t access the Wi-Fi information from your computer. That’s why you don’t get the correct location. When that happens, Prey defaults to geoIP, which is a reference to the city or maybe neighborhood, if you’re lucky.

Could it be that you run some antivirus or firewall that could be preventing Prey from getting that data?

I am having this same issue…totally wrong state coming up in the location. My Google Maps showed the wrong one, too (I checked after reading a help file), but Prey is still wrong. I’ve gone through all the help topics and am not sure what to do. Thank you!