/etc/hosts contains: 127.0.0.1 localhost 192.168.1.2 steve2.com steve2 apache is set to listen on all IP's My computer name is steve2.com I can ping all four of the above internally. http://127.0.0.1 works (it shows me my webpage) None of the others will give me my webpage. I want to be able to type the same address internally as I do externally in Internet whilst developing my site especially when copying links. Can anyone help me? Thanks
Am Dienstag, 8. August 2006 20:01 schrieb Primm:
/etc/hosts contains:
127.0.0.1 localhost 192.168.1.2 steve2.com steve2
apache is set to listen on all IP's
My computer name is steve2.com
I can ping all four of the above internally.
http://127.0.0.1 works (it shows me my webpage) None of the others will give me my webpage.
I want to be able to type the same address internally as I do externally in Internet whilst developing my site especially when copying links.
Can anyone help me?
Thanks
can you ping to steve2.com? have you checked /etc/host.conf? -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch
Primm wrote:
/etc/hosts contains:
127.0.0.1 localhost 192.168.1.2 steve2.com steve2
apache is set to listen on all IP's
My computer name is steve2.com
I can ping all four of the above internally.
http://127.0.0.1 works (it shows me my webpage) None of the others will give me my webpage.
I want to be able to type the same address internally as I do externally in Internet whilst developing my site especially when copying links.
Can anyone help me?
Please verify that apache is listening indeed on the desired ports: What does "netstat -antp | grep ':80'" say? If that shows Apache listening on 0.0.0.0 or at least on localhost and ip address then shut down the firewall and test again. If you can connect then modify the firewall settings to allow access to http port. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Tuesday 08 August 2006 21:08, Sandy Drobic wrote:
Primm wrote:
/etc/hosts contains:
127.0.0.1 localhost 192.168.1.2 steve2.com steve2
apache is set to listen on all IP's
My computer name is steve2.com
I can ping all four of the above internally.
http://127.0.0.1 works (it shows me my webpage) None of the others will give me my webpage.
I want to be able to type the same address internally as I do externally in Internet whilst developing my site especially when copying links.
Can anyone help me?
Please verify that apache is listening indeed on the desired ports: What does "netstat -antp | grep ':80'" say?I get this with or without the firewall.
Hi. I get this with or without the firewall: netstat -antp | grep ':80' tcp 0 0 :::80 :::* LISTEN 21883/httpd2-prefor tcp 0 0 192.168.1.2:80 64.148.188.113:32024 ESTABLISHED 23799/httpd2-prefor tcp 0 0 192.168.1.2:80 64.148.188.113:32025 ESTABLISHED 24093/httpd2-prefor tcp 0 579 192.168.1.2:80 72.192.172.160:3063 ESTABLISHED 23730/httpd2-prefor tcp 0 9714 192.168.1.2:80 4.157.5.253:1243 ESTABLISHED 23779/httpd2-prefor tcp 0 0 192.168.1.2:80 4.157.5.253:1236 TIME_WAIT - tcp 0 0 192.168.1.2:80 86.143.60.236:3566 FIN_WAIT2 - tcp 0 285 192.168.1.2:80 72.192.172.160:3064 ESTABLISHED 24091/httpd2-prefor I can now connect on 127.0.0.1 and via localhost but not via 192.168.1.2 nor the computer name. Any ideas?
Primm wrote:
Please verify that apache is listening indeed on the desired ports: What does "netstat -antp | grep ':80'" say?I get this with or without the firewall.
Hi. I get this with or without the firewall:
netstat -antp | grep ':80' tcp 0 0 :::80 :::* LISTEN 21883/httpd2-prefor tcp 0 0 192.168.1.2:80 64.148.188.113:32024 ESTABLISHED 23799/httpd2-prefor
This seems to say that a client with the ip 64.148.188.113 has established a connection.
tcp 0 0 192.168.1.2:80 64.148.188.113:32025 ESTABLISHED 24093/httpd2-prefor tcp 0 579 192.168.1.2:80 72.192.172.160:3063 ESTABLISHED 23730/httpd2-prefor tcp 0 9714 192.168.1.2:80 4.157.5.253:1243 ESTABLISHED 23779/httpd2-prefor tcp 0 0 192.168.1.2:80 4.157.5.253:1236 TIME_WAIT - tcp 0 0 192.168.1.2:80 86.143.60.236:3566 FIN_WAIT2 - tcp 0 285 192.168.1.2:80 72.192.172.160:3064 ESTABLISHED 24091/httpd2-prefor
Other clients can obviously also connect from the internet.
I can now connect on 127.0.0.1 and via localhost but not via 192.168.1.2 nor the computer name.
If you have a network connection between your apache server and your client, then you should be able to connect. How did you test the connection exactly? What is written in the apache log at that time? Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Tuesday 08 August 2006 22:34, Sandy Drobic wrote:
Primm wrote:
Please verify that apache is listening indeed on the desired ports: What does "netstat -antp | grep ':80'" say?I get this with or without the
firewall.
Hi. I get this with or without the firewall:
netstat -antp | grep ':80' tcp 0 0 :::80 :::* LISTEN 21883/httpd2-prefor tcp 0 0 192.168.1.2:80 64.148.188.113:32024 ESTABLISHED 23799/httpd2-prefor
This seems to say that a client with the ip 64.148.188.113 has established a connection.
tcp 0 0 192.168.1.2:80 64.148.188.113:32025 ESTABLISHED 24093/httpd2-prefor tcp 0 579 192.168.1.2:80 72.192.172.160:3063 ESTABLISHED 23730/httpd2-prefor tcp 0 9714 192.168.1.2:80 4.157.5.253:1243 ESTABLISHED 23779/httpd2-prefor tcp 0 0 192.168.1.2:80 4.157.5.253:1236 TIME_WAIT - tcp 0 0 192.168.1.2:80 86.143.60.236:3566 FIN_WAIT2 - tcp 0 285 192.168.1.2:80 72.192.172.160:3064 ESTABLISHED 24091/httpd2-prefor
Other clients can obviously also connect from the internet.
I can now connect on 127.0.0.1 and via localhost but not via 192.168.1.2 nor the computer name.
If you have a network connection between your apache server and your client, then you should be able to connect. How did you test the connection exactly?
I typed http://localhost into knoqueror and firefox. Neither will connect. Then I typed http://127.0.0.1 into the same browsers and it connected. I and everyone else can connect just fine from the Internet. It's the internal connection that's failing.
What is written in the apache log at that time?
THis sort of stuff: "http://127.0.0.1/news.php" "Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko)" 127.0.0.1 - - [08/Aug/2006:15:12:05 +0200] "GET /e107_themes/khatru/images/wblogo.png HTTP/1.1" 404 1176 "http://127.0.0.1/news.php" "Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko)" 127.0.0.1 - - [08/Aug/2006:15:12:05 +0200] "GET /e107_images/newspost_images/newsabstractth.jpg HTTP/1.1" 304 - "http://127.0.0.1/news.php" "Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko)"
Sandy
THanks for your effort. Steve.
Primm wrote:
On Tuesday 08 August 2006 22:34, Sandy Drobic wrote:
tcp 0 285 192.168.1.2:80 72.192.172.160:3064 ESTABLISHED 24091/httpd2-prefor Other clients can obviously also connect from the internet.
I can now connect on 127.0.0.1 and via localhost but not via 192.168.1.2 nor the computer name. If you have a network connection between your apache server and your client, then you should be able to connect. How did you test the connection exactly?
I typed http://localhost into knoqueror and firefox. Neither will connect. Then I typed http://127.0.0.1 into the same browsers and it connected.
That was on the server itself?
I and everyone else can connect just fine from the Internet. It's the internal connection that's failing.
internal client ip (192.168.1.30) internal server ip (192.168.1.2) So, on client you start Firefox and type http://192.168.1.2 into the address field? That should work if network connectivity is established and no firewall prevents it. Can you actually successfully ping the internal server ip from your client? Can you ping the server name?
What is written in the apache log at that time?
THis sort of stuff:
"http://127.0.0.1/news.php" "Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko)"
Looks okay. That is without name resolution. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Tuesday 08 August 2006 22:59, Sandy Drobic wrote:
Primm wrote:
On Tuesday 08 August 2006 22:34, Sandy Drobic wrote:
tcp 0 285 192.168.1.2:80 72.192.172.160:3064 ESTABLISHED 24091/httpd2-prefor
Other clients can obviously also connect from the internet.
I can now connect on 127.0.0.1 and via localhost but not via 192.168.1.2 nor the computer name.
If you have a network connection between your apache server and your client, then you should be able to connect. How did you test the connection exactly?
I typed http://localhost into knoqueror and firefox. Neither will connect. Then I typed http://127.0.0.1 into the same browsers and it connected.
That was on the server itself?
Yes.
I and everyone else can connect just fine from the Internet. It's the internal connection that's failing.
internal client ip (192.168.1.30) internal server ip (192.168.1.2)
The client and server are the same IP 192.168.1.2. I have no 192.168.1.30 address
So, on client you start Firefox and type http://192.168.1.2 into the address field?
Yes.
That should work if network connectivity is established and no firewall prevents it.
No It doesn't. 192.168.1.2 gives me a blank screen
Can you actually successfully ping the internal server ip from your client?
Yes. I can ping 127.0.0.1, localhost, 192.168.1.2 and the server name.
Can you ping the server name?
Yes.
What is written in the apache log at that time?
THis sort of stuff:
"http://127.0.0.1/news.php" "Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko)"
Looks okay. That is without name resolution.
Sandy
-- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
Primm wrote:
I and everyone else can connect just fine from the Internet. It's the internal connection that's failing. internal client ip (192.168.1.30) internal server ip (192.168.1.2)
The client and server are the same IP 192.168.1.2. I have no 192.168.1.30 address
If the client and the server are different machines you NEED different ip addresses within the same subnet to be able to connect. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Tuesday 08 August 2006 23:15, you wrote:
Primm wrote:
I and everyone else can connect just fine from the Internet. It's the internal connection that's failing.
internal client ip (192.168.1.30) internal server ip (192.168.1.2)
The client and server are the same IP 192.168.1.2. I have no 192.168.1.30 address
If the client and the server are different machines you NEED different ip addresses within the same subnet to be able to connect.
Sandy
Hi. I have only one machine. The server on 192.168.1.2. I just ant to be able to access my website via the name of the server just as I can from the Internet. I can access it fine externally from Internet. I just can't access it from the server, internally.
Primm wrote:
On Tuesday 08 August 2006 23:15, you wrote:
Primm wrote:
I and everyone else can connect just fine from the Internet. It's the internal connection that's failing. internal client ip (192.168.1.30) internal server ip (192.168.1.2) The client and server are the same IP 192.168.1.2. I have no 192.168.1.30 address If the client and the server are different machines you NEED different ip addresses within the same subnet to be able to connect.
Hi. I have only one machine. The server on 192.168.1.2. I just ant to be able to access my website via the name of the server just as I can from the Internet. I can access it fine externally from Internet. I just can't access it from the server, internally.
Did you enter the correct name in /etc/hosts? /etc/hosts: 127.0.0.1 localhost 192.168.1.2 servername.example.com servername That should enable you on the local machine to use the address http://servername.example.com Sandy PS: Sorry, I sent the previous mail also to your private address. -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Tuesday 08 August 2006 23:31, Sandy Drobic wrote:
Primm wrote:
On Tuesday 08 August 2006 23:15, you wrote:
Primm wrote:
I and everyone else can connect just fine from the Internet. It's the internal connection that's failing.
internal client ip (192.168.1.30) internal server ip (192.168.1.2)
The client and server are the same IP 192.168.1.2. I have no 192.168.1.30 address
If the client and the server are different machines you NEED different ip addresses within the same subnet to be able to connect.
Hi. I have only one machine. The server on 192.168.1.2. I just ant to be able to access my website via the name of the server just as I can from the Internet. I can access it fine externally from Internet. I just can't access it from the server, internally.
Did you enter the correct name in /etc/hosts?
/etc/hosts: 127.0.0.1 localhost 192.168.1.2 servername.example.com servername
That should enable you on the local machine to use the address http://servername.example.com
Yes. I have that entered. The ONLY one which works is 127.0.0.1
Sandy
PS: Sorry, I sent the previous mail also to your private address.
No problem. Thanks for helping.
Primm wrote:
I have only one machine. The server on 192.168.1.2. I just ant to be able to access my website via the name of the server just as I can from the Internet. I can access it fine externally from Internet. I just can't access it from the server, internally. Did you enter the correct name in /etc/hosts?
/etc/hosts: 127.0.0.1 localhost 192.168.1.2 servername.example.com servername
That should enable you on the local machine to use the address http://servername.example.com
Yes. I have that entered. The ONLY one which works is 127.0.0.1
Sandy
And you are absolutely sure that the firewall is NOT running? iptables -L /sbin/SuSEfirewall2 status Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Wednesday 09 August 2006 00:07, Sandy Drobic wrote:
Primm wrote:
I have only one machine. The server on 192.168.1.2. I just ant to be able to access my website via the name of the server just as I can from the Internet. I can access it fine externally from Internet. I just can't access it from the server, internally.
Did you enter the correct name in /etc/hosts?
/etc/hosts: 127.0.0.1 localhost 192.168.1.2 servername.example.com servername
That should enable you on the local machine to use the address http://servername.example.com
Yes. I have that entered. The ONLY one which works is 127.0.0.1
Sandy
And you are absolutely sure that the firewall is NOT running?
iptables -L /sbin/SuSEfirewall2 status
SuSEfirewall2 status SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. SuSEfirewall2: SuSEfirewall2 not active I've tried it with and without. When it's running I have port 80 open assigned to external zone.
Primm wrote:
On Wednesday 09 August 2006 00:07, Sandy Drobic wrote:
Primm wrote:
I have only one machine. The server on 192.168.1.2. I just ant to be able to access my website via the name of the server just as I can from the Internet. I can access it fine externally from Internet. I just can't access it from the server, internally. Did you enter the correct name in /etc/hosts?
/etc/hosts: 127.0.0.1 localhost 192.168.1.2 servername.example.com servername
That should enable you on the local machine to use the address http://servername.example.com Yes. I have that entered. The ONLY one which works is 127.0.0.1
Sandy And you are absolutely sure that the firewall is NOT running?
iptables -L /sbin/SuSEfirewall2 status
SuSEfirewall2 status SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. SuSEfirewall2: SuSEfirewall2 not active
I've tried it with and without. When it's running I have port 80 open assigned to external zone.
Sigh, for today, I am out of ideas. Though it did happen to me also that there were rules left behind when the firewall was startet on boot and later stopped. Just for curiosity, could you deactivate the starting of the three firewall services and then reboot? That should definitely remove any kind of firewall rules. chkconfig SuSEfirewall2_final off chkconfig SuSEfirewall2_init off chkconfig SuSEfirewall2_setup off reboot I assume you only have one network interface? Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
Sigh, for today, I am out of ideas. Though it did happen to me also that there were rules left behind when the firewall was startet on boot and later stopped. Just for curiosity, could you deactivate the starting of the three firewall services and then reboot? That should definitely remove any kind of firewall rules.
chkconfig SuSEfirewall2_final off chkconfig SuSEfirewall2_init off chkconfig SuSEfirewall2_setup off reboot
Sandy. I can now see the webpage internally. Brilliant work! But I couldn't then see it from Internet. I re setup the firewall with Yast and opened HTTP server and did rcSuSEfirewall2 start and it worked both internally and externally. I can't thank you enough for your help. Steve.
Primm wrote:
Sigh, for today, I am out of ideas. Though it did happen to me also that there were rules left behind when the firewall was startet on boot and later stopped. Just for curiosity, could you deactivate the starting of the three firewall services and then reboot? That should definitely remove any kind of firewall rules.
chkconfig SuSEfirewall2_final off chkconfig SuSEfirewall2_init off chkconfig SuSEfirewall2_setup off reboot
Sandy. I can now see the webpage internally. Brilliant work! But I couldn't then see it from Internet. I re setup the firewall with Yast and opened HTTP server and did rcSuSEfirewall2 start and it worked both internally and externally. I can't thank you enough for your help.
Glad to hear that you could solve your problem. (^-^) Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
participants (3)
-
Daniel Bauer -
Primm -
Sandy Drobic