 |
|
 |
Remote Viewing - Clover DVR behind router using DSL modem
|
|
|
| minko |
|
Posts: 27
Joined: 26 Apr 2008
|
|
Posted: Mon Jun 02, 2008 5:17 pm
Post subject:
|
| gto_don wrote: |
| minko....thanks so much for that bit of information. Reading it all certainly makes some sense. I am going to try all of this (one at a time to determine what works/fixes the issue) when I get home tonight. I appreciate your time and information. BTW my model is the CDR-4570 but I don't know that it would make a difference. I'll keep you posted and thanks again. |
You're welcome and I hope for the best. I should also note that within the LinkSys Router, I changed the Port Forwarding option of "BOTH" to "TCP" and it seems to work fine.
I installed the CLOVER Software on my computer at work - totally different internet service - and it worked just fine.
Please do keep us informed about your results.
|
|
|
|
|
|
|
| gto_don |
|
Posts: 7
Joined: 31 May 2008
|
|
|
Posted: Mon Jun 02, 2008 10:06 pm
Post subject:
|
|
Well...first let me say that I referenced port 5800 in previous messages. Th set port is 5700, not 5800 as I previoulsy stated. I did get in my router (netgear) and setup the port forwarding for ports 5700 thru 5703. Let's see what happens.
|
|
|
|
| gto_don |
|
Posts: 7
Joined: 31 May 2008
|
|
|
Posted: Mon Jun 02, 2008 10:32 pm
Post subject:
|
| |
 |
 |
