Server Thinks Local Connections are Remote

Channels DVR Server
#1

I replaced my router and in the process changed my internal network from the standard 192.168.1.X to a new IP address. I verified that all of my devices and the channels DVR server recognize that they are on the same network (e.g. 11.22.33.XX). All of the apps say that the DVR is not "set up" even though it is. I am only able to access the DVR by saying I am remote and logging in.

There is only one router on my network so that is not the issue. My Channels DVR Server is running on my Ubuntu server and all other services on my server work just fine with no issue using local access.

I have run all updates on my Ubuntu server and the Channels DVR and restarted all devices to no avail. I believe there is something with Channels that is having trouble the IP change.

EDIT: I have no issue accessing the web interface using the local IP.

EDIT2: Also as info the clients automatically found the IP address for the DVR Server, but just say, "Your DVR is not quite set up yet"

Thanks!

#2

11.22.33.xxx is a routable Internet IP address.

On your internal LAN you need to use one of the reserved IP address ranges set aside for private networks.

   10.0.0.0/8      (10.0.0.0 - 10.255.255.255) | Private networks (Class A)
 172.16.0.0/12   (172.16.0.0 - 172.31.255.255) | Private networks (Class B)
192.168.0.0/16 (192.168.0.0 - 192.168.255.255) | Private networks (Class C)
#3

11.22.33 is not my actual internal IP I did not want to post that. That being said how does this stop the DVR server from working on my internal network? The client finds the server in discovery. Is Channels DVR programmed to treat anything outside of these IP addresses as external regardless of location.

#4

Private network IP addresses are not reachable from the Internet, so no problem posting it.
Mine is 192.168.1.4 and cannot be reached from the Internet.
What you don't want to post is your WAN (Internet) IP address.

If you still don't want to post it, it makes it hard to help you.
At least post the first two parts of it, like 192.168.x.x

#5

It was on a 11.x.x.x network. I changed everything to a 10.x.x.x and restarted everything, Router, WAPs, Server and Client devices and now it works.

Thanks!

#6

Smart move.
Making your internal LAN network available to the Internet is not smart.
Your router and everything on your internal network could be compromised very quickly by bad actors.

#7