• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

This forum thread needs a solution.
Kudos0

Address Reservation not sticking to device

Now that I can assign static address to a device, I have tried several times without success. I have always checked first which 3rd octet values are assigned, then select something very different. Norton Core shows the assignment worked, but when I actually connect the device (and I am aware it must first be restarted for assignment) it does not take. Checking device IP address shows it has something else. I have roughly 10 devices that may be on the router at any one time, generally less. I have never seen a 3rd octet greater than 12, so I have chosen 20, 44, 50, 60. When I return to the assignment page there it shows the octet I selected, but that is not what is assigned. The assigned octet still appears to be handled by the DHCP?

Now 1 point of observation. All my IP addresses have 2 as the 4th octet. And 2 is shown when initially adding a device to Address Reservation. However, once the address is assigned the IP address comes up as 123.123.123.null. What is null telling me? Should it not be showing 2? Does Address Reservation automatically choose a different 4th octet value?

ALW

Replies

Kudos0

Re: Address Reservation not sticking to device

ALWeeds. It sounds like port forwarding rules for those devices are the issue. Follow the setup in the article below and see if things change for you: https://support.norton.com/sp/en/us/home/current/solutions/v118380605_core_en_us

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

Per the instruction within the link you forwarded me and I had seen previously, I checked Port Forwarding. No devices are set to Port Forwarding. That is not the problem. Thanks for the suggestion.

ALW

Kudos0

Re: Address Reservation not sticking to device

ALWeeds: Please post a screenshot of the 123.123.123.null so we may see what you are seeing. Here is how to post images to the forums: https://community.norton.com/en/forums/how-post-image-forums-0

Now 1 point of observation. All my IP addresses have 2 as the 4th octet. And 2 is shown when initially adding a device to Address Reservation.

The 2 in the 4th octet is normal as ONLY the 3rd octet can be changed. Are you restarting your Core after making these IP reservations? Please note step 7 under "assign a static IP address" in the previous article

https://support.norton.com/sp/en/us/home/current/solutions/v118380605_core_en_us

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

Permalink; the requested screenshot show "null" as the 4th octet value.

Kudos0

Re: Address Reservation not sticking to device

