Els E

Q: pairing the wireless keybord doesnt't work properly

Our Imac doesn't recognise the wireless keybord anymore (suddenly todag), neither does the ipad air, but the ipad 1 connects fine, how is this possible? both ipad1 and ipad air work with ios 8.3. 

iMac, iOS 8.3, As well as ipad air and ipad 1

Posted on May 30, 2015 11:17 AM

Close

Q: pairing the wireless keybord doesnt't work properly

  • All replies
  • Helpful answers

  • by jeremy_v,Helpful

    jeremy_v jeremy_v Jun 1, 2015 9:13 AM in response to Els E
    Community Specialists
    Jun 1, 2015 9:13 AM in response to Els E

    Hello Els E, 

     

    Thanks for visiting Apple Support Communities. 

     

    It sounds like your Apple Wireless Keyboard is not recognized by your iMac or iPad Air, but you can pair it with your iPad 1. 

     

    In this situation, start with the troubleshooting advice in the "Wireless Connection issue" section of Troubleshooting wireless mouse and keyboard issues

     

    If you're pairing the keyboard with your iMac and see "the pairing attempt was unsuccessful, see the information in Apple Wireless Keyboard: Difficulty during pairing process.

     

    For more help with your iPad Air, see the steps in Get help connecting your iOS device with a Bluetooth accessory as well.

     

    Best Regards,

     

    Jeremy 

  • by Els E,

    Els E Els E Jun 1, 2015 10:09 AM in response to jeremy_v
    Level 1 (0 points)
    Jun 1, 2015 10:09 AM in response to jeremy_v

    Hi Jeremy, thanks for your help. I already tried a lot of steps you mention. But in the meantime yesterday I got both ipads working with the keybord.

    Then the issue remained that the Imac still didn't work with the keybord. So I got us an attached keybord with which at least we could enter the imac.  As We had also  heard from a friend and in the meantime read online that Yosemite was not always steady with the remote appliances, we checked if there was an update and there was. Something with remote client.....we didn't understand but we executed it anyway. And you don't believe it: After the update we tried again and YES, we got it working. So we are not sure if it was truly the update, but otherwise it was a great coincidence as we already tried many times in vain.

    So problem solved, but thanks again for your help. Maybe this answer can also help other people.

    Kind regards,

    Els

  • by jeremy_v,

    jeremy_v jeremy_v Jun 1, 2015 4:09 PM in response to Els E
    Community Specialists
    Jun 1, 2015 4:09 PM in response to Els E

    Hi Els, 

     

    Thank you for your reply. I'm happy to hear that it's solved. 

     

    Cheers, 

     

    Jeremy