|
I used the port checker tool from http://portforward.com to make sure port 80 ATP and UDP was open and then I installed Apache server to listen on port 80. When I use the port open tool from http://dyndns.com the port times out. I have reconfigured the TTL to 800 instead of the default 60 and still timing out. At this point I don't think anyone can see my website. I haven't confirmed it yet because I don't know anyone else with a computer. The website is at http://www.pridellc.org. The only thing I can think of that would cause this is that Apache is misconfigured but I've tried everything I can think of. The instructions on how to use Apache with dyndns is ambiguous. I can see my website with localhost but I don't think anyone else can. |
|
Do a nslookup http://www.pridellc.org. or a dig http://www.pridellc.org to ensure that you get your IP address returned (currently 67.235.168.229). And yes, I can confirm that I cannot reach your site via port 80. Btw, you would need only TCP, not UDP, for HTTP. And also TTL is of no relevance here, this is only related to DNS caching. Please work through this wiki to possibly find a solution for your problem. For example, your ISP may be blocking port 80, or your router may not forward this correctly, so try another port number, e.g. 8080. If you got it sorted out, please report back how. Regarding your Apache configuration, see in httpd.conf if you have any IP address or port restrictions introduced with the Listen directive. That still doesn't explain why the port open tool is timing out even when Apache is off.
Feb 26 at 12:29 AM
pridellc
I've turned UDP off, I just turned it on tomake sure the port open tool wasn't using UDP but evidently it works the connection is timing out, now I just have to figure out why.
Feb 26 at 12:49 AM
pridellc
I read that post and many others before making this post.
Feb 26 at 12:51 AM
pridellc
DNS server handling your query: localhost DNS server's address: 127.0.0.1#53 Non-authoritative answer: Name: http://pridellc.org Address: 67.235.168.229 I'm not sure what the 127.0.0.1#53 means.
Feb 26 at 12:56 AM
pridellc
The listen directive is set to default; Listen 80
Feb 26 at 07:10 AM
pridellc
|
|
Your problem could be because your router doesn't correctly forward it's administration port. Try configuring Apache to also listen on 11080 and forward 11080 to the Apache server. Then try http://www.pridellc.org:11080/. Also, if your router can't do port translation, i.e. 11080 to 80, you had to change your httpd.conf to get Apache listen on port 11080 instead of default port 80. Regarding "I'm not sure what the 127.0.0.1#53 means": This means that the DNS server 127.0.0.1 (localhost) has handled the lookup. As it says, "DNS server handling your query: localhost DNS server's address: 127.0.0.1#53". DNS lookups are normally UDP through port 53.
Feb 26 at 05:24 PM
RotBlitz ♦
I figured it out. The XP firewall added an exception for the Apache Monitor but didn't specify a port. After adding an exception for Apache port 80 it seems to work. Still doesn't explain why it wouldn't work with the firewall down though.
Feb 26 at 06:13 PM
pridellc
Thanks for everyones help
Feb 26 at 06:14 PM
pridellc
|
The OP hasn't returned to the thread in over a month, closing to stop the forum bot bumping this thread.