Network Monitor Fails to Connect to Remote Alpha-based Agent

View products that this article applies to.

This article was previously published under Q218978

Expand all | Collapse all

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.

Back to the top

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.

Back to the top

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/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
152734 (http://support.microsoft.com/kb/152734/EN-US/ ) 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://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

Back to the top

STATUS

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

Back to the top