I had read the note about restarting the device in step 7, as you have indicated. Your question, Am I restarting my CORE... raises the question, What is the device being referred to? I was assuming it was the device being assigned the static IP address, not the CORE router. I was also assuming that if the CORE router was the "device" to be restarted it would have been more explicit. ("Restart the CORE router.) "Device" seems like a term that would be used when the actual device is not exactly known; phone, table, etc.

ALW

Kudos0

Re: Address Reservation not sticking to device

Whom ever the device is assigned to is what is being presented with that IP. Most likely there is a conflict with a duplicate reserved IP, by device assignment or grouping. The subnet IE 255.255.255.0 SHOULDN'T be changeable so I will rule that out. Restarting BOTH the Core and the device where the new assignment is what is being referred to.

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

I am not sure I fully understand your response. I am aware that the static IP address will be assigned to my device, not the CORE router.

I stated initially that I had checked which 3rd octet values have been assigned and I choose values not assigned; therefore this is not a duplicate IP address assignment. Fact is if you try that, you are immediately blocked by the CORE application as it recognizes the conflict.

I am not sure what grouping is, but I have not attempted to group anything, so I question this as the cause.

Not sure why you brought up the SUBNET address, as this has not been mentioned and is not the problem.

I have now restarted both devices at the same time, giving plenty of time between shutdown and restart to clear any residual memory that might be holding the address. I continue to have the same problem.

Can you explain, please, why the 4th octet while initially showing 2 as the value, switches to null once I assign a static address? This can be seen in the requested screen grab I attached earlier.

ALW

Kudos0

Re: Address Reservation not sticking to device

ALW:

Can you explain, please, why the 4th octet while initially showing 2 as the value, switches to null once I assign a static address? This can be seen in the requested screen grab I attached earlier.

The device in your screenshot named "Harold" and reporting "null" as the 4th octet means that IP is sending data into a black hole. Rebooting THAT device should clear the "null" 4th octet you are seeing on the Core app. The device will not receive and respond to the new IP until rebooted. Once rebooted Core should show the device at 176.16.60.2

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

Pardon me for repetition; but I did state in the initial problem that I had realized the device required rebooting for the static IP address to be assigned and this was done. I have implied that again in other statements, and in just my last posting I mentioned again explicitly that the device had been rebooted yet again. The device Harold has been rebooted after each occurrence of Address Reservation assignment. 

Repeatedly I have removed the device from Address Reservation, verifying it is not present. I have then checked the IP address and I see Harold has been assigned an IP address automatically and that address has 2 in the 4th octet. When I next attempt to assign a static address the 2 is visible up and until I press the save in assigning the static address. Then when on the main screen listing assigned devices (picture provided earlier) the word null appears in the 4th octet. And finally I reboot Harold as I understood the instruction #7. 

Per your instruction the last reboot was done simultaneously with a reboot of the CORE router. I am still getting the same result. 

In the Address Reservation page, I see Harold and the static address assigned 176.16.60.null. However, if I go to the Device page listing all devices and select Harold I see a automatically assigned address similar to 172.16.3.2. 

ALW

Kudos0

Re: Address Reservation not sticking to device

Reset your Core: https://support.norton.com/sp/en/us/home/current/solutions/v118380611_core_en_us

Wipe ALL your data and unattache the Core from your account during the factory reset. Make sure you have the app version 1.27.2 which has some new onboarding to follow. Any "null" value in any IP address is the result of, an intentional/unintentional setting, naming or IP conflict. Something on your network is causing the IP conflict. Resetting Core will correct that as you reconnect your devices.

If a factory reset doesn't solve this issue give support a chat: http://norton.com/chat

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

I have a similar issue with static IP addresses. When I attempt to reserve an address for any of my devices, regardless of the address I choose, I get: “Something went wrong, please try again”. I've rebooted both the device and Core multiple times. This is a necessary feature, as my IP cameras must have static IP addresses. I’m getting really tired of this beast…

Kudos0

Re: Address Reservation not sticking to device

Hello Chris Have you followed these instructions? Please remember that ONLY the 3rd octet can be set for IP reservation, port forwarding and UPnP should also be set and utilized. https://support.norton.com/sp/en/us/home/current/solutions/v118380605_core_en_us

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

Yes, I have followed the Norton support KB. As an IT consultant, I am fairly familiar with what should happen when reserving an IP address, and which octet I can change. In the end, I find this router to be applicable only to families - those which need to protect their kids and who have no understanding of what a router does. For the rest of us, who need a robust set of tools to manage IP addresses, FTP, etc., this was not a good choice. My mistake.

Kudos0

Re: Address Reservation not sticking to device

Chris

This is a necessary feature, as my IP cameras must have static IP addresses.

As the KB article states full static IP's are not supported on the Core router. IP reservations are the only choice at the present time. FWIW, I use FTP religiously with Core for my game servers at NFO. Moving files to and from the servers, SQL databases for our forums, and resource fast downloads. Never have any issue. Funny thing is, IP cameras all become a PITA when port forwarding and IP reservations on Core. Until a Windows / browser interface comes for Core along with FULL IP and DNS selection we are stuck with what we have. There's nothing like being in the "Delta" arena with a new product.

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

The Core factory reset did not fix the address reservation problem. Nothing changed. I did verify that the firmware version was 1.27.2. Will contact Norton Core support directly.

ALW

Kudos0

Re: Address Reservation not sticking to device

ALWeeds Please let us know what support tells you. FWIW, the Core firmware is version 223, Android app is 1.27.2 / iOS app is 1.2.7 at present.

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos1 Stats

Re: Address Reservation not sticking to device

How I got the static IP to work is the following:

  1. Leave the device on DHCP. 
  2. Let Norton Core assign it an IP address.
  3. From the Network Setting, Address Reservations, click add.
  4. Select the device from the listing.
  5. Click save.

I have rebooted my printer many times and it seems to keep same reserved IP address.

Kudos0

Re: Address Reservation not sticking to device

ALWeeds Have you given the suggestion by CST1 a go?

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos1 Stats

Re: Address Reservation not sticking to device

CST1: Will try what you recommend. Seems we can't assign an address of our choosing, but can reserve the DHCP address with this process.

Following the instructions, I verified device was not in reserved list. Then checked the IP address assigned by DHCP; 4. Next, as instructed I added device to reserved list, NOT changing the 3rd octet (currently 4) and hit save.

In the reserved list the 3rd octet shows 4 as expected. 4th octet still coming up "null". 

My observation has been that IP addresses seem to stay with each device for a day or so. That device will leave house tomorrow and return. That would typical result in a new 3rd octet value. Will see what happens now.

Thanks CST1. Will get back later.

ALW

Kudos0

Re: Address Reservation not sticking to device

I have attempted the same thing as ALW above. But instead of a null issue, I get an error message: "Something went wrong. Please try again." This happens for any device, and regardless of the value I put in the 3rd octet. Even if I don't change the value before saving. And the device's address is not sticking over time - Core changes some of them on reboot.

Kudos0

Re: Address Reservation not sticking to device

Hello Chris Please give support a chat, I am fresh out of ideas. http://norton.com/chat

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93
Kudos0

Re: Address Reservation not sticking to device

I have been seeing others have issues with device connectivity.  I am wondering if the auto band selection is causing an issue.  If you separate the 2.4 and 5 to different SSIDs and set the camera to use one or the other.  Then add it to the static IP list.  I wonder if it will hold.

Kudos0

Re: Address Reservation not sticking to device

Everyone: Core firmware has updated to version 226. Please check for the update and allow us to know if your issues remain or are mitigated.

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.379 / NCSP 22.17.0.183 / Norton Core v.278 on Android 1.93

This thread is closed from further comment. Please visit the forum to start a new thread.