Windows 10 Aniversary Update

[jaybolin]

Hello,
With the latest "Anniversary Update" from Microsoft I now longer see my IP2M-841B cameras listed in IP config. They show up fine in other computers that were not updated or are running Windows 7. I have read that Microsoft is aware of the problem but has not yet issued a fix. Is there anything I can do in the meantime to get them back on the updated computers?

jaybolin

[vbdino]

Got problems too, as the pictures shows in my own thread.

[Techie007]

I have never used the Amcrest IP Config tool, preferring to just go to my router and get new camera's IPs from the DHCP lease table and then assign static leases. However, that said, I just installed it and gave it a spin to see what would happen. I am disappointed at what I found. The problem appears to be Amcrest's fault. First off, they are aggressively port scanning (hacking) to find the cameras. A much better method would be to design the camera to respond to some broadcast UDP discovery method. Secondly (and this is where the Windows 10 incompatibility may come in), it fails to detect the correct IP range to scan. Which is also Amcrest's fault as that information remains readily available in Windows 10.

So, what can the end user do in the meantime to make it work?

1. Press [Ctrl]+[Shift]+[Esc] to start Task Manager.
2. Go to the Performance tab.
3. Depending on whether your computer is connected via wired or wireless, click on the Ethernet or Wi-Fi option on the left sidebar.
4. On the lower-right, look for IPv4 address.
5. When you find it, remember the first three sets of digits. For a home network, something like the following would be expected: 192.168.0, 192.168.1, 10.0.0, 10.0.1. For some silly reason, the IP Config software defaulted to the rarely used address space of 172.23.2 on my PC—which of course doesn't work.
6. Switch back to IP Config and click [Settings].
7. For Start IP, type in the first three sets of digits you remembered, followed by ".0" (without quotes). For example, when you're done, you should have a four-digit number like 192.168.1.0
8. Click [OK], and click [Refresh]. The list of cameras on your network should now successfully populate.

I would be curious to know where you found a place stating that Microsoft was aware of the problem though.

[jaybolin]

Update: by entering the ip address of each camera on my network and by checking the "search by IP domain" I am able to access the cameras.

Here is a link to one of the articles that stated that Microsoft knows about their breaking many webcams...
http://arstechnica.com/information-tech ... t-webcams/

[Techie007]

You shouldn't have to enter the IP of "each camera"; just use the IP from one of the cameras and replace the fourth (last) block of digits in Start IP with 0, and ensure that IP Number is 255. Unless you've got cameras spread over several subnets (and you would know if you did), it should automatically find all the cameras for you this way without you having to enter the IP of each camera to find them one at a time.

Thanks for the link. That's a completely unrelated issue. Microsoft changed some things in the video stack of Windows to better support programs sharing access to a USB webcam. The new (and half-baked) code doesn't support compressed video streaming from a webcam, which breaks functionality in software expecting a compressed video stream. But none of that is used during the operation or configuration of the Amcrest cameras. Here, it is failing to detect the cameras purely due to a networking issue between IP Config and Windows 10—most likely, a new issue with the broadcast function, while the IP scan feature has always used a bogus IP range (thus contributing nothing all along).