Normally, a computer on the LAN must pass the port, protocol, service, and verification when it wants to successfully access the shared resources in another computer through the Network Neighborhood window. , authorization, review and other aspects, if any of these links can not pass, then the network neighborhood can not play its role. Generally speaking, the access factors at the bottom of the network neighbor function include communication port, network protocol, system service, network component, etc. Only these factors are normal, and two computers in the LAN can establish an access connection through the network neighbor; Well, after accessing the connection, it does not mean that they can access each other's shared resources. In the middle, they need to pass the user authentication, the authorization of the system security policy, and the authority review of the server. If these links can pass normally. Then the network neighbor access process can be successful.
Check the agreement to ensure that the protocol is installed correctly
Through the previous introduction, we have realized that if the protocol workstation is not installed correctly or is not set correctly, it may cause the network neighbor access failure. When encountering a network neighbor access failure, you should first check the network communication protocol of the Vista system. Since the usual network access only uses the TCP/IP protocol, we only need to check if the TCP/IP protocol is installed correctly. Some people may say that the Windows system automatically installs the TCP/IP protocol by default. Skipping can be ignored in one step. This is really good, but the Vista system will install TCP/IPv6 protocol and TCP/IPv4 protocol by default, and TCP/IPv6 protocol is rarely used. If we keep the installation status of the protocol, then Our future network access speed will be affected by this communication protocol, which may lead to inefficiency in network neighbor access. For this reason, it is necessary to cancel the installation status of TCP/IPv6 protocol and correctly set the TCP/IPv4 protocol.
When canceling the installation status of TCP/IPv6 protocol, we can first enter the Vista system desktop as a system administrator, and then click “Start”/“Set”/“ Network connection & rdquo; command, right-click the "local connection" icon in the pop-up network connection list window, execute the "property" command from the pop-up shortcut menu to open the local connection property setting window; > In the "Network" tab of the settings window, check if the TCP/IPv6 protocol option is selected. If you find that the option has been selected, we must cancel its selected state in time, so that TCP/The IPv6 protocol will not affect and interfere with normal access to the Network Neighborhood window.
Then use the mouse to select the TCP /IPv4 protocol option, and click the "Attributes" button to enter the TCP /IPv4 property settings interface, in which we must correctly set the computer's IP address, gateway address, DNS Server address and other parameters; if you want to be able to access shared resources on other computers in the LAN through the host name, we also need to click the "Advanced" button in the TCP/IPv4 property settings interface, and in the advanced TCP/IP In the property interface, click the “WINS” tab to open the tab settings page as shown in Figure 2. Select the "NetBios" option on TCP/IP in the page, and finally click the "OK" button to end the network. The setting operation of the communication protocol is modified.
Check the port to ensure the network channel is smooth.
The communication port is also at the bottom of the network neighbor function. If the relevant communication port in the computer is not open, then the network between the local computer and other computers in the LAN The channel will be closed, so LAN users will not be able to share access or other communication operations through the Network Neighborhood window. In general, shared access through the Network Neighborhood window requires the use of communication ports such as 135, 137, 139, and 445 of the computer system. If these ports are not opened, the shared communication operation through the Network Neighborhood window will fail.
When checking whether the local computer system has opened communication ports 135, 137, 139, 445, etc., we can first click on the "Start" "Start”/“Run” command in the Vista system desktop, in the pop-up In the system running dialog box, enter the “cmd” command, click the <;OK" button, switch the system state to the ms-dos window, and execute the string command at the command prompt of the window<quo;netstat -a&rdquo From the subsequent results interface, we can clearly know whether the local computer system has opened communication ports such as 135, 137, 139, and 445. In the default state, the Windows system will automatically open the communication ports 135, 137, 139, 445, etc. If it is found that there is no port successfully started, we can follow the previous steps to enter the interface as shown in Figure 1, "will ;File and Printer sharing for Micosoft Net…” The project is re-selected, and then the remote desktop function is enabled, which ensures that all communication ports 135, 137, 139, and 445 are turned on.
Of course, if the Vista workstation system is enabled with a firewall, then the firewall may limit the communication behavior of the relevant network ports, which may result in the sharing of access through the network neighbors. In this case, we can set the system as follows: With a firewall, make sure it is released to the shared access port:
First click on the "Desktop" in the system desktop, click "Start", "Settings", "Control Panel" command, open local In the control panel window of the workstation, click the “Security” in the window, and then click “Allow the program to pass the Windows Firewall” project to enter the parameter setting window of the firewall; in the “Programs or Ports” list of the window In the box, select the "File and Printer Sharing" option, and then click the "Apply" button, so that the Vista firewall will not restrict the normal access behavior of the network neighborhood.