Most of Z-Blog’s configuration parameters reside in c_option.asp. I downloaded a fresh copy of the latest Z-Blog 1.8, then replaced the c_option.asp on my hosting space with the new one. After that, I could log in鈥攕o clearly this file was the culprit. When comparing the old and new c_option.asp, the main content is largely the same; only some parameters differ. So I guessed that certain parameters might affect the workload during login. Because the latest Z-Blog 1.8 version has integrated the “Rebuild Cache” function into many operations, it boosts automatic execution and streamlines the workflow. However, this inevitably increases the workload during those operations, and on top of that, I also have a static page generation plugin installed.
That鈥檚 one side of the issue. There is another scenario worth noting, and it can resolve the login timeout problem through a different approach from the c_option.asp replacement mentioned above鈥攖hat is, modifying the “MTU” (Maximum Transmission Unit) value.
The general testing method is basically the same as described here, and this adjustment approach is largely consistent with the previous one.
MTU stands for Maximum Transmission Unit.
It refers to the largest data packet that can be transmitted over a network. The MTU unit is bytes. Most network devices have an MTU of 1500. If your local machine’s MTU is larger than the gateway’s MTU, large packets will be split into fragments for transmission, which generates many packet fragments, increases packet loss rate, and reduces network speed. Setting your local machine’s MTU to be smaller than or equal to the gateway’s MTU can reduce packet loss.
How to Detect the Gateway’s MTU?
Open a DOS window on your local machine and execute:
ping -f -l 1452 192.168.1.1
Here, 192.168.1.1 is the gateway IP address, and 1452 is the data packet length. Please note that the parameter above is “-l” (lowercase L), not “-1”. If the ping succeeds, it means the packet does not need to be fragmented and can be sent through the gateway. If you see:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
It indicates the packet needs to be fragmented for sending. In that case, reduce the packet length and run the ping command again. Try several values between 1400 and 1472 until you find a suitable packet length. Add the 28-byte packet header to this length to get the MTU value. If the detected gateway MTU is 1500, no modification is needed. If the gateway has a firewall and ping fails, you can try directly setting the MTU to 1400.
C:\Documents and Settings\Administrator>ping -f -l 1452 192.168.1.1
Pinging 192.168.1.1 with 1452 bytes of data:
Reply from 192.168.1.1: bytes=1452 time=5ms TTL=64
Reply from 192.168.1.1: bytes=1452 time=5ms TTL=64
Reply from 192.168.1.1: bytes=1452 time=5ms TTL=64
Reply from 192.168.1.1: bytes=1452 time=1ms TTL=64
Replies came back! This means this MTU value is workable! However, it is strongly recommended to find the largest feasible MTU value! That way, you can achieve the best network speed when configuring it!
Finding the MTU Value: The value found using the above method is not the actual MTU yet! Due to certain packet overhead, you need to add 28 to that value to get the required MTU value! So, in the example above, the required MTU value is 1464 + 28 = 1492!
Side note: After I set it to 1452 + 28 = 1480, some websites still couldn’t open, and Remote Desktop couldn’t log in via domain name (it could log in normally via IP). But after setting the MTU to 1452 instead, these problems were all resolved effortlessly. Moreover, at this point, logging into the Z-Blog backend worked fine, and Remote Desktop login via domain name also worked normally.
Generally speaking, setting the proper MTU on your local machine can fix situations where some websites fail to open. However, if your shared host or router’s MTU configuration is problematic, issues may still persist, or the network speed may be too slow. Properly configuring the MTU values on both the router and the local machine can completely resolve the above problems and maximize your Internet speed.
How to Modify the Local Machine’s MTU? The modification method is as follows:
(1), Run regedit
(2), Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
(3), Under Interfaces, there are multiple subkeys, each corresponding to a network adapter. Select the adapter as follows:
(4), Identify the IP address of the network adapter or dial-up