1. Home
  2. UK Do-It-Yourself Forum
  3. Setting up Hikvision DS-2CD2142FWD-IWS wi-fi

Setting up Hikvision DS-2CD2142FWD-IWS wi-fi

I've spent hours (days) on this and have got pretty much nowhere so...

I have three of these cameras, one of which will communicate over wi-fi with no problems, the other two which will only connect if the Ethernet cable is also being used. Unplug the Ethernet cable and I lose the connection.

I have set the router (Fritz!Box 3390) to accept all wireless connections while I'm doing this and have set it to link the MAC address to the same IP address each time the camera connects.

When I have activated each camera I have set its IP address to the one I have reserved in the router. I have unticked DHCP on the wi-fi side (which has a separate MAC address) and have given it another IP address. However, one version of the instructions says to give it the same IP address as the wired side. Neither seems to solve the need to have the Ethernet cable attached to get a wi-fi connection.

All three cameras have been upgraded to the latest firmware so it seems odd that one will connect without the cable and the other two will not. They're all UK spec and sourced in the UK.

Anyone able to offer any kind of insight into what is happening (or not happening!)?

Reply to
F
Loading thread data ...

Instead of giving static IP address to each and setting it in router, just enable DHCP and allow router to give them IP address.

Reply to
Raj Kundra

Just a thought, but can you ping the 2 cameras in question and get a reply back. Also I take that they are all on the same IP range. In my case 192.168.0,12 etc.

Reply to
BobH

You are using different IP address's for each camera aren't you? Stupid question but the only really stupid question is the one that isn't asked...

That sounds as if you are giving the camera two IP address's. OK it does have to interfaces but they may just be a single one at the IP layer.

Seems you've tried setting a single IP address on the wired and wireless interfaces. You have checked that MAC/IP set in the router is the same as the MAC/IP in the camera with the same MAC and that the wired/wireless MACs haven't got mixed up in a camera or across the two that don't want to play?

Reply to
Dave Liquorice

Yes also of course it would be helpful if you could tell us if its just the first one enabled that connects or always the same physical one if they are all physically in the same place. You really do need the addresses to be dynamic or chaos usually ensues whether they be printers, cameras ofr for that matter toasters! Another issue, rouund here at any rate is that the wifi bands are so stuffed full of things that getting one connection is a win most of the time. Brian

Reply to
Brian Gaff

I've spent several more hours playing after reading the suggestions here and have got fairly reliable wi-fi connections on two cameras. The third just refuses and so I've got it running on a homeplug.

Of the other two, one continues to connect wirelessly, directly to the router, without any problems and the other is now connected wirelessly through a wireless homeplug which is plugged in close to it.

Pinging the two wirelessly connected cameras is successful on *both* IP addresses they have allocated to themselves. Does this explain anything (it means nothing to me...)?

Reply to
F

Thanks, done that but they still won't connect reliably.

Reply to
F

Three cameras, six different addresses.

The configuration pages show IP entry fields for WAN and LAN.

Thanks. Yes, the addresses all match...

Reply to
F

My NAS has just emailed me this...

freenas kernel log messages: arp: 192.168.178.22 moved from bc:ad:28:cd:b9:00 to 28:f3:66:8c:de:46 on epair0b arp: 192.168.178.21 moved from 00:95:69:a9:7b:f0 to a4:14:37:7b:73:bf on epair0b arp: 192.168.178.22 moved from 28:f3:66:8c:de:46 to bc:ad:28:cd:b9:00 on epair0b arp: 192.168.178.22 moved from bc:ad:28:cd:b9:00 to 28:f3:66:8c:de:46 on epair0b arp: 192.168.178.21 moved from 00:95:69:a9:7b:f0 to a4:14:37:7b:73:bf on epair0b arp: 192.168.178.21 moved from a4:14:37:7b:73:bf to 00:95:69:a9:7b:f0 on epair0b

-- End of security output --

Each switch is between the Lan and Wlan MAC addresses within each of two cameras. Weird!

Does it throw any light on what's happening? Why would they be switched and why is the NAS reporting it?

Reply to
F

I should have added that these are the two problematic cameras. Nothing from the one that connects wirelessly without any problems.

Thinking back to installation, the two cameras with problems were missing a small cable-tied bag of brown granules (desiccant?) inside the housing that was present on the OK camera. Clutching at straws here?

Reply to
F

Are there any other wireless clients (phones, etc.) getting IP addresses via DHCP that conflict with your manually assigned ones? I'm sure you'll know this, but if you enable DHCP and also use static IP addresses, you need to make sure that the DHCP range isn't going to overlap with them. Unless DHCP servers are clever enough to detect conflicts nowadays? They certainly weren't 'in my day' :-)

Reply to
Dan S. MacAbre

Thanks, but no overlaps/duplicates.

Reply to
F

Only thing I can think now would be to check the router's configuration pages to see if each device's MAC address is listed as having made a data link layer connection. That's if I'm thinking of the correct OSI layer, and that's what they actually display :-)

Reply to
Dan S. MacAbre

Well it's what you would expect if you've (at different times) had the same IP address on different interfaces, sounds like the NAS is running arpwatch or similar and is noticing the move.

If the correct IP address ends up on the wifi interface, it should work, assuming the wired interface is then unplugged, I think I'd be tempted to either disable the wired interface, or set it to DHCP and leave the wifi on fixed address, or leave all interfaces on DHCP and reserve an IP address to the wifi MAC address of each camera.

Are the cameras pingable at any stage?

One comment which could be neither here nor there, but usually if you buy several devices all at one, the would have similar or maybe even consecutive MAC addresses, doesn't seem to be any similarity with yours

Reply to
Andy Burns

En el artículo , F escribió:

Sounds like you have both the wireless and the LAN connected. Don't do that. Once wireless is working unplug the wired.

The logs showing change of MAC address may be because the wireless link to the router has dropped out so the camera falls back to the wired connection.

I've got a crappy Foscam knockoff here. That allocates the same IP to wired and wireless. If you connect a cable, you're meant to disable the wireless in the camera setup (or it's done automagically - can't remember).

Reply to
Mike Tomlinson

So it's watching rather than initiating?

Unplug the wired side and the camera disappears from view.

Unfortunately, the interface doesn't offer the option to set wired to DHCP. That's only offered on the wireless side.

I've got fixed addresses for wi-fi but that dioesn't seem to have made any difference.

Yes, but not very reliably on wi-fi addresses.

They're similar but not close.

Thanks for the suggestions: why has wi-fi got to be so difficult?

Reply to
F

yes.

If you've got packet loss showing up on pings, other communication with them is going to be difficult. if you use "ping -t cam.ip.addr" and leave it running for a few minutes, then stop it with control-C, what %loss does it show?

Reply to
Andy Burns

The simple answer is 'it varies a lot'!

I've had a play with a wi-fi strength app on my phone and it may be that the signal strength is just not up to it with the two problematic cameras, with the third one seeing a slightly stronger signal than those two. I did say 'slightly' but I suppose there are thresholds.

Reply to
F

Anything above 1% is going to hurt, ideally it should be 0 at all times for an in-house network whether ethernet or WiFi.

Tried different channels on the Access Point? I presume the cameras are

2.4GHz rather than 5.2GHz? Do they have internal or external aerials?
Reply to
Andy Burns

HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.