minko....some additional (GOOD NEWS I hope) information. In Netgear setup for port forwarding, where you reference "BOTH" for Linksys, I think you speak of TCP/UDP correct? (mine didn't say "both") Mine was set to TCP/UDP and I changed it (as per your recommendation) to TCP only and as I referenced before, ports were/are now 5700 - 5703. Those were the only new changes I made. Everything else I had already setup.
Now...for the good news (I hope)...I left my desktop and got on to my lap top which is set up for wireless connect. I connected to someone else "unsecured" wireless network (which I hate doing) to ensure I was not accessing my own network (which is secure). I have the clover software install on the laptop and BINGO....I was able to pull up the camera's. As a final check, I have the clover s/w installed on my work laptop too and will attempt a connect there first thing in the morning to ensure this is the final fix. For the first time in a LOOOOOONG time, I am actually looking forward to going into the office tomorrow to try this out. 
Either way, your assistance is forever appreciated. I will post tomorrow to let you know final outcome. Best Regards....
|
|
|
|
| minko |
|
Posts: 27
Joined: 26 Apr 2008
|
|
|
Posted: Tue Jun 03, 2008 4:43 pm
Post subject:
|
| |
|
|
| gto_don wrote: |
minko....some additional (GOOD NEWS I hope) information. In Netgear setup for port forwarding, where you reference "BOTH" for Linksys, I think you speak of TCP/UDP correct? (mine didn't say "both") Mine was set to TCP/UDP and I changed it (as per your recommendation) to TCP only and as I referenced before, ports were/are now 5700 - 5703. Those were the only new changes I made. Everything else I had already setup.
Now...for the good news (I hope)...I left my desktop and got on to my lap top which is set up for wireless connect. I connected to someone else "unsecured" wireless network (which I hate doing) to ensure I was not accessing my own network (which is secure). I have the clover software install on the laptop and BINGO....I was able to pull up the camera's. As a final check, I have the clover s/w installed on my work laptop too and will attempt a connect there first thing in the morning to ensure this is the final fix. For the first time in a LOOOOOONG time, I am actually looking forward to going into the office tomorrow to try this out.
Either way, your assistance is forever appreciated. I will post tomorrow to let you know final outcome. Best Regards.... |
Sounds promising gto_don! Let us know how your attempt at access the DVR at work goes.
I hope the original poster of this thread, epols, has been following this discussion. Maybe his problem will reflect yours. I think Clover may have the wrong port number (5800 vs 5700) listed in their manual for your model. In my manual, the only reference to forwarding all four ports was listed in a note about 6 pages before the chapter on DDNS. Clover needs to work on their technical documentation.
I too have only accessed my DVR because I know my Dynamic IP Address (that hasn't changed in months). Next project - define the steps necessary to activate the DDNS feature and really be able to access the DVR anytime, anyplace. I haven't had time to look into the steps necessary to make this happen.
|
|
|
|
| gto_don |
|
Posts: 7
Joined: 31 May 2008
|
|
|
Posted: Tue Jun 03, 2008 8:30 pm
Post subject:
|
| |
|
|
minko....well, SUCCESS and not really a failure, but a (let's call it )"hurdle" or "setback".
I got to work this morning and attempted to connect from my work computer. NO LUCK!  Depressed and contemplating leaving and getting a cold beer with a whiskey chaser, I reconsidered the thought and just couldn't see starting this kind of activity(drinking) at 5AM. Was it possible something still wasn't right after doing the test with my laptop the night before?
I got home from work, loaded the clover s/w on to my ftp server and called my son who attends school in Irvine California. He downloaded it and after setup and configuration, he was successful in viewing my camera's. EUREKA ! ! The router setup that you recommended did in fact fix the problem. I believe (now) that my office is blocking port 5700 (and possibly others) which is why I can't and couldn't connect from the office.
Now I may have another challenge...one for another time.
I think Clover Tech Support could use someone like yourself. You have my vote.
I too, hope others read these messages and it helps them. I know I learned alot. Many thanks again minko...
Don
|
|
|
|
| minko |
|
Posts: 27
Joined: 26 Apr 2008
|
|
|
Posted: Tue Jun 03, 2008 9:44 pm
Post subject:
|
Well by virtue of the fact that your son could access your DVR indicates no problem with your setup. I couldn't access my DVR from within my own company's network either - I can't even play a You Tube - No streaming video of any kind. Not much you can do about that I guess.
Luckily I have a non-networked computer at work and I can access my Clover that way.
I'd like to get the DDNS thing setup and maybe we can post a Clover "go-by" instruction set of instructions.
Salute'
|
|
|
|
| epols |
|
Posts: 6
Joined: 25 May 2008
|
|
|
Posted: Mon Jun 16, 2008 8:55 pm
Post subject:
|
Found the solution to my problem... My DSL modem was indeed in "Router" mode, and it needed to be in "Bridged". The modem wasn't forwarding all requests to the router, so then the router could never redirect the request to the proper computer with port forwarding. As soon as I was able to switch the modem over, it worked perfectly as advertised. I had only used cable modems before, and never experienced such problems. I'd much rather my higher quality linksys be doing all of the routing tasks rather than my free POS DSL modem.
Anyways,thanks for the suggestions!
|
|
|
|
| bryanf |
|
Posts: 2
Joined: 28 Jun 2008
|
|
|
Posted: Sat Jun 28, 2008 4:43 pm
Post subject:
|
| |
|
|
I seem to be having the same problem you guys had. I am trying to view my system remotely. I too have a clover 4570 model. I have no problem accessing the cameras within the local network (so long as i use the local IP address, 192.168.0.150 i believe it is). However, when i try to access the cameras from any other computer outside the network, i get the classic, "DVR not found !" message. So far i think i have tried a million combinations. To make things as simple as possible, i am not using a DDNS account, yet, and i enabled the system in my router configuration as DMZ. Nonetheless, i have port forwarding, AND virtual server settings configured for the system. I cannot figure out how to access my settings for my sprint dsl modem. The default gateway on my router says 192.168.1.33, which, in my previous experiences means this is the address for the dsl modem itself. However, when i try to access it, iexplorer cannot find the page. Given everything I have done so far, i tend to think it is my dsl modem that is "blocking" a port, or as one of you guys said, "acting as a router." It's a sprint 935 series modem. Any clues on how i can access my dsl modem settings?
p.s., not sure if this is totally relevant, but i was able to successfully ping that ip address where the system is set up.
|
|
|
|
| bryanf |
|
Posts: 2
Joined: 28 Jun 2008
|
|
|
Posted: Tue Jul 08, 2008 11:05 pm
Post subject:
|
| |
|
|
Ok, i see this is a popular thread. No one here solved my problem but i figured it out myself. So for those of us poor souls that are googling this problem. this is for you:
I had to "bridge" my dsl modem. You find your modem address by going to your router configuration page, finding your default gateway, and then type that address in your browser. If you have an older style modem, like i did, you access this instead through telnet using the command prompt. For example at the CP type "telnet [modem ip address]." Also, come to find out, I had over-did my configuration. I had both port forwarding AND DMZ set up, which caused a conflict since my port forwarding settings were incorrect and port forwarding overrides DMZ. I did not find truth to the fact that the IP address needs to be in the form "045.002.003.076" for it to work as another poster had stated. So again, check off this list:
modem = bridged
router set properly for port forwarding OR DMZ, not both
triple check your settings, I was told IP addresses, particularly dsl, can change very frequently, as much as every hour.
Good luck! if this saves one person the trouble that I had to go through, than I have done my job.
|
|
|
|
| palancaman |
|
Posts: 3
Joined: 05 Aug 2008
|
|
|
Posted: Sat Aug 23, 2008 10:36 am
Post subject:
|
|
On the router, at the Security>Firewall>Block WAN Requests area (for linksys), set the Filter Internet NAT Redirection to "Disabled". Read the Help section to help understand what this does.
|
|
|
|
| mouse89145 |
|
Posts: 2
Joined: 23 Sep 2008
|
|
|
Posted: Tue Sep 23, 2008 11:10 am
Post subject:
|
The biggest problem most people are having is that their modem is set up as a router. what you need to do is bridge the modem to the router so you dont have 2 routers working against each other. The reason the modem is set up as a router is so that you can set up a 10/100 switch and hook up multiple computers to a network...
Call your ISP and have them help you bridge the modem!!!
|
|
|
|
|
Options and Permissions
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
