Server 2012 - External Company website not updating on internal network
I have a customer whose external company website has been upgraded to HTTPS with associated certificate, since this upgrade, if the customer accesses the website on their internal network it warns that the corticate is not valid, the customer then proceeds to access the website. Once on the website the customer noted that it is not updating showing latest changes to the website. If you access the website external to the network it works fine showing the updated changes. The problem seems to be only apparent when accessing the website from the internal network. The customers network is attached to a server 2012 standard with Exchange server 2016 and has a self-certificate. I have tried clearing the cache on the server and flushed the DNS but to no avail. Is this a case of a missing DNS entry to accommodate the upgrade to the server, currently the DNS server has a www A record pointing to the External website IP address.
Is it possible the problem is nothing to do with the 2012 server settings but is caused by the the Web designer when upgrading the website to HTTPs?
Does anyone know what may be causing this problem
Is it possible the problem is nothing to do with the 2012 server settings but is caused by the the Web designer when upgrading the website to HTTPs?
Does anyone know what may be causing this problem
DrDave242
Is the customer's AD domain name the same as their registered (Internet) domain name?
In addition to DrDave's question, Is the server hosted elsewhere or on the company LAN?
ASKER
In answer to DrDave - the AD domain is the same as the registered (Internet domain name)
In answer to Masnrock - if you are talking about the External Web site it is not being hosted elsewhere or on the company LAN.
In answer to Masnrock - if you are talking about the External Web site it is not being hosted elsewhere or on the company LAN.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What does the browser say is invalid about the cert when you're browsing from the inside? Does it show that there's a name mismatch or something like that? (You might have to view the cert itself to find out, depending on how much info the browser actually gives you.)
ASKER
In answer to Masnrock - I have checked with the web designers and they confirm the IP address has nnot changed.
In answer to DrDave - I am having difficulty viewing the certificate to glean any information.
In answer to DrDave - I am having difficulty viewing the certificate to glean any information.
Which browser are you using? And are you able to provide screenshots of what you can see? (Be sure to blur out any sensitive info)
ASKER
In answer to Masnrock - I tested accessing the website using Google chrome omn an internal PC and it presented the certificate error page with the following message:-
"This server could not prove that it is www.Domain.co.uk; its security certificate expired 45 days ago. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Friday, 15 June 2018. Does that look right? If not, you should correct your system's clock and then refresh this page."
I checked and the computers clock was correct, it did not offer me the opportunity to view the certificate.
"This server could not prove that it is www.Domain.co.uk; its security certificate expired 45 days ago. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Friday, 15 June 2018. Does that look right? If not, you should correct your system's clock and then refresh this page."
I checked and the computers clock was correct, it did not offer me the opportunity to view the certificate.
ASKER
The problem has been resolved - I used Tracert to confirm the IP address it came back witha different IP to the one I was told so I rechecked with the web designers and indeed the IP address had been changed. Once I changed the www A record on the Server DNS the website started working correctly.
Glad you were able to get resolved. The fact you mentioned an old version of the site was what prompted me to think the IP was off, whether because of a new account at the same web host or a move to a new hosting provider (the latter being more likely).