Troubleshooting


Unable to Connect to a Remote Client Computer

If you are denied access to a remote client computer, perform the following steps:

  1. Verify that the client computer is connected to the network: At the command prompt on the server, type ping <client system name> and press <Enter>.
  2. If both the server and the client computer are in a domain, verify that the domain administrator account has administrator privileges for both systems.
  3. If both the server and the client computer are in a workgroup and not in a domain, perform the following steps:
    1. If the client computer is running the Microsoft* Windows* XP Professional operating system and the server is running Windows 2000, verify that Service Pack 2 or later is installed on the server.
    2. If the client computer is running Windows XP and is not part of a domain, edit the registry to allow remote connection with administrative privileges. 
      CAUTION: Back up your computer data files before making changes to the registry. Incorrectly editing the registry may render your operating system unusable.
      To make the registry change on the client computer, click the Start button, click Run, then type regedit, and click OK. In the Registry Editor window, navigate to:

      My Computer\HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Lsa

      Set the ForceGuest value to 0. By default the value is 1. Unless you modify this value, the user remotely connecting to the machine has Guest privileges only, even if the supplied credentials should provide administrative privileges.
    3. Create an account on the client system with the same user name and password as an administrator account on the computer running your Windows Management Instrumentation (WMI) management application.
    4. Verify that DCOM and CIM are enabled on the client machine.

Installation Problems

If you are unable to complete installation of the Intel® ASF Alerting Agent, check the following:


Problems Receiving Alerts at the Management Station

If you are unable to receive any alerts or heartbeats, confirm that ASF is enabled (Enable = True) and the correct remote management station IP address (DestinationAddress) is set, by checking the Settings tab of the Intel ASF Agent WMI Console or by using a WMI browser. To confirm that heartbeats are enabled (EnablePresenceHeartbeats = True), check the console Timers Settings tab or use the WMI browser. Verify that your remote management console supports ASF alerting.

If you are unable to receive chassis intrusion alerts, verify that chassis intrusion alerting is turned on in the client's system setup program.

If you are unable to receive system password alerts, verify that the system password (not only the BIOS password) is set up in the client computer's system setup program. Note that an alert is sent only after the third unsuccessful password entry attempt.

If the ASF management console intermittently fails to receive all packets, increase the retransmission count (RetryCount). User Datagram Protocol (UDP) packets are not guaranteed delivery, and heavy network traffic may be causing the Platform Event Trap (PET) packets to drop.


Too Many Heartbeats Received

If you are seeing too many heartbeats at the remote management console, adjust the heartbeat timer (PresenceHeartbeatInterval). Reducing the retransmission count (RetryCount) could prevent alerts from being seen at the management station if heavy network traffic causes the PET packets to drop. 


Copyright © 2002 Intel Corporation.
Legal Information
Last modified on 11/05/02 1:32p Revision 1