The need for Network Diagnostics, System Mojave and above.

Keywords: "Network Diagnostics" Ethernet "Hard-wired" "System Mojave"


Greetings,


This applies to ETHERNET and not Wifi.

Reference is made to the System High Sierra oriented message thread,

https://discussions.apple.com/thread/8098137?login=true

Although derailed some (by injection of wifi concerns) in it's 7 pages of replies, an excellent procedure

was provided for adding Network Diagnostics back into System High Sierra.


As a System Sierra user, I use Network Diagnostics many times every day to

remedy Mac borne network misbehavior, which I went into detail in another,

unrelated message thread.


Upon doing a test upgrade to System Mojave (on another drive, of course) and carefully following

all the instructions for otherwise enabling it to work normally in System High Sierra, it failed to

work in System Mojave.*


The question that was never answered, on many web pages, pertains to why Apple Computer disallows Network Diagnostics. Presently, Microsoft Windows 10 enjoys Network superiority with their easy to use Network Troubleshooter - a function that went away upon the demise of Network Diagnostics. The "why" was never answered, but the end result is a strong Windows advantage.


Heroic efforts by 3rd party software developers, such as Ethernet Status, by Appyogi Software,

allows for quick observation of whether or not the Mac is using Ethernet (or strayed off to wifi as it sometimes does) and whether or not data is being passed. The remedial portions of Network Diagnostics are still gone, and, unless there is some unknown application out there, and not replicated.


Recommendation for Apple Computer: Either re-enable Network Diagnostics in System Mojave and above, or place the source code (for it) into the Public Domain so that other developers may bring it back.


According to the "Report to Apple" crash report, apparently it's a "Library Missing" error for which I don't know how to resolve. Posting the crash report exceeds limit of this message. Maybe it will appear in "additional Text"


Any advice will be most appreciated.

Posted on Sep 12, 2020 9:36 AM

Reply

Similar questions

13 replies

Sep 12, 2020 11:43 AM in response to leroydouglas

Sure. The exact issue is.... No more Network Diagnostics application above System Sierra.

The one sentence you require: Network Diagnostics is needed in System Mojave and up.

Exact Mac - Late 2013 Mac Pro

Exact MacOs --- System Sierra clean install upgraded to System Mojave

Feedback, Apple or otherwise, was already done in the https://discussions.apple.com/thread/8098137?login=true

Did any Apple employees read the above link? Doubtful.

Phoning Customer Support? What are the odds that my phoning them would cause them to re-enable Network Diagnostics into Systems Mojave and above? What are the odds that they would give me the exact line by line procedure to enable Network Diagnostics in System Mojave? Odds are 1000x better at the slots in Las Vegas.


Am I asking too much?


So what am I requesting? Again, advice on how to enable Network Diagnostics, in System Mojave.

Sep 12, 2020 6:08 PM in response to Adonsa

Adonsa wrote:

I'll appreciate a reply from another Mac User who can address my concerns, and ultimately the concerns of those Mac users who first cited the problem in https://discussions.apple.com/thread/8098137?login=true


It's my pleasure to reply and to address your concerns: Follow leroydouglas's recommendations.


Several participants of that three year old Discussion made those very same recommendations. Nothing has changed since then. Network Diagnostics is gone and it's not coming back. Refer to many other Discussions regarding the same topic: Network Diagnostics missing - Apple Community to cite one of many.


User to user is exactly where this question belongs,


Incorrect. Apple does not participate on this site.

Sep 13, 2020 6:29 AM in response to Eau Rouge

Thank you, Eau Rouge, HWTech, and John Galt for your replies.


Okay, I'll take the blame for being critical of Apple Computer.

I should have stated up front that I am aware that Apple Computer has never resurrected a discontinued application.

I should have omitted my reasons for desiring the functionality of Network Assistant.

Justification: System High Sierra users did it without repercussions from any website moderators. I should have focused on the 6 successful steps that System High Sierra users used to bring Network Assistant over to System High Sierra. With SIP temporarily disabled, they moved these:


/System/Library/CoreServices/Network Diagnostics.app

/System/Library/CoreServices/Network Setup Assistant.app

/System/Library/PrivateFrameworks/NetworkDiagnosticsUI.framework

/System/Library/PrivateFrameworks/SetupAssistantFramework.framework/Versions/A/S etupAssistantFramework

/System/Library/PrivateFrameworks/SetupAssistantSupport.framework/Versions/A/Set upAssistantSupport

Change ownership and permissions according to the way System High Sierra users did.

With SIP re-enabled, success was achieved for System High Sierra users.


Crash report is an "additional text" at the bottom of this message.

With SIP disabled, I applied the exact above exact steps to a virgin newly installed Mojave.


Summary:

The crash error narrative reveals that a termination reason DYLD, [0x1] Library missing

" Library not loaded: /System/Library/PrivateFrameworks/NetworkDiagnosticsUI.framework/Versions/A/NetworkDiagnosticsUI"


Note: I did previously copy the NetworkDiagnosticsUS.framework into Mojave exactly as the High Sierra instructions required. But that didn't suffice.


"No suitable image found" Wish I knew what image needs to be found.


It appears that I am just one unknown step away from making it work in Mojave - to come up with the image file that the crash report requires.


Please don't refer me to the Apple feedback web page. There is no discussion forum there, and Apple employees are highly unlikely to provide me with a fix, given my efforts to modify Mojave in violation of their policies. All I'm asking for is to know the "suitable image" and the "Library missing" that the crash report tells me it couldn't find. Even a "try this, try that" will be most welcome.


Respectfully,

Adonsa


Attached, under the "Additional Text" icon below, is the narrative of the crash report log.



Sep 13, 2020 6:38 AM in response to Adonsa

Hmmm, it was looking for...


/System/Library/PrivateFrameworks/NetworkDiagnosticsUI.framework/Versions/A/NetworkDiagnosticsUI


But only found..


/System/Library/PrivateFrameworks/NetworkDiagnosticsUI.framework/Versions/A/NetworkDiagnosticsUI:


With a Colon on the end?


You don't suppose a colon sneaked in where i didn't belong?



Sep 12, 2020 10:23 AM in response to Adonsa

Adonsa wrote:

Keywords: "Network Diagnostics" Ethernet "Hard-wired" "System Mojave"

Greetings,

This applies to ETHERNET and not Wifi.
Reference is made to the System High Sierra oriented message thread,
https://discussions.apple.com/thread/8098137?login=true
Although derailed some (by injection of wifi concerns) in it's 7 pages of replies, an excellent procedure
was provided for adding Network Diagnostics back into System High Sierra.

As a System Sierra user, I use Network Diagnostics many times every day to
remedy Mac borne network misbehavior, which I went into detail in another,
unrelated message thread.

Upon doing a test upgrade to System Mojave (on another drive, of course) and carefully following
all the instructions for otherwise enabling it to work normally in System High Sierra, it failed to
work in System Mojave.*

The question that was never answered, on many web pages, pertains to why Apple Computer disallows Network Diagnostics. Presently, Microsoft Windows 10 enjoys Network superiority with their easy to use Network Troubleshooter - a function that went away upon the demise of Network Diagnostics. The "why" was never answered, but the end result is a strong Windows advantage.

Heroic efforts by 3rd party software developers, such as Ethernet Status, by Appyogi Software,
allows for quick observation of whether or not the Mac is using Ethernet (or strayed off to wifi as it sometimes does) and whether or not data is being passed. The remedial portions of Network Diagnostics are still gone, and, unless there is some unknown application out there, and not replicated.

Recommendation for Apple Computer: Either re-enable Network Diagnostics in System Mojave and above, or place the source code (for it) into the Public Domain so that other developers may bring it back.

According to the "Report to Apple" crash report, apparently it's a "Library Missing" error for which I don't know how to resolve. Posting the crash report exceeds limit of this message. Maybe it will appear in "additional Text"

Any advice will be most appreciated.


For some clarity...if you are having an issue

Can you distill this down to a one sentence question ?


What exact Mac?

What exact macOS ?



If it s Apple Feedback you are looking to give: Apple Feedback http://www.apple.com/feedback


or

Call Customer Support (800) MY–APPLE (800–692–7753)




Sep 12, 2020 12:47 PM in response to Adonsa

Adonsa wrote:

Sure. The exact issue is.... No more Network Diagnostics application above System Sierra.
The one sentence you require: Network Diagnostics is needed in System Mojave and up.
Exact Mac - Late 2013 Mac Pro
Exact MacOs --- System Sierra clean install upgraded to System Mojave
Feedback, Apple or otherwise, was already done in the https://discussions.apple.com/thread/8098137?login=true
Did any Apple employees read the above link? Doubtful.
Phoning Customer Support? What are the odds that my phoning them would cause them to re-enable Network Diagnostics into Systems Mojave and above? What are the odds that they would give me the exact line by line procedure to enable Network Diagnostics in System Mojave? Odds are 1000x better at the slots in Las Vegas.

Am I asking too much?

