NEXTECH QC3908 WIFI Security Camera

General Chatter
1

Happy New Year All !

I Have a NEXTECH QC3908 Security Camera recently installed. I had to use a specific app on my phone, Samsung and the app is called Tyua.

Works great on the app but the connection to PC version drops out every 5 seconds.

It’s a weird setup. I had to set it up through app on phone to connect to my router. Which is fine, but I can’t actually see it on my router’s LAN. It’s has a weird IP address, 101.185.156*.

Just wondering if anyone is familiar with these types of cameras. I’m asking here as want to use it in WD as a webcam.

Many thanks

Chris

2

Is 101.185.156.x your home broadband IP address? That address is issued by Telstra in Western Australia so that looks possible.

If so then it’s possible that the app is somehow accessing the camera from outside your router using your external IP address.

3

Yes it is. Not sure how my camera is accessing outside the router. It’s all done through the app is hit and miss.

4

The camera might be using UPNP on the router to open a link for the app to use. The camera should still have an internal address though. Does your router have a management interface that allows you to see all the DHCP issued addresses? The camera should show up in that list if you can access the list.

5

I can’t see my wireless IP camera on my router DHCP list either, in fact I can’t remember how I discovered the local IP address. But I set it up with a wired connection first, so maybe I just guessed it would be close to that. . .

Can you see the camera settings if you type http://101.185.156.x in your browser?

6

If it’s been given a static address it should still show up in the connected devices list.

7

You would think so, but no. . . :roll_eyes:

It’s an old BT Home Hub 5. . .

8

You could try using Angry IP Scanner to scan your sub-net and see what you can find that you can’t identify.

9

Yes as Admin said use an Ip scanner to find all the devices on your network

10

I think (hope!) that there is only the camera unaccounted for. . . but maybe I’ll check, just in case :laughing:

11

Cheers. Yes, I have full access and a fairly good understanding of how to navigate it. (I think lol)
Can’t see the device at all, however, saying that are a lot devices I don’t recognise as they don’t say what they are in the list.

12

Sorry, replied to instead of Chris. But no, I cannot see it using the assigned IP address.

13

Hi
If you know what the ip is just open a browser and type the ip in the url and it should open to a page

15

This is the IP registered on the device, 101.185.156.* Cannot find any IP on my router for it

16

If you camera is not showing up, then thats not the IP address and thats your public ip address.
When you used the IP Scanner did it scan you local network?
whats the ip of your PC? as the camera will have a similar IP address eg: 192.168.0.1, 10.10.10.1,10.20.30.1

17

There may be an alternative way to find the IP address. All network devices have a MAC address (Media Access Control - MAC address - Wikipedia). This is more or less globally unique to the device, although these days that’s not strictly true but we won’t worry about that here.

Think of the MAC address as a unique identifier for a piece of physical hardware, e.g. ethernet or wifi controller port. An IP address is assigned to the port but the IP address only needs to be unique to the ‘network’. The port may change IP address many times a day but, in most cases, the MAC address will never change.

A MAC address has the format aa:bb:cc:dd:ee:ff where the letters are hexadecimal digits (0-F). The camera app might display the MAC address as an identifier for the camera and your router may also display the MAC address associated with each IP address that’s connected. So you might be able to find the internal LAN address of the camera this way by matching up the app and router info. Sometimes MAC addresses are displayed just as a 12 digit string with no colons between pairs.

If that doesn’t work, there may be another way, but it’s less reliable. If your router displays the MAC address for each IP address then you can look up the vendor associated with the hardware the MAC address is assigned to, e.g. at https://www.macvendorlookup.com/

If you copy the MAC address for an IP address into that web site (there are other lookup sites too) it will tell you who manufactures the hardware associated with the MAC. So if you’re lucky you might find a MAC address on your network that’s assigned to NexTech. I’ve had a quick look in the database though and they don’t seem to have their own hardware assigned. That’s not unusual, because many device manufacturers buy in ethernet/wifi modules from another company so the MAC will belong to the original equipment manufacturer rather than the camera/other device manufacturer.

You can still sometimes be lucky, e.g. the app might refer to the network card type which might match up with something you see in your router.

Alternatively, you could trawl through all devices connected to your router and identify them by known IP/MAC address. Many routers allow you to name each device so you can see what they are next time you look. This obviously takes time to do, but (in my opinion as a paranoid ex-cyber-security manager) is well worth doing. It’s always best to know what’s connected to your network! Once you identify as much as you can, start tracking down the unknowns, by turning things off temporarily if possible and seeing what disappears from the network.

That ends todays lesson in networking :rofl:

18

I did use Angry IP to confirm, as expected, that the IPCam was the only thing missing from my router’s DHCP list :wink:

19

I think you have a faulty router!

20

BT are a law unto themselves. . .

Maybe lack of IP address is why they are called security cameras :slightly_smiling_face:

21

I wondered if your camera was using RFC 2549 but even that’s IP based.