After moving the website to a new host, our internal systems cannot see the site
We're having some issues getting to our website from inside the network. The website host crashed this past week. We moved our website server to a new host. I changed the IP in the DNS area, but it still won't connect. The site works fine from outside of our network. The domain is the same internally as externally. companyname.net so when I go to ping www.companyname.net it shows the updated IP internally but for some reason the site isn't coming up. The old site isn't either. The site refused to connect is what I see.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have seen that it does. When I type in https://www.companydomain.net it comes back https://companydomain.net
ASKER
Do I just need them to change that?
If the host will remove that redirect, everything should be back in working order, since you've already updated the internal "www" host record in DNS. Your internal users will need to include the www in the URL when browsing the website, but I'm assuming they're already doing this.
If you get stumped, publish your actual site URL + likely anyone can test + tell you how to fix all problems.
ASKER
There is a utility on the server. XAMPP an Apache webserver utility.
The old engineer used this to redirect the website because he setup the internal domain as the external one.
The old engineer used this to redirect the website because he setup the internal domain as the external one.
I'm admittedly not an Apache guru at all, but now I'm a little confused. Is this website hosted on one of your servers, or is it run by a third-party web host?
ASKER
Its run by a third party. But the Apache has to be used internally to redirect I guess. Just found the utility.
Is that utility installed on one or more of your domain controllers?
If ISP cannot change it you can do a NETSH v4tov4 rule on all your DCs
Check the port like 80 and 443 to your host is accessible from your network.
you can use telnet IP 80
telnet IP 443
you can use telnet IP 80
telnet IP 443
ASKER
They made a change on the hosting end that allowed the site to keep the https://www.companywebsite.net instead of https://companywebsite.net
Now, the only issue seems to be that 1/2 of the graphics don't work internally.
There are images which are missing from the banner from the inside of the network but from the outside they come up fine.
I think that for now, the issue seems to be resolved as to it not coming up at all. The site is hosted by a third party Dr. Dave.
The old IT admin made the mistake of hosting the active directory with the same domain name as the website is using.
Now, the only issue seems to be that 1/2 of the graphics don't work internally.
There are images which are missing from the banner from the inside of the network but from the outside they come up fine.
I think that for now, the issue seems to be resolved as to it not coming up at all. The site is hosted by a third party Dr. Dave.
The old IT admin made the mistake of hosting the active directory with the same domain name as the website is using.
ASKER
Thank you all for your attention to this. We were able to get the site back up with the help of your feedback and through consistent communication with the new hosting entity.
The issue was a configuration on the hosting end.
The issue now is that the internal staff don't see the website graphics like images in the banner that should scroll by. It is just blank internally. But most likely that is a configuration of the site on the back end, pointing to the wrong location or somewhere the internal hosts can see.... I'll dive into that endeavour next.
The issue was a configuration on the hosting end.
The issue now is that the internal staff don't see the website graphics like images in the banner that should scroll by. It is just blank internally. But most likely that is a configuration of the site on the back end, pointing to the wrong location or somewhere the internal hosts can see.... I'll dive into that endeavour next.
Your internal domain is probably the same. When you go to www.domain.com it works because your A record for www has correct IP. When the website redirects www.domain.com to just domain.com, internally it doesn't work because domain.com points to your DCs.
Tough to guess. Easy to test + know for sure.