September 11th, 2003, 10:36 PM
I just started running a web server. poeple can access my site by going to http://www.theouternet.net. but i can't. i can go to http://localhost and see it. but i can't go to http://localhost/folder_name/filename.html and see the file. whats going on and what can i do to fix it? i have a SMC router. hooked up to 3 computers.
September 11th, 2003, 10:46 PM
I can't go to http://www.theouternet.net as for the router, e-mail SMC with the model name / etc and the problem and they will reply, hopefully.
September 11th, 2003, 11:30 PM
Your DNS info:
The DNS info looks like it is pointing at a companies name servers and not your own. Also, have you opened up the correct ports on the router? 80 for web 53 for DNS?
WHOIS information for theouternet.net:
Registration Service Provided By: RegisterFly.com
Domain name: theouternet.net
Created: 04/14/03 00:00:00
Expires: 04/14/04 00:00:00
N00b> STFU i r teh 1337 (english: You must be mistaken, good sir or madam. I believe myself to be quite a good player. On an unrelated matter, I also apparently enjoy math.)
September 12th, 2003, 02:18 AM
He doesn't have his own name server. He uses the default one for his registar. I don't have a name server for UnError I just use zoneedit. It wouldn't matter what name servers his domain points it, rather what A Names they point to in the name server. :-)
PS. I know about all his DNS ****, becasue he's my cousin', heh.
September 12th, 2003, 05:46 AM
This could be a NAT/PAT and or routing issue...Is your web server ona DMZ witha public address or is it on your private LAN with RFC 1918 address.. and if the latter is your setup, are you natting statically one to one to your webserver or are you performing whats referred to as port forwarding??
September 12th, 2003, 12:39 PM
I've had the same problem. It's because www.theouternet.net resolves to your outside address. Since you are accessing it from the inside packets need to travel through your router, get natted and need to travel back in. This will probably freak out the NAT state tables.
I solved this by running a DNS server on the inside and created an identical dns domain. The only difference was the inside DNS server resolved my site to the internal adres.
Edit: another solution just dawned on me. You could also set your browser to an external proxy. That way the proxy will connect back to you.
Experience is something you don't get until just after you need it.
September 12th, 2003, 10:59 PM
If i got my own connection, without going through a router, would that solve all my problems