NVR4032H unusable after firmware 1.0.5 upgrade today
This morning Vigi app prompted for firmware update on NVR4032H to 1.0.5 but after the upgrade it appears as though the NVR runs out of resources within a few minutes of a restart. The monitoring screen stops showing all 24 cameras and the device is unresponsive. You can click to login as long as you are very patient to allow the pattern login to complete (takes about 4 minutes). I have looked for firmware 1.0.4 to downgrade to but cannot find it anywhere to download. NVR has been working perfectly before today's upgrade.
Any help or advice happily received.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Clive_A Thank you for your assistance.
The support team worked with me to identify the issue and it is now completely resolved. From firmware 1.0.4 to 1.0.5, there was some change in handling of IP addressed of devices and that was causing the issue.
- Copy Link
- Report Inappropriate Content
Hi @thmark
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240553005, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
@Clive_A Thank you for your assistance.
The support team worked with me to identify the issue and it is now completely resolved. From firmware 1.0.4 to 1.0.5, there was some change in handling of IP addressed of devices and that was causing the issue.
- Copy Link
- Report Inappropriate Content
Hi @thmark
Thanks for posting in our business forum.
thmark wrote
@Clive_A Thank you for your assistance.
The support team worked with me to identify the issue and it is now completely resolved. From firmware 1.0.4 to 1.0.5, there was some change in handling of IP addressed of devices and that was causing the issue.
Great to know it is resolved and it is not a firmware issue but a new mechanism with the IP stuff.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 153
Replies: 3
Voters 0
No one has voted for it yet.