Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[grumser]

I have a new DIR-826L that replaced my old linksys wrt54g and I would like to port forward my web server so that I can access it from outside my LAN. However, the port forwarding doesn't seem to be working.

The server has a static ip address on localnet and I set up the router to port forward all port 80 connections to that address. It didn't work, the server is accessible from inside the LAN but isn't accessible from outside. The server's firewall does not register any blocked connections which makes sense because it was working before.

Interestingly, when the router is set to port forward port 80, canyouseeme.org says that it can see the open port while when the router isn't set to port forward port 80, it says that it cannot see the port.

I have a Comcast cable connection.

[FurryNutz]

Have you tried using Virtual Server?

Link>What Firmware version is currently loaded? Found on routers web page under status.
What region are you located?
Are you wired or wireless connected to the router?

What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Double NAT
To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.

Some things to try: - Log into the routers web page at 192.168.0.1.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking.

[grumser]

Thank you for the quick response,

I have tried using virtual server. It didn't work in exactly the same way as port forwarding didn't work.

Firmware version: 1.00
I considered changing to 1.01 (the only other version) but I read your post saying not to upgrade unless you have one of the problems that the release notes say the new version fixes.

The computer in question is wired to the router and it already has a reserved DHCP IP address.

My ISP is Comcast cable.

The modem is standalone and does not perform router functions.

Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.

I was unable to find the settings mentioned in the quote, but I tried all of the other suggestions with no observed effect.


I am pretty sure that there is no problem with the modem as a previous router successfully forwarded connections when placed in the same part of the network.

[FurryNutz]

How about setting up a QoS rule for this one PC and see if that helps get things connected?
Check out the Gaming and Gamefuel for XBL.. Even though it's for XBL, there is examples of setting up PCs for use.

[grumser]

I set up the QOS rule but it didn't seem to have any effect.

I also port scanned my WAN address and the scan said that ports 80 and 443 were filtered and ports 7777 and 49152 were open.

It says that port 80 is filtered when I am not trying to forward port 80 connections to the server.

That isn't to say that setting up port forwarding rules has no effect: I can set a rule for port 22 and the port scan says that port 22 is filtered although I am still unable to ssh to it from outside the LAN.

[FurryNutz]

Try setting the local and remote ports to 0 to 65535 and protocol to both or Any and see. Be sure you are using the port or actively using it or you'll get a false negative.

[FurryNutz]

Might need to start over:  
http://forums.dlink.com/index.php?topic=2659.0

Have you tried to put the Web Server PC in to the DMZ on the router?

[grumser]

You may need to do a port forwarding rule so as to use a different port than 80.  Port 80 is by default the router's internal web pages and may not let port 80 to be re-directed to the IP address for this web server.

I tried using the virtual server to set the external port to 20000 while leaving the internal port at 80. The connection still didn't go through. I don't think that that is the main problem because ssh connections on port 22 also do not go through even though the router doesn't use that port.

Try setting the local and remote ports to 0 to 65535 and protocol to both or Any and see. Be sure you are using the port or actively using it or you'll get a false negative.

I tried this but it didn't seem to do anything. Same for putting the computer on the DMZ. Still no signs of it receiving any sort of external connection.

[FurryNutz]

The only thing I guess we can try is the FW update if you want too.

I would follow the FW Update Process. I would set up the router from scratch, just one PC, the Web server and reconfigure VS first  or PF and see. I believe VS should work or PF should. Is there a external URL address that you have have me see if I connect? Can PM me the address if there is one.

[grumser]

Success!

The server works perfectly after the firmware upgrade. I only needed to set up port forwarding rules.

Thank you very much for your help.

[FurryNutz]

Awesome. Save the routers configuration to file. Enjoy.