Hello all & Happy Friday =)
This is the scenario:
One IIS 6.0 Server is hosting 3 sites, (same private and public IP address for the 3 sites - different port number for each one), all these sites are being protected by an application firewall and everything is up and running just fine.
Now, 3 days ago a 4th site, (again using same private and public IP address, but a different port number), was added to same IIS server using a different port. On the application firewall side we added the proper configuration to handled the traffic for this new site, it was just a matter of create a new tunnel using the same settings we used for the 3 firts sites, and only changing the TCP port number. For some reason we were not able to access the 4th site, after some troubleshooting, we decided to take the application firewall off and direct all production traffic to the IIS Server, without passing it through the app firewall. By doing this access to the 4th site was possible.
We cannot think of anything that might be blocking the traffic for the 4th site on the application firewall side, as this was a pretty straightforward configuration and even more the fact that the access to the first 3 sites was running without any problems. We also contacted the Radware team and their opinion is the same.
With this in mind, is there any configuration that we might be missing at IIS level that is causing this? or at network level?
As a reference, here is the list of sites URLs, (real address was replaced by x - the port number is the real one):
https://xxxx.xxxx.com/ - port 443 - Protected by App Firewall - Access OK
http://xxxx.xxxx.com:8090/ - port 8090 - Protected by App Firewall - Access OK
http://xxxx.xxxx.com:8082/ - port 8082 - Protected by App Firewall - Access NO
Thanks for your assistance.
María Eugenia Rivera
