Browse FAQs

Change in NetBotz private LAN IP does not fully update.

Published date: 29 March 2019

Issue:

NetBotz 750 Private Lan IP change fails to update

Product Line:

NetBotz

Environment:

NBRK0750
Version 5.1.0 firmware

Cause:

The private LAN on an NetBotz 750 comes with a default 172.16.0.x subnet range. If you set the public IP to a 172.16.x.x address this will conflict with the private LAN so the serial IP configuration wizard will prompt for a new IP range for the private LAN. If you give it a different address such as 192.168, DHCP will still try to pass out a 172.16.0.x IP to devices attached to that private LAN. Subsequently, devices will not properly communicate and NetBotz NBPD0165 cameras can not be discovered.

Resolution:

For the time being, we recommend not adding the NetBotz 750 to a network in this range. This issue is scheduled to be resolved in the next release of the NetBotz 750 firmware, 5.2.
 

Was this helpful?

What can we do to improve the information ?

Can't find what you are looking for?

Reach out to our customer care team to receive information on technical support, assistance for complaints and more.