Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm trying to configure port forwarding on my CNet router for a locally hosted HTTP server. The model number of my router is CQR-981 and the firmware version is 1.0.43.

The problem is that there's no field to enter the private port of the HTTP server (the local port). According to the manual there should be one.

Here's a picture of the manual:

As you can see, there's a private port field.

Here's a screenshot of my router page for port forwarding (with no field for private port):

enter image description here

Is there some way I can circumvent this problem. Perhaps manually make an HTTP request to the HTTP server on the router to update the table with the private port number, or perhaps update my firmware to solve this problem.

share|improve this question

migrated from serverfault.com Oct 8 '12 at 1:57

This question came from our site for professional system and network administrators.

    
Your router, at least from this screen, only supports port forwarding where only the destination IP address is changed. –  David Schwartz Oct 2 '12 at 12:08
    
Well my HTTP server is running on port 80 and even when I enter the public port range 80-80 and the correct local IP address to port forward it doesn't work. When I browse to my public IP adress on port 80 it tells me that the connection was closed by the foreign host. –  Aadit M Shah Oct 2 '12 at 12:13
    
It's not going to work for you since you're on the inside. Port forwarding only works from the outside to the inside (you need hairpin NAT to make local outside addresses work from the inside). Also, many routers can't forward port 80 unless you move their web-based GUI to a different port first. –  David Schwartz Oct 2 '12 at 12:13
    
So that means that if I ask a friend of mine to connect to my site then he'll be able to see it, but I won't? –  Aadit M Shah Oct 2 '12 at 12:17
    
If you have things working correctly, yes. Though, again, some routers can't forward the same port their web-based GUI is operating on. But if you moved that to another port, it should work. –  David Schwartz Oct 2 '12 at 12:19
show 2 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.