A plain “rg_conf_print” will dump the whole configuration. From there, you could try to identify the corresponding values you need to change. See my other BBox-2 tricks for examples of using the “rg_conf_set” command.

I don’t own a BBox-2 anymore, hence I am unable to test.

For example, many company firewalls block certain well-known ports, like FTP, RDC, NetBios, NFS or others. Some ISPs do, too. I would suggest trying to run RDC off another, non-obvious port, like 33389, if at all possible.

You could also try to connect from other places, at a friend’s house for example. At least, this would help eliminate external factors.

Also verify that the the IP address assigned to your dyndns domain actually matches the real IP address of the BBox-2 at any given moment. Some DNS resolvers could cache the old value for too long.

I’ve been desperately trying this for weeks now, but it doesn’t seem to work.

I have a Windows 7 machine attached to a BBOX-2. I want to use Microsoft Remote Desktop Connection for Mac to connect to it, so I have forwarded TCP port 3389 (standard port for RDC for mac, so I have read) to the local IP of the machine. On the machine, Windows firewall is configured to let traffic pass on port 3389 as well.

Inside the LAN, RDC connects just fine but outside of it (using a DynDNS) there is no connection. By the way, connecting to my FTP server doesn’t work either, although streaming servers Orb and Audiogalaxy do function. By the way, even pinging the DynDNS address doesn’t seem to work.

Any tips?