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