Dialatech Posted September 22, 2017 Share Posted September 22, 2017 Good Afternoon I've just started to look at Home Assistant, This needs to rules to be created and then triggered by certain things. so here comes my issue. i have setup my Alexa and my HTPC within Home assistant but for Alexa to talk to the HTPC i need to open port 2340, so i logged into 192.168.0.1 for my Netduma router and go to port forwarding and open 2340 on my internal IP for my HTPC. but when i go to a browser a type in my external IP:2340 i can a error saying the port is blocked. but if i do internal:2340 it works fine. Why is port forwarding not opening this port? Also with Home Assistant i have created triggers so when home assistant can ping my phone it will send a notification saying im home and when it cant ping it i get a notification saying im not away. This goes for everyone in the household. so my mobile ip address which is a static ip is 192.168.0.241 and i cannot ping it but the internet works fine. i can ping everyone else mobile in the household just not mine, i have checked the VPN but that disabled. Hopefully someone can help me these issues? Link to comment Share on other sites More sharing options...
Dialatech Posted September 23, 2017 Author Share Posted September 23, 2017 Any help would be appreciated thanks Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Jack Posted September 23, 2017 Netduma Staff Share Posted September 23, 2017 Any help would be appreciated thanks Try putting your Netduma into the DMZ of the router it's connected to. In theory that should work, so please let us know how that goes. To do this, copy the WAN IP from the Netduma device manager into the DMZ section of your ISP hub. The DMZ section should be under Security settings. Link to comment Share on other sites More sharing options...
Dialatech Posted September 23, 2017 Author Share Posted September 23, 2017 My virgin media router is in modem mode. So you don't have access to the advanced settings you do if you were in router mode. Any more suggestions Link to comment Share on other sites More sharing options...
Dialatech Posted September 24, 2017 Author Share Posted September 24, 2017 Anyone? Link to comment Share on other sites More sharing options...
RedBull2k Posted September 24, 2017 Share Posted September 24, 2017 Which device needs 2340 to be open? Alexa device or HTPC? and then what is that device ip address? Link to comment Share on other sites More sharing options...
Dialatech Posted September 26, 2017 Author Share Posted September 26, 2017 Which device needs 2340 to be open? Alexa device or HTPC? and then what is that device ip address? Thank you for your reply So I have configured Kodi HTTPS on my HTPC to use port 2340 to allow access to it. HTPC Internal IP = 192.168.0.180, if I go to a browser and type in 192.168.0.180:2340 I get the HTTP website for my Kodi Library but if I use the External IP address : 2340 I get a refused connection error. I have put port forwarding in to allow UDP and TCP 2340 to 192.168.0.180 but it does not work. Link to comment Share on other sites More sharing options...
RedBull2k Posted September 26, 2017 Share Posted September 26, 2017 What ip do you use to access duma? What ip do you use to access modem? Link to comment Share on other sites More sharing options...
Dialatech Posted September 26, 2017 Author Share Posted September 26, 2017 What ip do you use to access duma? What ip do you use to access modem? Netduma Ip is 192.168.0.1 Virgin Media super hub in Modem is already 192.168.100.1 Link to comment Share on other sites More sharing options...
RedBull2k Posted September 26, 2017 Share Posted September 26, 2017 ok thanks for that. have you tried connecting using your WAN:port using another internet connection? Link to comment Share on other sites More sharing options...
RedBull2k Posted September 26, 2017 Share Posted September 26, 2017 on your htpc go to http://canyouseeme.org/ and then enter your port you must have the program open that uses that port, if its closed then this test is useless. Link to comment Share on other sites More sharing options...
Dialatech Posted September 26, 2017 Author Share Posted September 26, 2017 ok I will give it ago when I get in from work and let you know Thanks for your help - Very Appreciated Link to comment Share on other sites More sharing options...
Dialatech Posted September 26, 2017 Author Share Posted September 26, 2017 Just tried WAN:port on a different internet connection and says it cannot display the page Link to comment Share on other sites More sharing options...
RedBull2k Posted September 26, 2017 Share Posted September 26, 2017 what about on the link canyouseeme? does your isp provide you with a WAN static ip? Link to comment Share on other sites More sharing options...
Dialatech Posted September 27, 2017 Author Share Posted September 27, 2017 on the canyouseeme link I see my static WAN IP. Which is the same one I'm trying to ping WAN:2340 and I have the port forwarding in on the netduma for both TCP and UDP. Link to comment Share on other sites More sharing options...
RedBull2k Posted September 27, 2017 Share Posted September 27, 2017 and what does it say for port status? Why are you using 'ping'? Link to comment Share on other sites More sharing options...
Dialatech Posted September 28, 2017 Author Share Posted September 28, 2017 I have now resolved this issue. Last night I decided to factory reset my Netduma and set it all up again and now its working fine. Very Weird but its working. Thank you for all your help RedBull2k Link to comment Share on other sites More sharing options...
RedBull2k Posted September 28, 2017 Share Posted September 28, 2017 You can always trust the old factory reset. To be honest though I never thought the problem was with the duma, Just thought it was a configuration with your HTPC and app, as you already done the portforward. Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Jack Posted September 28, 2017 Netduma Staff Share Posted September 28, 2017 I have now resolved this issue. Last night I decided to factory reset my Netduma and set it all up again and now its working fine. Very Weird but its working. Thank you for all your help RedBull2k Very weird indeed, I'm glad a factory reset resolved the issue. We usually only recommend factory resetting as a last resort, but it seems that's exactly what it needed! Please let us know if you have any more issues. I'll now close this thread. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.