Reasonably configure the server's hard drive
Users who work in a local area network (LAN) often use the network to print materials and access files. For some reason, the speed of network access may become abnormal, and we often mistakenly believe that the cause of reduced network speed could be bottlenecks in certain devices within the network, such as network cards, switches, or hubs. In fact, the biggest factor affecting network speed is still the speed of the server's hard drive. Therefore, correctly configuring the hard drive of the server in the LAN will greatly improve the overall network performance of the entire LAN. Maintaining a LAN brings many benefits to enterprises. Usually, when setting up the hard drive, we need to consider the following factors:
The hard drive in the server should preferably be one with high speed and large capacity, because a faster hard drive allows for quicker data access through the network;
The hard drive interface in the server should ideally be SCSI type, as this interface transfers data faster than IDE or EIDE interfaces, using parallel transmission mode to send and receive data;
If conditions permit, we can install a RAID card on the network server, as RAID cards significantly enhance the read/write performance and security of the hard drive;
Of course, it’s important to note that on the same SCSI channel, low-speed SCSI devices (such as CD drives) should not be shared with the hard drive, otherwise the high-speed data transfer capability of the hard drive's SCSI interface will not be fully utilized.
Correctly use "bridge" type devices
"Bridge" type devices are typically used for network devices within the same subnet, while routers are used for different segments of the network. At my workplace, we once installed a microwave networking device. After the physical connection was established and tested online, the server kept prompting that the current subnet number should match the other side's subnet number. After aligning the subnet numbers on both sides, the server's alarm disappeared. Ah! It turned out this was a device with bridging characteristics. Later, when installing microwave networking equipment at another location and switching to products from another manufacturer, we had already aligned the subnet numbers on both sides before installation. However, after the equipment was installed, the server again showed an error: incorrect current route. The issue resolved after modifying the subnet on one side. Therefore, correctly distinguishing between "routing" devices and "bridge-type" devices is crucial when setting network parameters.
Connect according to rules
Each computer in the LAN is connected using twisted pair cables, but simply connecting two computers with twisted pair cables does not necessarily enable communication. Connections must be made according to specific wiring rules. I once attempted to connect two computers over 100 meters apart with twisted pair cables to achieve communication, but despite all efforts, it failed. Later, I learned that the maximum distance for twisted pair cables is 100 meters. Additionally, if we need to connect two computers more than 100 meters apart, we must use conversion equipment, and when connecting conversion equipment to switches, we must perform crossover wiring. This is because Ethernet generally uses two pairs of twisted pair wires located at positions 1, 2, 3, and 6. If these pairs are separated and used individually, crosstalk (NEXT) will occur, significantly impacting network performance. In a 10M network environment, this issue may not be obvious, but in a 100M network environment, especially with heavy traffic or long distances, the network may fail to connect.
Strictly enforce grounding requirements
Since in LAN management, transmitted signals are usually weak, improper operation or failure to follow the specific operational requirements of network devices can lead to interference in the network, potentially causing severe disconnections across the entire network. Especially for some network conversion devices, since they involve long-distance lines, their grounding requirements are very strict; otherwise, the network device will not reach the specified connection speed, leading to various mysterious faults during networking. Once, I inadvertently plugged the router's power cord into a municipal power outlet, resulting in the inability to connect the 128k DDN dedicated line to the Internet. The telecom bureau found the lines were normal, but upon checking the zero-ground voltage of the router's power supply, it was discovered to be incorrect. Switching back to the UPS socket restored everything to normal. Another time, the grounding terminal of the router's power plug was damaged, causing frequent data packet loss, with ping connections fluctuating between good and bad. Replacing the power cord resolved the issue. Thus, it is clear that when using network devices, we must operate under specified conditions; otherwise, it will cause significant trouble for our work.
Use high-quality, fast new-style network cards
In a LAN, it is quite common for computers to fail to communicate with each other, and there can be many reasons for such failures. I have found that most faults in LANs are related to network cards—either the network card is not properly installed, the network cable has poor contact, or the network card is outdated and cannot be correctly identified by the computer. Additionally, some network cards installed in servers cannot withstand the impact of large amounts of data, eventually breaking down. Therefore, to avoid such issues, we must be willing to invest in quality network cards, especially if they are installed in servers. Servers generally run non-stop, and only high-quality network cards can endure long-term "work." Moreover, since servers transmit large volumes of data, the capacity of the purchased network card must match accordingly to ensure "good horses are paired with good saddles."
Reasonably configure the switch
Switches are an important data exchange device in LAN maintenance. Correctly and reasonably using switches can effectively improve data transmission performance in the network. I once configured a switch port to 100M full-duplex and installed an Intel 100M EISA network card on the server. Everything seemed normal after installation, but during high-traffic data transmission, the speed became extremely slow. It was later discovered that this network card did not support full-duplex. Changing the switch port to half-duplex resolved the fault. This indicates that the port rate and duplex mode of the switch must match the network card. Currently, there are many self-adaptive network cards and switches, which theoretically should correctly adapt to rates and duplex modes. However, due to differences in brands, full-duplex mode is often not correctly achieved. Even though the server network card is set to full-duplex, the duplex light on the switch remains unlit unless manually forced. Therefore, when setting network device parameters, we must refer to the network device parameters on the server or other workstations to ensure that all devices can work together effectively.