This is an typical example of someone that hasn't even tried to figure out what is wrong and instead decided to blame their mal-config on some other part of the system else and request help with that.... normally I wouldn't even try to respond to this kind of question but since I am feeling chariable today I will give you a few pointers
Hint, you problem lies in your basic design.... not in the MT config
#1, If you have onle ONE external IP then you should normally only have ONE physical webserver, this is since all HTTP traffic goes on port 80 and you can only have one machine receiving a address/port pair!
And before someone starts to correct me by saying that you can configure the router to examine packets and redirect to different places depending on the payload... please read the lines above, even that config still has only ONE machine listening to a IP/port pair... the router itself!
It's also a bitch to configure/maintain! Been there, done that when I was forced to FILTER/ROUTE pure NetBios (no IP) on a Token Ring network! A real bad design that I inherited when the designer got kicked out of the company... he had decided that he could bridge 5 offices running NetBios over 64Kb/s lines
#2, If you can consolidate your websites onto one server, do so! Windows 2003 CAN handle multiple web-requests (123.com, abc,com etc etc) and direct them to the correct website, just LOOK at the settings and READ the manual. RTFM-GTFW
#3, If you can NOT consolidate your websites onto one server you will have to configure an intermediate redirector AND set each server to listen to a different port...
Step 1: All HTTP traffic goes to the redirector which looks at the host header and identifies the requested host header URL. Depending on the host header it redirects the user web browser to a different port, example
This can easily be done using ASP code on a W2K3 server
Step 2: Set the respective web server to listen to the correct port
- Web server for http://www.abc.com
listens to port 81
- Web server for http://www.123.com
listens to port 82
- Web server for http://www.jkl.com
listens to port 83
Step 3: Configure your front end router to redirect traffic
to the correct server, some small changes to you previous code
/ip firewall nat
add chain=dstnat dst-address=126.96.36.199 protocol=tcp dst-port=81 action=dst-nat to-address=192.168.0.2 to-ports=81
add chain=dstnat dst-address=188.8.131.52 protocol=tcp dst-port=82 action=dst-nat to-address=192.168.0.3 to-ports=82
add chain=dstnat dst-address=184.108.40.206 protocol=tcp dst-port=83 action=dst-nat to-address=192.168.0.4 to-ports=83
ALSO PLEASE THINK BEFORE DOING ANYTHING ABOUT HTTPS!
That is a beast completely on it's own.... it is not a trivial thing to configure multiple HTTPS sites on one IP since you normally do NOT have access to the host headers in a request until it has been properly processed by the correct site