![]() |
Remote viewing of DVR My security DVR is connected to my home network through router "minifig". I can connect to minifig on my phone, and use the app to view the DVR using its local IP address, 192.168.1.12. But how can connect to the DVR from an external location? The challenge is that minifig is connected to my shaw modem/router. If you can advise on what to configure, and on which device(s) (shaw and/or minifig), that would be greatly appreciated. I know what my external IP address is. Thanks! |
Not familiar with "minifig" but the general process for enabling a DVR or NVR for remote access via WAN is the same: 1. Create a Port Forwarding Rule for the corresponding DVR/NVR ports in the Router. Alternatively you can set the LAN IP 192.168.1.12 as the DMZ. 2. Create a connection in the client with the Port(s) (same as identified in Step #1), Credentials, and most importantly the Modem IP address. Note: While we are talking about Modem IP's, if you have a Dynamic IP address from your ISP, consider using DDNS if your head end supports it. Usually the manufacturer will offer and host this for free. It will save you headaches in the future. Good luck and let me know if you have any further questions. |
Haha, "minifig" is the name of my wireless network. So I'm referring to that router (Linksys brand) as minifig. Do I need to set up port forwarding on the shaw router or on minifig? Sorry, you will need to dumb it down for me because while I've dabbled in home networking in the past, I haven't done this stuff in years! |
Ok that makes sense now that I re-read what you typed :) Port Forwarding is to be done on the Shaw Modem/Router. |
Quote:
I think I can figure out the IP address of "minifig" in relation to the Shaw router, but I don't know the IP address of the DVR recorder in relation to the Shaw router. |
The IP of your DVR seems to be 192.168.1.12 if you can access this address locally within your LAN. The port is defined within the DVR network settings. Usually there are 2 that need to be forwarded. Once you figure out the ports, all you need to do is set up the port forward on your Shaw unit using the DVR IP of 192.198.1.12 |
Use the Port(s) identified in the Network screen of the DVR. They should be configurable but should also have a default. Usually the default is fine as DVR manufacturers choose them not to conflict with ports of other common devices. Forward the port(s) 192.168.1.12 and enable TCP/UDP (or "all" if there is a choice). Most importantly, ensure the Port Forwarding rule is enabled after creation. |
I don't think I'm explaining my network properly. Check out this quick sketch: https://farm2.staticflickr.com/1700/...7c09641d_z.jpg I think I need to: 1) forward port 90 on the Shaw router to the "minifig" router 2) forward port 90 on "minifig" to the DVR I know step #2 is functional because I can access the DVR from my phone when my phone is connected to the "minifig" network, using 192.168.1.12. I think I have done step 1 correctly, based on this screenshot (while laptop is connected to shaw router): https://farm2.staticflickr.com/1698/...e5abc839_z.jpg I think I have minifig's external IP correct based on this screenshot (MAC address of minifig starts with C8D7): https://farm2.staticflickr.com/1591/...35046cd9_z.jpg Maybe there is something I'm missing between steps 1 and 2?? |
Why is "minifig" on a diff subnet? |
u have a router behind a router. do u have anything that is actually connected to the shaw router? if its just ur own linksys router connected to the shaw modem/router and everything else connected to ur own linksys router then i highly suggest u ask shaw to bridge ur modem so it disables its internal router. this way all u need to do is set the camera on a certain port number, then on ur own linksys router port forward that port number + what ever IP the camera is using. u can then access that camera externally by httpe://externalip: port into the address bar to access ur camera ur other way if u do plan to use the shaw modem/router is to have ur linksys set as access point with DHCP disabled so the shaw router does all the ip distributing. then do the above again but on the shaw router. |
need to fix the network first. so the shaw modem/router and the minifig is on the same network. the way you have it now is complicated to get what you want it to do. i would suggest what TOPEC is saying. switching the minifig to AP mode. (disabling the DHCP). This might cause problems if your DVR is using at static internal ip |
Thanks to all those who have offered suggestions so far! Quote:
Looks like I will need to disable DHCP on my linksys router... If everything gets messed up, I might just give up and revert back to my previous settings! :p |
i can probably help you set it up if you can't get it running. |
you should find out on the DVR which ports it requires to go out. every brand is different. i worked with alot of brands. i assume you are residential internet user, even if you are able to port forward and get it working, you probably have a dynamic IP address. what that means is: after 'x' amount of time. (days. weeks. etc.) your IP will change and you will have to port forward all over again. alot of modern cctv dvrs have a type of dns relay server. so you can give it a name and you dont have to worry about port forwarding. something like how teamviewer works? |
What DVR do you have? Some have a "cloud" function where you don't need to connect directly to it; the DVR connects to the manufacturer's server, and your app connects to the server, and they route that way. Other than that, I have the same setup as you - Shaw router used as WAP and a separate internet connection for my son's computer, then a second router behind it for the whole home. I set my second router's WAN IP as a DMZ in the Shaw router (so in your case, 192.168.0.12 would be the DMZ), so the Shaw unit is essentially just passing everything straight through to the ASUS, which just operates normally. Most DVRs have a UPnP option that will configure the port forwarding automatically, too. |
All times are GMT -8. The time now is 06:40 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
SEO by vBSEO ©2011, Crawlability, Inc.
Revscene.net cannot be held accountable for the actions of its members nor does the opinions of the members represent that of Revscene.net