I'm seeing this error too. It's okay through the web login, but it's very frustrating.
Failed to sign in. (-26000)
If you get -26000 error code on AirDroid Windows/Mac, please leave your AirDroid account here and attached your AirDroid logs. More details: http://forum.airdroid.com/discussion/14 ... red#latest
Hey folks.
Just wanted to mention that I believe a reboot of my Yosemite-infected (LOL) Macbook Pro may have helped the software to finally make the connection.
As many of you may well know, Yosemite introduced several issues to wifi stability. (As well as other subsystems - in particular graphics switching...) I wonder if this may be a contributing factor?
At any rate... A reboot later on seemed to have gotten me connected. Could you all try that and report your result here? Seems like a practical way to rule out or focus on certain things.
Just wanted to mention that I believe a reboot of my Yosemite-infected (LOL) Macbook Pro may have helped the software to finally make the connection.
As many of you may well know, Yosemite introduced several issues to wifi stability. (As well as other subsystems - in particular graphics switching...) I wonder if this may be a contributing factor?
At any rate... A reboot later on seemed to have gotten me connected. Could you all try that and report your result here? Seems like a practical way to rule out or focus on certain things.
@pyrrh0
Yep. I'm a data center engineer myself. I was connected to our corporate network, however. I doubt that any TCP/UDP ports would be the issue. Seeing as how this is a client/server scenario and the Macbook software is reaching out to the phone; it's more of an outbound connection request which should obviously run much smoother than an inbound connection request.
We don't mess with the corp network there unless the switches or other infrastructure experience issues, though. It's a whole separate network than what we're concerned with. We're more focused on production gear and relevant switches/routers.
The fact that I was later able to connect supports this conclusion, of course. Try that reboot, sir. See what kind of results you get?
Yep. I'm a data center engineer myself. I was connected to our corporate network, however. I doubt that any TCP/UDP ports would be the issue. Seeing as how this is a client/server scenario and the Macbook software is reaching out to the phone; it's more of an outbound connection request which should obviously run much smoother than an inbound connection request.
We don't mess with the corp network there unless the switches or other infrastructure experience issues, though. It's a whole separate network than what we're concerned with. We're more focused on production gear and relevant switches/routers.
The fact that I was later able to connect supports this conclusion, of course. Try that reboot, sir. See what kind of results you get?
Same issue here. Am on Yosemite and get errors logging in.
Have rebooted the system and still get -26000 error.
No luck with Mac desktop client.
Have rebooted the system and still get -26000 error.
No luck with Mac desktop client.
Same problem...Failed to sign in. (-26000)