Here are a few thoughts on setting up resources on your network.
Configuration notes
It looks like you have a router, so your router is tied to an external IP address, not to your computer. In this case, your computer does not have an external IP (75.75.75.75). It has only internal IP (10.0.0.6). You must configure the router to forward port 80 to the internal IP address of your computer. You must also bind IIS to the internal IP address.
I should note that, given your screenshots above, you are already close to already doing this. The only thing I will remove from your configuration above is the IIS binding to the external IP (75.75.75.75).
Testing
When testing your site, a potential problem is with the router itself. Typically, the router does not allow the machine internal access to an internal resource (for example, IIS) through an external IP. So, for example, if you try to browse from your network to 75.75.75.75, the router will not allow this to happen. Perhaps this is why you see the browser freeze. What you must do to test a website is to access an external IP address outside of your network. Ask a friend or relative (outside your network) to try connecting to an external IP address and see if it works.
So, how should you access the site from your network? Use only the internal address (10.0.0.6).
source share