Clearly, I am a newb. I am in a situation where we have one web server. On that web server I would like to host both internally accessible and public facing website [applications] where the internal applications are only accessible to employees INSIDE our domain.
The public facing websites should be accessible from both inside and out our local network.
Currently, I have all web applications organized under 'Default Website' configured as applications in IIS.
Is there a way to segregate the apps so that the 'internal' apps are blocked from being accessed from the outside?
Should this be done by moving the 'public' websites outside of the 'Default Websites' container in IIS and/or should this be done using ports like :80, :8080, :81, etc...?
Here is a quick outline of how the sites look in IIS right now with tags as to how I want them to be accessed:
Default Web Site >
Web App 1 [Should only be accessible internally]
Web App 2 [Should only be accessible internally]
e Commerce Site 1 [Should be accessible both internally and externally]
e Commerce Site 2 [Should be accessible both internally and externally]
Web App 3 [Should only be accessible internally]
The server has one IP Address and we intend to configure DNS for the Public Facing Site[s].
Thank you for your assistance.