Right now I run 3 services that I expose to the world:
Wake On Lan
I can set these services up as virtual servers on the DIR-655, but if I try to use port forwarding to accomplish the same thing, it doesn't work. For example if I try to set up port forwarding of public port 21 to private port 21 on 192.168.1.202 (my Dlink NAS static ip), it just plain doesn't work.
Why worry if I can get it to work as a virtual server? Because there very well may be cases in the future where I want to forward a range of ports - running a game server or something like that. This is one of those things that will annoy me until I figure out what is going wrong. Does anyone have any ideas as to other settings that might cause port forwarding to fail? Can you think of a way to use logging or wireshark to troubleshoot? So far, I have had no clues in the DIR-655's log. I haven't tried the syslog feature of the router - does that provide more information that the status log?
Here's my network setup behind the DIR-655:
* One desktop on a static IP (not DHCP reservation)
* Two laptops on DHCP
* VOIP box on static IP in the DMZ (not DHCP reservation)
* Dlink NAS on a static IP (not DHCP reservation)
* Old Trendnet router setup as an access point for wireless G traffic - static IP, connection is from LAN port on Trendnet to LAN port on DIR-655.
* The default gateway is the Dlink's IP address 192.168.0.1
* The subnet mask is not the default. It is 255.255.254.0. I have my static IPs on 192.168.1.xxx and the dynamic stuff and router on 192.168.0.xxx.
The dlink DNS server is the openDNS servers rather than the comcast ones - I can't imagine that would make a difference. The Advanced->firewall settings on the DIR-655 are all default.
Help me Obi-Wan Kenobi, you're my only hope