Unable to Sync via WiFi due to wrong IP address

Dklaus

I am currently unable to Sync from my iPad 2 to my Mac over a WiFi connection. My iPad is running iOS 8.4 and my Mac is running 10.10.3. When I select "Sync Now" on the iPad (with 1 Password unlocked on the Mac) it eventually times out with the message "Error Domain=NSPOSIXErrorDomain Code=60 The operation couldn't be completed. Operation timed out.". I have traced this to the fact that the IP address shown in 1Password on the iPad is not the one my computer is assigned. In 1 Password the computer is listed as "Davids mac Pro 192.168.4.10:63447" while on the Mac the Network control panel lists it as 192.168.4.101. The version of 1 Password on my iPad is 5.4.3. Any ideas on what the cause is?

---

1Password Version: 1Password 5 Version 5.3.2 (532001)
Extension Version: 4.4.2
OS Version: OS X 10.10.3
Sync Type: WiFi
Referrer: forum-search:unable to sync

Stephen_C

I suspect it's one of those occasions when OS X 10.10.3 has simply just got into a muddle. (Incidentally, 10.10.4 is much better with things like this: it's worth updating if you can.)

Please try this:
1. reboot both your devices; and, if that doesn't work
2. reboot your router.

Stephen

AGAlumB

"Error Domain=NSPOSIXErrorDomain Code=60 The operation couldn't be completed. Operation timed out."

(Incidentally, 10.10.4 is much better with things like this: it's worth updating if you can.)

@Dklaus: Indeed, 10.10.4 will run on your machine since you've already got Yosemite, so be sure to update. It's solved a lot of my network woes. And it does appear that you might have a cache poisoning issue (discoveryd can be pretty insidious).

At the very least you may need to shut down all (yes all) of your Wi-Fi connected devices along with any routers for a few minutes to clear everything, and the Bonjour should be able to pick up the current IP just fine (the error you're receiving is a simple timeout due to the invalid IP). But seriously, just update. ;)

Dklaus

Stephen, thank you. Rebooting both the iPad and Mac Pro resolved the issue. And yes, 10.10.4 update has been on my to-do list.

AGAlumB

@Dklaus: Awesome! That's been my experience as well. Thanks for the update! And don't put off that update any longer if you can help it. It will save you a lot of time and aggravation. :lol: