GE Healthcare MAC 5

Asset Type

Electrocardiograph (EKG) Machine

Manufacturer

GE Healthcare

Model

MAC 5

What This Guide Helps With

This guide helps troubleshoot the MAC 5 Shared Network Not Configured error when the device cannot use a shared network path for ECG export, archive access, or network storage. This condition usually points to a missing, incomplete, or incorrect shared path configuration rather than a hardware failure.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Confirm the MAC 5 is not actively being used to acquire a patient ECG.
• If the error appears after an ECG has been acquired, make sure the ECG is saved locally or printed if clinically needed before changing network settings.
• Do not troubleshoot network settings while the device is connected to a patient or needed for immediate clinical use.
• Expected result: Patient data is protected before troubleshooting begins.

Verify the Reported Error and Behavior

• Confirm the exact displayed message is: Shared Network Not Configured.
• Ask when the error appears, such as during ECG export, saving to a network folder, accessing a shared archive location, order/result transmission workflow, after a network configuration change, or after the device was moved.
• Expected result: The error is reproducible or clearly tied to shared network access.
• Why it matters: This message points to a missing or incomplete shared network path configuration, not necessarily a hardware failure.

Confirm Basic Network Connection First

• Check whether the MAC 5 is connected by LAN or WLAN.
• For LAN, verify the Ethernet cable is fully seated at the MAC 5 and wall jack.
• For WLAN, verify the wireless connection is active and signal strength is acceptable.
• Expected result: The device has a valid network connection before shared path troubleshooting continues.
• Why it matters: A shared path cannot be reached if the device is not connected to the network at all.

Check Whether the Issue Is Shared Network Specific

• Determine whether other network functions work.
• Check whether the MAC 5 can access worklist, send ECGs to another configured destination, or communicate with the normal ECG management system if applicable.
• Expected result: Other network functions may still work even though the shared network path is not configured.
• Why it matters: This separates a general network failure from a shared folder configuration issue.

Review Shared Network Settings

• Go to the MAC 5 network configuration area and review the shared network setup.
• Check the shared path, server name or IP address, folder/share name, username if required, password if required, domain if required, destination or archive selection, and any required file naming or export settings.
• Expected result: The shared path is present, complete, and matches the intended network share.
• Why it matters: The error specifically indicates that the shared path is not configured on the device.

Configure the Shared Path

• Go to Network > Shared Network settings.
• Enter or correct the shared network path using the facility-approved path format.
• Confirm the path points to the correct network share and not a local computer folder, old server, retired share, or test location.
• Expected result: The shared path field is populated and saved.
• If this resolves the issue, perform a test export or network save, verify successful completion, and return the MAC 5 to service.

Check for Recent Changes

• Ask whether anything recently changed, such as device replacement, software update, network migration, server rename, shared folder relocation, password change, domain change, department move, new VLAN, wireless profile change, reimaging, or configuration reset.
• Expected result: Any recent change is identified and compared against the current shared path settings.
• Why it matters: Shared network errors often appear after IT or server-side changes, even when the ECG machine itself is functioning normally.

Verify Credentials and Permissions

• If the shared path is configured but still fails, confirm the account used by the MAC 5 has permission to access the share.
• Check with IT or the ECG system administrator as needed.
• Confirm the account is active, the password is current, the account is not locked, read/write permissions are correct, the folder is still shared, and the MAC 5 is allowed through network security controls.
• Expected result: The shared path is reachable using valid credentials.
• Why it matters: A configured path may still fail if the device account cannot authenticate or write to the destination.

Test with a Known Good Network Location if Available

• If facility policy allows, compare the MAC 5 configuration to another working MAC 5 in the same department.
• Verify the shared path format, server name, destination settings, and credential requirements match the working device where appropriate.
• Expected result: Configuration differences are identified.
• Why it matters: This helps isolate whether the issue is device configuration, network access, or server-side permissions.

Restart and Retest

• After configuration changes are saved, restart the MAC 5 if required by the device workflow.
• Retest the shared network function.
• Expected result: The error no longer appears and the device can access or save to the shared network location.
• If this resolves the issue, document the configuration correction and return the device to service.

If the Problem Persists

If the shared path has been configured correctly, the network connection is active, credentials are valid, and the shared folder is reachable from other devices, the issue may involve device software, network stack, or configuration corruption.

At that point, external causes such as disconnected Ethernet cable, weak WLAN connection, missing shared path, incorrect server/share name, expired credentials, and obvious permission problems have been ruled out.

Remove the MAC 5 from service if the clinical workflow depends on shared network export or archive access.

Label the device Out of Service and send it for repair or bench evaluation. Escalate to GE Healthcare service, internal networking/IT, or the ECG system administrator as appropriate.

Clinical Use Tip

Never troubleshoot on an active patient. Move the patient to a backup device first and maintain therapy or diagnostic workflow continuity.

If ECG transmission or shared storage is unavailable, make sure staff know whether local save or printed ECG workflow is acceptable before returning the device to use.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"User reported GE Healthcare MAC 5 displaying Shared Network Not Configured when attempting to save or export ECGs to the shared network location."

Cause

What was observed during troubleshooting.

Example:
"Shared network path was not configured under Network > Shared Network settings. Device network connection was present, but no valid shared path was entered."

Resolution

What action was taken.

Example:
"Configured the approved shared network path, verified required network settings, restarted the MAC 5, and confirmed successful test export to the shared location. Device returned to service."

Helpful Details to Include (If Known)

• Alarm behavior and when the error occurs
• Accessories swapped, including Ethernet cable, wall jack, or network adapter if applicable
• Power behavior during restart and retest
• Environmental factors such as department location, WLAN signal strength, VLAN, or recent device move
• Indicator lights, network icon status, LAN link lights, or WLAN connection status
• Shared path entered or corrected
• Server/share name verified
• Credential or domain issue found
• Comparison to a known working MAC 5
• Whether ECG export, archive, or worklist was affected
• Final test export result
• Final device status

Final Thought

The Shared Network Not Configured error should be approached as a configuration and workflow issue first. Confirm patient data safety, verify the message, check the basic network connection, then correct the shared path under the network settings. If the path, credentials, and permissions are all correct but the error persists, escalation is appropriate.

That is successful troubleshooting.