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

Well, despite so much warning about vulnerability of FTP connection, I am still willing to try as a basic step to open the gate for my DNS-323.

Even with that simple thing, I haven't successfully set it up

My configuration is as follows:
* ADSL connection provided by my apartment management office
* Wireless Router LinkSys WRT54GS
* DLink DNS-323 + Seagate Barracude 7200.11 650GB connected to the LinkSys
* Computer running Win XP Pro

I have done the followings:
* Setting & turning on the FTP server in DNS-323 Web UI using port 28 (just in case my ISP is blocking port 21); Including making a dummy user named "coba" and a temporary folder named "ftp" in the root to be accessed by the FTP
* I have set up the gateway of DNS-323 (via LAN menu) to 192.168.2.1 (my router IP address)
* I have set up the port forwarding (range 21 - 30) to 192.168.2.105 (the DNS-323 static IP)
* I have set up the DMZ to IP 192.168.2.105

I try the FTP connection while my computer is connected to the LAN (i.e. the FTP server address is 192.168.2.105) and it works as expected.
Then I try to go to http://www.ip-adress.com/ipaddresstolocation/ to know my router WAN address.
When I cut down my computer from the LAN and use a dial-up (GPRS) then try to connect to the FTP via the router WAN address, my FTP software (Filezilla) says "Unable to connect"

What's wrong?
How can I make it work? At least using the normal FTP?
I also have suspected that the WAN IP is not solely belong to me, sometimes, when I try to download from Rapidshare, it said something like this: "Your IP is currently downloading from us, please wait until it finish"

Please help

You did a great job explaining things right up to the point of how you try connecting via ftp.  Are you indeed asking your computer to look at port 28?  Do you know if your isp blocks all ftp connections regardless of port (my job does that).  Next, did you set the user name and password in filezilla?  Lastly, is filezilla set for passive mode or active mode?

Next, why did you seet up port fowarding and then put the DNS in the DMZ?  The DMZ does not require port forwarding because is is essentially "live" on the internet.  Next, the point of port forwarding is to set it up to forward, for example, port 28 from the WAN to port 21 on the LAN.  In this case you could leave the DNS on port 21 and you would select port 28 when connecting from the internet.

I have just checked with the apartment management office, it seems that we share the same WAN IP among the tenant.
Is it the cause this FTP failure?

To ensure everything, I have tried to activate DMZ again and try to connect to the WAN IP of my router using active FTP, but the result is the same unable to connect.
Then I switch to passive, but it remains the same.

My apartment officer suggest I call the ISP directly and declare that I am the tenant, however due to language limitation, I think that I must clearly mention about what I want otherwise there will be chicken and duck conversation.
What should I ask them?

Indra wrote:

I have just checked with the apartment management office, it seems that we share the same WAN IP among the tenant.
Is it the cause this FTP failure?

I believe that is your problem - to share the single WAN ip address will require some form of network address translation which will in turn require port forwarding so that the incoming connection request is sent to your private ip.

Please also give suggestion about what to ask if I also want to turn on the web server, as well as SSH.

Hi fordem,

Thanks a lot for the enlightenment.
I'll talk to the administrator (man, how I hate to urge people to do something with their network)

OK, confirm that port 21 & 80 will have to be opened.
I'll try to find information about SSH port so that I just need to talk once to the administrator.