Apache accessible from localhost, but not from LAN: Socket error # 10061 Connection refused

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Hi samri,

I can ping from B to A and from A to B.

I didn't do any changes to the configuration file, except two lines for the DocumentRoot.

Listen 80

The bind directive isn't there.

the error that you are getting is from a customized application -- which i am not sure of the behavior.

Please could you test with using a normail web browser, and do http://ipaddressofapache/ or do a "telnet ipaddressofapache 80". If using telnet, you should be getting a blank screen, type in anything, and press enter twice. If there is a problem with connection, you should get "connection refused" error.

Give it a try.

ASKER

I don't know the exact English translation of the error that I get in IE6 because the error page is in Dutch, but it should be something like this:

The page cannot be displayed/found.

At the bottom:

Cannot find the server or DNS error

Each time I do the request, I can very briefly see some network traffic on the apache machine.

ASKER

Oh telnet didn't work either :-(

can you not access using IP, or using hostname?

ASKER

ahoffmann: both.

I also have apache installed on the "remote" machine; i can access it without a problem from my "apache" machine if you see what i mean

_manu_,

So we you can reach apache on machineB from machineA, but not be able to reach apacheA from machineB.

Do you had any chance of try from another machine. (if you could, then maybe something is funny with machineB),

If not, then -- it's heck of a problem (to me).

Could you check if the network setting for both machine A and B is the same .. Ip address got to be different (of course), but check the netmask, gateway.

Also try to do tracert (traceroute) from A -> B and B -> A , and check the hops. I would suspect that there should be no problem since both machine can ping each other.

Do you use proxy setting on machineB. (doesn't make much sense since "telnet machineA 80" does not work at all).

Personally, I would try to reboot, and reinstall Apache, or maybe totally remove it, and do fresh install -- kind harsh suggestion, but knowing windows env, most of the time the problem will just "mysteriously" self-resolved. :)

ASKER

I can't reach apacheA, not from machineB, nor from machineC :-)

so it is heck of a problem to me too

subnet mask and default gateway are the same; ip 192.168.123.120 & 192.168.123.110 ...

it IS a fresh installation on machineA and i've also rebooted it

and no problem with tracert

try a re-reinstallation? :-)

check with:
netstat -pan|grep 80

ahoffmann,

on which machine? A (running apache) or B ?

Okay..

onmachineA (which is running apache), we can confirm that you could do http://127.0.0.1/ or http://localhost/, but could you test http://ipaddress/ <-- which is the ipaddress of network card.

ASKER

http://127.0.0.1, http://localhost/, http://192.168.123.120/ on Apache machine: they all work.

hmm... it's almost 2 in the morning... (it;s hard to think when half of you brain is already in bed :)

> http://127.0.0.1, http://localhost/, http://192.168.123.120/ on Apache machine: they all work.
and not from machineB, then either routing or firewall problem
did you see somthing in error_log when trying to connect from machineB?

ASKER

ahoffmann, machineA does not have a firewall; both machines are connected to a router; and if - on my router - I explicitly allow machineB to connect to machineA on port 80 the page cannot be displayed

there is one other thing that I think of now: machineA is in a domain, machineB isn't (just a workgroup); could it have something to do with this?

ASKER

I don't see anything special in the error_log

can you sniff the network on machineA, ethereal or whatever ...