This article was previously published under Q124837
This article has been archived. It is offered "as is" and will no longer be updated.
Network Monitor can capture traffic on another subnet by connecting to asystem that is running the Remote Agent software on that subnet. TheNetwork Monitor Agent software is included with both Windows NT Workstationand Windows NT Server. In Network Monitor, when you click Networks on theCapture menu, Remote is one of the options. Provide the Agent's computername (with or without "\\") to connect to it.
For Network Monitor to connect to a Remote Agent across a router, theRemote Agent's computer name must be resolved. If the name cannot beresolved, you receive the following error message:
Failure connecting to <computer name of Agent>
The Remote Agent registers a NetBIOS name which is 16 characters long. Itconsists of the computer name followed by 0xBE (extended characters). Forexample, a machine named "HITME" would be registered as"HITME\0xBE\0xBE\0xBE..."
Use the following steps to connect to the agent across a router:
Ensure that the Manager and the Remote Agent systems have a routable protocol such as TCP/IP or NWLINK installed.
Install the Network Monitor Agent software on the remote computer.
Start the Network Monitor Agent Service by doing one of the following:
At the command prompt, type the following command:
net start nmagent
Double-click the Services icon in Control Panel, click Network Monitor Agent in the Service list, and then click Start.
If TCP/IP is the protocol that is used, then there are two ways to resolve a NetBIOS name to an IP address. If both the management station and the remote agent are using Microsoft Windows Internet Naming Service (WINS) then the name will be resolved by WINS and WINS locates the Agent. If not, then the Lmhosts file on the management station must contain a special entry for the remote agent.
If TCP/IP is used and WINS is not available, add the Agent's name in the Lmhosts file. Non-printing (extended) characters can be added by using \0xnn format where nn represents the ASCII code for the character.
Microsoft Systems Management Server 1.0 Standard Edition, Microsoft Systems Management Server 1.1 Standard Edition, Microsoft Systems Management Server 1.2 Standard Edition, Microsoft Systems Management Server 2.0 Standard Edition, Microsoft Systems Management Server 2.0 Service Pack 1, Microsoft Systems Management Server 2.0 Service Pack 2