denzoid 57 Posted November 27, 2019 Posted November 27, 2019 Title says it. Log attached embyserver112719.txt
mastrmind11 722 Posted November 27, 2019 Posted November 27, 2019 need more info. local/remote? what clients? what have you tried to help diagnose? etc
denzoid 57 Posted November 27, 2019 Author Posted November 27, 2019 I can only access from the local machine Emby Server is running on. I am trying to access on local network from Windows via a Browser and from a Mac via a browser and from a Toshiba/Fire TV, I reinstalled from the emby.media website. I checked my firewall permissions on the server machine. I restarted my router & switch.
Luke 42083 Posted November 27, 2019 Posted November 27, 2019 I would suggest checking out our connection troubleshooter: https://github.com/MediaBrowser/Wiki/wiki/Connectivity Please try the steps listed there and let us know which ones succeed and which ones do not. Thanks.
denzoid 57 Posted November 27, 2019 Author Posted November 27, 2019 I went through the connectivity troubleshooting and still can't connect. There was already an entry "EMBY8096" in the rules but I went ahead and added it again per the instructions.Also ran a virus check which was clean.
Luke 42083 Posted November 27, 2019 Posted November 27, 2019 When you try to access from other devices, are you sure you're using the correct server ip address?
denzoid 57 Posted November 27, 2019 Author Posted November 27, 2019 Positive, I even ran ipconfig to verify.
rbjtech 5284 Posted November 27, 2019 Posted November 27, 2019 (edited) Your log is suggesting your IP networking is not working as expected. Going back to basics - what does ipconfig show you ? 192.168.1.23 ? Can you ping your local router/gateway (192.168.1.1 - possibly) or the clients if you know their IP's ? From an Admin command window - netstat -a | find "8096" will show you the IP Emby is listening on. Edited November 27, 2019 by rbjtech
denzoid 57 Posted November 27, 2019 Author Posted November 27, 2019 Connection-specific DNS Suffix . :Link-local IPv6 Address . . . . . : fe80::a1df:c16a:a5ac:84c0%3 IPv4 Address. . . . . . . . . . . : 192.168.1.23Subnet Mask . . . . . . . . . . . : 255.255.255.0Default Gateway . . . . . . . . . : 192.168.1.1 C:\Users\denni>ping 192.168.1.1 Pinging 192.168.1.1 with 32 bytes of data:Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=2ms TTL=64Reply from 192.168.1.1: bytes=32 time=1ms TTL=64Reply from 192.168.1.1: bytes=32 time=1ms TTL=64 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 4ms, Average = 2ms C:\Users\denni>ping 192.168.1.50 Pinging 192.168.1.50 with 32 bytes of data:Reply from 192.168.1.50: bytes=32 time=5ms TTL=64Reply from 192.168.1.50: bytes=32 time=4ms TTL=64Reply from 192.168.1.50: bytes=32 time=9ms TTL=64Reply from 192.168.1.50: bytes=32 time=4ms TTL=64 Ping statistics for 192.168.1.50: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 9ms, Average = 5ms C:\WINDOWS\system32>netstat -a | find "8096" TCP 0.0.0.0:8096 NUC:0 LISTENING
rbjtech 5284 Posted November 27, 2019 Posted November 27, 2019 (edited) C:\WINDOWS\system32>netstat -a | find "8096" TCP 0.0.0.0:8096 NUC:0 LISTENING ok - so local networking is good, the netstat is suggesting that emby is NOT listening on IP 192.168.1.23 as it should say something like TCP 192.168.30.100:8096 bedroom-firetv:36805 ESTABLISHED TCP 192.168.30.100:8096 bedroom-firetv:37763 ESTABLISHED ... where emby is 192.168.30.100 (in my case) and bedroom-firetv is the client. What does the dashboard show you ? Mine says - Running on HTTP port 8096, and HTTPS port 8920. In-Home (LAN) access: http://192.168.30.100:8096 Remote (WAN) access: *** to match the netstat above. You could also force a bind to the correct IP in emby itself via 'Server > Network' Bind to local network address: <192.168.1.23> in your case. then re-start emby and try it again. Edited November 27, 2019 by rbjtech
denzoid 57 Posted November 27, 2019 Author Posted November 27, 2019 (edited) Dashboard says: Running on http port 8096. In-Home (LAN) access: http://192.168.1.23:8096 Remote (WAN) access: http://xxxxxxxxxxx:8096 I put 192.168.1.23 in the Bind to local network address, restarted Emby but still can't connect I re-ran netstat -a | find "8096" command and get this now: C:\WINDOWS\system32>netstat -a | find "8096" TCP 0.0.0.0:8096 NUC:0 LISTENING TCP 192.168.1.23:8096 NUC:50839 ESTABLISHED TCP 192.168.1.23:50839 NUC:8096 ESTABLISHED TCP 192.168.1.23:51535 NUC:8096 TIME_WAIT Edited November 27, 2019 by denzoid
rbjtech 5284 Posted November 28, 2019 Posted November 28, 2019 (edited) ok - so the most obvious thing now is the windows firewall. (assuming NUC is the local device?) Temporarily disconnect your internet connection, and then disable your Windows firewall and try again. If this then works, then you know it's a Windows firewall related issue. Turn it back on again and follow the next steps. netsh advfirewall firewall show rule name=all | find "8096" will show you if you have a rule for incoming 8096 requests but due to the output it won't tell you the full info... netsh advfirewall firewall show rule name=all > fw.txt will dump all your Windows firewall rules - then use notepad to search fw.txt for '8096' Mine shows this - Rule Name: Port 8096 - Emby non SSL ---------------------------------------------------------------------- Enabled: Yes Direction: In Profiles: Private Grouping: LocalIP: Any RemoteIP: Any Protocol: TCP LocalPort: 8096 RemotePort: Any Edge traversal: No Action: Allow Assuming your local LAN is 'Private' (it should be..) then this is the rule which allows your clients to communicate with Emby. Emby usually creates this for you when you install it - so it should be there. I hope this helps. **edit** just remembered, these were my own rules - but hunt for 'emby' or 'mediabrowser' based rules instead and i'm sure you will find them. Edited November 28, 2019 by rbjtech
Solution denzoid 57 Posted November 29, 2019 Author Solution Posted November 29, 2019 I finally figured it out...it turns out to be an ethernet cabling issue. I have no idea how an ethernet cable stops working but the one going to my Emby server did. Maybe mice ate it? But anyway, I had a roll of CAT5 sitting around so I ran a line directly from my router to the switch I have my Emby server plugged into (a switch which I replaced but that was not the issue) and BOOM! everything worked again! I'd like to thank all who replied especially rbjtech! I really appreciate the support! I am just so thankful to have my beloved Emby server back on this Thanksgiving holiday. 2
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now