LAN Connections Timing Out

[Kurty 2]

Hello,

I am trying to set up an Emby Server for the first time. The machine running the Server can access the server without problems, but when I try to access from any other device the connection times out.

Both the server and the other devices are connecting over Wi-Fi 2.4Ghz and are not connected through Ethernet.

I have followed the troubleshooting here but it hasn't helped. I note below the steps taken:

1- I have created a rule for the Firewall to open Ports 8096 and 8920.

2- I have scanned for viruses/

3- No devices on the router have an active VPN.

[Abobader 3470]

Hello Kurty,

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

[rbjtech 5284]

Can any other PC/Device on the LAN access the emby server OK ?

Are the wifi IP addresses on the same subnet/LAN as the Ethernet devices ?

ie are they all something like 192.168.x.y - where the only octet that changes between devices is y ?

in powershell (type powershell from a command prompt) - type

test-netconnection IP-ADDRESS-OF-SERVER -Port 8096

ie 

test-netconnection 192.168.1.10 -Port 8096

what does it show ?

 

Edited March 18, 2022 by rbjtech

[Kurty 2]

1 hour ago, rbjtech said:

1) Can any other PC/Device on the LAN access the emby server OK ?

2) Are the wifi IP addresses on the same subnet/LAN as the Ethernet devices ?

ie are they all something like 192.168.x.y - where the only octet that changes between devices is y ?

in powershell (type powershell from a command prompt) - type

test-netconnection IP-ADDRESS-OF-SERVER -Port 8096

ie 

test-netconnection 192.168.1.10 -Port 8096

3) what does it show ?

 

Thanks Rbjtech, I've number your questions above for ease of answering.

1) No other device I've tried can access the emby server.

2) Yes all WiFi IP addresses are on the same subnet.

3) Apologies, had to edit as I screwed up this instruction

ComputerName     : 192.168.1.148
RemoteAddress    : 192.168.1.148
RemotePort       : 8096
InterfaceAlias   : Wi-Fi 2
SourceAddress    : 192.168.1.148
TcpTestSucceeded : True
 

Edited March 18, 2022 by Kurty
Erred in an instruction

[rbjtech 5284]

14 hours ago, Kurty said:

Thanks Rbjtech, I've number your questions above for ease of answering.

1) No other device I've tried can access the emby server.

2) Yes all WiFi IP addresses are on the same subnet.

3) Apologies, had to edit as I screwed up this instruction

ComputerName     : 192.168.1.148
RemoteAddress    : 192.168.1.148
RemotePort       : 8096
InterfaceAlias   : Wi-Fi 2
SourceAddress    : 192.168.1.148
TcpTestSucceeded : True
 

ok - so 'TcpTestSucceeded' = TRUE, means the response got a reply on the correct port (from Emby) but you tested from the Emby Server I presume (192.168.1.148).

Do you have anything else on the Wifi that can you can use the same command on - maybe another PC on wi-fi for example ?

ie - in powershell type -

test-netconnection 192.168.1.148 -Port 8096

If this comes back as True as well - then from a networking and firewall perspective - you are all good.  if it comes back as False, then all it can be is the INCOMING firewall rule on your Emby Server (host - 192.168.1.148).   To proove this (don't leave it like this..) just disable the Windows firewall and try again.  If it then connects, then you know it's the Windows firewall - turn it back on again and we can check that next.

Edited March 19, 2022 by rbjtech

[Kurty 2]

I seem to have discovered the culprit, I tried turning off the firewall, and it allowed me to connect. In looking through the rules, it looks like somehow a rule was automatically created to block embyserver.exe on private networks, so I wasn't able to access it while on my home network. I turned off that rule and the server is now accessible. 

Thank you so much for all your help!

[Luke 42085]

Thanks for the feedback !