HTTPS does not work internally but works externally after a new website is launched

My client just launched a new website to replace the old one. Externally the website works fine. We had to change the DNS entries on the server for it to work internally. However, HTTPS still does not work internally. Everything else does. I'm assuming I have to make some changes to get HTTPS to point to the correct IP. But I can't find anything on how to do so. Any help is appreciated!
Thanks!
swinger22Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jan SpringerCommented:
The certificate is tied to the host name.

1) has the host name of the secure web server changed (www.domain.com)?
2) is any firewall blocking TCP port 443 to that IP?
0
swinger22Author Commented:
The host name of the secure webserver has not changed, only the IP has. I can't find anything that indicates that port 443 is blocked to the new IP.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gikkelCommented:
Are you connecting to https://[i]servername.domainname[/i].[b]local[/b]/exchange when connecting internally?  Can you connect to companyweb?  
0
Jan SpringerCommented:
If the web site was moved internally behind the same firewall that you sit, you may be running into a hairpin problem (traffic going out and coming back in the same public firewall interface).

Find out if your firewall supports DNS doctoring.  Some firewalls will allow that configuration option to provide the internal IP address of the web server instead of the external (public) IP.

If that's not an option, perhaps the firewall can be configured to allow hairpin traffic.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.