October 30, 2007 11:39
This is just an FYI for everyone. I've just spent days working with a user who couldn't download the latest version of Mr. Tides. The updater didn't work, the web site failed to load, even going directly to the iDisk via the Finder failed. It only occurred on two of his machines, so I was certain that it was a local networking issue.
After a lot of troubleshooting, it turned out that he had installed notMac on those two machines (notMac being a replacement for .Mac). Somehow notMac intercepted ALL calls to the .Mac site, including web.mac.com and idisk.mac.com, and every attempt to download the file failed. Well, it failed because the file wasn't on his server, it was on Apple's. Which wasn't reachable.
Big oops!
I don't know if notMac is configurable to avoid this problem or not. For now, I'd say leave notMac alone - at least until I finally decide if I want my own domain or not.
August
After a lot of troubleshooting, it turned out that he had installed notMac on those two machines (notMac being a replacement for .Mac). Somehow notMac intercepted ALL calls to the .Mac site, including web.mac.com and idisk.mac.com, and every attempt to download the file failed. Well, it failed because the file wasn't on his server, it was on Apple's. Which wasn't reachable.
Big oops!
I don't know if notMac is configurable to avoid this problem or not. For now, I'd say leave notMac alone - at least until I finally decide if I want my own domain or not.
August