Link>Welcome!
- What Hardware version is your DCS? Look at the sticker behind or under the camera.
I cannot tell you as I'm currently a hundred miles away from it. I'll check when I'm there next. However, it was just purchased two months ago, so I would expect it would be the latest.
- Link>What Firmware version is currently loaded? Found on the DCSs web page under status.
The firmware is 1.01.02. I see there is now a 1.02.02. I'll give that a try. Thanks.
- What region are you located?
I'm in the USA.
What Mfr and model is the main host router?
It's a Asus RT-AC87U, running DD-WRT v3.0-r29440 std (04/11/16). The RT-AC87U is a dual-band, 802.11ac router, with beamforming enabled on both bands.
What wireless modes are you using?
The router is running in mixed mode, so 802.11b, g, n, ac.
What is the distance between the Camera and the main host router?
It is perhaps 40 feet. It had been working fine with this router at this distance until one morning it just stopped and images retrieved are empty. And the web application in the camera works fine and is snappy indicating it has a fine connection.
How many other wireless devices do you have connected to the main host router?
Perhaps 6-7 low bandwidth devices (nest thermostat, nest protect, 2 other D-Link cameras, Chumby, a couple laptops and android devices when I'm there). Also TiVo, Sony Blu-ray, Raspberry Pi on the Ethernet.
- Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
- Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?
Other wifi APs are a hundred feet or more away and site survey shows that they use different channels. There is nothing else nearby on the 5ghz band. There is a 2.4ghz phone in the house, but it is rarely used and is not being used now. Again, this was working fine (100% reliability) and then just stopped.
I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.26 DHCP
I use DHCP, but with static lookup by MAC addresses. I know there's no problem with the IP address as I can connect to the web server just fine.
Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com
UPnP is enabled. I think UPnP port forwarding is irrelevant because it fails on the local network which doesn't need port forwarding.
PC Web Browser Configurations
What browser are you using?
Try Opera or FF? If IE 8, 9, 10 or 11, set compatibility mode and test again.
Disable any security browser Add-ons like No Script and Ad-Block or configure them to allow All Pages when connected to the camera.
Clear all browser caches.
Java up to date?
Well, my main test case is using the wget command line browser which only retrieves the JPG from http://<cameraname>/image/jpeg.cgi. Thus there is no cache, no plugins, no Java. However, it also fails in Chrome on Linux, Chrome on MacOS and Firefox on MacOS. In particular, the cameras web app in Setup->Image Setup which shows an embedded video (as motion jpg) also fails, and doesn't use any plugins. It shows a broken image icon. It also fails when trying to stream RTSP to VLC, and it fails in the Android app "IP Cam Viewer" (which I recommend) and which works with my two other D-Link cameras.
I still think it's a hardware error. Does anyone think differenly?