I have a small network (DC=SBS 2008, Web server=W2K w/IIS & SQL Server 2000) that I'd like to add a 2nd Windows 2008 Server w/IIS 7 to. The initial IIS install (ServerA.domain.com) has an app that we''ll need to run for another 6-8 months, along with our company's public website. The app is accessed by offsite employees through IIS.
The new 2008 server (ServerB.domain.com) has an app for employees-only access, with 99% of them offsite.
To run both web servers concurrently, I had planned to add a non-standard port for serverB.
I have a Sonicwall TZ170 firewall that I have set for all http, port 80 traffic to go to serverA.domain.com's IP address. I created a rule on the Sonicwall for http, port 8081 traffic to go to serverB.domain.com.
I set the binding on server B's default site to port 8081 and restarted IIS 7.
Here's where it comes unglued: The second I change the binding on serverB from 80 to anything else, I cannot access serverB's site (www.domain.com:8081 or, internally, serverB.domain.com:8081).
I am looking for help on fixing this problem and I'm open to alternative ideas on accomplishing the same task.