Works with android app and local PC but not with remote PC

[duckhouse]

Hi Shane,
I have a Lorex Eco LH110 series and have gotten everything to work EXCEPT I cannot log into http://myname.lorexddns.net:90. When I try, I get a message that the server is not responding. I believe the DDNS setup is good because I can use my mobile phone to see the cameras just fine. Locally, I can type http://192.168.xxx.xxx:90/ and get the web client to work fine. But I'd like to be able to log in remotely. I saw your post about a potential reverse NAT issue, so I emailed the http://myname.lorexddns.net:90 link to a friend and had her click it, but she got the same error as I so I don't think that's the problem. Any suggestions or other info I can provide? Thank you.

[duckhouse]

Oh, I should say, the subdomain is not really "myname" but if you need it, I'll tell you what it is... 

[Shane]

Well I connected to your IP you posted with http://66.168.xxx.xxx:90/

And got the login screen for the DVR.

Now when your home you need to use the local ip to the dvr and when outside your home like I am you will use the ddns name or internet IP.

The reason for this is your router doesn't like reverse nat
http://www.pcwintech.com/test-for-reverse-nat

Shane

[duckhouse]

Really! Hmm... I just tried it again from a coffee shop and got:

The connection has timed out
The server at 66.168.xxx.xxx is taking too long to respond.

This is the same thing I get whether I use the ddns or IP. How is it you could get there and not me? I've tried two different computers. I've tried IE as well as Firefox. 

Also, I put the x's in this time into the IP address in my post (but not in the browser, of course). Should I be concerned about people knowing the actual IP address of the Lorex box and being able to do something malicious with it? I didn't realize you could just change the first number to 66 and actually access the Lorex box.

[Shane]

Did you put the :90 at the end of the IP?

I had used the IP on the post you made. Was that not your home internet IP address?

Shane

[duckhouse]

Yes, I did put the :90 at the end. The local IP is 192.168.xxx.xxx:90. That works locally just fine. You said you connected to 66.168.xxx.xxx:90 remotely. I tried that this morning from a remote location and got the timeout error. I also tried using the ddns name and got the same timeout error. I had my mother in another city try the name link I sent you originally and it didn't work for her. Do you need the IP again or the subdomain name? Is it safe to just post it or is there a security concern? I see most people don't post their actual IP or subdomain. Thanks for staying on with me here.

[Shane]

Yeah I replaced the IP numbers with X's

I attached a screen shot showing I am getting tot he DVR, I blurred out your internet IP

Shane

[duckhouse]

Ok, I called my sister in another state and had her type in the internet IP address just as you did in your screenshot (66.168.xxx.xxx:90, except instead of the x's, she used the corresponding numbers from my local IP address). Unfortunately, she, too, gets a timeout error. It seems you are the only one who gets the Lorex screen. I had her try the domain name as well and again same problem. What could make the difference? I have now tried three different computers, five different browsers, and three different ISPs. Are you sure you're connecting to MY server? Just a thought, but can you send me an email with the actual IP address you're using? Thanks!!

[Shane]

I sent you a message of the IP that I am using.

Do me a few things.

1. Reboot the DVR
2. Post a screen shot of the network settings in the DVR
3. Post a screen shot of the port forwarding page in the router.

This way I can double check everything

Shane

[duckhouse]

Shane,
Solved! Thanks for your helpfulness. You were right all along about the reverse NAT thing being the problem. It wasn't working remotely because I wasn't putting in the right IP address - I didn't understand it needed to be my router's IP address, but now I understand that. Seems like everything works now. It was a little tricky getting the login prompt to display in IE but I found in another post in this forum some helpful tips to make that work. Then I installed the Lorex Client 10 and that's even better. So anyway, I think everything is as it should be. Many thanks!!

[Shane]

Glad to hear your fixed

Locking thread.

And as always...
If your happy with my work. Then all I ask in return is you simply let others know about my site and programs. I help with anything computer or network related
Also always feel free to make a post in the feedback forum.
And a facebook like at the top of the page of my site is nice as well.

Shane