OnvifDeviceManager

regi

n3wb
Mar 15, 2025
4
0
manchester
i viewed a camera properties in the network settings and changed the dhcp to on
now the camera has no ip address and i can't access it period
is there any way i can change it back to a static adddress
thanks reg
1742072668729.png
 
Without knowing the camera, a factory reset usually puts it back to a known IP address.

Or if it is connected to the router, look up what is connected to the router to find the camera IP.
 
i've tried what i think is a factory reset . . .but i have no documentation ( but found a button )
anyway this didn't work ( ie press reset /power up and hold for 30 secs )
it is a generic camera so i dont have a make or model number ( long gone )
i've tried pinging it but no response + it doesn't show up in cmd arp -a
( assuming its remembering the original ip )
 
Is that a TP-LINK Tapo camera? If so, it has a reset and use their app to re-configure, not ODM
It appears the HTTP port 80 has been disabled.
 
Is that a TP-LINK Tapo camera? If so, it has a reset and use their app to re-configure, not ODM
It appears the HTTP port 80 has been disabled.
i dont know the make of the camera
is there any software for this situation?
the camera has no ip address . . . its as if its in limbo
 
Does it have IR?
If so, power up, press and hold reset until the IR filter clicks (try for twice) then release.
If truly no IP being assigned or held as static it likely won't show in router (assuming router on same subnet, whatever that is)...it appears was originally on 192.168.1.XXX subnet as gateway was 192.168.1.1.

How old is this camera and what is the form factor?
 
Does it have IR?
If so, power up, press and hold reset until the IR filter clicks (try for twice) then release.
If truly no IP being assigned or held as static it likely won't show in router (assuming router on same subnet, whatever that is)...it appears was originally on 192.168.1.XXX subnet as gateway was 192.168.1.1.

How old is this camera and what is the form factor?
camera has IR and is on the same subnet . . . i will try the reset suggestion
the camera is not new but it was working with BI before the issue ( although a bit of a b. to get it recognised )
thats why the mess up happened . . . its bin used before and is supposed to be replacing a failed camera
it is a dome tamperproof onvif camera and was streaming with ODM ( but not BI ) before the issue