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 remot...
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
RussJ wrote:
......
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
......
Thank you,
In fact the timeout in the second hop (the ISP modem/router) can be a result of the NAT session timeout.
Do you always get this if you repeat the same command a number of times?
I've run this a number of times always with the same result.
Does this indicate what might be the problem?
Russ
Can you describe for us the physical connections between your modem and your Orbi.... e.g. all equipment on your network, especially the modem, any other routers, switches, etc.
Include all make, models, etc. and any switches in between. Be very specific. The fact that your Tracert times out in the same place indicates there is definitely something misconfigured.
