有不少问题/答案与“ System error 53 has occurred
”有关,而且有很多答案与此问题无关。
我有一台名为'凯科斯'以及 DNS Cname '分享'相同。使用 NetBIOS,一些计算机接受 cname'分享'而其他则不然。我们需要备用名称来使此共享计算机独立。客户端和服务器两台计算机都是 2008 R2 域成员。我怀疑这是由流氓补丁更改的域策略(?)
所以,凯科斯,分享和192.168.0.26 是同一台计算机。
笔记:此配置已运行了 10 多年,但无缘无故地停止了运行(在某些域成员上)。
问题
- net view \\caicos works OK
- net view \\192.168.0.26 System error 53 has occurred.
- net view \\share System error 53 has occurred.
一些调试数据
C:\Users\administrator.W>nslookup caicos
Server: xxx
Address: fe80::5404:70ab:4ec6:f268
Name: caicos.w.com
Address: 192.168.0.26
C:\Users\administrator.W>nslookup share
Server: xxx
Address: fe80::5404:70ab:4ec6:f268
Name: caicos.w.com
Address: 192.168.0.26
Aliases: share.w.com
C:\Users\administrator.W>net view \\caicos
Shared resources at \\caicos
Virtual Machine Host
Share name Type Used as Comment
-------------------------------------------------------------------------------
backup Disk
*redacted* Disk
library Disk
reports Disk Internal use Reports
sales Disk Sales information.
users Disk User shares
The command completed successfully.
C:\Users\administrator.WE>tracert caicos
Tracing route to caicos.w.com [192.168.0.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms caicos.w.com [192.168.0.26]
Trace complete.
C:\Users\administrator.W>net view \\192.168.0.26
System error 53 has occurred.
The network path was not found.
C:\Users\administrator.W>ping 192.168.0.26
Pinging 192.168.0.26 with 32 bytes of data:
Reply from 192.168.0.26: bytes=32 time<1ms TTL=128
...
Ping statistics for 192.168.0.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\administrator.W>net view \\share
System error 53 has occurred.
The network path was not found.
C:\Users\administrator.W>ping share
Pinging 192.168.0.26 with 32 bytes of data:
Reply from 192.168.0.26: bytes=32 time<1ms TTL=128
...
Ping statistics for 192.168.0.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
答案1
回答我自己的问题。
我们的配置中有多个网络,因此从客户端到服务器有多个路径。此外,一个路径要经过坚固的防火墙,另一个路径则只是普通的 LAN 连接(内部防火墙)。
使用 nbtstat、名称 (-A) 和 ip 地址 (-a),我能够确认问题:没有 IP 连接。标准网络套接字通信足够智能,可以使用正确的接口,但(看起来)NetBIOS 只使用第一个接口,然而,当直接使用 NetBIOS 名称时,会使用 LAN 地址。
改变网络接口的优先级足以完全恢复 NetBIOS 通信。