Posted by: Chris Barylick
Date: Thursday, March 17th, 2011, 11:32
Category: MacBook Pro, News, Software
As nifty as the 2011 MacBook Pro notebooks are, there may be some debugging that needs to be done.
Per AppleInsider, a number of early 2011 MacBook Pro owners report being unable to connect devices or maintain connections through iTunes Home Sharing.
A support thread in Apple’s Discussion forums has received over 200 posts from owners of Apple’s latest MacBook Pros reporting issues with iTunes Home Sharing. Several readers have also contacted AppleInsider regarding the issue.
“This is turning out to be a bigger problem than I thought with many people giving up and returning their new MBP 2011 due to this conflict. Apple has yet to find a fix but it has been widely documented via phone through AppleCare and through many Apple retail stores,” wrote one reader.
According to forum user ‘themacbear,’ the new MacBook Pro was able to stream to a second-generation Apple TV at first, but then the Apple TV reported being unable to connect or would display the error message “There are no movies in this library.”
In March, Apple released iOS 4.3 with new Home Sharing features. The Mac maker also issued iTunes 10.2 and then iTunes 10.2.1 to add compatibility with iOS 4.3 and Home Sharing. In spite of the updates, a number of users continue to report being unable to connect or maintain connections with iOS devices on their early 2011 MacBook Pros.
Recent improvements to the Home Sharing feature expand iTunes library sharing from just between Macs, PCs and Apple TVs to include mobile devices such as iPods, iPhones and iPads. When working properly, Home Sharing in iOS 4.3 allows an unlimited number of iOS devices to access content over Wi-Fi.
Though early 2011 MacBook Pros appear to be having the most trouble with Home Sharing, owners of older machines have also reported problems with the feature in a support thread for Home Sharing in iOS 4.3 that has reached 60 posts.
Stay tuned for additional details as they become available and if you’ve seen this issue on your end, please let us know.