Can't loop back to my device on Intranet using Router IP add

May 3, 2014 at 16:58:04
Specs: Windows Vista 64bit, SP2, , Quad Core, 8 gig
Here is the problem. I just changed from a Bright House router (5 wired ports) to a Bright House Wi-Fi router and this is where the problem begins. On the old hardwired router, I was able to access my DVR (on HomeNetwork) using the IP address of the Bright House router. Not sure it went out to the Internet and came back, but it worked. I had Bright House install their Wi-Fi router and from that point on I have had to use the DVR's 192.168... IP address (
Home PC and ALL smart devices), which irritates me because I will have to set up another APP on all the devices to access the DVR from within the house, or outside the house using the 192.168... IP address.

Are there any setting on the Bright House Ubee DW3201B Wi-Fi router that will allow me to use the Internet IP address of the router? I have the DVR port forwarded, and I am now thinking of going back to a non-wireless Bright House Wi-Fi router and getting a new Wi-Fi router of my own to attach.
Any assistance would be GREATLY appreciated.
Don


See More: Cant loop back to my device on Intranet using Router IP add

Report •


#1
May 3, 2014 at 18:34:14
I don't see how anything went out to the net & came back again. You didn't access the DVR using the address of the router, either. If the DVR was accessible at all, it had it's on IP address that was given to it by the router. That has to be setup with the new router first. You don't need a second access point.

http://support.brighthouse.com/Arti...

The world is full if rats, Republicans & Democrats.


Report •

#2
May 4, 2014 at 08:10:08
It sounds like you had a port forward configured on the old router.

If you still have the old router handy, I would turn it on and connect to it physically (ie: network cable to LAN port) and then I would check through the settings for Port Forwards. If there is one, write the information down and then create one on the new router.

A typical port forward looks something like this:

forward [Port Number] to internal IP address [xxx.xxx.xxx.xxx]

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#3
May 4, 2014 at 12:57:51
Access to the Camera DVR will only work through one router.

The old D-Link and NetGear wireless routers were set up with port forwarding to the DVR 192.168.. address, same as with the current Ubee Bright House Wi-Fi router. Never had an issue with either the D-Link or the NetGear units. The iPhones, Android tablets, PC’s all used the internet IP address and port and got a connection everytime while at home. With this Ubee Wi-Fi router I tried port forwarding, and any of the iPhones, tablets, PC's get a message can not connect with the network.

If I go to McDonald's and use their Wi-Fi, they all connect with no issues.
I am about ready to dump BrightHouse....

Thanks

Don


Report •

Related Solutions

#4
May 4, 2014 at 19:30:41
Your original post said access not remote access. What does McDonald's have to do with it? What did I miss?

The world is full if rats, Republicans & Democrats.


Report •

#5
May 5, 2014 at 07:12:19
If I'm reading this right, the OP wants to be able to access his DVR from within in his LAN by typing in the LAN IP of his router. He claims this worked previously on his old hardware (router).

I assumed that if it did work, it was because he had a port forward setup on his router to forward incoming traffic on whatever port his DVR operates on.


Mustang65

Did you look at the port forwards on the old router and compare it to your new one?

Honestly though, internally you should be using the IP of the DVR and not the LAN IP of your router.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#6
May 5, 2014 at 08:24:40
" I was able to access my DVR (on HomeNetwork) using the IP address of the Bright House router"

I suspect he was able to use the wan ip to access his local dvr. Some routers, not all, have this smart loopback ability.

Mustang64 it is normal to access when on the lan via a local ip. When not on the local lan you access via the routers wan ip and port forwarding to the dvr.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#7
May 5, 2014 at 10:05:35
I have always (4 years) used only the Internet IP address (the address of the Bright House router) as the IP address and the PORT, in all my devices. I have PORT Forwarding set up the same way as I had it in the previous modems. I never had to set up the devices for access using the LOCAL IP address, (iPhone, Android tablet,or home PC). For some reason I can not access the DVR locally (using the BH router ip/port), but works when I am remote, like McDonnald's, Starbucks....
I have tried every possible setting un the BH Ubee router that is available, with no luck.
It looks like I will dunp the current Bright House Wi-Fi/router for a non Wi-Fi Bright House router, and buy a new personal Wi-Fi Router of my own again.
Don
I believe that the other wifi routers allowed the request to go out to the internet to the DNS server and it was routed back into my router, something like a loop-back

message edited by Mustang65


Report •

#8
May 5, 2014 at 11:13:41
Buying new equipment may not address your issue.

The local request never goes out the wan port of the router. Wan ip address: port number never goes to any dns server anywhere. Internet dns has no knowledge of your local lan names or ips.

