DS-2CD2142FWD-IWS 2.8 mm WIRELESS "upgrading failed" error

Apr 27, 2018
6
0
I have a Hikvision Version 5.5.0 build 170725 for the DS-2CD2142FWD-IWS 2.8 mm WIRELESS dome camera. Hikvision sent me a link for V5.5.3 171025. Can I upgrade directly to this version or is there another version I must upgrade to first before I do this upgrade? ALSO...

Facts:
It has a 12 volt 2A power supply attached.


It has settings as follows:
IP Address LAN: 192.168.0.188
IP Address WLan: 192.168.0.211
PW: 12345scw

ONVIF:
User: admin
PW: 12345scw


Here is the problem: when the ethernet cable is attached to a non-PoE port and to the camera, everything works great and the wireless IP address is active 192.168.0.211. However, when I unplug the ethernet cable, the camera disconnects from the network and the network cannot find the IP address when we ping for it.

Furthermore, the camera works wirelessly when the ethernet cable is plugged in, but does not work wirelessly when the network cable is unplugged from the camera. The wi-fi gets dropped when the cable is unplugged.

Has anyone else had this issue and if so, will upgrading the firmware to V5.5.3 fix this issue?

Thank you!

WaterskierDave
 
when the ethernet cable is attached to a non-PoE port and to the camera, everything works great and the wireless IP address is active 192.168.0.211.
Furthermore, the camera works wirelessly when the ethernet cable is plugged in, but does not work wirelessly when the network cable is unplugged from the camera. The wi-fi gets dropped when the cable is unplugged.
How do you know it works wirelessly?
If it's by pinging the 192.168.0.211 address while the LAN cable is connected, that can be reached via the LAN interface, and internally forwarded across the eth0 and wlan interfaces.
The symptoms suggest to me that the camera is unable to authenticate and connect to the WiFi network.

See this as an example. The WiFi connection is not in use, there is no valid authentication - check out the traffic counters :
Code:
alastair@PC-I5 ~ $ telnet 192.168.1.105
Trying 192.168.1.105...
Connected to 192.168.1.105.
Escape character is '^]'.

Hikvision login: root
Password:


BusyBox v1.19.3 (2014-07-11 11:25:54 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

# ifconfig
eth0      Link encap:Ethernet  HWaddr C0:56:E3:A6:E8:88 
          inet addr:192.168.1.105  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::c256:e3ff:fea6:e888/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:403168787 errors:0 dropped:398 overruns:0 frame:0
          TX packets:822267492 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2921772539 (2.7 GiB)  TX bytes:4024453148 (3.7 GiB)
          Interrupt:27

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5049 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5049 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:439676 (429.3 KiB)  TX bytes:439676 (429.3 KiB)

wlan0     Link encap:Ethernet  HWaddr A0:F4:59:A8:F3:0D 
          inet addr:192.168.1.205  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

# Connection closed by foreign host.
alastair@PC-I5 ~ $ ping 192.168.1.205
PING 192.168.1.205 (192.168.1.205) 56(84) bytes of data.
64 bytes from 192.168.1.205: icmp_seq=1 ttl=64 time=1.24 ms
64 bytes from 192.168.1.205: icmp_seq=2 ttl=64 time=0.539 ms
64 bytes from 192.168.1.205: icmp_seq=3 ttl=64 time=0.544 ms
^C
--- 192.168.1.205 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.539/0.775/1.244/0.332 ms

alastair@PC-I5 ~ $
 
alastair@PC-I5

Hi Alastair,

Well, I am truly computer-illiterate. I read your reply but honestly don't understand what it means. I called Hikvision USA, only to discover that this is not a US model--ugh!! So they told me that their firmware upgrade will not work on this model. The current firmware is Version 5.5.0 build 170725 for the DS-2CD2142FWD-IWS I also had the tech guy at Security Camera Warehouse connect to my computer to see if he could figure it out but when I disconnect the Ethernet cable, it still drops the Wi-Fi. Is there any way you could help walk me through this?
 
I called Hikvision USA, only to discover that this is not a US model--ugh!!
Unfortunately, this seems to be a typical unhelpful response.
I read your reply but honestly don't understand what it means.
What I'm demonstrating is - that even though you can ping the IP address assigned to the WiFi interface when the ethernet cable is connected - this may not mean that the camera has actually connected to the WiFi access point.

It's fair to say that the WiFi configs on these cameras are not the most informative for status, also as I don't use WiFi I'm not the most experienced in it.
Somehow you need a positive indication that the camera has connected and authenticated to the WiFi.
This may well vary with the camera model, and firmware version, but on the 2432 that I tested, with valid and invalid WiFi SSID and key settings :

With invalid WiFi configuration, the 'Test' button at the WLAN interface IPv4 settings showed 'This address is not used'.
With correct WiFi configuration, the 'Test' button at the WLAN interface IPv4 settings showed 'This address is used'.
Somewhat counter-intuitive, but that's the only way it showed that the WiFi was valid and connected.
You must select the WiFi connection from the 'found list' that results from using the Search button in the WiFi tab of Network configuration, then configure it with the known, correct, key.
 
Hi Alastair,

Here is what I discovered:
With invalid WiFi configuration, the 'Test' button at the WLAN interface IPv4 settings showed 'This address is not used'.
With correct WiFi configuration, the 'Test' button at the WLAN interface IPv4 settings showed 'This address is used'.
Somewhat counter-intuitive, but that's the only way it showed that the WiFi was valid and connected.
You must select the WiFi connection from the 'found list' that results from using the Search button in the WiFi tab of Network configuration, then configure it with the known, correct, key.


When I test the system, it says, "This address is not used" which means the Wi-Fi connection is invalid. When I go to the wireless list it says my wireless is disconnected but I don't know how to connect it. Here's how it looks:

Wireless List
No.SSIDWorking ModeSecurity ModeChannelSignal StrengthSpeed(Mbps)Connection Status
1LakehouseManageWPA2-personal892150Disconnected
2LakehouseManageWPA2-personal351150Disconnected
3DIRECT-ky[BD]EM59ManageWPA2-personal1145150Disconnected
4xfinitywifiManagenot-encrypted1143150Disconnected
5HanieManageWPA2-personal1143150Disconnected
6LakehouseManageWPA2-personal227150Disconnected

Maybe I don't have WPA-2 security? Not sure what to do next. In the past, it has shown "connected" but when I unplug the Ethernet cable, there is no wifi connection.
 
Maybe I don't have WPA-2 security?
The list shows that most of the access points do - it's getting that info from the WiFi itself.

Do you use the same WiFi WPA2 key for all the access points?
Long shot - I'm wondering if you have a key that's either too complex or has characters maybe not supported by the camera.
Is there one access point you could experiment with by temporarily setting a simple alphanumeric key, to see if the camera will then connect to it?
 
Hi Alastair,

Many thanks for getting back to me, much appreciated!! I do use the same WiFi WPA2 key for all the access points. My password is 4 numbers and four letters, no weird characters. It's an 8-digit password. Don't know what else to do...