巧用Sniffer解决Dameware故障

    最近，笔者下载使用了Dameware NT 5进行公司局域网电脑的集中管理试用，在使用过程中，碰到了一个问题：Dameware 可以管理客户电脑的磁盘、服务等，就是其中一项“进程” 不能管理，当在客户电脑上右击选择“Processes”时，提示Error:53 找不到网络路径，百思不得其解。到底是什么样的问题导致出现这样的情况呢？

  于是我尝试着使用google与百度进行搜索，查找问题，下面引用官方对此问题的描述与解决方案：

Troubleshooting "System Error: 53 - Network Path not found" errors 

  
The information in this article applies to:

DameWare NT Utilties
DameWare Mini Remote Control
 

--------------------------------------------------------------------------------
 
System Error: 53
ERROR_BAD_NETPATH
The network path was not found.

System Error: 53 is not directly related to our software, however, it is a fairly common error message. Please make sure NetBios is enabled (i.e. NetBios over IP (NetBT/WINS), NetBios over IPX, etc...). You should easily be able to duplicate this issue outside of our software by attempting to map a drive to a shared resource on the remote machine (i.e. Net use X: or X: ).

Please also verify that File & Printer Sharing is installed on the remote machine. Also, if the remote machine is on a different subnet, please also keep in mind that all the necessary "File & Printer Sharing" ports must also be open on the routers/firewalls between the machines for the Mini Remote Control program to remotely install, start, stop, or remove the DMRC Client Agent Service or for any of DameWare NT Utilities functions to work properly.

Please reference the following FAQ for more information about the ports that the DNTU & DMRC programs use.

Using DameWare Development software in conjunction with a Firewall:

However, if the remote machine was running Windows XP SP2, then this issue could be related to the new SP2 Firewall which is enabled by default, and you will have to modify the default XP Firewall settings. Our software is compatible with any firewall, however, you will have to properly configure the firewall to allow the necessary traffic to pass through.

Please see the following knowledgebase article for more information:

Using DameWare Development products in conjunction with XP SP2

 

  根据官方的描述，我检查了远程计算机的配置，均正确。但为何还是连接出现问题呢？

下面谈谈笔者使用sniffer解决这个问题的思路：

  为了排除问题，我选择了对一台特定的计算机进行操作，并用sniffer监听这两台电脑的数据包。在sniffer中设定好过滤器后，开始监听。使用Dameware进行远程电脑的“Processes”管理。当连接显示失败时，停止监听。查看其通讯数据包。发现如下错误：

CIFS/SMB:C NT Create AndX Name=\winreg

CIFS/SMB:R NT Create AndX Status=Error:STATUS_OBJECT_NAME_NOT_FOUND

从这里的情况可以断定，这是Dameware对远程电脑进行注册表操作时的错误，于是检查远程电脑的“远程注册表”服务，发现未启动。原来问题就在这里，OK，在Dameware中对远程电脑的“远程注册表”服务双击，在弹出的对话框中，在启动帐户那里指定帐户：NT AUTHORITY\LocalService(好像必需是这个)，然后 指定一个密码(必须指定密码，否则无法启动服务)，启动服务，OK。再对远程电脑进行进程管理，成功了。

  至于Dameware的使用请参考其说明或者利用百度搜索。

  希望以上利用手头的工具解决问题的思路能对大伙有所启发与帮助。本文是笔者工作实践经验的总结。转载请注明出处。谢谢。