rikardo67 wrote: Artex ZUT wrote: you are rather wrong I have nothing on this address and the range is from 1 to 254
Exactly! Do you think DHCP allows a rigid IP?
Is DHCP letting in something? Interesting ? :D
All DHCP does is respond to the device's DHCP request.
There is nothing to be said about what goes into the LAN and what can work in it .....
As for the crossover cable. At the moment, most devices can detect TX / RX on ETH interfaces. If the link lights up after connecting the straight line, it usually means that it is equipped with auto-MDI.
As for the author of the query.
Perhaps the device you have has a fixed IP configured and no messing around here will help. There are methods to identify this but they are time consuming.
I would personally focus on resetting the device to factory settings - the manufacturer has certainly anticipated it, the question of finding a way - for example, holding the buttons when connecting the power supply or using a reset pin and button (if it is naturally so) :D
Added after 4 [minutes]: Jones_ wrote: on some computer, run the command line and type arp -a
if the camera is not displayed, it means that it has a different address
ie from a different pool not 192.168.1.xx
Entries in ARP will be visible only after prior query for the hardware address of the device. And this, in turn, requires at least partial communication with him of the station from which you want to issue this command.
If the camera does not exchange any data with the station then the arp table will not contain its MAC.
By the way, is there sometimes no MAC address on the camera sticker?