Trouble setting up an I.P. Camera on network

Combat squirrel

Combat squirrel

Combat squirrel

Soldato
Joined
7 Aug 2004
Posts
11,245
Hi, just got a Verint Nextiva S2610e IP camra but its default IP address is 169.254.x.x , x being the last 2 numbers of the MAC number, mac number is 00079AE20752 , but my router is assigning DHCP from 192.168.0.1 upwards, so I tried to change that to 169.254.5.1 upward, ASSUMING the camera is 169.254.5.2, didnt work at all, Verints software cant find the camera and I cant see it anywhere on the 'attached devices' list, how can I make the network see ANY ip address and not just a small amount ?

I need to find what the hell IP address the camera is basically.
 
change the default router ip to 169.254.5.1 and then try again...setting dhcp to 169.254.5.10 upwards or something.
Should then assign ip correctly..and you should see it
 
Tried no joy (obviously previous owner changed the ip, i reset it but its not that, so may not change ip on reset), any way to open any and all IP address's ? i.e. 0.0.0.1 to 999.999.999.999 ?
 
not easily..though you could try a port scanner and set it to scan everything..and wait for a few hours. If the IP address was changed I'm pretty sure it would have been changed to a public ip address like 192.168.0.x or 192.168.1.x
 
169.254.x.x is not the camera's default IP, its just taken that IP as it can't see your router to obtain a valid IP via DHCP

169. addresses are non valid IP addresses which are assigned when any device is trying to get an address via DHCP and fails. You can't use 169. addresses on a LAN.

Why on earth are you trying to change the router address ? Change the camera IP to a static address on your router's range - ie 192.168.0.10 or something !

Doh ! :rolleyes:

In fact I've just looked it up on the camera's website and in the installation guide for your camera it says the below. (pay attention to step 11 !)

1. Ensure that the camera is powered and connected to the Ethernet
network.
2. Start SConfigurator by double-clicking SConfigurator.exe on your
hard disk.
3. In the General tab, click Program Options.
4. Check Detect All Units on LAN.
5. Ensure that the VSIP Port is 5510; otherwise, click Default.
6. Ensure that the Discovery IP Address is 255.255.255.255;
otherwise, click Reset to Broadcast.
7. Click OK.
8. Select the Units tab, then click Discover. A device of type “Unknown”
with a 169.254.X.Y IP address appears in the Units box; it
corresponds to your new device.
9. Select the unknown device, then click Configure.
10. In the Reconfigure unit? confirmation window, click Yes.
11. If you have a DHCP server on your network, check Use DHCP.
Otherwise, enter the IP address, subnet mask, and gateway of the
device, as provided by your network administrator (ie your router)
12. Click OK. The device reboots with its new network settings.
13. In the Units tab, click Discover to update the list of devices and see
the S2600e with its new settings. The S2600e initial configuration is
now complete. You can now adjust the image coming out of the
camera.

If you are not getting a valid IP from your router its either not connected properly or you need to determine whether DHCP is on or not.
 
I tend to find lost devices using nmap, e.g. nmap 192.168.0.*

It's probably better to sign into the dhcp server and look through the list of attached devices, but nmap will spit out a list of everything connected that can then be searched through easily enough.
 
Combat squirrel said:
Hi, just got a Verint Nextiva S2610e IP camra but its default IP address is 169.254.x.x , x being the last 2 numbers of the MAC number, mac number is 00079AE20752
Click to expand...


Does that mean your camera should default to 169.254.07.52??

If so, set a static IP on your PC of 169.254.07.xx and then you should be able to connect to the cam
 
As far as I'm aware devices can have difficulty connecting to each other unless they are on the same subnet, e.g. if your camera has an address of 169.254.07.52 then you wont be able to communicate with it too well unless your PC has an IP address in the range of 169.254.07.xx

I would get my PC on the same subnet as the camera and see If i could then log into the camera and change it's IP to the 192.168.0.200 or something similar.
 
Are you not reading what I have put ??

YOU CAN NOT HAVE A 169.254.x.x ADDRESS AS THESE ARE NON VALID IP ADDRESSES GIVEN TO A DEVICE WHEN DHCP FAILS !!!!!!

You can not use any device set to a 169.254.x.x address doesnt matter whether you set it manually or not !

sheesh !

The camera gets that address as it either can not SEE the router, ie check the ethernet cable or the router is not giving out DHCP or the camera is not set to get an IP via DHCP !!!!!

:p

11. If you have a DHCP server on your network, check Use DHCP.
Otherwise, enter the IP address, subnet mask, and gateway of the
device, as provided by your network administrator (ie your router)
 
Last edited:
varkanoid said:
Are you not reading what I have put ??

YOU CAN NOT HAVE A 169.254.x.x ADDRESS AS THESE ARE NON VALID IP ADDRESSES GIVEN TO A DEVICE WHEN DHCP FAILS !!!!!!

You can not use any device set to a 169.254.x.x address doesnt matter whether you set it manually or not !

sheesh !

The camera gets that address as it either can not SEE the router, ie check the ethernet cable or the router is not giving out DHCP or the camera is not set to get an IP via DHCP !!!!!

:p

11. If you have a DHCP server on your network, check Use DHCP.
Otherwise, enter the IP address, subnet mask, and gateway of the
device, as provided by your network administrator (ie your router)
Click to expand...

