Here is my exact quote from case #08768023. Had anything been done to fix the problems I would not be bringing it up now but since false information was again sent today see below...
"We need to see if there is anything we can do about fixing your very inaccurate location database. Is this something you need help with? Just this last Sunday I was sitting in church with one of my emloyees who are forced to authenticate as if they were not in a familiar location and as it turns out your system thought they were in Silver Springs, Nevada. Do you have anyone technically competent enough to look at a map and figure out how far Yreka, CA is from Silver Springs, NV and start to make your service a little better without you committing what will end up being perjury in court if you do not admit your geolocation service stinks. I hate to point out the obvious but when a judge and jury looks at this and is asked if Yreka, CA is Silver Springs, NV you are pretty much hosed. It might be time to pull your head out of the sand. "
hammer185 Thanks for the feedback and the case scenario. While the risk based authentication methods are the industry standard at this point, you raise some valid points with regards to mobile users, and the behaviors of their telecom providers. I.e. where they are routing traffic through, and how this automatically triggers a device warning on our side.
So what is the problem besides something like arrogance, obstinate stupidity, or just a total lack of common sense? Does LogMeIn lack the intelligence to explain where they got the location data from in any scenario that may come up and cite the source in case it's wrong. Do you have a business policy problems or just stupid programmers or something like that. You obviously have a serious problem if you know often the data in the emails you send out about locations is wrong and yet you refuse to acknowledge that it may be incorrect and cite the source of the data so it can be looked into when its wrong.
hammer185 This is actually the first time something similar has been reported.
Under most circumstances, if a user is having difficulty with the RBA authentication, Customer Care can help to 'whitelist' specific devices. When I use the term 'device', I don't mean one location or computer -- but several qualifying factors that go into the risk factor.
I am the owner and manager for my company on these things. I want accurate location data to be used in making these informed decisions. I expect others in my position making these decisions would feel similarly. These are not personal devices we use, they are work tools often used for remote access when needed in helping our customers and keeping our networks running. I do not want to just "whitelist" a device or devices that could potentially be stolen and we might not notice it until it's been used to get into a system I do not want gotten into by the thiev(ves).
If the location data were accurate there are several cool things we could probably do. The location data has to be accurate though.
