Hello Carlo (italia?

)
i've your "same" problem...i'm running the 1.31EUB02 firmware on my 655 and i'm trying to connect from the outside of the network using dyndns (that works for me!there is a "little bug" when you try to insert the info in the router, you have to, before writing your dyndns account, choose "dyndns" in the first listbox, save the settings and then write in the form the account info. After that obviously re-save and see on the bottom of the page if the router has syncronized with the dyndns server....), open the right port in the port forwarding, open the port locally in the windows client (of course even enabling the "allow remote desktop connection") and try the connection...BUT nothing happens, i mean the rdp call get error that cannot find the remote machine, if i go checking in the router log (without any filter of course!) there is NO log about the remote connection!!!
So i made two tests:
- PING my dyndns account and found that IT WORKS!!!in the log i see the ICMP packet been filtered by the firewall...
- Make a TELNET to my dyndns and even this WORKS, because i see in the log the entry trying to connect to my telnet default port (23)........
So it is an RDP bug?Or a "port" bug?So i moved on, i edited the default port of Windows for RDP, restart the system, modified the rules in the various firewalls local and not, retried to connect with RDP on the custom port but...i got the SAME, no connection, no log entry in the router...retried PING and TELNET and i get the log entries....

I tried even with virtual server but nothing change.......so, who i have to shoot? Microdoft ,DLink or DynDns? or everyone? eheheheheh
cheers!!!!