Member Avatar for Ron_16

I have made the changes to the Apache http.conf file

    AllowOverride All
    Require all granted

    And added the Listen:   192.168.1.20:80
     Save the conf file and restarted Apache

But when I try to start I get the following error message
This site can’t be reached
192.168.1.22 took too long to respond.
Search Google for wordpress
ERR_CONNECTION_TIMED_OUT

My Windows 7 machine is 192.168.1.20
My Windows 10 WAMP64 server is at 192.168.1.22

I can net use back and forth between the systems.
Sounds like a networking situation, just not sure on which machine.

  • 2 Contributors
  • 1 Reply
  • 469 Views
  • 51 Minutes Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

Likely cause: Apache on the WAMP machine was bound to the wrong interface so it never accepted connections directed at the WAMP host. already changed Apache’s config and restarted, but the Listen binding must be either the WAMP host’s IP (the server’s address) or “all interfaces” (e.g., a generic listen on port 80) so the server actually receives requests from other LAN machines. ’s tip to check firewalls is also important—firewall rules often allow file sharing but block HTTP.

Quick verification and useful commands:

# On the WAMP server (cmd):
netstat -aon | findstr :80

# Map any found PID to its process:
tasklist /FI "PID eq 1234"

# From a Windows client (PowerShell):
Test-NetConnection -ComputerName 192.168.1.22 -Port 80

# From a client (if available):
telnet 192.168.1.22 80
curl -v http://192.168.1.22/

Checklist of things to confirm:

  • Apache is actually running and listening on the WAMP host’s interface (not the other PC). Adjust the Listen/VirtualHost settings accordingly and restart Apache.
  • Windows Firewall (and any third-party firewall) allows inbound TCP port 80 for the Apache executable or for the port on the Private network profile. Temporarily disabling the firewall for a quick test will reveal if it’s the blocker.
  • Router/Wi‑Fi settings: ensure client/AP isolation is off so LAN clients can reach each other.
  • No other service (IIS, Skype, etc.) is already occupying port 80; netstat will show conflicts.

Also check WAMP’s “Put Online” behavior and any vhost entries that are bound to localhost only. Back up config files before edits and restart the Apache service after each change.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.