So what am I requesting? Again, advice on how to enable Network Diagnostics, in System Mojave.


This is a user to user support community— you need to direct your inquiries about Apple policy directly to Apple.

https://getsupport.apple.com/


That is a no on "how enable Network Diagnostic"



As a System Sierra user, I use Network Diagnostics many times every day to remedy Mac borne network misbehavior, which I went into detail in another, unrelated message thread.


It sounds to me you may need to hire a better Network administrator .


You can still use the Network Utility.app if that gets you any closer to your issue(?)

Use the spotlight search " Network Utility.app"


Sep 12, 2020 3:10 PM in response to leroydouglas

User to user is exactly where this question belongs, given the low odds that an Apple employee will give me a solution.

So the official answer is "That is a no on "how enable Network Diagnostic"

I disagree. Users helped each other to enable Network Diagnostics to work on the above cited 7 page discussion message thread.

I do not appreciate condescending reply.

I am a network administrator.

Network Utility.app does NOT replicate the functionality of Network Diagnostics as was made very clear in the System High Sierra message thread cited above. For your information, Network Utility does not specifically replicate screens 2 thru 6 of Network Diagnostics.


I'll appreciate a reply from another Mac User who can address my concerns, and ultimately the concerns of those Mac users who first cited the problem in https://discussions.apple.com/thread/8098137?login=true



Sep 12, 2020 6:45 PM in response to Adonsa

Adonsa wrote:

I'll appreciate a reply from another Mac User who can address my concerns, and ultimately the concerns of those Mac users who first cited the problem in https://discussions.apple.com/thread/8098137?login=true

If you have been following the progression of macOS over the years you will notice that Apple has been removing lots of useful pieces from macOS. This is an unfortunate trend that has been occurring for the last ten years. Apple loves their secrets so if there exists any hidden utilities or features most users will not be aware of them. Plus anything you find now may be removed in the next update or upgrade.


Most users realize they must rely on third party utilities or use a Linux PC to monitor network connections for packet captures or if you are a Network administrator, then use the tools provided on the enterprise grade network switches.


Apple does not care about providing useful troubleshooting utilities or logs. Apple has allowed their system logs to degrade into an utterly useless mess. If Apple cannot be bothered to provide useful information in their own system logs why would they provide any specialized utilities that require even more work to develop and support?


I don't understand why you are surprised by the responses here. Your original post wasn't really asking a question that could be answered and even portions of your later posts are mixed. You only asked for advice. You were told by several respected forum contributors that the functionality you are looking for no longer exists (or if it does still exist they are unaware of it).


If you want assistance in troubleshooting a specific issue, then provide relevant details and the exact issue and error messages you are receiving. If you want to post a log report here, then click on the "Additional Text" icon which looks like a piece of paper to paste the report here.

Sep 13, 2020 2:08 PM in response to BDAqua

Thank you BDAqua, for inspiring me to dig deeper into the crash report log.


Adequate Success, not total, but sufficient.


On a new plain-Jane test drive, with a virgin unmodified, un-migrated, System Mojave,

I performed the steps that were successful for High Sierra users, making sure there was

no stray syntax got appended to critical file names.


Crash Report recurred. Nosing around in Mojave's

System/Library/PrivateFrameworks folder, I noticed that

the Assistant.Framework folder was absent. With nothing to lose,

given that it's a test drive, I copied the Assistant.Framework folder

from my System Sierra drive into Mojave's PrivateFrameworks folder.


After that, I

Tested Network Setup Assistant - 100% operational.

Tested Network Diagnostics - Usable

Instead of opening to the "Select Location" window, Network diagnostics opens to the most important window, the "Choose Network Port Configuration" window, and still displays the 5 network status indicators on the left side,. Select location is replicated in Network Settings anyway. As is, pressing the Continue button within Network Diagnostics produces a real nasty crash report log. Therefore, using Diagnostics without clicking the continue button, all good. The main benefit is achieved without Network Diagnostic's other screens.


Recommendation: for Mac Users who would like to do this, it's probably best to do it on a test drive first. The High Sierra message thread instructions apply, then copy the Assistant.Framework folder into Mojave's PrivateFrameworks folder, all the while being mindful to set ownership to root/wheel and the permissions as stated in the High Sierra messages. I also added read rights to everyone and that didn't seem to harm anything. I also made sure that everything in the sub folders were set to Root, Wheel. rwx, rx, rx, or rws, rx, x


Above System Mojave? Speculation - doubtful.


Regards.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

The need for Network Diagnostics, System Mojave and above.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.