Thanks for the input ill try this later, however the problem is I think by default the camera is not set to receive DHCP by default, because of this SConfigurator does not find it, it simply says 'no devices found', DHCP IS setup on my router, but the camera is NOT listed on its 'connected devices list' in the router, only my computers, ipad, iphone etc are on the list. Saying that I have 4 other IP cameras that dont show up on the list either, but they work as I knew the original log in for those cameras and assigned static IP's.,

Ill try the steps listed and try and make sense of them, the camera IS connected to the network as network activity is present on the LED lights, the camera is also powered by a POE device (does this make a difference?)

Thanks
 
PoE makes no difference to the network operations.

You could connect it all up and use a network scanner to scan the different ranges to see if something comes up. (Will take a while.)
 
varkanoid said:
Are you not reading what I have put ??

YOU CAN NOT HAVE A 169.254.x.x ADDRESS AS THESE ARE NON VALID IP ADDRESSES GIVEN TO A DEVICE WHEN DHCP FAILS !!!!!

You can not use any device set to a 169.254.x.x address doesnt matter whether you set it manually or not !
Click to expand...

Pretty sure this is incorrect. I'd go so far as to say that anywhere, chosen arbitrarily, between 1 and 254 would be fine for the first three octets. It's customery to go for 192.168.*.* at home, but you don't have to. Both the off-the-shelf dhcp servers I have running will let me set whatever numbers I want to.

Which is really funny, what with you using massive, bold, underlined yellow letters, while being wrong. :D
 
it's not a normal ip address, that's for sure....but...people set non-standard ip's all the time, it could have been deliberate for security for example.
 
varkanoid said:
YOU CAN NOT HAVE A 169.254.x.x ADDRESS AS THESE ARE NON VALID IP ADDRESSES GIVEN TO A DEVICE WHEN DHCP FAILS !!!!!!

You can not use any device set to a 169.254.x.x address doesnt matter whether you set it manually or not !
Click to expand...


You should read up on APIPA. It IS a valid IP address and thats the whole point. When a NIC is set to DHCP and does not receive a valid offer, then the NIC is allocated a 169.254.x.x address. WHat would be the point of allocating a "non-valid" IP address when it had that already (0.0.0.0). The only thing "wrong" with an APIPA address is that it's non-routeable, so only allows access to the local subnet. In the OPs case this is not a problem as he wants to get onto the camera to set it up with a routeable address.

Best bet would be to plug the PC and the camera directly together and run Wireshark to watch the traffic on the wire - that would quickly show the cameras IP, at which point you can config your NIC with an IP in the same subnet, log into the camera and set it's IP.
 
Get it on the same physical network.

Run the .exe tool which COMES WITH THE CAMERA to connect to it WITHOUT it needing to have an IP address assigned.

Follow the manual, configure device to use DHCP. Job done.
 
varkanoid said:
169.254.x.x is not the camera's default IP, its just taken that IP as it can't see your router to obtain a valid IP via DHCP

169. addresses are non valid IP addresses which are assigned when any device is trying to get an address via DHCP and fails. You can't use 169. addresses on a LAN.

Why on earth are you trying to change the router address ? Change the camera IP to a static address on your router's range - ie 192.168.0.10 or something !

Doh ! :rolleyes:

In fact I've just looked it up on the camera's website and in the installation guide for your camera it says the below. (pay attention to step 11 !)

1. Ensure that the camera is powered and connected to the Ethernet
network.
2. Start SConfigurator by double-clicking SConfigurator.exe on your
hard disk.
3. In the General tab, click Program Options.
4. Check Detect All Units on LAN.
5. Ensure that the VSIP Port is 5510; otherwise, click Default.
6. Ensure that the Discovery IP Address is 255.255.255.255;
otherwise, click Reset to Broadcast.
7. Click OK.
8. Select the Units tab, then click Discover. A device of type “Unknown”
with a 169.254.X.Y IP address appears in the Units box; it
corresponds to your new device.
9. Select the unknown device, then click Configure.
10. In the Reconfigure unit? confirmation window, click Yes.
11. If you have a DHCP server on your network, check Use DHCP.
Otherwise, enter the IP address, subnet mask, and gateway of the
device, as provided by your network administrator (ie your router)
12. Click OK. The device reboots with its new network settings.
13. In the Units tab, click Discover to update the list of devices and see
the S2600e with its new settings. The S2600e initial configuration is
now complete. You can now adjust the image coming out of the
camera.

If you are not getting a valid IP from your router its either not connected properly or you need to determine whether DHCP is on or not.
Click to expand...



OK iv finally found the time to do this, been so busy, ok I get to this point:

8. Select the Units tab, then click Discover. A device of type “Unknown”
with a 169.254.X.Y IP address appears in the Units box; it
corresponds to your new device.

But that doesnt happen it says 'discovery has not found any unit!'

The device is powered on and there is network activity on the LAN port on the back, it is connected to my netgear gigabit hub which in turn is connected to my sagam router (sky box), all the other IP cameras on the network work fine so it cant be this, suggestions why its not discovered?

My firewall is allowing the app full access as well.
 
You must log in or register to reply here.
Back
Top Bottom