Port forwarding in both directions using Windows Server 2003

Question

Windows Server

There is this OS, a rule has been created in routing and remote access that allows you to get access to the machine behind nat on port 80 through an external server IP, but when someone from the local network tries to connect through the real address of the server, it fails connection.

Is it possible to somehow set up port forwarding in both directions with regular means?

Answer 1

No, now you have port forwarding using NAT, it will only work if the incoming packet came from the external interface. From an internal network without NAT, this option will not work, because. a client that contacts the server at an external address will receive a response not from an external address, but from an internal one. Solutions are as follows:
1. Make a DMZ network, move the server there. Use real addresses in the DMZ network, or configure both the internal and external address on the server, configure routing from the internal network to the "external" address in the DMZ network.
2. Keep the external and internal DNS zone, in the internal zone register the internal address of the Web server
3. Install a portmapper or proxy that works at the application level and really “listens” on the port, and does not translate network packets.

Answer 2

there is a winserver (let's say some WS) with an IP address outside 86.xxx.xxx.xxx(wan0) and there are 4 interfaces 192.168.1.1 (lan1), 192.168.2.1(lan2), 192.168.3.1(lan3), 192.168.4.1( lan4), behind the winserver there is a webserver (colinux with ubuntu) 192.168.4.2 (let's say some CS). In routing and remote access, all 4 interfaces are added to nat and they share the Internet via wan0, also by means of the winserver (Properties of WAN0-tab services and ports) port 80 is forwarded to CS. Clients behind the wan0 interface can work with CS through the address 86.xxx.xxx.xx, but clients with lanX only through 192.168.4.2. But I would like to give everyone the opportunity to work through 86.ххх.хх.хх.
In other words, the vinserver listens on port 80 only on wan0, but I would like it to be on all 4x.

Answer 3

There is a very simple solution: split-brain DNS