Having trouble with remote access

[dhgoldman 0]

It still did not work when I turned the firewall off.  I checked to see if the server was running in task manager and I saw that the application is running which makes sense because I can access it from one computer but the emby server service is stopped and I can't start it.

[dcook 299]

So you can connect to EMBY from the local computer its installed on, but not from another computer.

Can you do an ipconfig from both computers and paste the results?  Also can you try ping from the 2nd computer to the computer that has EMBY?

[dhgoldman 0]

Exactly.  Below is the ipconfig from the computer running emby.  The other computer is my phone so can I still get that info or ping?

 

Windows IP Configuration

 

 

Wireless LAN adapter Local Area Connection* 13:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

 

Wireless LAN adapter Local Area Connection* 14:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

 

Ethernet adapter VirtualBox Host-Only Network:

 

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::a9f3:2a29:fdfd:7685%3

   IPv4 Address. . . . . . . . . . . : 192.168.56.1

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . :

 

Ethernet adapter Ethernet:

 

   Connection-specific DNS Suffix  . : home

   Link-local IPv6 Address . . . . . : fe80::ed47:d4cb:9ecd:688a%7

   IPv4 Address. . . . . . . . . . . : 192.168.1.11

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.1.1

 

Ethernet adapter Ethernet 2:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

 

Wireless LAN adapter Wi-Fi 3:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : home

 

Tunnel adapter isatap.home:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : home

 

Tunnel adapter Teredo Tunneling Pseudo-Interface:

 

   Connection-specific DNS Suffix  . :

   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:1830:24b:ba81:7e2b

   Link-local IPv6 Address . . . . . : fe80::1830:24b:ba81:7e2b%11

   Default Gateway . . . . . . . . . : ::

 

Tunnel adapter isatap.{2AA7EECA-1A2F-4640-977B-82320471C365}:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

[dcook 299]

So you have one interface using 192.168.56.1 and another using 192.168.1.11

Which of these is your emby server setup on?  

And what ip address does your phone get?

[dhgoldman 0]

Emby is set up on 192.168.56.1.  My phone is 69.126.xxx.xxx when its on wifi which is embys remote address

Edited May 12, 2016 by Happy2Play
Edited Remote Address

[Happy2Play 9780]

If canyousee.org can't see your external/remote address port you won't be able to connect remotely.

 

Something is blocking your port access.

Edited May 12, 2016 by Happy2Play

[Ponyo 22]

So you are running Emby server inside a VM? This might be causing problems because now you have a double NAT to deal with.

 

Go into VirtualBox and change the network adapter from NAT to bridged. Your server should now have an IP in the 192.168.1.xxx range. To keep things easy assign a static IP, something like 192.168.1.100.

 

On the Emby server login to the web interface and from the management page make sure local access is listed as 192.168.1.100:8096 (or whatever you set as the IP) and remote access is 69.126.xxx.xxx:8096 (or whatever your global IP might be).

 

Now on a different device on your local network (meaning a device assigned with a 192.168.1.xxx IP) open up the web browser and see if you can access 192.168.1.100:8096.

 

If that isn't working try pinging 192.168.1.100. If you can’t ping the server check the network setup on your VM and the VM host computer.

 

If you can access the Emby web page from your local network go into your router and make sure port 8096 is forwarded to 192.168.1.100.

 

Try connecting from outside your local network. I assume you are using the Emby android app and have an Emby Connect account set up on your server. You can also try browsing to 69.126.xxx.xxx:8096 from your device’s browser. You can check the Emby management page to make sure you are trying to connect to the correct global IP.

 

If that isn’t working and you are 100% that your port forwarding is set up correctly then go to your server, shutdown Emby, go into the windows firewall and remove everything related to mediaportal.exe or port 8096. Download the Emby installer and run it (don’t worry; this won’t touch any of your settings). Run Emby server and now the windows firewall should ask if you want to allow Emby. Accept.

Try again.

[dhgoldman 0]

Its not on a VM though.  I do have an ethernet connection to a laptop because I get faster internet through that than a usb wifi adapter I bought.  Could having multiple internet connections or going through the laptop be blocking access?

[dcook 299]

You are getting two different non routable ip addresses.  This is either because you have configured it this way manually, or your router DHCP is not setup properly.

Either way you have network connectivity issues, it is not a EMBY issue.

 

You said you are not running a VM, but in the IP CONFIG you posted it clearly says:

VirtualBox Host-Only Network 192.168.56.1

 

Did you setup all this yourself? or did someone else set it up for you?

 

No offence but I don't think you understand basic networking, and without basic network functionality EMBY is not going to work.

Edited May 13, 2016 by dcook

[Ponyo 22]

Its not on a VM though. I do have an ethernet connection to a laptop because I get faster internet through that than a usb wifi adapter I bought. Could having multiple internet connections or going through the laptop be blocking access?

Yes, it appears Emby is picking the virtual box adapter but that's not the right one.

 

It should pick the adapter with the 192.168.1.xxx address.

 

Go into the windows control panel -> network and sharing center -> adapters -> right clicking on the virtual box adapter and disable it.

 

Go into your Emby server and check if the local access address says 192.168.1.xxx.

[dhgoldman 0]

None taken, I am well aware I am a computer novice but I try to learn through these kinds of projects.  A while ago I tried to set up a VM so I could play old games but I never got it working.  The connectivity problem was fixed by uninstalling it though.  Thank you all for bearing with me.