Smart TV's only detect Emby if server pc has DHCP I.P.

[atomicmoon 152]

I recently moved all my media to an external drive connected directly to the router.

After a couple of hiccups, I'm pretty happy with the results except for the following:

 

I have 2 different smart tv's in the house and they can access emby directly through upnp IF the server's I.P. is not static.

The moment I give the server a static I.P. the tv's no longer display emby as an option.

The moment I let the router handle the I.P. address the TV's can see emby and stream with no problems.

I'd like to connect externally though, and can not if the servers I.P. is not static.

 

Any help or links would be appreciated!

 

Thanks

[rbjtech 5284]

Are you providing the correct subnet, dns and gateway settings to the static IP ?  

 

Either that or just reserve a DHCP address for the 'server' on the router - assuming you never change the servers network card (mac address) then it will always be given the same IP settings and no other client can be given that IP address.

Edited March 14, 2017 by rbjtech

[atomicmoon 152]

Thanks RBJtech, I'm on the same idea, just fighting my router over a preferred I.P. 

Will report back within 48hrs of success/hangups.

[zigzagtshirt 55]

@@atomicmoon

 

What TVs do you have?

 

My Samsung KU7000 works just fine in detecting the server with static IP.

[atomicmoon 152]

@@atomicmoon

 

What TVs do you have?

 

My Samsung KU7000 works just fine in detecting the server with static IP.

An LG LF5500 and a Hisense baked potato (model escapes me).

I used rbjtech's advice and reserved the IP address to allow for remote access.

So far, so good. I'm not sure what would cause the TV's to not be able to see Emby when the server's IP is static, but reserving is a solid work-around.

 

Off to bigger and more fun challenges!

Thanks for the help.

[overClocked! 65]

I'm not sure what would cause the TV's to not be able to see Emby when the server's IP is static, but reserving is a solid work-around.

 

Off to bigger and more fun challenges!

Thanks for the help.

I think that must have been something with the values entered into the static configuration (incorrect subnet octet, incorrect subnet mask, gateway or DNS server address(es)). Also could have been an IP address conflict with an existing device on the network or that static address was within the DHCP scope and another device was being issued that same IP address to cause a conflict.

 

Whatever the reason, glad you sorted it with a DHCP reservation (always the best choice so long as the router config doesn't get reset).

 

 

Sent from my iPhone using Tapatalk

Edited March 16, 2017 by overClocked!