LAN clients can't connect to 10.0.0.xxx TCP address

[rkjjkr 1]

Until recently my server address was always 192.168..xxx.xxx (Class C network) and all my Rokus and TVs worked with no problems.  I changed to a new ISP and now my Emby server LAN address is 10.0.0.250 (Class A network) and none of my LAN clients can connect when I add a server with that address. 

Has anyone else experience this? Any ideas on a fix?

[Abobader 3470]

Hello rkjjkr,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Junglejim 385]

No I haven't but I haven't changed my IPS.

Have you tried removing the old server from the client?

Then try connecting manually again?

[pwhodges 2012]

Have you checked that your client devices have also got a new 10.0.0.x address?  If not you need to force them to refresh their DHCP connection.

Paul

[rkjjkr 1]

Yes, client has 10.0 address and I've deleted server and manually entered new server's new address. Client thinks awhile and the says unable to connect. Timeout waiting for a response. Same on all TVs and Rokus.

My new provider Xfinity enables IPv6. Could that be the problem? I can't test that because their router management is so limited and you can't turn it off without bridging to a personal router.

[pwhodges 2012]

IPv6 shouldn't cause a problem - but there is a general lack of understanding of its niceties.  Sometime people report turning it off as a fix, but I suspect that's just obscuring something else.

Check the server's firewall - perhaps it is set up with IP addresses, and needs updating.

Paul

[rkjjkr 1]

Checked the firewall and emby server was being blocked for public traffic but allowed for private. I opened up the app for public and now it's working.