Network Monitor Fails to Connect to Remote Alpha-based Agent

ID: Q218978

The information in this article applies to:

Microsoft Windows NT Server version 4.0 SP4
Microsoft Windows NT Server, Enterprise Edition version 4.0 SP4
Microsoft Windows NT Workstation version 4.0 SP4
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server

SYMPTOMS

After you apply Windows NT 4.0 Service Pack 4 to an Alpha-based computer, the following events are logged in Event Viewer:

The Network Monitoring Agent service has successfully started.

The Network Monitoring Agent has failed to start. The Agent failed registration. The return code is 0x45.

Both the Network Monitoring Agent and the Network Monitoring Manager require that NetBIOS be bound and active. NetBIOS was either not found or is not active on this machine.

Also, the Network Monitor remote monitoring functionality fails. You cannot connect to the Alpha-based computer in Network Monitor when you click Capture, click Network, and then select the Remote option and enter the name of the Alpha computer.

CAUSE

This problem occurs because Windows NT 4.0 Service Pack 4 installs the x86 version of Bhnetb.dll instead of the Alpha version.

This problem only occurs in the U.S. English version of Service Pack 4. International versions are not affected.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/Windows/ServicePacks/

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0 Service Pack 4. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Additional query words: 4.00

Keywords : kbbug4.00 kbfix4.00 nt4sp5fix
Version : WINDOWS:2000; winnt:4.0 SP4
Platform : WINDOWS winnt
Issue type : kbbug