topic Re: Cannot enable Remote KVM at DQ67SW in Intel vPro® Platform

Cannot enable Remote KVM at DQ67SW

idata — Mon, 28 Mar 2011 11:37:29 GMT

Using default user "admin" for enabling Remote KVM in "Intel System Defense Utility". When i set option "Standard Port (5900)" to "Enabled" i get error "KVM Redirection Error Changing Settings". Telnet doesn`t walk through tcp port 5900.

Motherboard BIOS version is 0049

CPU model is i7-2600

Intel System Defense Utility ver 2.0.1)

Please help!

Re: Cannot enable Remote KVM at DQ67SW

Jacob_G_Intel — Tue, 29 Mar 2011 00:03:11 GMT

I'm not very familiar with IDSU. However, when I try this on my DQ67EP (same BIOS, same IDSU version) I get pretty much the same error. The end result is, I can't tell if it's enabling KVM or not. I'm going to see if I can find someone who knows IDSU a little better than me.

In the mean time, there are a few alternatives to get KVM working. First, http://www.realvnc.com/products/viewerplus/index.html VNCViewer Plus is very easy viewer with IDEr support. It has a 90 day trial, but then you ahve to pay. One free option is to use a free VNC viewer and use/docs/DOC-4795 this UCRD to enable KVM. Final free option I'm aware of is to usehttp://software.intel.com/en-us/articles/download-the-latest-version-of-manageability-developer-tool-kit/ Managability commander. It's similar to IDSU so that might suite you're needs.

Re: Cannot enable Remote KVM at DQ67SW

Ylian_S_Intel — Tue, 29 Mar 2011 01:01:09 GMT

I just saw you message. Let me investigate this tomorrow. In some cases, I have noticed that you need to go into MEBX to change settings since they can't be done remotely. I am also working on a new version of ISDU with a few fixes in this area.

Ylian

Re: Cannot enable Remote KVM at DQ67SW

idata — Tue, 29 Mar 2011 17:13:50 GMT

Thank You. I`ve solved this problem with Russian comunity and "Manageability Commander Tool". This one tool shows me that password that i want to install for remote kvm is bad. System Deffense gives very poor error text. Also it allows to enter passwords with mor than eight symbols.

Now i`ve got some other problems with this motherboard.

1) "Boot to BIOS" point anyway doesn`t work for me (System Deffense, Manageability Commander Tool, Radmin)

The error text in Manageability Commander Tool is:

"Call SendRemoteControl returned error:FAILED_WEB_CALL

BIOSSetup not supported"

2) Adaptec ASR-5405 Raid Controller doesn`t work in x16 slot. Motherboard doesn`t boot with this controller. With Intel PRO/1000 PT Desktop Adapter in this slot motherboard boots normaly, network adapters woks fine.

Re: Cannot enable Remote KVM at DQ67SW

Ylian_S_Intel — Tue, 29 Mar 2011 19:43:40 GMT

I just finished working on ISDU v2.0.3, it's available here.

https://sites.google.com/site/opensoftwareprojects/ISDU_2.0.3.msi?attredirects=0&d=1 https://sites.google.com/site/opensoftwareprojects/ISDU_2.0.3.msi?attredirects=0&d=1

Please give it a try and see if it fixes your problem. I am also looking for any other feedback.

Thanks,

Ylian

Re: Cannot enable Remote KVM at DQ67SW

Ylian_S_Intel — Tue, 29 Mar 2011 21:48:24 GMT

Good feedback on the KVM 8 character max, I just updated v2.0.3 and added a check for this. I also added better error text when SOL fails to connect, but yes, ISDU needs better error reporting.

Re: Cannot enable Remote KVM at DQ67SW

Ylian_S_Intel — Wed, 30 Mar 2011 16:50:55 GMT

This morning I worked on ISDU some more. Fixed network discovery issues and problems with large font support. Same link as before, still labeled v2.0.3 but the readme.txt file has more chages. Anyone using ISDU, please try it and comment!

https://sites.google.com/site/opensoftwareprojects/ISDU_2.0.3.msi?attredirects=0&d=1 https://sites.google.com/site/opensoftwareprojects/ISDU_2.0.3.msi?attredirects=0&d=1

Enjoy!

Ylian

Re: Cannot enable Remote KVM at DQ67SW

GRoes — Fri, 23 Sep 2011 21:56:43 GMT

My experience as a Linux user is that I needed a Windows program (Manageability Developer Tool Kit) to enable KVM. I used it to remotely connect to the vpro box and enable KVM (including the fixed 8-char password). Only after that, the box showed port 5900 open. I think it's weird that you can say "KVM: enable" in the BIOS but that that won't enable it.

I can't connect to the vpro box with "xtightvncviewer" (connection reset by peer) but I can with gtkvncviewer. I can see everything, including the BIOS and such. It's cool, but setup is non-trivial.

Gerben