NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear Orbi/Harmony/Alexa issues - NAT Session Timeout?
I have an RKB40, Harmony hub and Alexa Dot and am having some compatibility issues.
I set up a simple Harmony Activity to switch one item, linked it to Alexa and this works perfectly both via remote and voice control, so I assume that all the systems are functioning correctly.
However when I try a more complex and lengthy Activity which turns on a selection of items (projector, receiver, screen etc), then only the receiver switches on and nothing else.
I've Googled the issue and it seems that the NAT Session Timeout setting is likely to be the problem.
Can anyone advise how I can amend this value in my Orbi system please?
Russ
25 Replies
What FW is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?
Is the Orbi system operating in Router or AP mode?
RussJ wrote:
I have an RKB40, Harmony hub and Alexa Dot and am having some compatibility issues.
I set up a simple Harmony Activity to switch one item, linked it to Alexa and this works perfectly both via remote and voice control, so I assume that all the systems are functioning correctly.
However when I try a more complex and lengthy Activity which turns on a selection of items (projector, receiver, screen etc), then only the receiver switches on and nothing else.
I've Googled the issue and it seems that the NAT Session Timeout setting is likely to be the problem.
Can anyone advise how I can amend this value in my Orbi system please?
Russ
Firmware = V2.2.1.210
Operating in Router mode
Modem is a BT Openreach badged Huawei Echolife HG612.
Russ
Are all devices connected to the Orbi have reserved IP addresses ON the Orbi router?
NAT has to due with traversal of internet traffic from the modem thru the router to devices.
http://computer.howstuffworks.com/nat.htm
I don't believe this is a NAT issue if your dealing with devcies only on the LAN side of the router.
Are the devices connecte to the base or mixed between the base and satellite?
Try enabling Beamforming and MIMO. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).
RussJ wrote:
I have an RKB40, Harmony hub and Alexa Dot and am having some compatibility issues.
......
I have 2 Harmony Hubs (Harmony Elite and Harmony Ultimate) and also have them integrated with my Google Home (similar functionality as Alexa).
Both work fine from the remote and via voice control for short as well as very long activities.
I think your issue is more related to that you have double NAT as your ISP modem is acting as a router and does NATing on the incoming WAN traffic which can cause different issues since Orbi is also doing NATing. You need to check if you have double NAT.
A simple way to test if you have such issue is to use tracert. Please open a Command Prompt on any computer attached to Orbi and type:
> tracert 8.8.8.8 (traceroute to Google’s DNS server)
- If you see two private IP addresses listed in the first two hops then you have double NAT. Please check the model of your ISP modem and if you have a manual for it.
- If you see only one private address and the second hop shows a public address, then you’re all good and we need then to troubleshoot further to find the root cause of the issue,
Sorry about the delay in getting back to you on this. I didn't get any notification that someone had replied.
I ran tracert 8.8.8.8 with the following result:
Microsoft Windows [Version 10.0.17134.648]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\russe>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 8 ms 8 ms 31.55.186.177
4 9 ms 8 ms 9 ms 31.55.186.184
5 8 ms 8 ms 8 ms host213-121-192-120.ukcore.bt.net [213.121.192.120]
6 9 ms 13 ms 9 ms peer3-et-0-0-0.redbus.ukcore.bt.net [62.172.103.236]
7 9 ms 9 ms 9 ms 109.159.253.3
8 * * * Request timed out.
9 11 ms 11 ms 12 ms 72.14.237.58
10 9 ms 9 ms 9 ms 216.239.54.83
11 9 ms 9 ms 9 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Not sure what this means, can you help?
Russ
Means you don't have a router built in with the ISP modem which your model suggested its only a modem.
RussJ wrote:
Sorry about the delay in getting back to you on this. I didn't get any notification that someone had replied.
I ran tracert 8.8.8.8 with the following result:
Microsoft Windows [Version 10.0.17134.648]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\russe>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 8 ms 8 ms 31.55.186.177
4 9 ms 8 ms 9 ms 31.55.186.184
5 8 ms 8 ms 8 ms host213-121-192-120.ukcore.bt.net [213.121.192.120]
6 9 ms 13 ms 9 ms peer3-et-0-0-0.redbus.ukcore.bt.net [62.172.103.236]
7 9 ms 9 ms 9 ms 109.159.253.3
8 * * * Request timed out.
9 11 ms 11 ms 12 ms 72.14.237.58
10 9 ms 9 ms 9 ms 216.239.54.83
11 9 ms 9 ms 9 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Not sure what this means, can you help?
Russ
Can you take the PL out of the mix to see if anything changes?
Opps. Meant to say IPv4 NAT Filter.
That should be under Advanced tab, setup WAN setup or Internet setup.
Nat Filtering is set as "secured"
There is also a check box called "disable SIP ALG" and this is unchecked.
Try disabling NAT Filter only, save settings and reboot the RBR and Alexa devices. See if this does anything. If not, seems like there maybe an issue that NG support needs to look into.
