Network Diagnostics app missing

Unbelievable, PATRICKMELE, you are at least the 5th person in this discussion who has brought up Wireless Diagnostics, which is NOT the same thing as Network Diagnostics.

https://discussions.apple.com/thread/8098137?answerId=32652172022#32652172022

In your previous post you said you were still on Sierra, but now it seems you've discovered you're actually on High Sierra. That's what this whole discussion is about, the fact that Apple removed Network Diagnostics and Network Setup Assistant from High Sierra. If you have a backup of your Mac from before you upgraded, then you're not screwed. If you don't, then I'm afraid you are, unless someone has posted the needed files somewhere. In case you have a backup or can otherwise find the files (like from someone who hasn't upgraded yet), my detailed instructions for restoring them are on the previous page of this discussion here: https://discussions.apple.com/thread/8098137?answerId=32636980022#32636980022

@LeonOJ, your solution only works for WiFi connections, not ethernet or anything else. For WiFi, there's still Wireless Diagnostics.

@Steven Jamar, see my detailed instructions for restoring Network Diagnostics earlier this discussion here: https://discussions.apple.com/thread/8098137?answerId=32636980022#32636980022

Just be careful when you copy the chown commands, as there will be an extra space at line breaks that you need to remove.

@Scouserboy, thanks for the positive feedback!

MariaNinguem, just to clarify, Network Diagnostics and Network Setup Assistant are two separate apps, each with their own frameworks. You don't even need Network Setup Assistant if all you want is Network Diagnostics. The latter has only one framework, so that's why it works. Have you tried the setup assistant to see if it works with only the one framework? It might be that the 10.10 version required only one. They're adjacent to each other in the same folder, so if you don't see it, SetupAssistantFramework.framework may not have been used yet.

I do recommend that you change ownership of the files back to root, especially after you re-enable SIP. All files in the System folder should be owned by root:wheel (shows up as "system" & "wheel" in Finder).

You are correct that Apple could change something else to make diagnostics stop working. This is another reason to set the ownership of the files correctly: the next time there's an OS update or upgrade, those files will likely be removed if they have the wrong owner. Make sure you store them in a safe place in case you need to repeat the process of restoring them in the future.

Don't forget to express your outrage to Apple, since I doubt if they read all of these discussions: Feedback - macOS - Apple

Can you add yourself to the Sharing & Permissions pane, otherwise you may need to disable System Integrity Protection, boot to your Recovery Disk go to Utilities ,click on Terminal and enter csrutil disable press return and then reboot.

You almost certainly need to have System Integrity Protection disabled to do this. I already had SIP disabled when I followed your steps.

In addition to changing SetupAssistantFramework.framework, you also need to change SetupAssistantSupport.framework, just below it.

And to do everything correctly, the owner of all 4 files should be changed to root and the permissions set to rwxr-xr-x.

Finish by re-enabling SIP.

I've followed all these instructions to the letter and now Wireless Setup Asst works, but Network Diagnostics keeps crashing on opening. Any idea why this would be?

Cannot believe Apple removed this great little app!

j

@jake, check the crash report, but you're probably missing:

/System/Library/Frameworks/NetworkDiagnosticsUI.framework

Copy it from a Sierra machine, paste it into the correct location & fix the permissions.

Wireless Diagnostics is not the same as Network Diagnostics. Go to /System/Library/CoreServices/Network Diagnostics.app. You will not find it in High Sierra. See my instructions on how to restore it (and the Network Setup Assistant) elsewhere in this thread.

Alas blanchr, I could not agree more; and I have been using Apple computer since the days of the old Apple II.

As an aside, I really don't care for the way that Apple is making my desktop look like a Macbook or iPad, but that is just me (guess that's why I use Terminal so much.)

I'm afraid I'm not tech savy so I need a real detailed step-by-step please? Where do I find the Sierra install?

Ugh................ why Apple???? Why do you do this with one of the most valuable tools?

Seriously.

Shawnnafromwa,

Please use the links previously provided to let Apple know that you are unhappy.

Unless you have a Startup/install copy of Sierra to install, you can't. When they released High Sierra, they pulled Sierra from your purchases listing at the App Store.

From what I have seen, you have to BACKUP your drive, erase it, and then startup and install your copy of Sierra.

If you can't back up, don't even think about it.

Here is a more detailed link (there are others):

https://www.imore.com/how-downgrade-macos

After reading all these thoughtful and helpful suggestions for a work around, which I wouldn't dare try for fear of mucking something up, it just drives home the point that Apple seriously screwed up by deleting the Network Assistant from High Sierra. It was readily available, reliably worked to get the network up and running again, and needed frequently. What was Apple thinking?

Regarding ISP failed , open mail application > connection doctor .

Only rotating circles will be observed in front of SMTP and IMAP connections and there will be no red dots , it means server is down .

The only one setting- network diagnostic tool , users are looking has been distributed .

Thanks for this. I am not a programmer but I followed almost all your instructions and I have Network Diagnostics working again. As a novice, however, I don’t understand the meaning of “Change owner of all files to root and permissions to rwxr-xr-x.” Which files, precisely? What does it mean to change their ownership to “root”? Do these things need to be done from Terminal? The new files I placed in the system folder seem to have my personal account as owner, whereas the other files have “system” as owner. To be more precise, when I display information for the newly added files (such as Network Setup Assistant) under sharing and permissions I see on the first line my username with read & write privileges, on the second line staff with read privileges, and on the third line everyone with read only privileges. Do I need to change the name on the first line to “system”? If so, how?