Viewing IP addresses behind router
#1
Viewing IP addresses behind router
This problem isn't really a big deal, but just want to know how to fix it. I have a web server on one of my machines, ip address is say 192.168.0.8. All port 80 traffic is set to be forwarded by router to this address. Works great, except when i type the complete name of the website in when i am on my network, i get the config page for the router/modem. So i when i am using another computer on my network i have to type 192.168.0.8 for it to work. Outside of the network the site works fine. Any idea how to tell to router to forward to 192.168.0.2 and not display setup screen, but still be able to access set up screen when I type in say 192.168.0.5?
#3
Yes, DNS works fine. For some reason when I request the site from behind the router it goes out to the DNS server and then comes back and the router looks and finds that it came from "it" and it’s destination is “it” so directs it to the config page. But will forward all port 80 requests that originated from the "outside" Let me know if this is not how it works, it is just my understanding.
#4
edit: definitely ALL port 80 traffic, or just incoming?
still sounds a little goofed up. give these tests a try... it may reveal what's going on.
1) ping a known, public IP address like 4.2.2.4 (a big DNS server) - fails, network issue; works, goto 2
2) ping its name (vnsc-pri-dsl.genuity.net) - fails, DNS issue; works, goto 3
3) ping IP of a known, public www server like google (66.102.7.104) - fails, possible routing issue; works, goto 4
4) ping google by name (www.google.com) - fails, possible routing issue per 3; works, goto 5
5) try to http-access google via its IP (http://66.102.7.104) - fails, possible router blockage of port 80; works, goto 6
6) http-access google via URL - fails, possible cache corruption (flush and retry), hosts redirect, etc; works, go be happy.
you might also try a tracert to 4.2.2.4 to see just where it goes. i'd expect a couple hops in your net, then right out to your ISP and beyond. too bad there's no portwise ping.
still sounds a little goofed up. give these tests a try... it may reveal what's going on.
1) ping a known, public IP address like 4.2.2.4 (a big DNS server) - fails, network issue; works, goto 2
2) ping its name (vnsc-pri-dsl.genuity.net) - fails, DNS issue; works, goto 3
3) ping IP of a known, public www server like google (66.102.7.104) - fails, possible routing issue; works, goto 4
4) ping google by name (www.google.com) - fails, possible routing issue per 3; works, goto 5
5) try to http-access google via its IP (http://66.102.7.104) - fails, possible router blockage of port 80; works, goto 6
6) http-access google via URL - fails, possible cache corruption (flush and retry), hosts redirect, etc; works, go be happy.
you might also try a tracert to 4.2.2.4 to see just where it goes. i'd expect a couple hops in your net, then right out to your ISP and beyond. too bad there's no portwise ping.
Last edited by photoleif; Feb 16, 2006 at 11:32 PM.
#5
Originally Posted by photoleif
edit: definitely ALL port 80 traffic, or just incoming?
still sounds a little goofed up. give these tests a try... it may reveal what's going on.
1) ping a known, public IP address like 4.2.2.4 (a big DNS server) - fails, network issue; works, goto 2
2) ping its name (vnsc-pri-dsl.genuity.net) - fails, DNS issue; works, goto 3
3) ping IP of a known, public www server like google (66.102.7.104) - fails, possible routing issue; works, goto 4
4) ping google by name (www.google.com) - fails, possible routing issue per 3; works, goto 5
5) try to http-access google via its IP (http://66.102.7.104) - fails, possible router blockage of port 80; works, goto 6
6) http-access google via URL - fails, possible cache corruption (flush and retry), hosts redirect, etc; works, go be happy.
you might also try a tracert to 4.2.2.4 to see just where it goes. i'd expect a couple hops in your net, then right out to your ISP and beyond. too bad there's no portwise ping.
still sounds a little goofed up. give these tests a try... it may reveal what's going on.
1) ping a known, public IP address like 4.2.2.4 (a big DNS server) - fails, network issue; works, goto 2
2) ping its name (vnsc-pri-dsl.genuity.net) - fails, DNS issue; works, goto 3
3) ping IP of a known, public www server like google (66.102.7.104) - fails, possible routing issue; works, goto 4
4) ping google by name (www.google.com) - fails, possible routing issue per 3; works, goto 5
5) try to http-access google via its IP (http://66.102.7.104) - fails, possible router blockage of port 80; works, goto 6
6) http-access google via URL - fails, possible cache corruption (flush and retry), hosts redirect, etc; works, go be happy.
you might also try a tracert to 4.2.2.4 to see just where it goes. i'd expect a couple hops in your net, then right out to your ISP and beyond. too bad there's no portwise ping.
All steps ping right through, and all my other internet works great, i only get the config page when i type the ip address of the modem/router or when i type my website or even if i enter it in the form of it's ip address... like 259.188... so on. But if i enter the ip address of the machine hosting apache like 192.168.4 then the site comes right up. Site always works great when accessing it from anyware but behind my router.
#6
OH. so let me see if i understand. if you try to access your *own* website (which is served off your machine), then that's when you get the router config page. other URLs from that machine *do* work ok? in that case, i think it could well be a DNS vs. cache vs. hosts kind of issue. remember the cycle of name resolution... and if your website has a public IP address, you'll need to try using that to test, too. if you hit it via its private IP then who knows what may happen. what do you get if you ping your URL? (not so much does it work, but rather which IP shows)?
#7
dont know if this will help or not but a great website is http://www.network-tools.com/ when you load the page it will show your internet IP address in the box as default.
it might be your router.. i dont have a webserver going, but playing around with my 2 computer networked on my wireless router. the only time i could get the router setup page is when i type 192.168.0.1, if i typed 192.168.0.100 it took me to this computer which i have muliple hard drives shared acting as a file server type thing. and 192.168.0.101 took me to my laptop. if i type 192.168.0.x (where x != 1,100, 101) it just sat there
it might be your router.. i dont have a webserver going, but playing around with my 2 computer networked on my wireless router. the only time i could get the router setup page is when i type 192.168.0.1, if i typed 192.168.0.100 it took me to this computer which i have muliple hard drives shared acting as a file server type thing. and 192.168.0.101 took me to my laptop. if i type 192.168.0.x (where x != 1,100, 101) it just sat there
Last edited by ToferUOP; Feb 17, 2006 at 01:31 PM.
Trending Topics
#8
Some routers have something called remote configuration (managment) make sure thats not enabled on your router sounds like your hitting it when you use your outside address (WAN IP) from the inside. Just something to check.
Last edited by WT; Feb 17, 2006 at 06:44 PM.
#9
Remote management is off, but that is exactly what is happening, when i enter my WAN IP address from inside, whether in the form of the actual IP address or on the form of the website address which get's translated into IP. i get a config page. If i ping my WAN IP address it responds fine, and if i ping the machine address it also responds fine.
#10
From your alias and other threads, can I/we assume that this is happening from a linux machine?
If not (ie, you're running Windows), then what happens after you clear your local DNS cache? (from a prompt type: ipconfig /flushdns).
And then, in either case, is it possible that you have a hosts file entry that's superceeding the actual IP resolution? (windows: \windows\system32\drivers\etc\hosts)
What router are you using? Any chance that yoou have it configured for server forwarding versus port forwarding?
If not (ie, you're running Windows), then what happens after you clear your local DNS cache? (from a prompt type: ipconfig /flushdns).
And then, in either case, is it possible that you have a hosts file entry that's superceeding the actual IP resolution? (windows: \windows\system32\drivers\etc\hosts)
What router are you using? Any chance that yoou have it configured for server forwarding versus port forwarding?
Last edited by midiwall; Feb 19, 2006 at 12:18 AM.
#11
From your alias and other threads, can I/we assume that this is happening from a linux machine?
If not (ie, you're running Windows), then what happens after you clear your local DNS cache? (from a prompt type: ipconfig /flushdns).
And then, in either case, is it possible that you have a hosts file entry that's superceeding the actual IP resolution? (windows: \windows\system32\drivers\etc\hosts)
What router are you using? Any chance that yoou have it configured for server forwarding versus port forwarding?
If not (ie, you're running Windows), then what happens after you clear your local DNS cache? (from a prompt type: ipconfig /flushdns).
And then, in either case, is it possible that you have a hosts file entry that's superceeding the actual IP resolution? (windows: \windows\system32\drivers\etc\hosts)
What router are you using? Any chance that yoou have it configured for server forwarding versus port forwarding?
When i posted this thread it was on a linux server, but i am takeing iis classes now and i have to use server 2003, so it is now hosted on server 2003.
Still the same problem tho. I have kind of been able to get around it by editing the host file on the other machines on my network so when i type in the www.blahblah.com address it will redirect to the internial network address of the server. But if anybody has any ideas let me know.
Edit: my site is not blahblah.com!
Last edited by linuxrunner; Feb 26, 2007 at 09:24 AM.
Thread
Thread Starter
Forum
Replies
Last Post
PNW94Runner
86-95 Trucks & 4Runners
3
Sep 29, 2015 02:55 PM
PureTacoma_Tundra
PureTacoma_Tundra
0
Sep 24, 2015 12:14 PM
mordell
95.5-2004 Tacomas & 96-2002 4Runners
4
Sep 12, 2015 10:13 AM





