ASUS Q170M-C running i5-6600k
MEBx Version 11.0.0.0010
FW Version 184.108.40.2066
LMS Version 220.127.116.119
MEI Driver Version 18.104.22.1682
MEI DeviceID PCI\VEN_8086&DEV_A13A&SUBSYS_86941043&REV_31\3&11583659&0&B0
SOL Driver Version 22.214.171.1249
SOL DeviceID PCI\VEN_8086&DEV_A13D&SUBSYS_86941043&REV_31\3&11583659&0&B3
I cannot remotely (from a different computer) connect to my Q170 no matter what I do (yes i Have a monitor hooked up to it and it is in use, I'm using it now!). i also have multiple Q170s and they all work fine. i've tried:
-RESETTING BIOS on motherboard
-DISABLE & RE-ENABLE physical jumper PIN on motherboard
-Unprovision, disable AMT from BIOS and also from AMT menu many many times.
-I've used KVMControlApplication.exe (from 11.6 SDK package), Mesh Commander 0.4.2, Intel Manage Commander 1.0.8 and nothing works.
Here is an error from Intel MC 1.0.8 Error:
KVMRedirectionSAP, RequestStateChange Error 400.
Here are the workflows that has worked on many Intel AMT KVMs I've worked with previously and have been successful with:
-Within BIOS enable AMT (if not enabled)
-ctrl+p into the AMD configuration, enter default admin password, change pw and proceed to enable network IP
-I use KVMControlApplication.exe to "edit machine settings and change KVM Status to Enabled - all ports
-Then I can use any tool like VNC Viewer to connect and manage product out of band.
Are there commandline methods to change this KVM Status setting without resorting to UI? Seems like there is an issue with a variety of UI programs adjusting this 1 setting to redirect the port.
IS THIS a HW-component issue?
I would like to add that when I first purchased and stood this machine up the remote KVM worked fine. It was post 11.6 FW that it stopped working for some strange reason.
vPro Platform Solution Manager query shows:
Exception: Attempt to use an unsupported feature: KVM is not supported by the Intel AMT device.
Stack Trace: at Intel.Manageability.Impl.AMTInstanceManager.get_KVMSetup()
at Plugins.IDER.ctrlIDERDetails.UserControl_Loaded(Object sender, RoutedEventArgs e)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)
at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
PS Could this be a HW component issue?
I should also note that event log show NOTHING at all. All clear nothing NEW vs. all the other event logs I've seen. HW FW upgrade corruption?