Server not discovered at home

Channels DVR Server
#21

I’ve never had any problems with any other networkable devices. Why is this something the developer is choosing to do if no one else is doing this? Or am I missing something?

I’m not going to change my entire network for one app, so if this is really the root of the problem, I guess I’ll have to look elsewhere. And I was really hoping to get this working easily as my wife and kids are not too computer savvy. It just needs to work.

Thanks you everyone who helped me. Unless the developer is willing to make an update to the software, looks like I’m going to have to find another solution.

Jaime

1 Like
#22

If "it just works" is a prerequisite, then choosing to use network addresses outside of the reserved private network ranges was just asking for problems to crop up some time in the future, and definitely not a "just works" choice. The reasons those three IP ranges are reserved are specifically for use in LANs not directly connected to the public internet.

#23

Yes....Channels is following network standards and your network is not. I suspect a lot of things are not working as they should for you, even if you do not realize it.

PS - You do realize that part of that block of addresses you are using is owned by a service provider in Iran....also owners in at least France, Spain and the Netherlands just from a quick check of a couple of addresses.

3 Likes
#24

I guess I was missing a lot more than I anticipated😹. Didn’t realize my local IP was not within best practices. You’re right in the fact that if this is an issue now (first one), more will likely follow if I don’t address it.

I guess once I update everything that needs updating, I’ll try again.

Thanks everyone for the help. I will be back with an update.

1 Like
#25

I want to thank everyone for the help and guidance I received yesterday in resolving my issues. After updating my network to a private subnet, Channels app automatically detects the server and all is well.

Thanks again,

Jaime

4 Likes