Jump to content

Local Network Connection to server


Go to solution Solved by Neminem,

Recommended Posts

Posted

Hello everyone.. I am having an issue connecting clients to the server. All of the clients are on the LAN and they all worked fine until Saturday night. I have a windows 11 emby server and the clients are a Fire Stick and Fire cube. I have gone through the connectivity kb to no avail.. I have also modified the xml file to reset the firewall ports having removing all the emby firewall ports. I have tried entering the ip of the server manually, nothing. The only change was that the server upgraded from Windows 10 to 11.

Any other ideas?

Posted

Hello cookmi1,

** 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

Posted

Hi, what exactly did you do from the connectivity guide?

Posted

I tried everything listed. I can not access the server from another browser, added firewall ports to the servers windows firewall, scanned for virus's and don't have any VPN software running.

rbjtech
Posted
2 hours ago, cookmi1 said:

Any other ideas?

If you disable the Windows 11 firewall temporarily, does emby then work ok ?

Posted

Nope, still not able to connect after disabling.

rbjtech
Posted
10 minutes ago, jaycedk said:

Check that the emby server is on private network in windows.

I have see upgrades can put it as public network.

Here is a good guide How to Change Windows 11 Network from Public to Private (thedroidguy.com)

Also check all the devices are on the same network and same subnet - are they all automatically getting their IP addresses from the router (dhcp server) or have you manually entered any IP addresses ?

On the emby server - you need to check that emby is 'listening'

At a command prompt - enter

netstat -a | find "8096"

It should return something like - 

  TCP    0.0.0.0:8096           <hostname>:0                LISTENING

 

  • Agree 1
Posted

Thanks, i will try these 2 options and will update when i get home.

  • Thanks 1
Posted

Son of a biscuit, it was set ro Public network..errrrr.. working now.. Guess this can be added to the connectivity kb..

Thanks everyone for the help.

  • Like 1
  • Thanks 1
rbjtech
Posted
10 hours ago, cookmi1 said:

Son of a biscuit, it was set ro Public network..errrrr.. working now.. Guess this can be added to the connectivity kb..

Thanks everyone for the help.

@cayars

It does seem Win 11 is defaulting to Public now 'out the box', as I've had to change this to private for all my Win 11 builds.

Worth adding to the 'connectivity troubleshooting steps' for sure.

  • Agree 1
Posted
On 4/4/2023 at 3:22 AM, rbjtech said:

@cayars

It does seem Win 11 is defaulting to Public now 'out the box', as I've had to change this to private for all my Win 11 builds.

Worth adding to the 'connectivity troubleshooting steps' for sure.

"Pseudo public" :)

Just ran a quick setup on .29 beta and it does default to "Allow remote connections to this Emby Server" but has "Enable automatic port mapping" unchecked. So, unless the router was already setup the reality is that it's still private.

rbjtech
Posted
18 minutes ago, cayars said:

"Pseudo public" :)

Just ran a quick setup on .29 beta and it does default to "Allow remote connections to this Emby Server" but has "Enable automatic port mapping" unchecked. So, unless the router was already setup the reality is that it's still private.

I think you missed the subject Carlo - this is about the Windows Network 'Profiles' - Private, Public and Domain - nothing to do with external access.

I haven't checked, but believe Public is not included in the Emby firewall rule (correct) and only Private (local lan's) is.   I don't run anything on public, but believe it might also be doing full network isolation (ie even a host on the same lan cannot see/discover each other)..

Need to dig a little deeper when I get the time.

 

  • Thanks 1
Posted

Thanks for that.  Yes, a few changes will be made to the knowledge base to add information about this!

Carlo

Happy2Play
Posted
10 hours ago, rbjtech said:

I haven't checked, but believe Public is not included in the Emby firewall rule (correct) and only Private (local lan's) is.   I don't run anything on public, but believe it might also be doing full network isolation (ie even a host on the same lan cannot see/discover each other)..

Isn't that users choice at the time the rule was made.  But yes becomes a issue if network status changes.

image.png.11c03df523bf5d8e7f4f4670d1b78cb6.png

  • Like 1
rbjtech
Posted
38 minutes ago, Happy2Play said:

Isn't that users choice at the time the rule was made.  But yes becomes a issue if network status changes.

image.png.11c03df523bf5d8e7f4f4670d1b78cb6.png

Agreed - but think the key issue is Win 11 now defaults to Public (the most secure), thus the above 'default' is not gonna work for them.

  • Like 1

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...