Jump to content

Local client connects via WAN


Go to solution Solved by pwhodges,

Recommended Posts

KegTapper
Posted

I'm stuck and need advice. I was running Emby successfully on my old windows 10 machine for years. I have remote access via CF tunnel (CGNAT SUCKS),  emby.mydomain.com. The Local clients on LAN are all firesticks. 

I recently migrated to a new machine running windows 11. Wife and kid were complaining about buffering. I checked the dashboard and noticed wan IP  with transcoding. I deleted cache and data on firestick and manually added lan address. But they revert back to using WAN on next app start. I have removed remote access from these profiles and they work as intended but would like to find a solution.  

visproduction
Posted (edited)

KT, 
Logs would be helpful.  Since you mentioned the change to Windows 11, perhaps this search result might be worth looking through.
 https://duckduckgo.com/?q=Windows+11+buffering+streaming+video+settings&ia=web

You should test with a professionally made demo video, so you don't waste time trying to find fixes when the video has issues.  Just because you can play a video fine on a 3rd party player, means nothing.  The video could still have hidden issues.
 https://duckduckgo.com/?q=Demo+videos+testing+h.265+h.264&ia=web

It's also quite possible that a new install of Emby on a Windows 11 server may have some settings that were not the same as your Windows 10 setup.  The log files will tell you more.  You should run the demo video, find issues and upload the log files to this forum post, that were just created during the problem buffering.

Hope that helps.

Edited by visproduction
Posted

Hi, does your emby server dashboard display the correct lan and wan addresses?

Posted

So maybe the LAN address is not reachable from those devices? the way it works is that emby apps will first try to connect using the lan address, and then fallback to the wan address if that can't be reached.

Happy2Play
Posted
3 minutes ago, Luke said:

So maybe the LAN address is not reachable from those devices? the way it works is that emby apps will first try to connect using the lan address, and then fallback to the wan address if that can't be reached.

But how would it work properly when disabling Remote access?

  • Solution
pwhodges
Posted

Is the server's networking set to "Public"?  It needs to be "Private" - recent installs or updates of Windows sometimes change this...

Paul

  • Thanks 1
KegTapper
Posted

Thank you!!!! That was the problem. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...