NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
SXK80 - Firmware Version 4.2.3.102 bug
I found a bug in the firmware, after restoring the factory settings, when the ISP is on the 192.168.1.0/24 network segment, the device will automatically switch to the 10.0.00/24 network segment, and...
shejialun wrote:
I just don't understand why it would fail to run NSCI on an SXK80 device after restoring factory settings and switching to a 10.x subnet.
Don't worry, me neither. Simply no time to waste more time on this special case. Keep in mind not many users have to factory default, and all this in the double-NAT context.
Is the problem prohibitive for bringing up a SKX80 (or for the sake of it the similar SXK50 or SXK30 system) from a factory default re-config?
Realistically, 99.9x% of these systems are configured once, and run forever. There it goes the expectation for a utility, beyond plain standard tftp - available on many different platforms and OSes. If it's not broken already as of writing, unlikely Netgear does spend time and resources on this 80/50/30 product line.
For my part, I'm done with this, as I don't own such one of these product, and never got one for Beta testing. Other community members seem to have the better contact to the Orbi Pro router team than me. I'm just yet another community member trying to help where he can. Netgear does not care for us at all. We're accepted to spend time and effort for free, but this is the end for now. One day, if I find a pre-loved European device, I might be willing to buy one for some Cents. Just like the BR500 I own for the fun or pun of it.
Said this: Sorry for asking silly questions - now you understand, why.
Hello schumaku
I think you misunderstood or I didn't explain clearly.
When the WAN port of the device is connected to subnet 192.168.1.0/24, the LAN of the device switches to subnet 10.0.0.0/24, which is not a problem, because I was using an R7000 before using the SXK80, and it already had this feature.
The bug I'm talking about is that when the device's LAN is working on subnet 192.168.1.0/24, it will not activate the windows 10 client's NSCI function, but when the device switches to subnet 10.0.0.0/24 subnet, it will activate the windows 10's NCSI function to the extent that the web management page jump error in the screenshot occurs, unless the web management page jump error in the screenshot is first Turn off NCSI function.
shejialun wrote:
The bug I'm talking about is that when the device's LAN is working on subnet 192.168.1.0/24, it will not activate the windows 10 client's NSCI function, but when the device switches to subnet 10.0.0.0/24 subnet, it will activate the windows 10's NCSI function to the extent that the web management page jump error in the screenshot occurs, unless the web management page jump error in the screenshot is first Turn off NCSI function.
No Netgear router, in fact no Linux system, does participate in any way (certainly not active) with Windows NSCI. This happens only on your Windows system(s).
Hello schumaku
But what I can't understand is why it only happens on the 10.0.0.0/24 subnet and is fine on the 192.168.1.0/24 subnet, whereas the previous device, the R7000, didn't have this problem on either subnet.
Do you have the SXR set for 192.168.1.0 or 192.168.1.1?
Does this happen if you set 192.168.0.1 on the SXR router?
shejialun wrote:
But what I can't understand is why it only happens on the 10.0.0.0/24 subnet and is fine on the 192.168.1.0/24 subnet, whereas the previous device, the R7000, didn't have this problem on either subnet.
Hello FURRYe38
Sorry I missed the key point, the problem I was talking about only occurs the first time you visit the web admin page after restoring the factory settings.
When the device is restored to factory settings, if the WAN port is not connected, at this time the device works on the 192.168.1.0/24 network segment, no problem.
When the device is restored to factory settings and the WAN port is connected to the ISP's box, because the ISP's box is working in the 192.168.1.0.0/24 network segment, at this time the device automatically switches to the 10.0.0.0/24 network segment, and the error reported in the screenshot appears.
But my previous R7000 device, which works the same way, doesn't have the same problem, which is the main reason for the bug in my mind.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
