Summary of several ways to access intranet through public network

Some rooms may not want external users to have direct access to all servers, usually open a public network, as a transit point of interaction with the outside world. There are several ways to access the intranet server:

1. We can access these servers by establishing a channel through the CRT. Steps to build the channel:

1). Select the remote address of the public network, right-click, select Properties.

2). Select Port Forwarding and select Add. Note: Name can be arbitrarily named, local address is an unused port locally, note that it is local!

Remote address is the IP address and port of the server that you want to connect to. But not the public address!!!

3). Connect to the public network via the CRT and keep the connection constant. Must always keep the public network connected continuously. You can then access the services on the appropriate server by accessing the appropriate local ports.

Cons: Must be consistent through the CRT, need to configure the channel for each port

2. With Firefox and CRT, via HTTP or sockes proxy. Steps to establish an agent:

1). Select the remote address of the public network, right-click, select Properties

2). Select Port Forwarding and select Add. Different from the channel: Select dynamic forwarding Using SOCKS 4 or 5 in Remote, then connect to the public network.

3). Firefox also needs special settings: Tools------Advanced network----Settings, select Manual agent, the socks host is filled with the IP address: 127.0.0.1, the port is the local port configured in the CRT.

4). Enter the intranet IP and port directly in the browser to access

Disadvantage: The extranet cannot be used. Non-browser access content in the intranet is still inaccessible.    such as: Plsql connection database. Pros: You do not have to establish a channel for each service.

3. Install the configuration Nginx

Related reference content (forget the following content from the big God that look, can not attach links, forgive me!) )：

HTTP proxy : The ability to proxy client HTTP access, mainly proxy browser access to the Web page, its port is generally 80, 8080, 3128 and so on;

Socks proxy : Socks Proxy Unlike other types of proxies, it simply passes the packet without caring about what application protocol, which can be an HTTP request, so the SOCKS proxy server is much faster than other types of proxy servers.

Socks agents are divided into SOCKS4 and SOCKS5, the difference is that the SOCKS4 agent only supports TCP protocol (Transmission Control Protocol), and the SOCKS5 agent supports both the TCP protocol and the UDP protocol (that is, the user Packet protocol), but also supports a variety of

Authentication mechanism, server-side domain name resolution, and so on. SOCK4 can do SOCKS5 can be obtained, but SOCKS5 can do SOCK4 is not necessarily able to do, such as our commonly used chat tool QQ in the use of agents when using the SOCKS5 agent, because

It needs to use the UDP protocol to transfer data

Summary of several ways to access intranet through public network