Member Avatar for akshayinbox

Hello.

My PC (Windows 7) on which WAMP Server (PHP + mySQL + Apache) is installed is connected to a WiFi router which is further connected to a DSL Modem (for broadband access).

I've fully functional WAMP that I can access via 127.0.0.1 , localhost, (IP assigned by my WiFi router).

Now, the address of Control Panel of my WiFi router is (accessible via web-browsers of all devices connected to WiFi router).
- However, when a device connected to same Wifi router navigates to , WAMP Page doesn't show up! but instead "request timed out" or "No Response" (on mobile) is shown.

- Also, before when my PC was connected to Internet via a 3G USB Modem, My external IP when accessed via anywhere on globe showed WAMP's page, but, now it shows my DSL Router's Admin Panel at (which is understandable).
I tried setting up port forwarding, but doesn't work....Like i tried redirecting or to but it doesn't work!

I need to make my wamp site at accessible both LOCALLY (WLAN/WiFi) and GLOBALLY (Internet).

Any help is appreciated!

Thank you! :)

  • 3 Contributors
  • 3 Replies
  • 315 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by c-tech

Dani AI

Generated

Quick diagnostic checklist (building on 's tip and 's request for clarity) — focus on three places: Apache itself, the PC firewall, and the router/modem chain. Typical causes are Apache bound to localhost, Apache access rules that only allow local requests, Windows firewall or AV blocking incoming connections, wireless “client isolation” on the AP, or a double‑NAT (modem + router) that stops external forwarding.

Check Apache + Windows quickly

  • Confirm Apache is listening on all interfaces (not only 127.0.0.1):
netstat -ano | findstr ":80"

Look for a LISTENING line on 0.0.0.0:80 or [::]:80. If you only see 127.0.0.1:80, change the Listen directive in Apache's httpd.conf to Listen 80 (or Listen 0.0.0.0:80) and restart Apache. For access control, if using Apache 2.4 ensure the site Directory allows LAN access:

<Directory "C:/wamp/www/">
    AllowOverride All
    Require all granted
</Directory>

If still using Apache 2.2, use the equivalent Allow from all approach. Then add a Windows firewall rule (run as admin):

netsh advfirewall firewall add rule name="Apache" dir=in action=allow protocol=TCP localport=80

Router/topology items many guides miss

  • Disable any “AP/Client Isolation” or “Guest network” that prevents Wi‑Fi clients talking to each other.
  • Check for double NAT: compare the router’s WAN IP to the public IP reported by an external lookup. If the WAN IP is private (e.g., 192.168.x.x, 10.x.x.x or 100.64.x.x), the upstream modem is NATing too. Solutions: put the modem in bridge mode, move the Wi‑Fi device to AP mode, or forward the port on both boxes (external -> modem -> Wi‑Fi router -> server). Also watch for “remote admin” on port 80 (router admin exposed) — change or disable it.

Testing & safety

  • Test external access from outside your LAN (mobile with Wi‑Fi off) — many routers don’t support loopback. Use curl -I http://PUBLIC.IP[:PORT]/ from outside to verify.
  • If exposing WAMP to the Internet, secure phpMyAdmin, use strong passwords, consider HTTP auth or a VPN, and move admin interfaces off port 80.

These steps cover the common gaps not yet mentioned in the thread: Apache binding/Require directives, AP isolation, NAT loopback/double‑NAT and router admin conflicts.

Recommended Answers

All 3 Replies

Member Avatar for akshayinbox

You can also see my previous thread at
(Got no answers yet :( )

Member Avatar for jingda

State your problem more clearer, i can't understand

Member Avatar for c-tech

Hi akshayinbox,

To start off from the really simple before heading on to the complicated, when you right click on the WAMP icon on the taskbar there is the option for put online, have you enabled this option already? This needs to be done so that the the WAMP services can be accessed on your host's I.P not only localhost.
If you have already done this, then kindly check to see whether there is translation or rules(on the wifi router and Windows firewall) that might be preventing access to port 80 on your server. You could also try changing your Apache webserver port to something like 8080 and allowing it on your Windows Firewall.


Goodluck.

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.