port forwarding on linksys WRT54G

November 11, 2011 at 13:25:38
Specs: Windows 7

Port forwarding on my linksys is not seem to be working from outside the network. It works fine if I try on the same network.

External ip address: 69.117.132.xxx
Ports from 8080 through 8080 forwarded
Internal ip address: 192.168.1.150 - static ip address assigned to the webserver.

I understand 80 could be blocked by the ISP. Can 8080 also be the same case?

Let me know how best to troubleshoot this issue.

Thank you for the help.


See More: port forwarding on linksys WRT54G

Report •


#1
November 12, 2011 at 07:03:51

Ports from 8080 through 8080 forwarded. <---That's wrong.
The rule should be from ANY to 8080. Source ports are not the same as destination ports. Source ports are random in both Windows & Unix.

You could put 192.168.1.150 in the DMZ as a test. Then port forwarding wouldn't be needed. Right now I don't see anything on that external subnet in the DMZ.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
November 12, 2011 at 11:10:46

@guapo

What you are talking about is a firewall rule, where you allow connection from the internet to you network.

Port from 8080 through 8080 forward is correct !!!

You simply forward one port, in this case 8080 on the public ip address to one port in this case also port 8080, to a private ip address.


Report •

#3
November 12, 2011 at 13:04:16

Then why didn't it work if you say it's correct? I see nothing on that class C subnet that is listening on port 8080.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
November 12, 2011 at 13:12:02

Maybe because there is no service, listening to port 8080.

So you first have to configure the webserver, to listen to port 8080.
Otherwise, you can do port address translation (PAT) at the router, so that you forward the public port 8080 to the privat port 80 on the webservers private ip address.


Report •

#5
November 12, 2011 at 14:11:48

He said that he had the web server configured on his internal IP of 192.168.1.150 A default configuration would be port 80.

Then he said he used the port forwarding rule of Port from 8080 through 8080, which you said was correct, on the external subnet 69.117.132.xxx but it's not working.

His web server isn't listing on port 80 nor 8080. I checked that already.

I guess we have to wait until the OP returns.

How do you know when a politician is lying? His mouth is moving.


Report •

#6
November 12, 2011 at 15:48:32

The OP asked, whether his ISP may also block port 8080.

And yes, we have to wait for the OPs reply.


Report •

#7
November 12, 2011 at 16:53:59

The port on 8080 is listening fine. I am able to browse it using 192.168.1.150:8080. I am also able to browse it using 69.117.132.xxx:8080 when I am on the local network. Desktop, laptop etc.

When I try to connect it from an external computer over the internet, then 69.117.132.xxx:8080 is not reachable.

On the linksys router configuration, under application & gaming->port range forward,
I have port range start of 8080, end of 8080, protocol 'both' and ip address is 192.168.1.150.

Not sure what else could be wrong...


Report •

#8
November 12, 2011 at 17:30:48

aravindk wrote:

"When I try to connect it from an external computer over the internet, then 69.117.132.xxx:8080 is not reachable."

That's ^^ the most important statement in the post.

Please try my suggestion, that you change the port forwarding rule to From ANY port to port 8080.

There is also another possibility. If you are using a domain name & not an IP address from outside your LAN, to use dyndns.

As I said before, there is no IP address in that external subnet that shows port 8080 opened. Make sure that DHCP hasn't changed your IP since you started your web server & check your configuration. Are you using apache or IIS server software?

How do you know when a politician is lying? His mouth is moving.


Report •

#9
November 12, 2011 at 17:51:46

i changed it to 0 to 8080 for forwarding. I dont have ANY option. My linksys configuration screen looks like this:

http://portforward.com/english/rout...

This is not IIS or apache. It is a custom controller which monitors my fishtank while i am away. (i know i am crazy...).

The controller is just fine. The dhcp on the controller is disabled and it has a static ip address of 192.168.1.150. The webserver itself works just fine since I am able to load it while on the network.

The problem is with the forwarding of the port i guess.


Report •

#10
November 12, 2011 at 17:55:25

I also have dyndns configured. First I want to be able to test the ip address with port #. I also confirmed my internet ip address using whatismyip.com. So I know it is not changed.

Report •

#11
November 12, 2011 at 18:21:38

Open the web interface of the router again. Go to advanced & port forwarding rules. Set it there.

Edit: Now that I think about it, if it's not IIS or apache, I don't know if you can expect anything else.

How do you know when a politician is lying? His mouth is moving.


Report •

#12
November 13, 2011 at 08:21:32

it looks like 8080 was indeed blocked by my isp. I tried 8081 and it went through fine.

thanks for all your help guys


Report •


Ask Question