Emby (running on server) no longer casts to TV but plays OK on workstation

[LloydGM 8]

I switched Internet provides last weekend (Frontier to Comcast). Now Emby won't cast (Chromecast) any content to my TV, though Plex still casts fine. I upgraded my Emby from 3.2.33.0  to 3.2.34.0, still no joy. My setup is:

Emby running on Windows Server 2012 R2, 16GB RAM, 8 cores, 1Gb NIC

Workstations all running Win7 x64 Ult., 1Gb NICs, have always cast movies to TV via Chromecast

TV is Toshiba 55L621U, built-in Chromecast 2, wired LAN (100/1Gb, can't tell which), Chromecast upgraded on 9/23/2017 to v1.22.78594

LAN is 10/100/1000 switched, all workstations & TV using DHCP-assigned settings (server DHCP, all leases reserved {i.e. static}, gateway solo setting assigned via DHCP, server of course has static IP config)

Border router was FiOS gateway with class c IP ending in .3, replaced with Motorola gateway with IP ending in .1.

 

Test scenario:

1. TV already on and connected, shows available to cast in Chrome
2. Server: Restart Emby (running as service, but I tried running manually as well)
3. Workstation: Refresh Chrome browser viewing movie Sneakers
4. Click play link, movie plays fine on workstation in Chrome
5. Click Emby's back arrow, now viewing Sneakers page again
6. Click on cast link, Emby shows on TV as ready to cast
7. Click play link, spinning icon shows on TV, movie never starts even if waiting several minutes (have never had to wait more than a couple seconds before)

I've tried restarting Emby, running it both manually and via Windows service, no change. Some server logs were showing use of the old border router (.3), not always, though. Obvious server and workstations are reaching the Internet fine, even Emby can because it otherwise wouldn't have been able to update to 3.2.34.0.

 

Ironically, Plex is still casting to the TV just fine, and I can cast other content from workstations to the TV as well (youtube, netflix, etc.). Emby has been working fine for many months, never a problem casting, especially.

 

Can somebody please help? I've got a lot of content and would hate to have to reinstall Emby, so I'd like to salvage the installation if at all possible.

 

I have all kinds of logs, e.g. 1 captured showing movie locally in workstation browser, another captured while trying to cast to TV, plus many logs for various troubleshooting test cases. Would some of the logs help and, if so (assuming yes), which ones? Or would you like me to try specific troubleshooting steps and capture that?

[LloydGM 8]

No info regarding logs, so I'm attaching what I hope will help the most. This log file shows using Emby after a fresh server reboot, connect to Emby via Chrome browser, play movie Sneakers in Chrome ok, then selected the option to play on other device, connected to TV fine and got the "loading" spinner (see screenshot) and it stayed that way for quite a while; I then canceled the failed playback and again started the movie in Chrome just fine. The log file should show all that activity.

 

PS Looking in the log file for "error", I see port mapper references to a .104 address. That's really whacked out because that's the IP of another workstation on the network and nobody's even logged onto that box. IPs are DHCP-assigned but all computers have reservations so always get the same IP. Why would Emby be trying to map to that .104 address in the 1st place?

server-63644705230.txt.txt

Edited October 27, 2017 by LloydGM

[Luke 42085]

If you'd like to install the beta server it might be resolved there, thanks.

[LloydGM 8]

Would installing the beta version screw up the current version? Or is there a straightforward way of backing up the current installation and restoring it if the beta version goes sideways?

[LloydGM 8]

So is there any indication of what might've gotten broken simply by changing ISPs? It makes no sense, really, as the only thing that changed on my end was the IP for my gateway, dunno how that could affect Emby. Perhaps there's some cached IP info somewhere I can edit?

[Luke 42085]

There were also some changes to in-network detection so it is possible that the chromecast receiver is trying to use your external ip address, rather than internal. So that's why I suggested trying the beta server.

[LloydGM 8]

Ah that would make sense. How stable is the beta version? If something breaks on me, the kids'll kill me.