Troubleshooting

Unable to Connect to a Remote Client Computer
Installation Problems
Problems Receiving Alerts at the Management Station
Too Many PETS Received
Using Diagnostics from Intel® PROSet and Intel® Boot Agent with Intel® PRO Alerting Agent

Unable to Connect to a Remote Client Computer

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

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>.
If both the server and the client computer are in a domain, verify that the domain administrator account has administrator privileges for both systems.
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 4 or later is installed on the server.
2. If the client computer is running Windows XP and is not part of a domain, edit your security options.
  
  Click the Start button, click Run and type secpol.msc, and click OK. In the Local Security Settings window, navigate to Local Policies>Security Options and double click on Network Access: Sharing and security model for local accounts.
  
  Select Classic - local users authenticate as themselves. 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. The Windows Management Instrumentation (WMI) service must be running and not disabled. Create an account on the client system with the same user name and password as an administrator account on the computer running your WMI management application.

Installation Problems

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

You must have administrator rights on the target computer.
The computer must be running Microsoft Windows XP Professional, Windows 2000, or Windows NT* 4.0.

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 your system supports chassis intrusion alerting and you are unable to receive these alerts, verify that chassis intrusion alerting is turned on in the client's system setup program.

If your system supports system password alerting and you are unable to receive these 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 PETS Received

If the frequency of heartbeats you receive at the Remote Management Console is not to your liking, adjust the heartbeat timer (PresenceHeartbeatInterval). A higher interval means fewer heartbeats.

If you prefer to receive fewer retransmissions, lower the retransmission count (RetryCount) value.

NOTE: Reducing the retransmission count (RetryCount) can cause the alerts not to show up on the management console if heavy network traffic causes the PET packets to drop.

Using Diagnostics from Intel^® PROSet and Intel^® Boot Agent with Intel^® PRO Alerting Agent

When you are running diagnostic tests or updating the Boot Agent from Intel® PROSet, the software determines whether the ASF Alerting Agent service is running. If it is running, a message is displayed in Intel PROSet and indicates that the ASF agent will not be functional when the diagnostic tests are running. When you are finished with the diagnostic test or updating the boot agent, the ASF Alerting Agent service is started again automatically.