StarHub MaxInfinity Fiber Optic - Experience

[Bieffe]

sorry for the slow reply

StarHub - Broadband - Home Broadband

under Maxfinity elite

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

anyway i got a question:

My old set up under normal broadband is

Surfboard modem > Dir-655 > PC/NAS with DDNS

My new setup is this: ONT > DVG-N5402SP > DIR 655 > PC/NAS with DDNS

I wana keep the settings on my DIR 655 and everything else that is connected with it (hassle free)
Everything works, except that the DDNS/accessing my NAS from outside of my home network, doesn't work. I have already forwarded the port in the DVG-N5402SP router using the virtual server page, to the IP of my DIR 655. Did DMZ to the IP of my DIR655 also. Still doesn't work, anyone can advice or point to a page in this thread? tried reading through, but didn't come across (might have missed it)

Or should i just connect in this manner:

ONT > DVG-N5402SP > NAS with DDNS / DIR 655 > PC etc

why connect in such a way? Is like 2 router buy use one only. The settings not so difficult right? After all both devices dlink. Interface similar.
Mine is the same but I plan to remove 655. The 655 cannot be bridge also...so I remove. One device less should boost speeds? Also 655 is not gigabyte router correct?

 

[edwin21]

So it'll be like xxx.dlinkddns.com/191.168.1.52:6500?
Using synlogy so th port number is for their ui

meaning if ur NAS hostname is mynas then use http://mynas:5000 or if your nas lan ip is 192.168.1.52 then http://192.168.1.52:5000

 

[moozmoow]

meaning if ur NAS hostname is mynas then use http://mynas:5000 or if your nas lan ip is 192.168.1.52 then http://192.168.1.52:5000

Http://mynas:5000 cant access my nas although all the port forwarded correctly but 192.168.1.52:5000 works, still the same thanks for trying to help though!

 

[moozmoow]

why connect in such a way? Is like 2 router buy use one only. The settings not so difficult right? After all both devices dlink. Interface similar.
Mine is the same but I plan to remove 655. The 655 cannot be bridge also...so I remove. One device less should boost speeds? Also 655 is not gigabyte router correct?

I think 655 is gigabit. Anyway i tried without 655 also, but i still face the same problem as stated in the post above

 

[Gribber]

meaning if ur NAS hostname is mynas then use http://mynas:5000 or if your nas lan ip is 192.168.1.52 then http://192.168.1.52:5000

Http://mynas:5000 cant access my nas although all the port forwarded correctly but 192.168.1.52:5000 works, still the same thanks for trying to help though!

I think 655 is gigabit. Anyway i tried without 655 also, but i still face the same problem as stated in the post above

show us your port forward page then we can conclude if your "port forward" is done correctly or not

 

[moozmoow]

show us your port forward page then we can conclude if your "port forward" is done correctly or not

Ok, tonight? I outside now hope i did some settings wrongly then problem solved hehe

 

[edwin21]

Http://mynas:5000 cant access my nas although all the port forwarded correctly but 192.168.1.52:5000 works, still the same thanks for trying to help though!

is ur nas hostname mynas? this is for LAN to access, when outside then use ur ddns hostname to access
do readup on what is nat loopback 1st.
if u can access ur nas using ddns hostname using 3g/4g then it is working for port forwarding

 

[moozmoow]

is ur nas hostname mynas? this is for LAN to access, when outside then use ur ddns hostname to access
do readup on what is nat loopback 1st.
if u can access ur nas using ddns hostname using 3g/4g then it is working for port forwarding

Can't work on 3g. Prior to fibre when I was using cable, I'm able to access my nas worked. And yes my old dir 655 has nat loopback,I'm not sure about the dvg-n5402sp though

 

[moozmoow]

update on my case:

Called starhub yesterday concerning the NAT loopback for the DVG-N5402SP, that I am unable to connect to my NAS via internet/WAN using the dynamic DNS. Starhub tech support forwarded my case to the d-link tech support.

D-link tech support just called me, and I told him about whatever I was experiencing. I asked tech support if the DVG-N5402SP supports NAT loopback, he told me that the device does not, and will feedback to starhub about the device limitation. I also told him to feedback and recommend to starhub for a Direct ONT connection for my case.

Will post here if theres any more updates

 

[Gribber]

update on my case:

Called starhub yesterday concerning the NAT loopback for the DVG-N5402SP, that I am unable to connect to my NAS via internet/WAN using the dynamic DNS. Starhub tech support forwarded my case to the d-link tech support.

D-link tech support just called me, and I told him about whatever I was experiencing. I asked tech support if the DVG-N5402SP supports NAT loopback, he told me that the device does not, and will feedback to starhub about the device limitation. I also told him to feedback and recommend to starhub for a Direct ONT connection for my case.

Will post here if theres any more updates

I doubt you understand what exactly is NAT loopback same goes for the people who assisted you.

if you are using 3g to connect into your router to your NAS, there is no reason for you not able to.



since you did not put it clearly I will put it clearly what exactly is NAT loopback in the simplest form.
using the same internet your nas is connected to to browse into your nas via ddns.


if you are unable to connect to your nas with another Internet or 3g or what have you got, the problem is with your configuration! simi NAT loopback issue. zzz.

 

[moozmoow]

I doubt you understand what exactly is NAT loopback same goes for the people who assisted you.

if you are using 3g to connect into your router to your NAS, there is no reason for you not able to.



since you did not put it clearly I will put it clearly what exactly is NAT loopback in the simplest form.
using the same internet your nas is connected to to browse into your nas via ddns.


if you are unable to connect to your nas with another Internet or 3g or what have you got, the problem is with your configuration! simi NAT loopback issue. zzz.

yes you're right i don't exactly understand what it means
anyway, for configurations, is there anything i'm missing out apart from this? Sorry if i wasn't too clear previously, really hope i can make it clear and fix this problem

port doesn't seem to be forwarded properly

 

[Gribber]

yes you're right i don't exactly understand what it means
anyway, for configurations, is there anything i'm missing out apart from this? Sorry if i wasn't too clear previously, really hope i can make it clear and fix this problem

port doesn't seem to be forwarded properly

so to get the picture straight your configurations is as follows?

ONT > N5402SP > NAS?

 

[moozmoow]

so to get the picture straight your configurations is as follows?

ONT > N5402SP > NAS?

yup, its like that, i removed dir-655 from the picture now

 

[Gribber]

yup, its like that, i removed dir-655 from the picture now

so i assume
5007 & 192.168.1.7 is your NAS yeah?

for FTP or ? did you set 5007 in your NAS as well ?

 

[Gribber]

provide me your WAN if possible.

 

[sandpit_viper]

WOW

 

[IncTEh]

For people who are disappointed with the performance of Dlink DVG-N5402SP, and wishes that Starhub accepts returns of the RG for other forms of benefits, please sign the below petition.

Petition Return of DVG-N5402SP

 

[moozmoow]

thanks for the help gribber! Managed to access my nas from the outside world with his help

 

[Gribber]

For people who are disappointed with the performance of Dlink DVG-N5402SP, and wishes that Starhub accepts returns of the RG for other forms of benefits, please sign the below petition.

Petition Return of DVG-N5402SP

good effort but i doubt starhub will care.

thanks for the help gribber! Managed to access my nas from the outside world with his help

i don't usually assist privately just so you know.

 

[moozmoow]

good effort but i doubt starhub will care.



i don't usually assist privately just so you know.

okay, thank you even more! sorry to take up so much of your time troubleshooting for me. Overlooked the simple problem of ddns forwarding to wrong ip address