Answer the question
In order to leave comments, you need to log in
Hide server IP address from users?
So there is an office in which all clients work with documents on Windows 2003 Server via RDP.
The server is geographically located in a different location.
How to organize the work so that 2 conditions are met:
1. Users could not determine the IP address of the server
2. When transferring the server (changing its IP address), there was no need to reconfigure all clients.
Tell me in which direction to dig in order to organize this system.
Answer the question
In order to leave comments, you need to log in
Alternatively, you can install a gate in front of a server in another country.
Well, the hidden server itself should not be allowed on the Internet (that is, so that it is connected only to the gate).
Next, a VPN tunnel is made from the gate to the clients.
As a result, clients will see the IP address of the gate, and they will access the target hidden server using the local IP.
Put the server behind the gateway, and stupidly forward the port on the gateway?
It seems to me that SNAT + DNAT will save you, if I understand you correctly.
Buy another server with the ip that you are ready to show to users and forward the port from it so that port 3306 on the external ip of the new server is forwarded to the old one.
If the server moves, just change the forwarding settings.
In particular, on VDS with Linux using ssh, this is done in the following way:
ssh -L external_ip_vds: 3306: server_ip_s_rdp: 3306 127.0.0.1
rent any cheap VDS,
run any portmap on it, for example, tcppm from the 3proxy set,
the launch is simple - put it into autoload:
/tcppm -d -t 3389 address_of_real_rdp_server 3389
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question