iChat Video Problems + Solutions, or Don’t Return Your New Mac Yet
I love Apple’s iChat. Currently in version 4.0.2, and once known as iChat AV, this single, simple-looking program enables even novice users to quickly establish video, audio, or text chats, and is one of several key reasons that I repeatedly hear that people are switching to the Mac. But iChat has a serious problem: more than any other program most people use on the Mac, it depends on a properly set up network to work, and if your network’s not set up properly, it doesn’t provide detailed error messages or a troubleshooting wizard to help you trace what’s wrong. So when I heard that a family member just bought and almost returned a Mac because he couldn’t get video iChat to work properly, even after searching for help in Apple’s Discussions boards, Help menus, and Google, I realized that I might be able to share a few solutions that could help other people get iChat video chats to work as expected.
The problem: everything else on the Mac worked, but iChat would not connect for video chats. You’ve probably seen the generic error messages before: “There was a communication error during your chat.” “No data has been received for 10 seconds” timeouts. “User cancelled the connection.” “Did not receive a response from user.” And so on. My family member spent five or so hours with the MacBook’s integrated help system and people on the telephone trying to figure out what the issue was. Was it port forwarding? No. A lack of general Internet connectivity? No. User error? No. Nothing seemed to help, and the computer was literally moments away from being boxed and sent back to Apple. What ultimately worked in this case was a solution that, in my view, should be your starting point: the wireless router was removed, and the Mac was connected directly via a wire to the cable modem via its Ethernet port. Suddenly iChat began to work perfectly—no mysterious errors. This single step demonstrated that the Mac was capable of working, and that the cable modem was doing everything it should be doing, too. There was something wrong with the wireless router. Maybe. At this point, I will tell you a little something about wireless routers. People have really bad experiences with them, and the companies that sell them. Unfortunately, these problems actually come from numerous sources: existing wireless home phones, microwave ovens, other wireless devices, poorly made routers, poorly written wireless software and firmware for both the routers and wireless computers—the list goes on and on. Because there are so many ways that wireless networks can hiccup or fail, router makers often throw up their hands and leave customers to troubleshoot their own problems. They point to Apple and other computer makers. They point to the cable modems, DSL systems, and their providers. And then, when you call your computer or cable modem company, these companies point somewhere else. It’s nobody’s fault.
I can’t tell you for certain that the iChat problem you’re having is going to be the exact same one as discussed here, but I can tell you this: eliminating the wireless router as a cause is a critical first step. Once your computer is connected directly to your broadband modem, and you confirm that your web browser can connect with a web site, you can then test your connection with one of three little-known Apple iChat test buddies. These are added using the + icon on iChat’s buddy list, keeping the Account type as AIM, and creating 3 separate buddies by entering one name at a time into the Account name: field, hitting the Add button, and repeating that process until all 3 are added. appleu3test01 appleu3test02 appleu3test03
The next step is to click on the bright green camera icon next to one of these names, the first two of which run Apple commercials on non-stop loops (below), the third of which is supposed to mirror back your video to you. If one of the three names is grayed out, someone else is testing with it now, but if it’s bright green, you can connect and do a test right away. If it works and runs stable, your machine’s just fine and your connection is just fine. If it connects but runs sluggish, your Internet connection is probably to blame if you’re not running any other programs and using a recent (G5 or Intel) Mac.
If it doesn’t connect, run your Mac’s Internet diagnostics, found under System Preferences > Network, with the “Assist me…” button at the bottom of the screen. This process should sort out whether the problem’s in your Mac, your broadband connection, or the wireless router, and it’s probably going to be the router. If everything works, you can try to reconnect the router again and work through the problems.
When my family member reconnected the router, it was obvious that the issue was tricky to diagnose. The correct next step, and one that worked immediately to solve his problem, was to temporarily turn off wireless security altogether: once WPA was turned off, iChat worked perfectly. But what about the need for wireless security? Ultimately, experimenting with this feature—trying WPA2 security, for instance, making sure that both the router and the computer were set up to use the newer, apparently more reliable WPA2 standard—was something that solved an iChat problem I had long ago.
The ability to talk over video or voice chat with family members, friends, and/or business associates is a killer feature of the Mac platform, but it’s obvious that people who have iChat problems can find their new Mac enthusiasm killed instead. Until a troubleshooting wizard for iChat or better diagnostic error messages appear, the steps above should help you figure out what’s really wrong with the most serious iChat failures. I hope they’re as useful for your family as they were for mine.
If you have a comment, news tip, advertising inquiry, or coverage request, a question about iPods or accessories, or if you sell or market products, read iLounge's Comments + Questions policies before posting, and fully identify yourself if you do. We will delete comments containing advertising, astroturfing, trolling, personal attacks, offensive language, or other objectionable content, then ban and/or publicly identify violators. Wondering why we're talking about something other than iPods? Check the Archives: Backstage has been here and kicking it since 2004.
- Apple now selling SIM-free iPhone 6s and iPhone 6s Plus
- AT&T opens up Wi-Fi calling for iPhone
- Battery impact of Samsung vs TSMC A9 chips overestimated? (Update: Apple response)
- Apple TV, iPad Pro to be sold online in late October, in stores early November?
- iBooks adds exclusive enhanced editions of Harry Potter series
- Report: Barclays to launch Apple Pay support in the UK early next year
- Apple reveals Beats Pill+ speaker
- Antitrust monitor: Apple is ‘its own worst enemy’
- Report: Apple holding $181.1 billion in offshore tax havens
- Apple releases fourth iOS 9.1 beta, third tvOS beta to developers
- Creative Sound Blaster Roar 2 Bluetooth Speaker
- Parrot Airborne Night and Airborne Cargo Drones
- Griffin Survivor Journey and Survivor Summit for iPhone 6/6s
- Parrot Jumping Night and Jumping Race Drones
- Trident Case Aegis Pro Case for iPhone 6/6s
- Scosche boomBOTTLE+ Waterproof Wireless Speaker
- Just Mobile Quattro Folio for iPhone 6s
- X-Doria Defense Lux for iPhone 6s/6
- Spigen Perfect Armor for iPhone 6s, Slim/Tough Armor for iPhone 6s Plus
- Spigen Neo Hybrid / Carbon / EX + Ultra Hybrid for iPhone 6s/6s Plus
- Instant Expert: Secrets & Features of iOS 9.0
- Under the Radar: A closer look at smaller iPhone 6s and iPhone 6s Plus changes
- A First Look at iOS 9’s Transit in Apple Maps (Updated for watchOS 2)
- Instant Expert: Secrets & Features of iTunes 12.2
- Instant Expert: Secrets & Features of iOS 8.4 + Apple Music
- CE Week 2015: IK Multimedia, Monowear’s Apple Watch bands + More
- Live From CE Week 2015: Brand New iPad, iPhone + Mac Accessories!
- Opinion: The ‘Grand Experiment’ of shifting to Google Photos
- Will removing a credit card from Safari also remove it from Apple Pay?
- Can I mute Handoff calls coming into my Mac from my iPhone?