Network problem, cannot access own site with url
Don't know what or when I did it, but I am no longer able to access my own web side via name or ip addr, only localhost or 127.0.0.1. I am on cable modem to router to eth0. host wahoo.no-ip.org 24.208.208.146 host 24.208.208.146 146.208.208.24.in-addr.arpa domain name pointer cpe-24-208-208-146.indy.res.rr.com /etc/resolv.conf search indy.rr.com nameserver 192.168.0.1 -router addr wahoo:~ # ifconfig eth0 Link encap:Ethernet HWaddr xx:xx::xx:xx:xx:xx inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14178998 errors:469 dropped:1282 overruns:469 frame:0 TX packets:14017960 errors:0 dropped:0 overruns:4 carrier:0 collisions:0 RX bytes:2999405714 (2860.4 Mb) TX bytes:1535720624 (1464.5 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:6072004 errors:0 dropped:0 overruns:0 frame:0 TX packets:6072004 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 RX bytes:2709506459 (2583.9 Mb) TX bytes:2709506459 (2583.9 Mb) What has changed or what did I change that I do not know about? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Monday 05 September 2005 6:33 pm, Patrick Shanahan wrote:
Don't know what or when I did it, but I am no longer able to access my own web side via name or ip addr, only localhost or 127.0.0.1.
I can access fine. Did you change anything on the router? Since it shows up externally, it would seem to be something related to your internal network. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.8-default x86_64 SuSE Linux 9.3 (x86-64)
* Scott Leighton <helphand@pacbell.net> [09-05-05 20:50]:
I can access fine.
Yes, I can ssh to a friends box and access it remotely.
Did you change anything on the router? Since it shows up externally, it would seem to be something related to your internal network.
No, I haven't even accessed the router administratively for over a year. No troubles there, but I will check anyway. WAN Port : IP Address : 24.208.208.146 DHCP : Client IP Subnet Mask : 255.255.248.0 LAN Port : IP Address : 192.168.0.1 DHCP : Server IP Subnet Mask : 255.255.255.0 open ports for ssh, smtp, and www-http I don't see anything different ??? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
* Patrick Shanahan <ptilopteri@gmail.com> [09-05-05 21:02]:
open ports for ssh, smtp, and www-http
I don't see anything different ???
One thing that I have noticed recently. It seems that the /etc/hosts file is no longer used. Have I done something to disable it and not realized? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Patrick, On Monday 05 September 2005 19:04, Patrick Shanahan wrote:
...
One thing that I have noticed recently. It seems that the /etc/hosts file is no longer used. Have I done something to disable it and not realized?
Did you modify /etc/resolv.conf? If it does not mention /etc/hosts, then that file will not be consulted. (Mine does not, but since I've never used it, I did not miss it.)
Patrick Shanahan
Randall Schulz
* Randall R Schulz <rschulz@sonic.net> [09-05-05 21:24]:
Did you modify /etc/resolv.conf?
yes, on several occasions
If it does not mention /etc/hosts, then that file will not be consulted. (Mine does not, but since I've never used it, I did not miss it.)
I didn't know that. /etc/hosts is *not* mentioned, but it's also not in the original /etc/resolv.conf ??? nor the man-page ??? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Monday 05 September 2005 7:33 pm, Patrick Shanahan wrote:
* Randall R Schulz <rschulz@sonic.net> [09-05-05 21:24]:
Did you modify /etc/resolv.conf?
yes, on several occasions
If it does not mention /etc/hosts, then that file will not be consulted. (Mine does not, but since I've never used it, I did not miss it.)
I didn't know that. /etc/hosts is *not* mentioned, but it's also not in the original /etc/resolv.conf ??? nor the man-page ???
Mine doesn't mention it either, I'm no expert but I don't think that's the problem. I can access my own site using dyndns.org and it's not in /etc/hosts I know my brother cannot access his own web cams from the external internet facing address, his router does something funky that doesn't allow it. He always has to use the internal ip. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.8-default x86_64 SuSE Linux 9.3 (x86-64)
On Monday 05 September 2005 9:33 pm, Patrick Shanahan wrote:
Don't know what or when I did it, but I am no longer able to access my own web side via name or ip addr, only localhost or 127.0.0.1.
host wahoo.no-ip.org 24.208.208.146
host 24.208.208.146 146.208.208.24.in-addr.arpa domain name pointer cpe-24-208-208-146.indy.res.rr.com
/etc/resolv.conf search indy.rr.com nameserver 192.168.0.1 -router addr I was going to ask a few questions, but I was able to access your system successfully (to the point where I was able to connect to your host using telnet to 25 and 80. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
participants (4)
-
Jerry Feldman -
Patrick Shanahan -
Randall R Schulz -
Scott Leighton