Benches macOS

16

No Network access: NSPOSIXErrorDomain:1

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I can't do anything that requires internet access--I can't access any websites in Safari, check for software updates, access email using Mac Mail, nothing.

In Safari, I get an error message saying "Operaiong could not be completed. Operation not permitted" (NSPOSIXErrorDomain:1) Please choose Safari > Report Bugs to Apple, note the error number, and describe what you did before you saw this message. (As for what I did before I saw this message, I can only answer, "I turned my back while my toddler was near my laptop... 😟. )

I get a similar message in Mac Mail; in Firefox, just a message saying it can't access the webpage; in software update, nothing at all.

I've looked for answers online; nothing seems to help. It does not seem to be a networking issue; according to Network Diagnostics my connection "appears to be working normally" and the other computers in the house can connect just fine. Nor is it restricted just to Safari, unlike most of the other NSPOSIXError discussions I've found. (I tried reinstalling Safari just in case, but it didn't help.)

Any thoughts? Would reinstalling the OS fix it, do you think? And if so, what do I need to do/know before I take a drastic step like that? (Don't be afraid of talking down to me πŸ™‚.)

16 replies

Sign in or join Beachball Help to reply.

  1. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Try this. Go to Library/Preferences/SystemConfiguration and delete the following (suggest you make copies to the desktop first if in doubt):

    com.apple.airport.preferences.plist

    NetworkInterfaces.plist

    preferences.plist

    com.apple.nat.plist

    Restart and test

  2. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Try this. Go to Library/Preferences/SystemConfiguration and delete the following (suggest you make copies to the desktop first if in doubt):

    com.apple.airport.preferences.plist

    NetworkInterfaces.plist

    preferences.plist

    com.apple.nat.plist

    Restart and test

  3. 0

    jbksm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for the suggestion, Sean Dale, but no joy.

  4. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Open HD/Applications/Utilities/Network Utility/Ping and type in 17.112.152.32 (Apple) and click Ping. If you don't get a response back off that try entering your router address in instead of Apple's one and ping that. Report back and we will see where we can go from there

  5. 0

    jbksm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ping works; 0% packet loss.

  6. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok, you've got internet access. Try this, in Terminal (in your Utilities folder) enter

    lookupd -flushcache

    to flush the DNS cache

  7. 0

    jbksm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    In Terminal, I get the response -bash: lookupd: command not found.

  8. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sorry, should have said enter dscacheutil -flushcache

  9. 0

    jbksm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hmm...the command itself runs this time, but still no luck with Safari or Mail. The same error message keeps popping up.

  10. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Just a thought but have you looked to see if you have somehow ended up with a proxy enabled?

  11. 0

    jbksm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I did check that, yes--no proxies. It's a very strange problem.

  12. 0

    Sean Dale1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Paste the IP address you pinged earlier (17.112.152.32) into the address bar of one of your browsers and hit return and see if it will connect then.

    Assuming you are currently using DHCP for your LAN network addressing test by giving your Mac a fixed IP. Remember if you use a fixed IP that you will need to put in the primary and secondary DNS server addresses of your ISP - you can sometimes cheat and put the IP address of your router in the DNS server field if you don't know them.

    Have you tried creating a another user account to test if the problem is purely restricted to your user account or systemwide?

  13. 0

    jbksm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It is system-wide; there is one other account on the computer already, and I created a new one as well--both have the same problem. I'll try your suggestion wiht the DNS server addresses and see what happens.

  14. 0

    Anthony Stevens

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi...sorry to bother you, but did you ever find a solution to this problem?...I'm currently having the same problem and am frustrated since I cannot resolve it...any help would be greatly appreciated!...thanks so much for your time and consideration.

  15. 0

    Alexn3

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi everybody (sorry to bother you too),

    I'm having the same problem with Safari (others browsers work fine).

    I also try to overwrite Safari application with the same version (I have a Mac mini, same MacOS), but nothing to do...

    Did someone solve this problem?

    Thanks

  16. 0

    Lyranei

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hello,

    I recently started getting the same message, both in Safari and Mail, but also having issues with Firefox and Norton Antivirus. Another thread suggested trashing Safari prefs, and that seems to have helped Safari at least at the moment. Mail is still having problems and I don't know about the others yet.