@wallabybob:
@_Adrian_:
@marvosa:
Other than that, your NAT:Port Forward should look like:
WAN | TCP | * | * | WAN address | 80 (HTTP) | <webserver ip="">| 80 (HTTP) | description |</webserver>
WAN TCP * * SERVER1 address 80 - 443 192.1x.x.x 80 - 443 IIS1
WAN TCP * * SERVER1 address 80 - 443 192.1x.x.x 80 - 443 IIS2
Why do you have two port forward rules? Since they have the same port range only one of them will be effective.
What is "SERVER1 address"? Since you mentioned DynDNS I suspect your WAN interface has a dynamic address. If so, the port forward rule needs to specify Destination type=WAN address (not the CURRENT IP address of the WAN interface) so the rule's behaviour will track changes in the IP address of the WAN interface.
Thanks wallabybob !!!
Its working :D
Had to do a couple changes…
It didn't want to play nice so i went to a port 8080 redirect.
With that being said...
NAT :
WAN | TCP | * | * |WAN address | 8080 | <webserver ip="">| 80 (HTTP) | SERVER1 ( Description )
and created an rule for it that ended up looking like this:
IPv4 | TCP | * | * | <webserver ip="">| 80 (HTTP) | * | none | NAT SERVER1 ( Description )
Now when going to adrculda.hopto.org or adrculda.zapto.org gets redirected to my first IIS7 Server.
Now i wonder if my provider offer multiple external IP's :P</webserver></webserver>