# Keyboard and Mouse not recognized when connected from a KVM switch

**URL:** <https://deeptalk.lambda.ai/t/keyboard-and-mouse-not-recognized-when-connected-from-a-kvm-switch/3427>\
**Category:** Technical Help\
**Created:** [January 3, 2023, 9:08pm UTC](https://deeptalk.lambda.ai/t/keyboard-and-mouse-not-recognized-when-connected-from-a-kvm-switch/3427 "2023-01-03T21:08:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karun](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@Karun](https://deeptalk.lambda.ai/u/Karun)\
**Post date:** [January 3, 2023, 9:08pm UTC](https://deeptalk.lambda.ai/t/keyboard-and-mouse-not-recognized-when-connected-from-a-kvm-switch/3427/1 "2023-01-03T21:08:44Z")

</div>

Both keyboard and mouse connected via KVM switchs are not being recognized by some of the recent Lambda machines.  
Two instances:

1. 4 port KVM switch with HDMI + USB connections. It happened when I connected 3 Quads and 1 Vector via a 4 port KVM switch. The Vector machine doesn’t respond to when I switch to this Vector machine. Other 3 Quads switch properly and I can see the display and responds to Keyboard and Mouse inputs.

2. 4 port KVM switch with VGA + USB connections… I also have similar issue with Lambda blade servers all hooked to KVM via VGA and USB interfaces. Here old blades work fine but nor the new 4 A6000 blade.

In both cases I have to use a separate wireless USB dongle to connect to the latest machines (Vector and the Latest Blade server).

Has any one faced this issue? And any suggestion?