Computing.Net > Forums > Networking > Linksys wrt54G not forwarding port

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Linksys wrt54G not forwarding port

Reply to Message Icon

Name: Vitus13
Date: October 31, 2007 at 15:09:27 Pacific
OS: Dell
CPU/Ram: 2.8 GHz 1.0GB Ram
Product: E310
Comment:

Here is my setup:

PC -----------------Router----------Internet
(192.168.1.10) (192.168.1.1)
PC---------------------/
(192.168.1.11)
subnet 255.255.255.0

problem:
192.168.1.10 is running Apache 2.2.6(newest version). However the webpage cannot be accessed from any other computer inside or outside the network.
the page can be accessed by 192.168.1.10, 127.0.0.1,localhost (from 192.168.1.10) but not from anywhere else.

Pings only work from PC to router, not Pc to Pc.

I have already forwarded port 80 to 192.168.1.10. I also tried moving it to 55555 among other various ports, no avail.

All help is appreciated



Sponsored Link
Ads by Google

Response Number 1
Name: StuartS
Date: October 31, 2007 at 15:42:50 Pacific
Reply:

Depending on how you configured Apache when you installed it it could be listening on port 8080. Have you tried that.

Look at the Apache configuration file and you should find a line:

Listen 192.168.1.10:xx

xx being the port it is listening on and the IP address of the computer it is installed on.

Stuart


0

Response Number 2
Name: Vitus13
Date: October 31, 2007 at 17:05:51 Pacific
Reply:

In my Apache file I have the following two lines

listen 55555
servername X.Y.Z.W:55555
(X.Y.Z.W is the outside IP for the Router)


0

Response Number 3
Name: StuartS
Date: October 31, 2007 at 17:40:53 Pacific
Reply:

Change x.y.z.w to the IP address of the computer Apache is running on.

When it is behind a router Apache knows nothing of public IP address, only private addresses.

In fact if you leave out server name and Apache will deduce it for itself but by putting in a specific IP address you are overriding that capability.

In my configuration I have which works:

ServerName saturn.MYOB:8080
Listen 192.168.2.4:8080

saturn is the computer name. MYOB is the workgroup name and 192.168.2.4 is the computers IP address. There is no mention of a public IP address anywhere. As it is likely to change every time the router re-boots which would mean reconfiguring Apache. This doesn't happen as all the work is done in the router.

Stuart


0

Response Number 4
Name: Vitus13
Date: October 31, 2007 at 19:10:05 Pacific
Reply:

Updated listen & servername commands to read:

Listen 192.168.1.10:55555
servername vitus.4699UPSTAIRS:55555

I can connect to the webserve by typing 192.168.1.10:55555 on 192.168.1.10 however I still cannot connect to 192.168.1.10 from 192.168.1.11 even though I made sure they are on the same workgroup and they recognize each other

as for outside the network testing, I have to wait to see if I can access it from an outside location tomorrow


0

Response Number 5
Name: StuartS
Date: November 1, 2007 at 04:19:52 Pacific
Reply:

I have just remembered something regarding Linksys routers. You cannot connect to your own web site using your public IP address from a computer within your own network. A minor inconvenience but something that might look wrong if you are not aware of it. Belkin routers will allow this.

You should still be able to connect from 192.168.1.11 though.

Stuart


0

Related Posts

See More



Response Number 6
Name: prestone683
Date: November 1, 2007 at 05:15:12 Pacific
Reply:

Try the simple and stupid thing first. Find out if you have Windows Firewall installed.
I went through this a couple of weeks ago, I have IIS running on 80, and tried to install a proprietary web server to run on another port, (and it didn't matter which port, just so long as I know), but if you don't specifically turn off, or allow the Windows Firewall its access, you won't see the server. So whatever port you want to see it on, turn off the firewall for that port.

You should be able to at least ping the machine, from another machine, if that works, inter-connectivity is good. Just play with the firewall.

You'll have her running in no time.

-Brian


0

Response Number 7
Name: Vitus13
Date: November 1, 2007 at 14:10:28 Pacific
Reply:

Ok, checked for firewall.

As suspected, I have the firewall turned off, but just to be safe I added a few ports to the allow list, including 80,81, and 55555

results:
no change, 192.168.1.10:55555 -> works
216.15.72.43:55555 -> doesnt work

if anyone wants to try, you can type the above address and see if you get the testpage. You'll know you got it because it will have "Apache Server 2.2.6 is currently Running" pasted across the top in big letters



0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: Linksys wrt54G not forwarding port

Remote desktop Linksys wrt54g setup www.computing.net/answers/networking/remote-desktop-linksys-wrt54g-setup/34744.html

ssh remotely into ubuntu www.computing.net/answers/networking/ssh-remotely-into-ubuntu/32360.html

Linksys WRT54g as accesspoint www.computing.net/answers/networking/linksys-wrt54g-as-accesspoint/35700.html