Hi I have a Dlink 614+ on a DSL line. Everything works fine except that port forwarding (port 80) will not work. My neighbor (using the same DSL provider) has a linux box doing NAT and his web server works fine from the outside, so it isn't the ISP. I'm using the latest firmware, 2.33 and I can ping the box from the internet (from a different line). A port scanner shows the port to be closed even though it is setup correctly. It used to work until I unplugged the Dlink for about an hour. Now it doesn't do port forwarding. Any ideas on getting it working? Thanks!

Not to be rude but, if it were setup properly, the scanner would show port 80 as being open and you would connect to your web page. I have a dlink DI-604 and while there are likely differences, I'm betting the configuration interface is very similar. If I were going to setup a web server on a LAN PC I would have two choices as to how to configure this in the router. Either through the 1) Virtual Server, or 2) through the DMZ. As for option 2, I don't really recommend it as it leaves the whole unit exposed. Find the Virtual Server setup on your router config (mines on the Advanced Tab under 'Virtual Server'). I wager there's already a preset for the HTTP (port 80). Just select it, enable it and give it the IP address (LAN IP that is) of the web server and it should work.

Yeah, that's what I've been trying to get it to work. Dlink seems to have problems with functions like these. I contacted their support with that initial message and they said I would have to call because I'd already tried everything. The thing did work at one point, then suddenly gave up the ghost.

Do you know if your ISP blocks that port ? By default, port 80 is blocked by my ISP - but the blocking can be disabled if needed (perhaps your neighbour has disabled the port blocking). You might want to chat to your ISP's tech support just in case.

As I said, my next door neighbor is running a server on the same ISP using a Linux NAT box to forward port 80 and it works fine. I've eliminated everything possible. The problem has to be a bug in the Dlink firmware. I may try downgrading / upgrading the firmware and a hard reset and see what that does.

My reply is based on the configuration of Cisco equipment so hopefully my lack of knowledge in the DLink space isn't a concern. Cisco configuration settings are saved to/in a binary file and loaded up when the device is booted up. Other vendor devices likely work in the same manner which leads to my idea that you're config file is corrupt. Assuming for a moment this is true, you may might want to recreate that file with the required settings and test the functionality. The corruption, if any, may be the result of your unplugging the device as stated in your original post? Pinging the device is good but if port scanning indicates port 80 being closed then something altered your settings.

I had to change the protocol on port 80 to both.. not just tcp... works now