Remote Connection Timing Out on Remote Address

[Iyashii 1]

This has likely been asked before, but as far as I can see my settings are all correct. I updated to 4.7.8.0 yesterday and since then my external address is timing out. I'm not able to see the address/port active externally.

ISP is AT&T Fiber 500/500. Tracert to 8.8.8.8 from Emby server shows 2 hop 107 address and 3 hop 75 address.

Emby is running on Windows 10 up to date. Firewall port forwarding inbount TCP allowed on ports 8096 and 8920. Network router port forwarding range 8096-8096 tcp/udp host port 8096. Same for 8920.

Emby server settings: network local http/https ports 8096/8920. Allow remote connections to Emby server enabled. Remote IP address filter mode Whitelist. Public http/https ports 8096/8920. Enable automatic port mapping disabled.

CanYouSeeMe.org showing service not seen on remote address:8096 reason connection timed out. Connection times out when trying to access externally.

[Abobader 3464]

Hello Iyashii,

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

[Iyashii 1]

Issue may stem from a port forwarding issue on the router. Will update if more info is found.

[Luke 42080]

Let us know what you find. Thanks !

[Iyashii 1]

I think I found the issue. My router is a bgw320-505 for AT&T Fiber. Long story short in order to get the device to properly forward the ports:

1. Disable IPv6 on the router; Home Network\IPv6\IPv6 Off
2. Set IP Passthrough on router; Allocation Mode: Default Server; Default Server Internal Address: Manual Entry
3. Add custom NAT/Gaming Service; Firewall\Nat/Gaming\Custom Services. Service Name, Global Port Range 8096-8096 Base Host Port 8096 TCP/UDP.
4. Assign new Custom Service to Application/Device: Firewall\Nat/Gaming: Service: (use custom one), Needed by Device: Select your device by device name.
5. Set Windows Firewall Inbound Rules (both TCP and UDP) for the port (8096) on the Windows machine (if applicable).

Once all that has been done and Emby server has port 8096 set and disabled automatic port mapping, the port should now be active.

[Luke 42080]

Thanks for following up !

[Q-Droid 989]

4 hours ago, Iyashii said:

2. Set IP Passthrough on router; Allocation Mode: Default Server; Default Server Internal Address: Manual Entry

You might want to go back and review what you changed on the router.  If I'm not mistaken the #2 step put the internal address in a DMZ making all unsolicited internet traffic go to your Emby server. In other words the system with the given internal address is fully exposed to the WAN.

The other steps to setup the port forwarding should have been enough.

[Iyashii 1]

On 10/7/2022 at 8:35 PM, Q-Droid said:

You might want to go back and review what you changed on the router.  If I'm not mistaken the #2 step put the internal address in a DMZ making all unsolicited internet traffic go to your Emby server. In other words the system with the given internal address is fully exposed to the WAN.

The other steps to setup the port forwarding should have been enough.

Correct; I was able to disabled IP Passthrough and the port appears to remain active, though it was not showing active prior to enabling passthrough but that could also have been a delay between changes at the time.

[EddyMerkxs 17]

On 10/7/2022 at 2:52 PM, Iyashii said:

I think I found the issue. My router is a bgw320-505 for AT&T Fiber. Long story short in order to get the device to properly forward the ports:

1. Disable IPv6 on the router; Home Network\IPv6\IPv6 Off
2. Set IP Passthrough on router; Allocation Mode: Default Server; Default Server Internal Address: Manual Entry
3. Add custom NAT/Gaming Service; Firewall\Nat/Gaming\Custom Services. Service Name, Global Port Range 8096-8096 Base Host Port 8096 TCP/UDP.
4. Assign new Custom Service to Application/Device: Firewall\Nat/Gaming: Service: (use custom one), Needed by Device: Select your device by device name.
5. Set Windows Firewall Inbound Rules (both TCP and UDP) for the port (8096) on the Windows machine (if applicable).

Once all that has been done and Emby server has port 8096 set and disabled automatic port mapping, the port should now be active.

THANK YOU for this. Just got that ATT router and was having trouble getting connected.

So what worked for me is just steps 3 and 4. I had done 3 already and it wasn't working. I had to do 4 to get it to stick. This was huge thank you!

[11thour 1]

Update,   BGW320-500,

If you are using your own network equipment and want to fully manage your own network and you just want to use the ATT router as a media converter (Fiber to copper ethernet) [ATT still has control of the box and you can not get around this].

Simply Go to Firewall and turn off each service, then turn on IP Passthrough.

Off - Packet Filter

Off - NAT Default Server

Off - Firewall Advanced

ON - IP Passthrough

EMBY, Plex, and all my network items are now happy once again.

 

[HanSolo 21]

Kind of new here but I wanted to add my experienc, thankfully this thread gave me the clues I needed to get things working. 

Just got AT&T Fiber, I have the BGW320-500 modem. Am running Emby on an ASUSTOR AS-604T NAS. The network has 2 NIC's configured for Adaptive Load Balancing. 

I just fiddled around for an hour trying to get port forwarding to work, I finally figured out it was IPv6.

I want to keep IPv6 on for my network, was able turn IPv6 off on the NAS to get Emby to work for remote hosts. Not sure what's going on here, open DM's if someone wants to troubleshoot further, happy to help.

Can confirm that steps #3 and #4 work. One only needs TCP though. 

 

 

 

[GHynson 9]

I just set up my new AT&T BGW-320 Fiber Modem and removed my old Spectrum Modem.

I've followed these steps above but my external Emby connection is still being refused.

 

This was my old Spectrum setup which worked fine with Emby.

Spectrum's modem  WAN IP 66.x.x.x  going to my ASUS GT-AC5300 Router With IP 10.0.0.1

ASUS router saw the modem's WAN 66.x.x.x and passed that traffic through it's own DHCP server assigned  internal LAN addresses 10.x.x.x.

The Emby server is at 10.0.0.9 and I have my ASUS router port forward all emby traffic to 10.0.0.9:8096

Everything worked fine.

 

However with this new AT&T modem, I noticed both an WAN IP of  23.124.x.x and the modem device IP of 192.168.1.254

Asus router gets it's WAN IP of 192.168.1.1 via the ATT modem's DHCP,  and then using it's own DHCP assigns IP's to my 10.0.x.x LAN 

I've tried turning off the BGW-320, DHCP server so the ASUS router would use the 192.168.1.254 as the devices WAN IP.

But turning off the Modems DHCP bricks my Asus router and it can't get to the internet. Asus router states it can't get an IP address from the modem.

 

All the computers behind my Asus router has internet access working fine with the ATT setup but can't access emby externally.  

Is there something I'm still doing wrong?

 

 

 

 

[Q-Droid 989]

Right now you seem to have a double NAT condition. Check the Firewall -> IP Passthrough settings to see what allocation and passthrough modes you're in. If they look correct then reboot the Asus router, not the gateway.

 

Edited November 5, 2023 by Q-Droid