from the outside and the inside and see if the IP address of your web server is the same. If it's different, then find out which DNS server is being used. There's probably a record on the DNS server that points to an internal IP address that's no longer valid.
~Sovereign
Okay, so my employer had a website that was created eons ago through various free/opensource products. We had the webserver onsite, prior to my time here, and as it started to become less reliable, I was asked to create a new site that would be hosted offsite.
New site has been created, domain has been pointed to it, it works very well with one little exception--you can't view it from our LAN. Outside of our network, it works beautifully.
My background is less in Networking, and more in GIS/spatial analysis, but that makes me the "tech guy" in our organization and I'm getting hammered over this. I've got the broad overview of the networking thing, but I'm far from an expert. I think the problem lies in our firewall, a Cisco ASA 5505. I think it was set up so that computers in our LAN would be routed directly to our old web server, rather than going out and back in to it.
I'm not sure how this was accomplished though, and I'm hoping some of you guys might have some suggestions as to how you would have done it (and how to undo it). From the research I've done, the easiest way to 'hairpin' it would be to configure the device to "enable traffic b/w two or more hosts connected to the same interface." This hasn't been done though, so I'm looking for other options. Any ideas or suggestions?

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic