Modify the service port of Memcached in Windows. windowsmemcached_PHP tutorial

Modify the service port of Memcached in Windows, windowsmemcached. Modify the service port under Memcached in Windows, windowsmemcached in command mode, you can use the memcached-p12000 to specify the port, after the service installation, but there is always only the service port-drun modifies Memcached under Windows, windowsmemcached

In command mode, you can use memcached-p 12000 to specify the port. after the service is installed, the parameter-d runservice is always used.

Modify the registry to modify the port.

Find an ImagePath string under HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ memcached Server, which is exactly the string of the service execution path,

Double-click the string, add-m 45-p 12000 (use 45 m memory, 12345 as the Port) to the end, and then start the service.

Configuration result

I used to install memcached in linux in java. now I have installed memcached on windows.

Use telnet to connect to the memcached listener port on the computer where windows is located to see if it can be connected.

How can I change the windows log port?

Modify the Windows rras vpn pptp service default port number through the registry

The default port number used by the first-layer tunnel protocol PPtp of VPN (virtual private network) is TCP 1723, which is a standard, that is to say, whether it is the VPN service provided by Microsoft Windows Server or other systems or hardware VPN, this port number is used, but if it is the route and remote access (RRAS) that comes with Windows Server) you can modify the port number through the registry to hide the VPN server. However, note that the VPN client used here is still a Windows-based VPN connection.

First, let's take a look at the connection status of the VPN Server built with the route and remote access (RRAS) provided by Windows Server: After the service is successfully created, the Server listens to TCP port 1723 on the Server and waits for a connection, the client dials through a valid account authorized by the server. after the connection is successful, enter netstat-an under the CMD client to see that the client also opens TCP port 1723, which is also listening. Through subsequent explanations, we can find that the TCP 1723 port opened here is not affected by the client firewall, that is, even if the client firewall does not open this port, the system can also open this port for listening.

The above is the connection through the default port. next we will modify the registry to achieve the purpose of customizing the port: first, find this item in the server Registry [HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Class \ {4D36E972-E325-11CE-BFC1-08002bE10318}], which sets the key value related to the network adapter, under this item, you can see the named branches such as 0000, 0001, and 0002. these branches set information about each interface, then we find the branch that contains the string DriverDesc and the value is the WAN micro port (PPTP). This branch may be one of the named branches such as 0000, 0001, and 0002, we can continue to find the TcpPortNumber key under this branch. we can see that the default decimal value is 1723, and this 1723 is the default port number opened by the VPN service. we can change it to any other port number.

Through the above settings, after we restart the server, enter netstat-an in the CMD of the server, and you will find that the VPN server has started listening for the modified port number, this indicates that the default port number 1723 has been successfully changed on the server.

Next, configure the client. The port number modified by the VPN service is different from that modified by the terminal service by adding a colon and a port number to the target IP address. The experiment shows that the VPN client computer also needs to modify the registry key value on the server to connect to the server, after the modification, the firewall that comes with the client system must be closed to successfully connect (only open this port is not available). Otherwise, the system will prompt error 691: the connection to the remote computer cannot be established, therefore, the port used for this connection is closed. Using the default 1723 does not require firewall port opening.

Summary: to modify the default port number for a VPN Server built using the route and remote access (RRAS) built on Windows Server, you must modify the TcpPortNumber key value in the registry at the same time on the Server and client; in addition to modifying the registry, the client must also disable the built-in firewall.
 

In command mode, you can use memcached-p 12000 to specify the port. after the service is installed, the only difference is-d run...