Unable to log into Statis IP GW IP Camera, No Reset Button

[shanked]

Hey Gang,

I am replacing my existing IP cam as it stopped working. I bought two used GW Security Cameras off a guy locally.
The Camera it self doesn't have any reset button, I tore it apart yet, still didn't find a reset button.

So I am trying to reset the camera now somehow.
I can see the camera turning on the IR turns on, my network switch (POE Enabled) sees it online, however its getting a 169 IP. My houses is 192. I tried to still go to the full 169.254.139.253 and still unable to get into the camera. I just get page cannot be found. I used all the network camera discovery tools known to me (Config Tool, IP Camera search tools, AJ tools) and none of them picked up that camera.


I then tried to connect the Cameras directly to my laptop (using a POE injector in the middle) I still got a 169.254.139.253 IP and i couldn't navigate to the camera's web-page UI. I even manually assigned it a 192.168.1.72 IP and still couldn't connect to it

I ran NetStat and got the below output. I tried to Navigate to all the IP with the Port # and didn't work

TCP 169.254.139.253:80 Basement-Server:46377 ESTABLISHED
TCP 169.254.139.253:80 Basement-Server:46378 ESTABLISHED
TCP 169.254.139.253:46377 Basement-Server:http ESTABLISHED
TCP 169.254.139.253:46378 Basement-Server:http ESTABLISHED
TCP 192.168.1.25:3389 192.168.1.24:63262 ESTABLISHED

I'm literally loosing more hair then I already have lost trying to connect to these cameras, any tips suggestion would be greatly appreciated!

Camera Model #'s

1) GW-5091IP
2) GW5167MIP

Let me if you need any more pics or have more questions.

 

[TonyR]

If that screenshot is of your PC's IP which is 169.254.139.253 and the PC is set for DHCP then it means there is no static IP assigned to it or the PC is not receiving an IP from your router's DHCP server. We'll get back to that later, but first:

According to manual for the GW-5091IP, these are the defaults:
Default IP address: 192.168.0.123 , Username: admin, Password: 123456
Try this:

1. Remove power from cam.
2. Run cam Ethernet DIRECTLY to Ethernet port on PC.
3. Set PC to static IP 192.168.0.100, subnet mask of 255.255.255.0 (for now)
4. Install Fing Desktop on your PC.
5. Power up cam
6. Wait 2 minutes
7. Run Fing, do network scan.
8. When cam is found, do a port scan.
9. Report results.

 

[holiday]

y not post a pic of the pcb and let ppl here identify where are the possible "reset pins" which may not be soldered on it.

 

[SouthernYankee]

The IP address 169.254.139.253 is not a local address,

======================================
Private ip addresses. Local IP addresses. These addresses are NOT used by the internet. They are for your local home/business network.
10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255

Note there is no reason to redact local ip addresses when posting.
-------------------------------------

169.254.0.0/16 addresses explained
By stretch | Wednesday, September 24, 2008 at 12:01 a.m. UTC
Occasionally you may encounter a host which has somehow assigned itself an IP address in the 169.254.0.0/16 range. This is a particularly common symptom of Windows machines which have been configured for DHCP but for whatever reason are unable to contact a DHCP server. When a host fails to dynamically acquire an address, it can optionally assign itself a link-local IPv4 address in accordance with RFC 3927. Microsoft's term for this is Automatic Private Internet Protocol Addressing (APIPA).
The purpose of these self-assigned link-local addresses is to facilitate communication with other hosts within the subnet even in the absence of external address configuration (via manual input or DHCP). Unlike in IPv6, implementation of IPv4 link-local addresses is recommended only in the absence of a normal, routable address. Hosts pseudo-randomly generate the last two octets of the address to mitigate address conflicts. Because of the broadcast nature of some local networking protocols (for example, Microsoft's NetBIOS), hosts may be able to detect one another even without any preexisting knowledge of the address scheme.
However, in practice, these auto-configured addresses tend to do more harm than good, particularly in SOHO networks. Receiving an IP outside of the expected subnet carries more potential for confusion and frustration for end users than does receiving no IP at all.

 

[TonyR]

+1^^.
If that screenshot is of your PC's IP which is 169.254.139.253 and the PC is set for DHCP then it means there is no routed IP assigned to it or the PC is not receiving an IP from your router.