[The network path is not found] [0x80070035] Why can't I access windows share?

Installing a 2008 VM, and being ready to do some testing, as a result, the following error occurred during the access of the VM using UNC,

This error is very common, in Google search error number can search a lot of articles, which is actually the most terrible place, the search out of strange things, but no one can and their own error corresponding.

This example is one where both Windows Firewall and AVG Firewall all shut down without any effect, and the target server critical service is also enabled and can be accessed by UNC itself.

So open the Wireshark to see where the problem is, where the green box is a complete communication failure record.

of which two points should be noted,

1. The UNC access share is clearly used, why is the protocol HTTP? It's only right that SMB does.

2. Http1.1 503 Service Unavailable

The 2nd is well understood, because unknown reason uses the HTTP protocol, and the server originally did not have web service, natural reported 503 HTTP error.

Then open Google again, search the SMB HTTP keyword, find the following article in MSDN, an article,

http://msdn.microsoft.com/en-us/library/windows/desktop/aa365233 (v=vs.85). aspx

The key parts of the summary are as follows

In the OSI networking model, Microsoft SMB Protocol are most often used as an application layer or a Presentation layer Pro Tocol, and it relies on lower-level protocols for transport. The Transport layer protocol that Microsoft SMB protocol are most often used with are NetBIOS over TCP/IP (NBT) . However, Microsoft SMB Protocol can also be used without a separate transport protocol-the Microsoft SMB PROTOCOL/NBT Comb Ination is generally used for backward compatibility.

Is my NetBIOS not open? Then check the network card configuration and services, found the following service is disabled.

Once enabled and then grabbed the packet again, there was a long-lost SMB protocol,

So the joy, opened the AVG firewall, the result of the network was not found error, again grabbed the packet, and the HTTP protocol appeared.

It seems that in addition to the services mentioned above, firewall also have problems, so open AVG Expert mode, view the screen cheat log, the original is AVG block to the remote server 137 port UDP packet.

For example, the default is only open to the security Network 137, that is, the white list, now you can choose to add the network segment whitelist, or if only for the rule hook online segment.

Confirm to the end, again access UNC, still the same error, and then open the AVG log again, see this time is 445 and 139 block. Follow the above figure to find the rules for 139 and 445, allowing the network segment to be able.