This guide helps IT staff quickly diagnose and resolve the most common issues affecting LAN and PACS connectivity. Follow the steps in order, starting with Identify the Problem and Basic Checks before moving to specific scenarios.
Identify the Problem
Ask these questions first:
Is the issue isolated to one modality or affecting all modalities?
Are studies stuck in "sending" status, delayed, or not appearing in PACS?
Is the upload slow or completely failing?
Is there an error message on the modality or PACS console?
Basic Checks (Always Start Here)
Confirm the LAN switch/router is powered on and functioning.
Ensure all network cables are securely connected.
Check that network activity lights are blinking on the PACS server and modality.
Verify the internet connection is active (if using cloud PACS).
Restart the modality or PACS service if it can be done safely.
Scenario 1: Modality Disconnected from LAN
When a single modality cannot send studies:
Confirm the network cable is properly connected to the modality and switch.
Check the modality’s network settings (IP, gateway, DICOM AE Title). Match with PACS configuration.
Test connectivity to PACS by pinging the server (if supported).
If ping fails, move the cable to a different switch port.
If still failing, escalate to IT for hardware diagnostics (modality NIC, switch, or cabling).
Scenario 2: Low Internet Bandwidth (Delayed Uploads)
When studies are uploading slowly to cloud PACS:
Run an internet speed test from a workstation.
Ensure upload speed meets minimum PACS requirement (≥5 Mbps per study stream).
Identify and limit other bandwidth-heavy applications (video calls, file transfers).
If bandwidth is consistently low, contact ISP for upgrades or issue resolution.
As a temporary fix, schedule uploads during off-peak hours.
Scenario 3: PACS Server Disconnected from LAN
When no modalities can send studies:
Confirm the PACS server is powered on.
Check the server’s LAN cable connection.
Verify the server’s IP address is within the LAN range.
From another workstation:
Ping the PACS server.
If ping works but studies aren’t received → restart PACS service.
If ping fails → replace cable or switch port.
If server is still unreachable, escalate to IT for server or switch diagnostics.
Escalation Checklist
If the issue persists, collect and share the following before escalating:
Error evidence: screenshots, logs, or messages.
Ping results from modality/workstation to PACS.
Study details: IDs, timestamps of failed transfers.
Network tests: internet speed results.
Steps already taken during troubleshooting.
Escalate to:
Facility IT support team, or
AlemHealth Support (include all details above).