asked on
Moved website to a new host - can't access it internally on our network
Our company has a Small Business Server 2003. We redesigned our company website and moved it to a new host. The new website is up and can be accessed from outside the office but cannot be accessed on our internal network. I have flushed the DNS on both workstations and the server (ipconfig /flushdns) and I have gone into administrative tools on the server and cleared the cache. When I type in our company website in my webbrowser I get the message "Forbidden. You don't have permission to access / on this server. Apache/2.2.11 (Unix) PHP/5.2.14 mod_fastcgi/2.4.6 mod_ssl/2.2.11 OpenSSL/0.9.7e-p1 Server at oolong.cloud9.net Port 80" Cloud9 is our old host so it appears that our sever still thinks our website is at cloud9 and not at the new host. Is there somewhere else I can look on the server to change this setting so that it points to the new host?
NetworkingMicrosoft IIS Web ServerDNS
Last Comment
tadmor
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
also restart your router
It certainly sounds like you may have static records for this website in dns. Also, check any Stub Zones you have and check the Host File on the Server that may have static entries, c:\windows\system32\driver
Yes, definitely an internal DNS issue. Depending on how long this network has been around and upgraded, over and over, you may want to look in the WINS, LMHOSTS and HOSTS tables along with internal DNS redirection. I still see a lot od networks running LMHOSTS and WINS to support cross-subnets for older workstations (NT4 & 2000) .. WINS is your local Windows Server intranet "DNS" system, if it is running.
It can be that your DNS forwards the requests to an external DNS which has not updated yet the record. Usually it can take up to 24 hours for a DNS server to get the old record out of its cache and get the new record.
ASKER
I'm looking at all these possible solutions....the new website was moved last week so any updates to the DNS, I think, would have been made by now...I didn't include the detail in my initial question.
That would be for external DNS ....NOT internal DNS
ASKER
Could it be an entry on our Netscreen Firewall?
Yes possible check fw rules
ASKER
Thanks for everyone's comments...I tried each one of them as they all could have contributed to the problem. What ended up working was I used the DNS snap-in under Administrative Tools on the server. I clicked the server icon just below the DNS icon and clicked "Forwarders" - the DNS tables were pointing to the old internet service provider…I updated those with our new internet service provider’s DNS ip address. I also checked the TCP/IP properties of the network adapter and updated the DNS tcp/ip addresses there too. It’s been 3 days now and it seems to have worked. Thank you, I couldn't have figured this out without your guidance...pointing me in the right direction.