Trouble setting up an I.P. Camera on network

Do you have a laptop?

If so hook up an cable between the camera and laptop directly. And ensure you are seeing that the network adapter has a connection if not you may need to use a crossover but it should auto sense hopefully. (depending on how the camera is getting power of course)

Ensure you have done a reset of the camera to make sure it is back at its standard IP.

Manually set your IP address on the laptop to 169.0.0.1 with a subnet of 255.0.0.0 download a utility called superscan and set it to scan everything from 169.254.0.1 - 169.254.254.254 if it doesn't find it you can try widening the range further if you are sure it should have a 169 IP.

Once it's found you should then be able to set the static IP for your network or ideally just use DHCP and reserve the address to save any hassle next time.
 
Thanks n30_mkii, unfort im on a mac laptop, iv setup my old router to connect my mac and the camera too, any free port scanners for mac that will work ?

EDIT Im using angry IP Scanner, so far no go my router has defaulted to 192.168.2.1 my mac is .2 at the end and the camera just aint showing up on the scan :( lost at what to do. Is the POE device stopping access somehow ? on the DHCP list in the router only my mac appears

EDIT2: Just done what u said in your post n30 its currently scanning .... the mac address ends 54 so im going to assume 169.254.5.4 should be a hit maybe :s soon find out
 
Last edited:
Indeed doing that you should hopefully be able to contact it, you obviously won't be able to contact your router whilst set on a different IP range but fingers crossed. I'm not familiar with Mac's but someone else may be able to advise on a port scanner if you have any issues.
 
Its so weird the manual says:

DHCP (Dynamic Host Configuration Protocol) allows devices and computers connected to a network to
automatically get a valid IP configuration from a dedicated server.
The APIPA (Automatic Private IP Addressing) scheme, available on the Windows operating systems,
enables a device to assign itself a temporary IP address.
At startup, an edge device searches for a valid IP network configuration. The device requires this
configuration prior to starting its functions. The network configuration for Nextiva devices consists of:
 An IP address
 A subnet mask
 A gateway
By default, the device tries to contact a DHCP server. If DHCP configuration fails—if the device does not
find a server or if it cannot get a configuration from it within one minute—the device assigns itself
temporary network parameters based on the APIPA addressing scheme. This scheme allows a device
to find a unique IP address until it receives a complete network configuration, either manually or from
a DHCP server.
A device in APIPA mode does not reside on the same subnet as the other devices on the IP network;
therefore, it may not be able to view or be visible by the other devices. Devices use the following
temporary APIPA configuration:
 IP address: 169.254.X.Y (where X and Y are based on the last two digits of the MAC address of
the device)
 Subnet mask: 255.255.0.0
 Gateway: 169.254. *. *
A device is in APIPA mode:
 After receiving a duplicate IP address
 When the DHCP server does not have any available IP addresses
DHCP configuration is automatically enabled after a factory reset.
Click to expand...

Which says to me it should just get assigned a DHCP , which it doesnt, is the POE stopping that ?? I cant not use a POE unfort as its not particularly cheap to get a 'normal' power supply for it, its running fine according to the lights on the back.

AGHHH just want it to darn find it !! lol
 
Actually scatch that iv found the specific manual for mine and says:

At startup, an edge device searches for a valid IP network configuration. The device
requires this configuration prior to starting its functions. The network configuration for
Nextiva devices consists of:
An IP address
A subnet mask
A gateway
The device first looks in its local memory. If no configuration is found, it tries to contact a
DHCP server. If DHCP configuration fails—if the device does not find a server or if it cannot
get a configuration from it within one minute—the device assigns itself temporary network
parameters based on the APIPA addressing scheme. This scheme allows a device to find a
unique IP address until it receives a complete network configuration, either manually or
from a DHCP server.
A device in APIPA mode does not reside on the same subnet as the other devices on the IP
network; therefore, it may not be able to see or be visible by the other devices. Devices use
the following temporary APIPA configuration:
IP address: 169.254.X.Y (where X and Y are based on the last two digits of the MAC
address of the device)
Subnet mask: 255.255.0.0
Gateway: 169.254. *. *
A device is in APIPA mode:
The first time it boots up
After receiving a duplicate IP address
After a hardware reset
When the DHCP server does not have any available IP addresses
After loading the default parameters
DHCP configuration is automatically disabled after a factory reset.
Click to expand...

so no dhcp then, but the scanner has not found anything on the port i think it would be ?
 
Edit....
Scrap the above I just read your re-post...

Has it got a link light on the router for the camera?
Has it got a link light for network on the camera?

Also it may be that the camera doesn't respond to a ping request, but can you browse to it's web administration if that is whats used to administer it?
 
Last edited:
The router doesnt have lights on as its crap but the camera does and its lit up when plugged in power and data, if unplug the data cable from the router (but leave the POE in the camera) the orange one goes out so im led to believe it is communicating. The status LED on the back of the cam is flashing green.
 
See above...

Also it may be that the camera doesn't respond to a ping request, but can you browse to it's web administration if that is whats used to administer it?
 
Yeah the manual says that but I dont know its ip address to enter this in the browser, so its catch 22, iv tried 169...etc and the last 2 digits of its mac address but no go :( properly weird, MAYBE its buggered but I shouldnt of thought so ? stuck as a pancake
 
There might be an option in your port scanner to check what ports are open even if a device doesn't respond to a ping.

Might be worth linking to a copy of the manual and dropping a link in the thread. It's looking more likely that it may be duff but fingers crossed.
 
I don't seem to be able to get to the manual at the moment. A simple ICMP should do the trick. It isn't looking good tbh I will let you know if I think of anything else, perhaps someone else who has one may post in the mean time :-)
 
You must log in or register to reply here.
Back
Top Bottom