After correcting a VLAN mismatch that was preventing a newly deployed clinic wing's workstations from reaching the pharmacy server, what is the best way to validate that the fix actually resolved the issue before closing the ticket?

Validating a resolution means directly confirming the specific symptom that was reported is gone, not just confirming that a related-looking condition (like a strong Wi-Fi signal, which is irrelevant here since these are wired workstations) looks fine. Since the root cause was identified as a VLAN mismatch, the correct verification steps are, in order: check that the workstation now shows an IP address consistent with the intended VLAN's subnet (proving the VLAN assignment took effect), and then actually test reachability to the pharmacy server, ideally including the specific service or port the clinical application uses, not just a ping. Asking staff to reboot and simply assuming success skips verification entirely and risks closing a ticket on an unconfirmed fix, which can let the same issue resurface, and checking only that the config was saved to the running configuration is incomplete because a running-only change is lost on the next reload, meaning the fix could quietly disappear later even if it appears to work right now. A thorough validation should also confirm the change was saved to the startup or persistent configuration so the fix survives a reboot, and ideally have the actual clinical application tested by a staff member rather than relying solely on a network-level check, since application-level issues can persist even after basic IP reachability is restored. Documenting the before-and-after state also gives a clear record if the problem is questioned or recurs later.