![]() The only way we have found to get everything working again is to completely restart. When the problem occurs, Safari and Firefox stop loading pages, Mail stops opening attachments, and the printer (hooked directly into the USB port, not accessed through the network) stops printing. This error cropped up on our Mini, purchased less than 60 days ago. This is a software bug (as upgraded systems suddenly have the problem) and I'm hope the proper resolution is provided soon. ![]() I don't have a solution yet and likely won't, but I'll continue to research and post any findings here. Rebooting the system seems to resolve the problem for a while but the problem creeps back up. The source of the long return times and significant packet loss is beyond me at this point. They symptom and error code together make sense, but it is wrong. So, the error that is popping up would be shown by busy servers but, in this case it is an "incorrect" error code. The PC had no issues, but the mac showed not only large return times for the packets, but packet loss. A simple ping to form the affected mac laptop and a PC laptop. I dropped down to the command line and threw out a quick test. This isn't a problem with any specific website, router, or hardware (that I'm aware of). The commonality between the laptop showing the problem here and other users is the operating system. This indicates that is is specific to the system. Both of the macs are wireless, but only the laptop exhibits the issue. Of the 2 macs in the house, the laptop is at the latest level and the desktop at an earlier version of OS X (my appologies here - I'm a UNIX/PC guy and just throwing info up that I've noticed to help my girlfriend). The problem never manifests on the PCs, so that validates it is not a problem with the network. This is definitely a problem with the operating system. While I have my Windows PC I'll be able to get my WoW news just fine □ If someone knows what's going on, I'd love to read about it. And I think the PDF that explains these errors is lacking of the kind of details I seek. I just want to understand what's happening. I'm more interested in the details of the problem, as opposed to seeking its solution. (kCFErrorDomainCFNetwork error 302.)” (kCFErrorDomainCFNetwork:302) Please choose Report Bugs to Apple from the Safari menu, note the error number, and describe what you did before you saw this message."įirefox reports something similar, but not the same exact error.Įdit: I didn't mean to sound arrogant or condescending if I came across that way, my apologies. The error was: “Operation could not be completed. The error I get, after a long time waiting (~120 seconds) is: I cannot get to certain sites, with being the latest exhibit. ![]() So, to recap: I use Leopard, own an iPhone 3G and have iTunes 8 and iPhone 2.1 software installed. With this much reporting, Apple should have at least recognized there's an issue. Google search yields little help, which surprises me given the incredible number of folks that have this problem with blog-related sites, both on the iPhone and in laptops/desktops. but perhaps the web site is doing something to offend Mac OS X, because other web sites work just fine. I mean, I also have a Windows PC that can access the sites just fine on the same network. I've tried restarting the network router (both soft and hard restarts) but it makes no difference. I'm set up with O2 Broadband in the UK, and am using a double-NAT network solution to get to the internet (Public -> O2 Router -> AirPort Extreme -> laptop) and I don't have problems with other sites. This worked fine before, but not sure what changed (and when) that caused it not to work any more. from both Safari 3.1.2 and Firefox 3.0.1 on Mac OS X 10.5.5. In my case: I have the problem from time to time, but most recently when requesting I've done searches and I've seen the posts in the Apple Discussions, but they are all in iPhone related forums, and quite frankly I think this is a Mac OS X Leopard problem, perhaps introduced with the iPhone 3G. Yes - the dreaded kCFErrorDomainCFNetwork error 302 message rears it's ugly head again.
0 Comments
Leave a Reply. |