Unable to connect to Apache over LAN

I have installed Apache, MySQL and PHP on RedHat 7.1 running on a Dell Latitude laptop, as described in Israel Denis's "Soothingly Seamless" tutorial.

I want to access this 'testbench' Apache, etc., from my Mac design workstation over a small LAN, but can't get a connection open.

All IP addresses are defined statically, since for the moment I have only 2-3 workstations running at a time.

From the Dell, Apache, etc., works fine using localhost/127.0.0.1. I get the default display page just fine.

From the Mac, I can PING the IP address of my Dell's Ethernet port, but when I try to connect to Apache (using the IP address directly), I get a Connection Error. It locates the address but cannot connect.

My Questions:
------------------
Where should I be looking for the problem: Apache configuration, Linux network configuration?, Mac configuration? Any suggestions?

So close, and yet so far...

FYI: This is my first Linux installation.

Thanks,

W Bentley

Tell Apache to use like 192.168.0.1, not 127.0.0.1. And take advantage of /etc/hosts file, C:\windows\hosts for win9x or C:\windows\system32\drivers\etc\hosts for winnt/2k/xp

Start here -> http://httpd.apache.org/docs/mod/core.html#servername

Thanks for the reply.

Nope. I tried it with the IP of its Ethernet connector. Still doesn't connect.

The browser goes through the "Looking for..." stage, then hangs on "Connecting to...".

Any other ideas?

(I want to get it working with IP address before I set up host names.)

Thanks for the reply.

Nope. I tried it with the IP of its Ethernet connector. Still doesn't connect.

The browser goes through the "Looking for..." stage, then hangs on "Connecting to...".

Any other ideas?

(I want to get it working with IP address before I set up host names.)

Launch a DOS prompt on windows, type telnet 192.168.0.1 80. If you get connection refused or something, there must be a firewall in between or your Apache simply is not up and running. If it's up and running and connected through, you would get a blank screen, no error, no nothing.

Tried telnetting again, but I get "Host or gateway not responding".

Apache is definitely running and accessible from the Linux machine using 127.0.0.1.

If there's a firewall, it was installed automatically or accidentally (!), not explicitly by me. How would I look for that?

[I tried stopping and disabling ipchains (using Webmin) and nothing changed... same problem.]

BTW, if this is moving outside the scope of this forum, please let me know.

Any more ideas? Thanks in advance for any further help.

>> Apache is definitely running and accessible from the Linux machine using 127.0.0.1

So it's up and running. Make sure it's listening to port 80.

>> Tried telnetting again, but I get "Host or gateway not responding"

So there is a firewall in between. As I said, if you telnet from windows to linux, you should get nothing at all, just a blank white screen.

Sorry I don't use Linux, ipchains or webmin whatever. Maybe you should try http://www.linuxnewbie.org/cgi-bin/.../ultimatebb.cgi

Thanks. It helps to know you think it's not an Apache setting. I'll try there.

Have you tried checking out the Networking-HOWTO? I had a problem with routing the other day and reading through that overview reminded me of a few things I could try to resolve the problem...

try 'rpm -qa | grep howto -i' at the command line to find out if you have the HOWTO's installed - if you do it'll tell you so and then you can use 'locate HOWTO' to find the directory they're installed to (doing 'updatedb' first if you haven't already!). Do these things as root is easiest...


Sounds like a network connectivity issue though if you can connect to the webserver locally. First step is to make sure you can ping (or telnet port 80 as above, but ping's easier;\) the linux box from the windows box - open a dos box and do 'ping 192.168.0.1'.

By sounds of it you can't do this yet, which suggests the IP address isn't assigned correctly to the adapter.

A few things to try then on command-line:

'ifconfig eth0' (presuming eth0 is your lan adapter;\) - check to see that the IP address is assigned correctly to the adapter (192.168.0.1 or whatever private address you assigned).

'route' - check the routing table to see if you have an entry including 'default' and 'gw' on same line - can mess things up by trying to send everything somewhere you don't want...

'ipchains -L' (I think - and unless it's another firewall you might be using;\) - if you see no chains listed (rather all empty chains), firewall's not problem, similarly if you get 'command not found' of course...


Above all though, read all the HOWTO's! Also in Red Hat I think 'netconf' could be useful...

Good luck

Problem solved. It's the default route entry, I think.

I wish it was something more esoteric, but that's usually how it is...

In fact, I had looked at many of the message boards and read through a dozen HOWTO's, but somehow that paragraph in networking slipped by.

Thanks, everyone. Really.

yeah dude... that bit battered my head too once about default routes...

nice one
;\)

what did you guys just say in the meantime? I mean how did this thing work out all of a sudden? what is "default route" ? how can one fix this problem?

i have the same thing (connectiong thru LAN) and i wanna solve it too .. (with your help)

P L E A S E ...

peter

read above.