DSM-G600, DNS-3xx and NSA-220 Hack Forum

DasCrushinator wrote:

I have tried the built in DDNS feature for the DNS-323, but for whatever reason I am only able to access the DNS-323 with that address while on the same network as the DNS-323.

So DDNS seems to be ok.

When I am at another physical location (e.g. my dad's house), it does not work.

Have you already setup Port Forwarding, on your WRT54G2. Setup a fixed IP on your local network, on you DNS-323 device first: it's the easiest way to configure Port Forwarding next.

Just to be sure DDNS is ok, open a command window, type:
ping xxxxxx.dnsalias.org

and look at the resolved IP adress: it should be your PUBLIC IP address, on the Internet ; not the DNS-323's IP on your local network.

Last edited by Electrocut (2009-06-09 13:40:13)

Never heared of pinging with a port number.
If you want ping the dns-323 to work you should setup port forwarding for the ping port number (and maybe in the router firewall enable the setting)

I think you should look up how to setup forward ports on your router.

Last edited by wortelsoft (2009-06-11 17:51:48)

wortelsoft wrote:

Never heared of pinging with a port number.
If you want ping the dns-323 to work you should setup port forwarding for the ping port number (and maybe in the router firewall enable the setting)

I think you should look up how to setup forward ports on your router.

I know how to and have known how to for about 8 or so years now. Did not know about the pinging with a port number part though.

Electrocut wrote:

Pinging with a port number is non-sense, because PING Requests are working over ICMP protocol. Ports number or only available with TCP or UDP protocols.

What you should try, is to redirect (on the router) the port(s) you know your DNS-323 is listening on: this could be :80 (web page), :23 (telnet access), :21 (ftp access), then try to connect from your remote location

Again, I have redirected the ports on the router to the DNS-323. It sees the xxx.dyndns.org as the proper IP now, but I cannot access the DNS-323 still. If it makes any of you feel better in my ability to do so, I can forward ports to my computer (which has a static NAT IP) for torrents and it fixes issues with that. So like I said, I am well aware of how to forward ports. Figured that sense I have the issue with the DNS-323 and not with any computers on the network that the problem might lie within the DNS-323 and not my abilities or the router.

Edit: Success! I forwarded port 80 (did not realize the port number had to be specific :S) and was able to access the remote web management. Now all I need to do is find a way to be able to access it via SSH and maybe AppleTalk/SMB from outside the network. Speaking of which, do you guys know if accessing outside the network via either of those protocols is unsafe so long as I have it specified to only allow access with a certain username/password?

Thanks for all of the help!

Edit 2: Forwarded port 22 and now SSH works. Just need to get SMB/AT working and I'm set! Is there anyway to change what ports different services are accessed on? Like SSH, FTP, etc.? Also, is it going to be picky about what ports I chose for Bit Torrent (or if usenet clients require it, usenet)?

Last edited by DasCrushinator (2009-06-11 22:44:44)