We've had an intranet for several years and have always accessed it by doing //ServerName. We wanted to access the intranet externally so I tried to add an SSL certificate to it last week. I first expanded the site so it would use SSL/port 443. I purchased the SSL from GoDaddy and installed it. In IIS I added a binding for port 443. I also changed the host file to add the new intranet name that we will use externally. We didn't have anything in the host file so I also added the IP address for the local server name as well as the external IP and name. I assumed I had more work to do before it would work externally, but figured our site would continue to work internally the same. We can't access it.
I have not done anything with DNS yet -because my intranet name I used for the SSL is not part of our domain name I wasn't sure if I created a new zone or added a name record or? I'm not sure if I need to change anything on the DNS side to fix the internal issue right now? I do know that even if I try that new intranet name that also doesn't work internally.
If I type the server name like I always did the site prompts for the login/password, but it will next come up. It prompts 3 times and then comes up with a blank page. I found that if I type the IP address instead, it will prompt me for the login and it will display after hitting ok twice on the login screen. But every time I go to a new page it prompts me again.
I need to first fix the intranet so it is working internally the way it always did. Once that is done I need to know my next steps for getting it working externally - but I'll submit another case on that. What do I need to do to fix the internal side??