How to solve the network neighbor access response "slow" in the LAN?

Q: How to solve the network neighbor access response "slow" in the LAN?

A: Did you come across this de situation?

In Windows98 and Windows95 peer-to-peer networks, access to other computers through the network Neighborhood can sometimes be refreshed several times to connect.

Access to other computers in Windows Server or Win dows Advanced server, especially when you are slow to access Windows 98 o'clock, wait 30-50 seconds.

On the internet is slow enough, and now even the LAN is so slow, how to do? Below we will work with the author to solve the problem of "slow" LAN.

The problem in the network is mainly in the hardware and software two aspects, the local area network "Slow" problem also must from these two aspects to solve.

One, the hardware: first "to hard" bar. The hardware that determines the speed of the network is nothing more than a network card, hub, and cable.

1. Network card

The early Ethernet card is mostly 10M, now the 10m/100m network card has replaced the 10M network card, and the Gigabit network card has been published. So, if you still use the 10M network card, I advise you to change it.

2. Hub

A hub is the central component of a network, and all data is allocated to other computers. The general hub, the hub, because of its way of working behind switched hubs (switches), it is much faster to use the switch with sufficient funding. But some of the best of the kitchen switch is not used, rather than spend more money to buy a 3COM, D-link. If you don't have enough money, you can use a better hub.

3. Network cable

Do not underestimate the network cable, a motley network of network cables and AMP, and other brands have significantly different transmission speed, especially in 100M networks. The production of Crystal Head is also the key. Many people think that as long as the line at both ends of the crystal head on the same line, but the five types of twisted wire four strands of the "resistance" is not the same. I once went to a school to help solve the network when the problem of intermittent, a look at the line of the crystal head wrong, and redo the results of a smooth solution. The production of Crystal Head has two commonly used standard t586a and t856b.

Second, the software aspect

In small networks, the efficiency of the NetBEUI protocol is high. So in the LAN as far as possible using TCP/IP and NetBEUI two kinds of protocol, or only with NetBEUI protocol, because in the peer network as long as there is NetBEUI on the line. Regardless of the protocol, you must ensure that the protocols are identical on the two computers to which you are accessing each other. If different, you can add a protocol in the following ways.

Right-click My Network Places to select Properties and press Add in the Network dialog box to select the protocol. Select the protocol you want to make your computer accessible to other computers, and select File and Print Sharing to "allow other users to access my files" before you hook up.

Achieved the above points, in the Windows98 can basically solve the problem. However, it is still slow to access other computers through your network Neighborhood in Windows Server. In fact, we can bypass Windows2000 's Network Neighborhood to access other computers. Here the author provides three kinds of solutions:

Method One

In Run, enter: "Computer name Share name" or "IP address share name" To access shared folders on other computers. (This is the quickest and most convenient way)

Method Two

Right-click My Computer or My Network Places to select "Map a net Drive", select a letter in "Drive", and enter your computer name and share name in the URL format in "path". It then accesses the shared folder as if it were a drive.

Method Three

Create a shortcut on the desktop to run the command in method one.

These three methods can quickly access other computers on your network.

Due to the limited level of the author, only a cursory description of the possible problems and some solutions. There may be other, more convenient solutions in the actual application process. This article aims to solve some of the reader's practical problems.

To introduce the working principle of the Network Neighborhood: browsing services, I hope you have harvested!!

"Browsing Services" is very important and many users have developed a heavy reliance on "network neighbors".

After a user successfully logs on to the network, the next step is usually to access network resources. To help users find network resources, Microsoft network uses a mechanism called "browsing Service" to complete network resource lookup and location. The customer's browsing process is as follows:

Add the server to the browse list by posting a bulletin to the master browser.

The master browser shares a list of servers (domains) with the backup browser.

The client retrieves the list of computers for the backup browser from the master browser.

The client and backup browser contact to retrieve the list of servers.

Clients and servers are contacted to retrieve a list of shared resources on the server.

On the network, to effectively locate network resources, the browse service for the Microsoft Windows network must have a specific "Browse Server" to participate in and provide.

The role of the browsing server is divided into "(domain) main browsing Server", "Backup browsing Server", "Potential browsing Server".

The browse server is typically the first computer to be started, and can then be automatically changed or handed over by an election.

Every 15 minutes, each subnet's main browser declares itself to other master browsers on the web.

Every 12 minutes, each domain master browser contacts wins to obtain a list of all domainname〈1b〉 domains.

Every 12 minutes, each master browser (subnet) contacts the domain master browser to update the browse table.

Every 12 minutes, each backup browser and its local master browser are contacted to retrieve and update the browse table.

All computers that have server components (that is, the ability to share network resources) declare themselves to the master browser in their local domain.

The browser election occurs when the local subnet cannot find the master browser or initialize the domain controller. The election is based on the operating system version number and identity to determine the outcome.

And most of the traffic in this process is broadcast traffic. This is why you need wins in a multiple subnet environment to use Network Neighborhood normally. It's also why we're trying to use "Network Neighborhood" as little as possible within the corporate network. Its working process determines that in a relatively large and dynamic network, doomed to be unreliable and have many problems, and bring chaos.

The browse service does not have direct control options, except that for Win9x you can control whether the computer becomes a browse server in the network properties-file and Print Sharing service properties, and you must do so by modifying the registry. Here are some registry control parameters: (tested only under Windows nt/windows 2000) Note case!

To hide a specific computer in a network Neighborhood:

While this can be achieved by turning off the "server" service, it also loses the means to provide shared resources. You can modify the registry:

Systemcurrentcontrolsetserviceslanmanserverparameters

To establish or modify:

"Hidden" =dword:1/0

1 is hidden. After being hidden, it can be accessed through a UNC pathname.

There's a registry key that controls whether or not to be a browse Server:

Win2000 Computer, modify registry:

Hkey_local_machinesystemcurrentcontrolsetservicesbrowserparameters

"MaintainServerList" =reg_sz:yes/no/auto

"YES" as a browse Server, "No" does not act, "auto" automatic.

Win9x computer, control face version-network-file and print shared Services properties:

Master Browse Server: Invalid/valid/automatic

Do not set the Win9x computer to be valid, and set the computer that is often restarted or disconnected from the network to be invalid, to improve the work of network neighbors and improve network efficiency.