Device configuration not supported & The site can’t be reached after the camera’s IP address change

[#1]

🕒 This procedure takes in average ~ 5 min to complete

Possible causes and solution(s)

Symptoms

After changing the camera’s IP address, the camera cannot be accessed any more from the PC via WEB interface or from Configuration Manager, the new details being:

IP PC: 169.254.24.212 PC subnet mask: 255.255.0.0

IP camera: 192.168.1.20 Camera subnet mask: 255.0.0.0

The “Device configuration not supported” (in Configuration Manager) & “The site can’t be reached” (in WEB GUI) messages occur when trying to connect to the camera.

 

Causes

The PC you are using may not be in the same IP range as the camera, which could be the obstacle preventing the connection. 

 

Solution

Please check if your PC is currently assigned in a static IP.  

Make sure that the PC you are using is in the same network segment as the camera (IP address range, subnet coverage etc). Otherwise, you will not be able to access and configure the camera at all from your PC. 

Good to know:

1. IP Address Range: Both the PC and the camera are assigned IP addresses within the same range:
   For example, they might both have IP addresses in the range 192.168.1.X, where X represents a unique number for each device.

2. Subnet Mask: The subnet mask determines the size of the network segment. If the PC and the camera are in the same network segment, they would have the same subnet mask, such as 255.255.255.0, indicating that the first three octets (192.168.1) represent the network portion, and the last octet (X) represents the host portion.

In summary, when the PC and the camera are in the same network segment, they share the same IP address range, subnet mask, and default gateway, enabling them to communicate directly with each other within the local network.