6,185
社区成员
发帖
与我相关
我的任务
分享2000系统下信差发送失败。
在执行以下命令时，信差发送失败。
net send 172.18.74.119 "sfs"
提示
An error occurred while sending a message to 172.18.74.119.
The message alias could not be found on the network.
请教大虾们是什么问题，多谢了！
net send 172.18.74.119 "sfs"
提示
An error occurred while sending a message to 172.18.74.119.
The message alias could not be found on the network.
请教大虾们是什么问题，多谢了！
...全文
请发表友善的回复…
发表回复
litaibai 2003-10-06
- 打赏
- 举报
对方的netmessege关了
ravenkatte 2003-10-06
- 打赏
- 举报
参照：
http://support.microsoft.com/default.aspx?scid=kb;en-us;259750
http://support.microsoft.com/default.aspx?scid=kb;en-us;259750
zenggao 2003-10-05
- 打赏
- 举报
对方Messenger服务没开。
spark_li 2003-09-30
- 打赏
- 举报
CAUSE
This problem can occur because the Messenger service delays reposting a listen for 5 seconds after responding to a request, and any request that is sent to the computer before the listen is reposted causes the error message to be displayed. Also, the problem described in this article only occurs under the following
conditions:
When you send multiple messages to a specific target computer in quick succession.
When the target computer has correctly registered the <03> NetBIOS name.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix.
This problem can occur because the Messenger service delays reposting a listen for 5 seconds after responding to a request, and any request that is sent to the computer before the listen is reposted causes the error message to be displayed. Also, the problem described in this article only occurs under the following
conditions:
When you send multiple messages to a specific target computer in quick succession.
When the target computer has correctly registered the <03> NetBIOS name.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix.
spark_li 2003-09-30
- 打赏
- 举报
CAUSE
This problem can occur because the Messenger service delays reposting a listen for 5 seconds after responding to a request, and any request that is sent to the computer before the listen is reposted causes the error message to be displayed. Also, the problem described in this article only occurs under the following
conditions:
When you send multiple messages to a specific target computer in quick succession.
When the target computer has correctly registered the <03> NetBIOS name.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix.
This problem can occur because the Messenger service delays reposting a listen for 5 seconds after responding to a request, and any request that is sent to the computer before the listen is reposted causes the error message to be displayed. Also, the problem described in this article only occurs under the following
conditions:
When you send multiple messages to a specific target computer in quick succession.
When the target computer has correctly registered the <03> NetBIOS name.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix.
