March 9th, 2004, 09:38 AM
Can't access webserver from IP or Domain!
I am experiencing some frustration setting up my own webserver. This a cable connection (w/static ip) going through a LinkSys Cable/DLS router to Apache2+ running under Windows XP Pro. I think it is a DNS or router configuration issue but I can't be sure.
Here is what I have done so far..
I installed Apache and configured it according to the directions. I can see the web server in my browser from "localhost", 127.0.0.1 and 192.168.1.100.
In the router I set the Static IP, Subnet Mask, Default Gateway according to the data sheet given to me by my internet provider.
I have also set the router's DNS1 and DNS2 to my provider's domain name servers. I have internet access (obviously). The Host Name and Domain Name fields are blank.
I have setup UPnP Port Forwarding for HTTP, FTP, SMTP and POP3 to 192.168.1.100 through the router.
I have set up an Edit Zone account with my domain pointing to the Static IP. This account was set up some time ago so it is sure to be active.
I have pointed the domain to the Edit Zone DNS. Again, done some time ago so I know it's active.
I cannot access the server through the static IP or Domain! And I can't figure out why. I thought it might be the DNS within the router, but when I change the DNS1 and DNS2 in the router to Edit Zone's DNS I lose internet access.
The only thing I haven't tried is to point my domains to my provider's DNS servers. But then how do I setup A and CNAME records? I'd much rather use Edit Zone's DNS.
I don't know if problem is too broad to solve on these boards. But please let me know if I'm missing something obvious. Thanks!
March 9th, 2004, 10:56 AM
You gave me everything I needed to know to help except your domain. I need to know your domain in order to diagnose the problem. Also when you say Edit Zone do you mean zoneedit dns hosting service?
Most definately keep DNS1 and DNS2 to the name servers provided by your ISP!!! Most definately do not use those same name servers as the host for your domain!!!
Once you give me your domain I'll work through your domain configuration with you.
March 9th, 2004, 12:17 PM
Thanks. The primary domain is stoneentertainment.com.
At the time I posted the thread, I didn't understand that the DNS provided by my ISP and the DNS assigned to the domain name had to be different. From what I undersatnd now one is for outgoing requests, and the other for incoming requests.
Yes, I did mean Zoneedit.com. Sorry.
I should add that I called the customer service of my provider and the guy I was speaking with said that I may have to setup static local ips on the machines behind my router in order to get port forwarding to work.
He also suggested to run the server on Port 4 (that is the physical port on the router) and Enable DMZ.
However there is no indication that my router has DMZ specifically on Port 4. The control panel provides the ability to assign DMZ to any local ip.
After dealing with customer service and fiddling with the router I can say without a doubt that it is NOT a DNS issue. It is a router configuration issue.
I now have access to the router through the exteral IP and Domain. But it is not port forwarding to the web server. Instead it is attempting to log into the router. I realize that takes us somewhat off topic, but if you have any advice I'd greatly appreciate it.
March 9th, 2004, 12:51 PM
yeah, I've seen that happen before. The guy gave me access to his router and I changed the configuration port to 8080 and disabled internet access to router configuration. So I suggest you find where you can change the router configuration port from 80 to something else like 8080. Then you access your router with a URL like this:
And btw, don't enable DMZ. there's no reason to take away the layer of protection the router firewall gives you.
March 9th, 2004, 02:25 PM
Well I disabled remote administration and set administration port to 8080 (actually was set by default). However I can still access the router from the domain/ip. It is as though the router is port forwarding Port 80 to 192.168.1.1 instead of 192.168.1.100.
Any ideas along those lines?
March 9th, 2004, 02:42 PM
The fix I suggested was so that internet people can reach your webserver. Currently there doesn't appear to be any web service at all at IP address "126.96.36.199". Connection attempts timed out which suggests a router or firewall is in the way or the IP is wrong, or the computer is offline.
As far as internal goes however, there's a good chance you will never be able to connect to your public IP. You must connect to your private IP.
March 9th, 2004, 03:56 PM
I have been fiddling with the connection settings. That probably why the ip wouldn't resolve when you tested it. The ip should be pointing to the router now, as is the domain.
It may also be possible that the issue is with Apache.
March 9th, 2004, 04:07 PM
no, I'm still not getting any love telneting to port 80 on IP 188.8.131.52.
And here's how you can test out apache. connect to your private IP like I suggested.
March 9th, 2004, 04:16 PM
HOLY FROG-ON-A-STICK IT WORKS!!!!!!
I reset my router to factory settings and went through the proceedure step by step. First I set the ip, the gateway, the subnet mask, kept DHCP settings enabled for local ips. Then I enabled UPnP, disabled user access to UPnP (Die Microsoft messenger! DIE!), the set UPnP port forwarding fields for SMTP and HTTP to 192.168.1.100, enabled those fields, clicked Okay and.. Voila! Ha ha!
Don't ask me why it wasn't working before. I had it configured exactly this way. At least I thought I did.
Umm you absolutely certain it's not working? I'd hate to go through the whole 'frog on a stick' spiel and still be stuck in limbo.
March 9th, 2004, 05:35 PM
looks like it works to me.
April 4th, 2004, 11:38 AM
im having a problem related to the above:
i can browse to my page via my ip and the domain (www.switchedonsolutions.net)
i can nslookup, i can ping
im running apache,pop3, and named(dns)
why cant users outside my system browse the page?
April 4th, 2004, 12:38 PM
Your NS information is jewish. You have a NS record for server.switchedonsolutions.net but it has no IP address. This is also not a registered name server.
April 4th, 2004, 08:26 PM
i noticed that as well, so i updated my dns files to reflect my ns as switchedonsolutions.net, it should be
registered ( i registered it with godaddy.com). The problem that just came up was when i removed the smtp block from my cable modem, the isp assigned me another ip, so i had to register the name server again!, as well as change all my configuration files. I dont think the changes have propogated yet...if i email you my named settings could you possibly check them over for me?
April 4th, 2004, 08:48 PM
nah, I'd rather not go blind staring at config files. Just tell me your (new?) IP and I can test your dns configuration. It doesn't need to propagate for me to directly test a dns server.
April 4th, 2004, 09:45 PM