I am a hybrid user. I have Apple devices that The Kiddo & I just love (4 iPods of various stripes, 2 iPads) and I use iTunes for Windows to manage all their content. I also use a good anti-virus & firewall, and I make sure that my computer is always up-to-date with the latest Windows patches.

I’m a pretty model user, as far as such things go. So, when iTunes needed to download & install updates to my devices, I didn’t think much of it.

Imagine my shock when, for seemingly no reason, installing Apple updates through iTunes started resulting in errors — typically, when iTunes would try to “verify with Apple.” Not just any error, of course: Error 3194.

In my house, Error 3194 is known as The Unresolvable Error. Oh sure, Apple has a lot to say about fixing it:

 Resolve error 3194 by updating to the latest version of iTunes

Ummm, ok.

For good or ill, I always update iTunes when a new version comes out. So, when the dread Error 3194 darkened my humble doorstep, I was already running the latest version.

iTunes Diagnostics

On a lark, I ran a diagnostics report to see what it came up with. It confirmed what I suspected: iTunes couldn’t communicate with Apple’s servers. Most likely the verification servers since iTunes never had any trouble downloading device updates. At any rate, not especially helpful, but it felt good to know that the software & I were on the same page.

Modifying the HOSTS file

Ok, so what next? I got some more info from OS X Daily:

If you run into Error 3194 within iTunes when you are trying to restore your iPhone, iPad, or iPod touch, you can fix it by temporarily blocking Apple’s firmware signing services. Error 3194 seems to be triggered when unsigned firmware is used, often during an iOS downgrade or even during some restores.

This worked for a little while. iTunes still wouldn’t install device updates on its own, but I could still download them. Then, I could press SHIFT while clicking Update or Restore in iTunes to point to the downloaded file and install it manually.

Unfortunately, this fix didn’t last forever. A search of the Apple support community revealed that I should probably remove the line I added to my HOSTS file, so I used this Microsoft KB article to just reset my HOSTS file to the default.

But this didn’t work, either. Error 3194 refused to back down.

Firewall Rules

Next, I found this Apple support article which lists several things to check with regard to security software. Now, as a seasoned Windows user, I come across software all the time that says “make sure to disable your firewall as it might interfere with this program” and it rarely turns out to be true. However, with iTunes, I was willing to give it a shot.

So, I disabled my firewall and tried to update again. Still, no luck. This article also suggests uninstalling my firewall, but of course this is a deal-breaker. Indeed, I’m thinking how very like Apple to suggest doing the one thing no sane responsible Windows user would EVER do (right?). I mean, it’s tantamount to waving a giant red flag in the midst of cyberspace and screaming, “Hey, hackers!! Woo-hoo, I’m over here!! C’mon in and have some tea!” It’s like the ghost of Steve Jobs is taunting me: “How badly do you want to update your iPods, you Windows heathen!?!?” As it turns out, pretty badly. I uninstalled my anti-virus & firewall and tried again. Still nothing. Indeed, I thought for a moment I could hear Error 3194′s maniacal laughter.

The article also lists the ports and servers that iTunes needs access to. So, after re-installing my anti-virus/firewall, I created custom rules that specified the servers (I didn’t need to specify the ports since these are enabled by default). Once done, I tried to update again, and again Error 3194 jeered at me.

Is it iTunes or is it Me?

After being thwarted by Error 3194 yet again, I started wondering what my security software maker, ESET, thinks about all this. One Google search later, I found this #1 result:  iTunes not working with your Windows ESET security product?

It was then that I realized I hadn’t upgraded my anti-virus/firewall program since I bought it 4 years ago. After I finished kicking myself, I proceeded to upgrade and then performed the rituals required to make sure nothing iTunes did was blocked.

Once I’d restarted, I tried once more: I pointed iTunes to the update file I’d already downloaded and attempted to install manually. I still got an error, but it was a different one, indicating the update file was corrupted.

I download the file again, through iTunes, straight from Apple. Three hours later, iTunes prompts me to install it and I say “Ok, install it already, you bastard.”

This time, something altogether wild and strange happened. iTunes installed the update.

No pauses. No errors. Just a confirmation message indicating the update installed successfully.

Holy crap, it’s a miracle!!

Recap

I don’t think I can adequately express my joy and relief at being able to update my devices. If you’re wrestling with Error 3194 and your Apple device isn’t jailbroken, here’s a checklist you can use to make sure you’re doing everything you can:

1. Make sure your operating system has all the latest updates and patches.
2. Make sure your HOSTS file doesn’t have any screwy IP addresses that Apple doesn’t like. Basically, either make sure your HOSTS file has the default verbiage for your OS or make sure the IP addresses that are there are non-Apple ones. (Indeed, hopefully, any changes to your HOSTS file are ones you’ve made, yourself. If not, then you have more serious problems than faulty iTunes updating.)
3. If you use a third-party anti-virus firewall solution (like me), try the following:
• Disable the software.
• Uninstall the softeware.
• Make sure it’s upgraded to the latest version. Also, search the maker’s knowledge base for any iTunes articles. In the time since you bought your software, they could have published something that solves this problem. If they haven’t, send them a support ticket & pester them mercilessly for a fix.
4. If you’re using Windows Firewall: iTunes 10 for Windows: Enable iTunes in the Windows Firewall

If you’ve tried all this and you’re still getting Error 3194, you are now free to backup all your data, wipe your hard drive clean, and rebuild your computer (or pay someone to do it). The items I list above are the sum total of all the info I’ve been able to find on this error. So if you’re still stuck and you’re not willing or able to dissect your computer on your own, then starting anew might be the last resort.

Hopefully, after reading this, you’ve been able to resolve this maddening situation with Error 3194. If you have, please feel free to leave me a comment and let me know. I love to hear good news!

If not, please don’t ask me to help. I’m just as clueless are you are. I’ve only written this article to consolidate what I’ve learned and share what’s worked for me. However, if you learn something more that I haven’t included, please do leave me a comment so I can update this post. Thanks!!

Well, if you’re using Windows, that’s not always the case.

It took me about 2 days of near-nonstop futzing to get the Airport Extreme and Airport Express base stations to work (and keep working). The issues I experienced were experienced by many, many others, some of whom documented their resolutions which in turn got me closer to getting things working. I’m writing this article to record my own resolution, paying it forward as it were.

The Purpose

Why install a wireless network? Among other things, I wanted to be able to stream music from iTunes to other rooms in my home. Since I don’t subscribe to a cable or satellite provider, I also wanted to eventually stream movies from my Netflix account to my TV.

The Setup

My Dell desktop computer is fairly recent, but it did not come with a wireless card. As far as setup, I just have a DSL internet connection and run Windows XP.

The Equipment

• 1 Airport Extreme base station to create the wireless network
• 1 Airport Express to extend the wireless network to another room and use AirTunes to stream music through iTunes

The Issues

Installing the Extreme (and later, the Express) was a no-brainer: Plug it in. Configuring the thing was something else entirely. My issues:

• The Airport Utility wouldn’t detect the base stations. I’d rescan and rescan, but they’d never show up. Eventually, the Extreme showed up (yeah, after 3 hours of restarting and rescanning) and configuration was a breeze after that. However, no amount of rescanning or restarting could get the Express detected. I briefly entertained the notion that it might just be a bad unit — after all, there are plenty of people who’ve had the same problem, replaced the unit, and everything worked. I knew my unit was good, though, because it would show up as a generic network (Apple Network 123456) on my iPod touch.
• The Airport Utility couldn’t communicate with the Express. Once I got the Express detected (more on that later), I had to configure it as an network extender. Unfortunately, the Airport Utility would return Error 6753 or Error 6722 every time I selected the Express and clicked either Manual Setup or Continue.
• The Airport Utility wouldn’t redetect the Express. Once configured, the Airport Utility needed to restart the Express. However, after the restart the utility couldn’t detect the device again. I could click “Configure Other” and enter its IP address to launch the configuration panel, but it wouldn’t show up as a configured device alongside the Extreme.

The Resolution

1. I turned off my firewall and antivirus. I use ESET Smart Security in automatic mode, which means it defaults to blocking traffic if there’s no rule allowing it.  When I turned it off, the Airport Utility was able to detect the Extreme and then later, the Express. Update: When I wrote this, I had only my third party security software running on my machine, and Windows Firewall was turned off by default. As one commenter noted, this might not be the case for everyone. So, when turning off your security software, double-check Windows Firewall to make sure it’s well and truly off as well.
2. After I established the network with the Extreme, I connected the Express to an Ethernet port on the Extreme. After a couple of minutes, the Airport Utility detected the device.
3. I ensured the security protocols I chose on both the Extreme and the Express matched. I also noticed that if I configured the Extreme as a 802.11n only (5 GHz) network and set the security to WPA2 Personal, the iPod touch couldn’t join the network. That worried me — if the iPod touch can’t join the network, it’s possible other wireless devices I want to use might not, either. So, I set the Extreme up as a 802.11n (802.11b/g compatible) network and set the security to WPA/WPA2 Personal on both the Extreme and the Express.
4. To resolve the Error 6753 issue, I used the solution in this Apple Support forum article. When I connected the Express via Ethernet, the Airport Utility detected it and displayed its IP address when I selected the device, which I wrote down. I also opened a command prompt in Windows and ran ipconfig to get the IP address, subnet, and gateway of my computer. I changed the computer’s IP to one in the range of the Express’ default IP — voilà, the Airport Utility could connect and let me configure the Express. I configured the Express to use an IP in the range of my computer’s original IP and then restored my computer’s original IP. Voilà encore, the Airport Utility could still detect and connect to the Express.
5. I fine-tuned my firewall. When I finished configuring the Express and set it up again in the target room, I turned my firewall and antivirus back on. The Express worked for a little while, but then Airport Utility wouldn’t detect it. To resolve this, I switched my firewall to “interactive mode” and used this article to open the right ports.

While I’m glad I got this all working, it was incredibly frustrating. Indeed, I opted for the Apple hardware in the first place because it was supposed to be so easy to set up. I guess it is easy when you’re all-Apple. But woe betide you if you mix makers.

Anyway, hopefully this will be useful to anyone else dealing with Airport issues. If it is, feel free to leave me a comment.