Cisco Cisco ASA 5550 Adaptive Security Appliance 故障排查指南
−−−− −−−−−−−−−−−−− −−−−−−−−−−−−− −−−−−−−−−−− −−−−−−−−−−−−−
dc 192.168.1.100 Administrator down
In addition, the adObserver log prints this error:
Mon Jan 23 08:24:23 2012: EXCEPTION OCCURED: .\DcMonitor.cpp:373
getDcVersion: Error with ConnectServer for DC: dc name: 192.168.1.100
hostname: 192.168.1.100 domain: mirober2.lab username: Administrator
password: <hidden> Error code: 800706ba
Solution
When you add the AD agent to the DC, ensure that either the host name or the fully qualified domain name
(FQDN) of the DC is used with the −host keyword.
(FQDN) of the DC is used with the −host keyword.
Note: The DC IP address should not be used. IP address is not a valid value for the −host keyword. Refer to
the adacfg dc create section of the Installation and Setup Guide for the Active Directory Agent for more
information.
the adacfg dc create section of the Installation and Setup Guide for the Active Directory Agent for more
information.
When the DC is added correctly and visible to the AD Agent, the adacfg dc list command shows the status of
the DC as up:
the DC as up:
C:\IBF\CLI>adacfg dc list
Name Host/IP Username Domain−Name Latest Status
−−−− −−−−−−−−−−−−−−− −−−−−−−−−−−−− −−−−−−−−−−− −−−−−−−−−−−−−
dc dc.cisco.com Administrator CISCO up
Note: Cisco Bug ID CSCto66192 has been opened as an enhancement request to allow an IP address as a
valid value for the −host keyword.
valid value for the −host keyword.
Note: Currently, there are known issues when you use the DC host name. If you experience issues, use the
FQDN, and then run the adacfg dc list command in order to check the status of the DC.
FQDN, and then run the adacfg dc list command in order to check the status of the DC.
Related Information
Technical Support & Documentation − Cisco Systems
•
Contacts & Feedback | Help | Site Map
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Jan 26, 2012
Document ID: 113424