Setting up the system to make shared access no longer bumpy

In the LAN working environment, it is common for Internet users to share access, but many people always think that shared access operations are simply as simple as double-clicking the "Network Neighborhood" icon; in fact, sharing access through the network. At that time, we often encounter failures that cost a lot of effort and can't see specific shared content. What is the reason? This phenomenon is mostly due to our improper "teaching" of Windows systems. In view of this, the following article From the system settings, to properly "tune" the relevant sharing settings in the system, so that shared access is no longer bumpy!

Set the protocol, do not let the shared access time or bad

When trying to share access in a computer system with two IP addresses configured, we sometimes encounter the trouble of sharing access. Why is this happening? I believe many people will subconsciously think of this. It is caused by poor contact on the network line! In fact, the probability of good or bad when sharing access caused by this factor is small, after all, if the network line is really When bad touch, as long as we try to access the Internet or other network operators will be able to quickly determine whether a factor is the network line.

In a computer system with two IP addresses configured at the same time, when there is a good or bad failure phenomenon during shared access, these nine out of ten cases are caused by improper setting of the sharing protocol of the local computer system; We know that in the Windows working environment, the shared access operation is done through the SMB sharing protocol, and the SMB sharing protocol has two working modes, one is the traditional NetBios Over TCP/IP mode, and the other is Direct hosting. mode. When the computer system works in the NetBios Over TCP/IP protocol mode, the shared access operation needs to use the 137 communication port of the computer system for the name resolution service, the 138 communication port for the packet delivery service, and the 139 communication port for the file. Transmission service; when the local computer system works in the Direct hosting protocol mode, the shared access process is much simpler. It does not need to use the NetBIOS communication port for name resolution and packet delivery services, and directly uses the port 445 of the computer system. File transfer operation.

In general, traditional Win9X systems use the NetBios Over TCP/IP protocol mode for shared access. In Win2000 and above, shared access operations start using the Direct hosting protocol mode. The traditional NetBios Over TCP/IP protocol mode still exists, and the protocol mode is directly bound to the NIC device, and can only correspond to the first IP address of the NIC device, while the Direct hosting protocol mode does not have such special restrictions. According to this theoretical analysis, when a computer system configured with dual IP addresses attempts to share access, it is possible to work in the NetBios Over TCP/IP protocol mode, and it is possible to work in the Direct hosting protocol mode. When working in a mode, the computer system where the target shared resource resides must use the address of the same network segment as the first IP address of the local system to ensure the successful access operation, otherwise the shared access will fail; if the local computer system adopts When the Direct hosting protocol mode is used for shared access, the shared access operation will always succeed, and as a result, we will naturally feel that the shared access is good or bad. In order to prevent sharing access, it is good or bad. We just need to let the local computer system prohibit the use of NetBios Over TCP/IP protocol mode to do the following:
Previous page 12 3 4 Next Read more