- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 04:54 AM . Last Modified: 2024-03-08 03:54 AM
Can't communicate with AP9640 from Server 2012R2 [Solved]
We're moving to the AP9640 NMC and need to be able to configure them initially with Putty. Actually we need to be able to script the initial configuration so it can be automated as part of our server configuration scripts.
These will be configured from Windows Server 2012R2
Since the Gen 3 cards only have USB connections we need to use the provided USB to USB cable.
We follow the steps in this faq, https://www.apc.com/us/en/faqs/index?page=content&id=FA386514&actp=search&viewlocale=en_US but there are
no steps specific to Server 2012. It gets to the Win10 step 2, with NMC3-CDC using winusb.sys, but can't map to a com port.
When we try to update the driver using usb_cdc_ser.inf as provided by APC, it says it's not signed and won't allow the update with this message, "The third-party INF does not contain digital signature information"
There's a MS techdoc for some USB port issues that refers to KB2990372 from 2014, but that KB isn't available anymore, plus the description doesn't really fit the issue we have.
What steps are people performing to get something like Putty to communicate with the Gen 3 cards via the supplied USB cable?
Regards,
- Tags:
- ap9640
Link copied. Please paste this link to share this article on your social media post.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 04:54 AM . Last Modified: 2024-03-08 03:54 AM
I was able to get updated drivers for the cable for USB to Com from APC.
Once installed it works fine. One thing I did learn though is if the cable is unplugged and plugged back in it will iterate the com port number by +1. i.e., initially COM3, then COM4, even though it still shows COM3 in device manager. At least on my HP DL380 G10.
Luckily the friendly name doesn't change so a PowerShell fucction will still find it and report back COM4 (or whatever it happens to be).
Link copied. Please paste this link to share this article on your social media post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 04:54 AM . Last Modified: 2024-03-08 03:54 AM
I was able to get updated drivers for the cable for USB to Com from APC.
Once installed it works fine. One thing I did learn though is if the cable is unplugged and plugged back in it will iterate the com port number by +1. i.e., initially COM3, then COM4, even though it still shows COM3 in device manager. At least on my HP DL380 G10.
Luckily the friendly name doesn't change so a PowerShell fucction will still find it and report back COM4 (or whatever it happens to be).
Link copied. Please paste this link to share this article on your social media post.

