sonorabill

I did a search and only saw one reference to the NVG510. Hope making a new topic will produce an answer. Recently ATT switched my DSL service. I no longer have separate modem and Linksys WRT54G router that I can simply refer to the settings I saved on how I did enable the DVR to operate on the internet. The new unit combines the two functions into one box, a Motorola NVG510. I'm using DVR WEB Client on Internet Explorer to view my cameras. But only get them locally. I'd like to see them from remote locations over the internet. The DVR is a 4CH model GS2008V. I plan to use no-ip.biz for a dns. So far I tried setting Port 80, but using a online test, seems I have not even got that right. Anyone have experience using the NVG510 modem/router?

Contacted Linksys tech support about the problem I was having. Walked me through the router settings and changed the following: 1. disable port forwarding on port 80 2. enable DMZ and set my DVR 192 dot 168 dot one dot ten 3. Slow down the MTU manual 1300 Reset modem, router, computer Went to my dyndns web page domain name and found the login. Logged in and video was clicking away as I watched. Thanks Rory for all the help. And hope this helps anyone else with a similar problem. BTW, telnet DVR ip address still doesn't work. So not sure the value of the telnet program.

Contacted Linksys tech support about the problem I was having. Walked me through the router settings and changed the following: 1. disable port forwarding on port 80 2. enable DMZ and set my DVR 192 dot 168 dot one dot ten 3. Slow down the MTU manual 1300 Reset modem, router, computer Went to my dyndns web page domain name and found the login. Logged in and video was clicking away as I watched. Thanks Rory for all the help. And hope this helps anyone else with a similar problem.

I'm starting a new thread for suggestions on buying a new router. My remote self ping problem seems to be caused by my Linksys router, since I can make an old intermittent D-Link DI-524 router do it. But my experience in the past makes me reluctant to buy another D-Link. Three bad ones in a year or so. The new Linksys WRT54G Ver8 seems to not handle the video porting or something. Tried two of them. So ruling out D-Link as unreliable and Linksys as non-functional, what router should I be looking to buy and install. One that is both reliable & functional?

Success of sorts. This morning re-installed my old flakey D-Link DI-524 and managed to do the port 80 forwarding. Actually was able for the first time to log on over the internet and view my cameras for a few seconds before the D-Link crashed itself again. Re-booted and downloaded the latest firmware, hoping that might fix the crashing. But looks like the poor flakey D-Link as met its maker with that firmware update. So now my problem is I should buy a new router to run my DVR video server. I've had 3 D-Links DI-524's that never lasted more than a year or so before becoming so bad I replaced them. Somewhere along the line D-Link used a 5V power supply and 7.5V power supply. The 5V one only lasted weeks. So I'm not inclined to buy another D-Link. I switched to Linksys WRT54G's for home and one for travel. They are both version 8. Which I find won't let me view the cameras from home over the internet. Sounds like earlier ones did work, but Linksys managed to improve them to non functional. So ruling out D-Link as unreliable and Linksys as non-functional, what router should I be looking to buy and install. One that is both reliable & functional?

The second linksys router acts just like the first one. I can not ping myself remotely. Took the Linksys that was setup yesterday and hooked it to my wife's computer. The second Linksys to my computer by cable so the wifi wouldn't interfere. Then menu by menu set everything on the second to match what I had in the one yesterday. Seems I should have two routers that work the same. But now I can't run Telnet and have it pass on either one. Telnet DVR IP or DVR IP:80 (1.10) returns a message about port 23. Don't know where that came from. Suppose they do run the same, but not the way I want. BTW I can ping the DVR and that works. Also the DVR can be viewed locally with the web browser as before. Going through the menus like that, I came across under Administration Tab Remote Management is disabled. Just wondering from the description if that needs to be enabled? What I'm thinking as far as remote ping is that I must have a setting that is wrong in the factory default, and needs to be something else. The firmware on both is the same ver 8.00.2. the latest. The flakey Dlink DI524 can still get a remote ping working from wormly. I replaced the Dlink because it got to where it had to be rebooted several times a day to reconnect to the internet.

I have a second linksys wrt54g router in my RV. I use that router with my hughsnet satellite internet system. Looks like its time to drive to the RV storage place, fetch the second router and try it out. At least I feel like I'm getting somewhere now with this problem. Thanks for all the help Rory, I'll let you know what happens.

The idea of a data/timing collision problem made me think to try my old flaky D-Link DI524 router; I had replaced with the new "better" Linksys WRT54G a few months ago. After unplugging and replugging and changing its address to match the Linksys, I went to the wormly website and did a self ping and it worked-- with the Dlink; where it would not with the Linksys wrt54g. So I think the router could well be the root of the problem. But I now run into a problem with the D-Link as far as doing port forwarding. I went to the port forward website and first thing it says for my DI524 is I need a static IP for it to do port forwarding. Somehow I thought the idea of the dynDNS was so I didn't need a static IP. Is there a work-around for the DI524 so I don't need a static IP? Or at this point may I just better off buying a router that can do what I need? Was there a post of using the Dlink 524 as I describe? I have gotten used to the Linksys and find myself lost with the dlink menu setup. If a new better router is called for, any recommendations as to brand & model?

Tried ports 81, 82 and 8080. They all worked with telnet. And they all worked with the DVR address thru the firefox browser with the :port number amended on in local mode. I run NO SCRIPT on firefox and did need the enable it for each one for Java to operate. As a precaution selected the options on no script and manually typed in the addresses permitting the dyns host name and my IP with scripts. But they still fail to bring up the dyndns host name website over the internet.

I set the dyndns account up about a week ago. From the PM looks like you can see the sun has gone down here, outside is dark unless a motion detector light is triggered. So it works for you, but not me. Wouldn't seem I need to do anything special with my firewall on the computer to view the cameras. Just made my IP and the host name at dyndns as trusted sites to the firewall. Tried accessing my video and still no luck. Since I'm trying to access the DVR using the same router that's trying to feed the data, could the outgoing and incoming be bumping into each other. Some kind of data/timing conflict? Seems I should be able to do this all from home to check and confirm operation before travelling. But maybe this is normal operation?

I enabled DDNS on the linksys. Settings as follows: Service: dyndns user name: as in my dyndns account password: as in my dyndns account Host Name: as I picked at dyndns with org at the end and it has my IP address same as I get with whatsmyip So I telnet "host name" 80 It waits and finally times out. If I put the "host name" on the browser address line, it times out. Does it need w w w or anything else h t t p to make it work? Does the DVR stay as static IP or do I need to make it DHCP? When you said it worked for you, could you see my camera views?

Great, what do I need to do next?

Set DVR to 1.10, gateway to 1.1, mask to .0. Disabled DMZ on the router still at 1.1, .0. Ran Telnet 1.10 80 The popup window appears, a command line flashes, it then goes all black with the blue title line at the top of the popup saying Telnet & IP I used.

Oops failed to set the at login to the 1.1. Redid it and yes the DVR can still be seen locally on the computer using the 1.1. address. Also can still be seen using Firefox browser using 1.1 as the But with the DVR IP set at 1.1 it's the same as the router's and causes the router to malfunction loading web pages. Still can't access the DVR thru the dyn DNS domain name I picked for that account.

I set the DVR to static & its IP to 1.1 to match my router. Set DVR Gateway the same 1.1. DVR Mask .0. This makes it fail to do a login, either locally or internet. Changed the only DVR IP back to 1.10. Left Gateway at 1.1. Mask .0. Can log on locally, but not thru the DDNS.