I am trying to help a client with a website setup by an employee who no longer works there. The site is on an internal "server" running WAMP. They used a free dns redirect to point a domain name to the company's public static IP. It's been working like a champ for years. (The free dns service was everydns.net, which was acquired by dyndns.org. They sent notices by email that no-one saw b/c employee was gone. Now Dyndns controls the dns for the domain and we can't contact them in any way because we don't have a paid account)
SO... I used another domain name and created "intranet.newdomain.com" and had the hosting company point web requests to the public IP. (the router is properly set up to forward port 80)
-The site (a front end for a database) is accessible from the LAN
side using "domain-intranet.com" because we have manually entered that name into host files on the local PCs.
-"domain-intranet.com" points to 192.168.2.2 in the hosts file.
-but if I enter "192.168.2.2" or "http://192.168.2.2
" in a web browser on a local PC I get this WAMP configuration type of page. (I'll attach a picture)
-I also get that "WAMP page" when I use the new "intranet.newdomain.com" OR when I use the public IP address. (I've tried to add port 80 ":80" to the end of the ip address also.
So, to sum up, I know the site is running because it's accessible from the LAN side using the hosts file and old domain name. But if I use the new domain from the WAN side, or WAN IP from outside or LAN IP from inside, it doesn't work.