SMS: "Unable To Locate <machine name>" Trying to Remote Control in a Wide Area Network (165589)

SYMPTOMS

When trying to remote control a Systems Management Server client in a wide area network (WAN) environment, the following error messages may occur in sequence:

Attempting To Locate <machine name>
Trying Additional Protocols
Unable To Locate <machine name>

CAUSE

On a TCP/IP WAN, communication over some routes may fail if intermediate network segments have packet sizes smaller than the communicating hosts, and routers do not send appropriate ICMP responses to this condition. A router that causes this condition is sometimes known as a "black hole" router.

The Windows NT Server PING utility is a great diagnostics tool that can help you find those "black hole" routers. Use the following PING command:

   PING -t -l 64000 <machine name>.

If the request times out, it is an indication that the router between those two computers may be a "black hole" router, and may cause Remote Control to fail.

To resolve this problem, correct the configuration of the appropriate router.

WORKAROUND

To work around this problem, modify the following registry key.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Run Registry Editor (Regedt32.exe).

From the HKEY_LOCAL_MACHINE subtree, go to the following key:

      SYSTEM\CurrentControlSet\Services\<adapter name and number>
      \Parameters\Tcpip

On the Edit menu, click Add Value.

Add the following values:

      Value Name: MTU
      Data Type:  REG_DWORD
      Data: <1500 or Ethernet segment's MTU size>

Click OK.
Quit Registry Editor.
Shut down and restart Windows NT.