As per Gordon's comment, using the resolver system was indeed the solution I needed, updated script follows:
# Alters routing and DNS to use private network routes and DNS for
# private network destinations
networks=( "10.10.0.0/16" "192.168.20.0/24" )
work_domains=( "intranet.company.com" "services.company.com&...
No, it is not so that Apple devices somehow cannot read the country code for North America.
Some WiFi devices comes with a settable country code - i.e. often you can access a configuration page from the router and set the country code to match where you are. For some vendors the country code can be changed with firmware updates. Also it is possible that you ...
The proper way on modern macOS to flush the dns cache is:
sudo killall -HUP mDNSResponder
You’ll want ensure your DNS is working well by bypassing your routers provided DNS and manually configuring Google or Cloudflare or other DNS provider on the MBP.
22.214.171.124, 126.96.36.199 is Google
188.8.131.52, 184.108.40.206 is Cloudflare
There are several other DNS providers to choose ...
How can I configure Catalina or issue a command on the command-line that convinces macOS GUI that Internet and dns are available?
macOS (every OS for that matter) doesn’t care about the Internet. The Internet, to your computer, is nothing special. It is to you can me, but to your computer, it’s just another network.
As far as DNS goes, it’s not required ...
Just go to System Preferences and follow the steps in my screenshots.
sorry for german screenshots.
once you removed all manually configured nameservers, Mac OS will use nameservers provided by DHCP again.
I was able to find out the issue.
Your router is keeping the device name stored. To fix it do this:
Log into your router admin interface
Click "Attached Devices" (or the corresponding screen in your router that tracks the devices currently connected to it.)
There you will see the device name you want to update
Now go to the "access control ...
I had a similar issue and got a positive response when using IPv6 (ping6) but not IPv4 (ping). I also had the symptoms described in the question Why will my Mac only load Google and Facebook?.
This problem started to appear after disconnecting from the VPN. So, after terminating the VPN service, networking began to work fine again.
sudo killall -9 vpnagentd ...
If you’ve already erased your hard drive then there’s no “command line” to use to begin with. You need a minimal operating system in which to boot into and it sounds like you don’t have that.
Here are a few options for you to move forward:
Get a USB Ethernet or USB WiFi dongle (I suggest Ethernet) to connect your Mac directly into your router/modem so you ...
You should not need to terminate the video port of your Mac mini as support for a headless machine is natively supported by macOS - Remote into Mac Mini after a reboot. I say “should” because while it is supposed to be supported, I’ve run into instances where it would simply fail without it - notably VNC.
Bottom line is that you shouldn’t need it. But, ...
I had the exactly same issue with my brand new Asus Router RT-AX58U supporting WiFi 6 mode and was not able to connect to my network on the 2.4 Ghz band on my MacBook Air running High Sierra 10.13.1. All my windows and android devices had no issues with connectivity. I had tried changing WPA2 to WPA2/WPA mode and from AES to TKIP encryption, forgot network ...
Solved, and obvious in hindsight: there was an entry for her site in /etc/hosts. Sister knows nothing about hostfiles and has no memory of editing it, but provider not so helpfully advises people to edit /etc/hosts to preview Wordpress ahead of domain transfers, and doesn't bother to warn them to clean up after, so we assume that's what happened.
You normally have to access a shared resource on the Mac rather than use a magic packet.
The simplest way is to set up file sharing (allowing SMB for the PC) and try to access that from the PC. This could be any folder you like so you do not have to worry about it being visible to others on the network and can (should) be password protected.
Other things ...
Same issue here - can't comment yet, but a little more insight nonetheless:
For me the issue was resolved with regards to the top comment, simply disabled locationd. (mbp 2010, osx 10.13, fresh install)
However, for me it occurred ONLY on en0 = ethernet, but somehow not on WiFi. This might sound benign, but having said that, for someone looking for this ...
I only managed to solve this by changing the port that I was using on my mail server to send emails (I was using a non-standard port to bypass ISP filtering). When I changed to using TCP port 587 (the Message Submission port) the issue was resolved.
I'm still not convinced that Mail and/or macOS (or possibly my mail server) is doing something weird as other ...