My customer has an isse with WAAS and XP remote assistance. If they try it via IP address it works fine but via hostname it fails. Doing some investigation reveals that the two methods use different bind calls.
Yes it does use RDP but it's not getting that far so far as I can see. Its failing to authenticate which it does before RPC binds RDP.
The customer has now logged this with TAC so I won't pursue it here. Thanks for replying though. I will post a summary of the solution when we have one so that if anyone searches for a similar problem they get an answer.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...