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

anhtien · 2010-02-25 17:34:16

Greetings,
I successfully installed ffp v0.5 and lighttpd, mediatomb 12 on my DNS-321. I used dyndns to access this NAS from the Internet and was able to get through port 21 (FTP server from DNS-321 itself), port 22 (SSH from ffp), and even port 81 to check my configuration (I followed the steps to kick goahead webser to port 81 and used port 80 for lighttpd).
The problem is that I can access the website (loaded in /mnt/HD_a2/www/pages) from any PC at home inside the router, I was not able to access the site via HTTP and yes I did the port forwarding on my router for all of the above ports including port 80. I hesitate to open port 49152 to check out mediatomb from outside but I might do it just to make sure that port 80 is the only guilty one.
Anyone has any idea ?

fordem · 2010-02-25 18:31:13

Since the website works from the local LAN and all of your other port forwards are working - perhaps your ISP has blocked port 80 (mine does) to prevent users from hosting websites.

anhtien · 2010-02-26 19:46:35

I just got a confirmation from my ISP that they do not block any port. I just came across the "host abuse state" on DynDNS (my dyn dns provider) which could be triggered if there are multiple clients updating the dynamic host. At one point in time, I turned on DDNS on both my router and the DNS-321 so this might be the cause for this port 80 blockage.
Mean time, I am contacting DynDNS to check on my host status, the quest for knowledge continues...

Last edited by anhtien (2010-02-27 00:50:05)

fordem · 2010-02-26 23:05:18

DDNS is not what's blocking port 80 - it won't block a single port - you'd lose the entire DNS resolution setup.

anhtien · 2010-02-27 00:23:46

Thanks, fordem, I called my ISP again and gave them a hard time, this time they admit they block port 80 among other ports. What a wild-goose chase.
Other blocked ports are:
25
135-139
445
1433-1434
1900
27374

Last edited by anhtien (2010-02-27 00:26:59)

fordem · 2010-02-27 03:04:21

Consider yourself lucky - my ISP will not release a list of blocked ports, although they will admit a particular port is blocked if you ask the right questions.

Blocked ports include 80, 81, 800 & 8080 - basically the ones that are popular for webserving - and the list changes - back when I was running the beta for Windows Home Server I had everything working and then one day it stopped, they had decided to block 443.

What you could do in your case is put the admin webserver back on 80 and lighttpd on 81, forward 81 and you're good to go.

anhtien · 2010-02-27 07:25:26

Thanks, fordem, port 81 is definitely stable since I was busy checking the goahead server to see if there was anything wrong with the setting. Switching between ports 80 & 81 sounds like a good plan for now. I will probably venture into port 443 since it's currently not on the forbidden list.
Regards,

Isildur · 2010-03-01 03:04:51

anhtien, I don't know about DynDNS, but no-ip.com has free service with very useful feature, just take a look to this quote:

Port 80 Redirects

Many residential ISPs Block port 80, No-IP Free DNS enables you to run a webserver on a non-standard port, yet users accessing your site never have to enter a port number. For example http://yourname.no-ip.com/ can redirect to http://yourname.no-ip.com:8833/

anhtien · 2010-03-01 17:09:26

Thanks, Isildur, I found another way through my domain provider. I subscribed to a real domain, say "MyRealWebsite.com", and they give me a free one page parking website. I placed the index.html file containing only the following lines in that free webpage.

<script type="text/javascript">
location.replace('http://MyDynamicWebsite:8081');
</script>

Looks familiar ? It's the same approach as goahead webserver on the DNS-321 except I forward my real domain to this dynamic dns domain using a different port (8081 in this case). I then revert lighttpd port to 8081 (instead of the default 80). After forwarding port 8081 in my router, MyRealWebsite.com is in business.
The only ugly thing is that the visitors would key in "MyRealWebsite.com" and then see it switched to MyDynamicWebsite:8081, it would be nice to mask it somehow. I will look into Javascript to see if there is such a masking function.

Last edited by anhtien (2010-03-01 17:11:47)

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

Announcement

#1 2010-02-25 17:34:16

why DNS-321 webserver can not be accessed from the Internet?

#2 2010-02-25 18:31:13

Re: why DNS-321 webserver can not be accessed from the Internet?

#3 2010-02-26 19:46:35

Re: why DNS-321 webserver can not be accessed from the Internet?

#4 2010-02-26 23:05:18

Re: why DNS-321 webserver can not be accessed from the Internet?

#5 2010-02-27 00:23:46

Re: why DNS-321 webserver can not be accessed from the Internet?

#6 2010-02-27 03:04:21

Re: why DNS-321 webserver can not be accessed from the Internet?

#7 2010-02-27 07:25:26

Re: why DNS-321 webserver can not be accessed from the Internet?

#8 2010-03-01 03:04:51

Re: why DNS-321 webserver can not be accessed from the Internet?

#9 2010-03-01 17:09:26

Re: why DNS-321 webserver can not be accessed from the Internet?

Board footer