Reason for your issue now is the router drops what it considers a invalid request. It does not resolve lan traffic. The router needs to know that wanipaddress:portnumber is equal to the dvr's local ip address so it can send it back to the lan instead of the normal behavior of dropping the request.

What is the deal with not wanting to use local addresses when on the local lan?
Pretty simple solution compared to getting new hardware

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

message edited by wanderer


Report •

#9
May 5, 2014 at 12:04:37
Here is the issue. I used 1 device in the above example that I use for port forwarding, I have a few other devices that need it also. So. I have 10 devices/10 Apps the old way, now I have to have 20 Apps.

Normally, no one uses port forwarding so it is not an issue for them. I on the other hand use port forwarding like it was made for:
- Security cameras DVR
- Home Control PC (HAL)
- Thermostat
- Home Security Sensors Control - HTTP Microcontroller
- Outdoor Watering/monitor system - HTTP Microcontroller
- House Fresh Water monitoring system - HTTP Microcontroller
- Weather station/data - HTTP Microcontroller
- Solar Charging system (for outdoor sensors) - HTTP Microcontroller
- House Fresh water monitoring sys - HTTP Microcontroller
-
-

and a few more I am working on at the test bench.
Electronics and Home Control/Automation are my hobby. So it is a pain if I need to have 2 apps for every item (re-programming them into one Menu is not an option, as it is so much easier to do it this way)
Don


Report •

#10
May 5, 2014 at 13:36:46
I suspect like wanderer said earlier "The local request never goes out the wan port of the router on this new router.

Here's what I would do if it were me and it were important to not have to use the LAN IP of the box in question.

I would put the old router back where it was since it worked for your purposes and I'd make the new router into a Wireless Access Point. Problem solved.

If you're interested in doing that simply click on my name above in this response and read my “how-to” guide titled, “Add a second Router to your LAN

You would want to use the scenario where you connect the Wireless router to the old router LAN port to LAN port

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#11
May 5, 2014 at 14:52:01
Thanks, I thought about getting a new router and plugging it into the existing BHouse router, but in the directions on the DVR, in all CAPITAL letters informs you that the DVR will not work behind a 2nd router. I may call BHouse and have them deactivate the Wi-Fi in this box, get a new Wi-Fi router of my own again and see I I can make it work like the old box.

Now to add salt to the wound, I just noticed that my getIP.vbs program (sends the current BHouse IP address to my webpage, in case BHouse changes it) does not work on windows 7 as it did on XP, but that will be another day after I debug it.

Sorry, just a little frustrated .

Thanks for all your help...

Don


Report •

#12
May 6, 2014 at 06:59:38
but in the directions on the DVR, in all CAPITAL letters informs you that the DVR will not work behind a 2nd router

My method would still work as the DVR and the new wireless router would both plug into LAN ports on the old router. Here's how I see it:

Internet >> Old Router >> clients/DVR/new Wifi Router

Just remember, you don't want DHCP enabled on both routers. I would leave the old router (the one connected to the internet) doing DHCP and I would disable it on the new one.

If your old router's LAN IP is: 192.168.0.1 then give your new one: 192.168.0.2 and make it's Default Gateway IP: 192.168.0.1 as well as DNS. You would use the same subnet mask on both.

One last thing, if your old router doesn't have enough LAN ports for everything you need to plug into it, you could move any client other than the DVR to the LAN ports on the new router.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#13
May 6, 2014 at 08:25:04
Think about it. There are multiple routers between your dvr and where you are remotely on the internet and that works.

Makes what they write not true doesn't it?

They just didn't want to get into multi device forwards. By writing that they don't have to support it.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#14
May 6, 2014 at 16:31:19
You must be missing another setting on the router. Port forwarding is port forwarding.

The world is full if rats, Republicans & Democrats.


Report •

#15
May 7, 2014 at 09:04:23
Port forwarding has nothing to do with using the wan ip:port number when on the lan.

Port forwarding is from the outside to the inside not the inside to the inside.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#16
May 8, 2014 at 12:36:45
He was talking about remote access as well & that's what I was answering. There is no reason to use the WAN IP when you are home.

The world is full if rats, Republicans & Democrats.


Report •

#17
May 9, 2014 at 08:30:00
But that is exactly what Mustang65 was doing, using the wan ip to access his local dvr. This was the whole reason for the thread.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

message edited by wanderer


Report •

#18
May 9, 2014 at 16:07:24
I see that now but in post #3, he mentioned McDonald's & in post #9 he mentioned all the other reasons why he needs remote access.

In post #8, you (wanderer) hit the nail on the head:

"What is the deal with not wanting to use local addresses when on the local lan?
Pretty simple solution compared to getting new hardware"?

However, if remote access isn't working from McDonald's, he missed some setting, on the router. That should work no matter what.

The world is full if rats, Republicans & Democrats.


Report •


Ask Question