Cisco Cisco Agent Desktop 8.5 Guia De Resolução De Problemas

Página de 126
Cisco CAD Troubleshooting Guide
50
April 3, 2014
Network Check
On the CAD services computer, verify that the IP address in the registry value 
HKEY_LOCAL_MACHINE\SOFTWARE\Calabrio\CAD\Site Setup\IOR 
HOSTNAME (in case of 64-bit machines, HKEY_LOCAL_MACHINE\WOW32\ 
SOFTWARE\Calabrio\CAD\Site Setup\IOR HOSTNAME) is the correct IP 
address of the public NIC.
To view information about the NICs on the computer, open a command 
window and type ipconfig /all.
Verify that the hostname and IP address are as expected.
Verify that the subnet mask is correct. It is probably 255.255.255.0.
If there are multiple NICs enabled, verify that the public NIC comes before the 
private NIC:
a. In the Control Panel, double-click Network and Dial-up Connections. 
b. From the menu bar, choose Advanced > Advanced Settings.
c. On the Adapters and Bindings tab, verify that the NICs are in the correct 
order in the Connections pane. 
Check the network connectivity by pinging from the CAD services computer to 
others in the configuration, for example, the Unified CM computer. Then 
reverse it by pinging from the other computers to the CAD services computer. 
Do this using both hostnames and IP addresses and ensure that the ping 
results match.
If hostnames are used, verify that the DNS, WINS, and hosts files are correct.
If there is a problem connecting to a particular service, try typing telnet <IP 
address/hostname> <port> in a command window, where <IP 
address/hostname> is the IP address or hostname of the computer where 
the service is running and <port> is the port used by the service. 
Use a network protocol analyzer like Ethereal to analyze network 
communications.
If security or firewall software is running on the computer, check its reports 
and/or logs to see if it is blocking any communication or ports.
Memory Check
Ensure that the amount of memory on the computer is at least the minimum 
required for CAD and other installed software. If the amount of memory is 
below the recommended level, it could be the source of the problem.
Use Microsoft Perfmon (perfmon.exe) to perform most memory checking.
— Add the following counters for _Total and process of interest:
Private Bytes