The best way to check this out is to use perfmon.exe (start-->run-->perfmon). Then connect with PerfMon to this specific machine, and select a few counters to check if they are accessible remotely. If perfmon cannot connect to them, then NetCrunch cannot, since it uses the same API.
Windows 2003 troubleshooting steps If you are running NetCrunch as an application, you may ignore this. However, if NetCrunch is running as a service, on Windows 2003 SP1 there is heightened security that inadvertently blocks connections to remote Windows devices. Therefore it is imperative that NetCrunch Login as a user with administrative rights.
XP troubleshooting steps
To connect to Windows XP remotely and read its counters, "Sharing and security model for local accounts" must be changed from "Guest only" to "Classic" in Computer Local Security Policy. 1. Start the Microsoft Management Console (MMC) Local Security Policy snap-in
(Start-->Control Panel-->Administrative Tools-->Local Security Policy).
2. Expand the Local Policies branch.
3. Select Security Options.
4. Double-click "Network access: Sharing and security model for local accounts."
5. Select "Classic - local users authenticate as themselves"
6. click OK.Make sure that the recommended ports are configured open on the firewall.
Remote Registry Service should be started in the list of services.
XP home edition Click here to find out why you are not able connect or pull counters from XP Home edition.
See also general NT connectivity hints.
