Trouble Shooting Common Issues with Deskwall
Issue 1: Keyboard and Mouse Lag or Stuttering Across Windows
Symptom: The cursor stutters or delays when moving from one server feed window to another.
- The Cause: Network latency or temporary packet dropping between the DeskWall processing node and your local KVM network switch.
- The Fix:
- Inspect the Ethernet activity indicators on the back of your local DeskWall receiver module; ensure a solid green link light is present.
- Avoid connecting your DeskWall processing nodes to standard office Wi-Fi networks or unmanaged daisy-chained network hubs. Ensure it is patched into a dedicated corporate gigabit switch port.
Issue 2: Connected Source Window is Completely Black
Symptom: A layout grid sector displays "No Signal" or stays entirely black while the source computer is known to be powered on.
- The Cause: An HDCP handshake error, a mismatched display scaling resolution, or an inactive video graphics driver sleep cycle on the target machine.
- The Fix:
- Bring up the DeskWall Admin Widget and click Refresh Source Input.
- Verify that the host computer's display output resolution is explicitly locked to $1920 \times 1080$ at 60Hz or $3840 \times 2160$ depending on your specific hardware baseline. Interlaced resolutions (like 1080i) are not supported.
- Ensure the physical video patch cable (DisplayPort or HDMI) connecting the host source machine to the local DeskWall transmitter unit is secured tightly.
Issue 3: "Follow Me" Control Disappears at Screen Edges
Symptom: Your mouse hits a virtual wall at the border of a window partition and refuses to transition over to control the neighboring screen feed.
- The Cause: A layout grid configuration mismatch or the local screen coordinate alignment has gone out of synchronization.
- The Fix:
- Open the DeskWall menu widget and reload your current default layout preset to force-realign the coordinate mapping grid.
- If the cursor remains trapped, press your emergency unlock sequence (
Scroll Locktwice orCtrl + Alt + K) to cleanly break the KVM loop and reset the cursor position back to the primary desk workspace.