HIBA KAdat

a incidències internacionals

Description of the Incident

An international user called reporting that they are unable to connect to the central server via SSH (Secure Shell).

  • Goal: Troubleshoot the remote connection, verify service status, and check network security policies.

Implementation Resolution

  • Service Verification: Checked the status of the sshd daemon on the Debian server using systemctl.
  • Network Diagnostics: Ran ip a and ping tests to confirm the server was reachable on the local network.
  • Firewall Configuration: Verified that Port 22 was open and not blocked by security rules.

Technical Justification

  • Network First: He fet un Ping per descartar fallades de xarxa abans de mirar el software
  • Security Standards: I verified the SSH service status and Firewall rules to ensure a secure, encrypted connection for the international client.
  • Efficiency: By following a systematic troubleshooting protocol, I minimized the client’s downtime and restored the connection promptly.
  • Professional Register: I maintained a formal linguistic register and used IT-specific terminology to ensure clear communication with the international user.

Solution Comparison

Option A
SSH (Secure Shell)

  • ros: High security via encryption, very low bandwidth usage (perfect for international connections), and native to Debian Linux.

  • Cons: Command-line interface only (requires technical knowled

    • Option B
    Quick Assist TeamViewer

    These tools are easier to use for bypassing complex firewalls. However, they are generally considered less secure for high-level corporate server environments.

    Conclusion: I chose SSH because it provides the most stable and secure connection for server management, minimizing the risk of unauthorized access.

    📊 Activity Log (Work Log)

    Phase Description Duration
    Diagnosis Identification of the connection issue in English. 45 min
    Resolution Network configuration and opening ports (SSH/RDP). 1h 15 min
    Verification Final testing with the client and documentation. 1h
    Status: Completed Total: 3 Hours

    Conclusion

    This challenge allowed me to apply my Debian Linux knowledge in a professional international support scenario. By using IT-specific terminology and a structured troubleshooting approach, I was able to resolve the connection incident efficiently while maintaining high security standards.