pcarfan 0 Posted January 17, 2017 It's a Q-see 818 NVR, router just recently rest to factory setting with no mods made since. Router is ASUS RT AC-68. I only have one camera hooked up for now, and I set the streaming video qualities to lowest possible. With that it's only sending out 155Mb/s. Yet, as soon as I plug the Ethernet to the router, I cannot access wifi in any of my other devices. Yet, I could view the camera via LAN. So, it's just hogging all the LAN 'bandwidth'. How could it possibly do that with only 155Mb/s uploading? I am a complete newbie, so please respond at that level. I could Google also, so I can decipher more complex responses, within Google's capability. What could I do fix this issue? What are potential culprits? Other than the camera, the only thing being used when it crashed this morning repeatedly was my ipad. Nothing else. No one watching Netflix etc. Thank you! P.S: Before, it took a few hours for the router to crash, now it's immediate. Share this post Link to post Share on other sites
pcarfan 0 Posted January 18, 2017 Today it is working fine. The immediate failure started just prior to my first post. On that day, I checked the NVR carefully. NETWORK LOAD (under the folder REMOTE DEVICE INFO) jumped up as soon as I plugged in the Ethernet. Today it does not. It only moves up when I actually view my camera via LAN or WAN and that too it spikes up very little. I don't know what happened, I didn't change anything, it seems to be fine. However, for the previous two days, it too 24 hrs prior to it crashing the router. So, let me see what happens in the next few days. Share this post Link to post Share on other sites
pcarfan 0 Posted January 19, 2017 Update Router is down again. I cannot access wifi with my iPads, yet I can view camera over LAN. Checked data load on the NVR, it is very high around 150 Mb/s. It stays the same even when I am not viewing the camera through LAN. So, something is causing the NVR to send out data at max bandwidth constantly. Could improper port forwarding or something going wrong with setting a static IP for NVR , cause this behavior. I doubt it very much as I can view the NVR via LAN even when I can't access LAN with any other device. But, I was asking because, when Q-see support remotely logged in to set up LAN/WAN for me, I know they went into the router interface to port forward and set a static IP. But, when I called Asus, they recommended setting it to factory setting, so we reset the router thus cancelling the port forwarding and static IP. However, even after the reset as I could access the NVR via LAN/WAN, I did not bother with it. I will be calling the excellent technical support at Q-see later today or tomorrow and will update. If anyone has any ideas in the mean time. Share this post Link to post Share on other sites
pcarfan 0 Posted January 19, 2017 My Asus router has real time graph also. My goodness, YouTube video spikes it up, the I turned on Netflix and it jumps to megabit range. I knew I had Netflix, Hulu, YouTube and some others open all at the same time and my internet service and router never skipped a beat. 150mb/s cannot be crashing the router. Share this post Link to post Share on other sites
pcarfan 0 Posted January 20, 2017 Yesterday the q-see guys installed something called 'Telnet fix" He remotely logged in, downloaded a file, did a bunch of things. Sort of like sending new data to the NVR. Not a firmware upgrade but sort of like a new packet involved. My NVR said it was processing something, rebooted. The scripts that was running on my computer said 'success' or something like that. He said that implied the 'Telnet fix" was successfully installed. Reading about telenet and security cameras. I see there were some hacking issues with these cameras with something called the root password being easily accessible. I don't know how hacking works, but I just installed my camera. But, it may have nothing to do with hacking. So, far so good. Will know for sure in 12 hrs. Router never worked for a 24 hr stretch after the cameras were installed. UPDATE: That fixed it. Share this post Link to post Share on other sites