472,129 Members | 1,696 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,129 software developers and data experts.

LAMP on a local network

Hi

I'm new to all this and I am trying to set up a web sever over a local
network. I currently have two boxes attached via a switch. Box 1 is
configured with windowsXP and the other with Fedora3.

The linux box has Apache installed and appears to be running ok. When I use
IE to access the site I get the response : "Page cannot be displayed" or
"The web page you requested is not available offline" depending what is
entered in the address control.

On the Linux box, if I use the command netstat -atn, this shows a host
192.168.123.10 listening on port 80

In the terminal window on the XP box, (192.168.123.12) when I ping
192.168.13.10 I get a successful response. If I telnet 192.168.123.10 80 I
get "could not open connection to the host on port 80:connect failed"

Does anybody have any suggestions /commands that will help me resolve this.

Also does anyone have a link to a good article recommending a development
set-up that includes the physical configuration as well as development tools
for a first timer.
Jul 17 '05 #1
1 1758
Geoff Blake wrote:
Hi

I'm new to all this and I am trying to set up a web sever over a local
network. I currently have two boxes attached via a switch. Box 1 is
configured with windowsXP and the other with Fedora3.
<snip>
On the Linux box, if I use the command netstat -atn, this shows a host
192.168.123.10 listening on port 80

In the terminal window on the XP box, (192.168.123.12) when I ping
192.168.13.10 I get a successful response. If I telnet 192.168.123.10 80
I get "could not open connection to the host on port 80:connect failed"

<snip>

Not a PHP question.

If it's listening but you can't connect then probably the connections are
being dropped by the firewall. Try running a web browser on the FC3 box
(IIRC RH comes with links as standard which will run in a terminal
session).
Alternatively, you could try (as root):
iptables -F
this will remove all the rules from the firewall.

Obviousl;y you'll want to have a working firewall but this should allow you
to confirm where the problem is.

HTH

C.
Jul 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Geoff Blake | last post: by
10 posts views Thread by Zabby | last post: by
reply views Thread by Rahsaan Page | last post: by
39 posts views Thread by Gilles Ganault | last post: by
9 posts views Thread by sid | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.