Shandy's Blog

Where Andrew Sutton, aka Shandy rants and rambles on as the fancy takes him

This blog hosted by:
http://blogs.vbcity.com      
  Home :: Syndication  :: Login

My name is Andrew Sutton, aka Shandy.

I am currently living and working in the UK within the garment industry as an IT specialist. This blog contains mainly IT related issues.

I was a Microsoft VB MVP for a couple of years (Apr 2004-Mar 2006) and was a vbCityLeader between April 2003 and June 2007.

If you are looking for my Sri Lanka or Morocco experiences check out Shandy's Sri Lanka Blog or Shandy's Morocco Blog. My personal (Non IT) blog is now at Shandy's Place

MarApril 2007May
SMTWTFS
25262728293031
1234567
891011121314
15161718192021
22232425262728
293012345

Articles

Archives

Topics

Image Galleries

.NET

Blogs I Read

Others

VB.Classic

Monday, April 23, 2007 #

Last Friday we re-organised the Keyboard/Video/Mouse (KVM) switches at one of our server rooms. Previously we had never bothered to daisy chain our KVM switches and consequently had three KVM switches, each with their own keyboard, mouse and monitor. As we had two identical KVM switches - Belkin Omni View Pro 8 Port KVM Switches (F1D108-OSD) - it seemed logical to place these physically together, daisy chaining them using a Belkin 2' Daisy-Chain Cable (F1D108-CBL) so that they could share a single keyboard, mosue and monitor. However, when we did this the monitor attached to the master unit would only work for devices attached to the master unit; we had to attach a second monitor to the slave unit to handle devices attached to the slave unit. The master unit keyboard and mouse worked successfully for both devices connected to the master and the slave unit. Has anyone else come across this problem and found a solution so that only a single monitor is required?
posted @ 2:43 PM | Feedback (2)