Moved and got new ISP, can't connect remote

[iamjarbear 8]

I just moved to a new home, me ISP. Originally on spectrum and now on ATT Fiber. New router -Model BGW320-500. Long story short, I've read all the knowledge articles on connectivity/remote setup and I still cannot get it up and running remote. Probably dumb of me but I even reset the entire server and started it from scratch. Still no go. Any assistance would be greatly appreciated 

 

 

Edited July 29, 2024 by seanbuff
redacted IP

[Happy2Play 9781]

Best guess may be CGNAT from ISP.

But you will need to go over port portwarding just in case UPNP is actually not working also.

https://emby.media/support/articles/Connectivity.html#setup-port-forwarding

https://emby.media/support/articles/Remote-Setup.html#:~:text=Verify Public IP and Port

 

 

[Happy2Play 9781]

You should edit or remove your WAN address above.

But your port appears to be open so may need to look locally at firewall.

What platform do you have Emby installed on?

Can other clients on your LAN connect to Emby?

[iamjarbear 8]

22 minutes ago, Happy2Play said:

You should edit or remove your WAN address above.

But your port appears to be open so may need to look locally at firewall.

What platform do you have Emby installed on?

Can other clients on your LAN connect to Emby?

All local devices are able to connect. When I do port test on canyouseeme it comes back with Error: cannot see your service. Reason: timed out

 

37 minutes ago, Happy2Play said:

Best guess may be CGNAT from ISP.

But you will need to go over port portwarding just in case UPNP is actually not working also.

https://emby.media/support/articles/Connectivity.html#setup-port-forwarding

https://emby.media/support/articles/Remote-Setup.html#:~:text=Verify Public IP and Port

 

 

I ran tracert 8.8.8.8 to see if it was CGNAT issue but I'm not entirely sure I'm following. It says if it starts with 10., 192., 172. And the second number is between 16-31 it means it's the ISP blocking. So on line 7 of the trace I received 172.253.... does that fall into the above category of 16-31 (decimal wise yes but I don't know if that matters for ip)

[Happy2Play 9781]

1 minute ago, iamjarbear said:

All local devices are able to connect. When I do port test on canyouseeme it comes back with Error: cannot see your service. Reason: timed out

 

I ran tracert 8.8.8.8 to see if it was CGNAT issue but I'm not entirely sure I'm following. It says if it starts with 10., 192., 172. And the second number is between 16-31 it means it's the ISP blocking. So on line 7 of the trace I received 172.253.... does that fall into the above category of 16-31 (decimal wise yes but I don't know if that matters for ip)

Looks like your WAN address has changed as port times out and your 443 att login page is no longer accessible.

Sorry but don't really follow but you are looking at the hop to see if you have multiple none routable addresses.  But unless something just changed I don't think you are on a cgnat as I was able to see port open previously.

You can post the tracert removing third and fourth octets to get a better answer.

 

 

[sa2000 674]

I added a section on CGNAT here https://emby.media/support/articles/Remote-Setup.html

If the public IP is in range of 100.64.0.0 - 100.127.255.255 then it would be a CGNAT address and the solution would be to pay for a static public IP address

 

[Q-Droid 989]

Did you forward ports on the BGW? 

Do you have another router connected behind the BGW? 

AFAIK ATT doesn't use CGNAT. 

Don't rely on UPnP for port mapping. It should be avoided/disabled. 

 

[iamjarbear 8]

3 hours ago, Q-Droid said:

Did you forward ports on the BGW? 

Do you have another router connected behind the BGW? 

AFAIK ATT doesn't use CGNAT. 

Don't rely on UPnP for port mapping. It should be avoided/disabled. 

 

 

7 hours ago, sa2000 said:

I added a section on CGNAT here https://emby.media/support/articles/Remote-Setup.html

If the public IP is in range of 100.64.0.0 - 100.127.255.255 then it would be a CGNAT address and the solution would be to pay for a static public IP address

 

Ok so slightly an idiot here and I think we probably need to start over on troubleshooting because again, I'm an idiot and changed stuff.... I have the BGW router set up in Passthrough Mode for My Synology Router (RT2600AC). TRACERT image below
 

[Happy2Play 9781]

So you have a Double NAT your personal router and ATT router correct?

If so have you done port forwarding on both routers?  ie forwarding router to router

[js28194 36]

Yeah, with AT&T (no CGNAT) and you are most likely double natted.  Below is a link that you can try to follow since I didn't see you actual model # in this post, but the process should be similar/same.

 

https://community.ui.com/questions/BGW320-500-Bridge-Mode-and-or-IP-Passthrough-Question/99786f13-1f76-46dd-9801-7102fd1d44d7 

 

 

[iamjarbear 8]

15 minutes ago, Happy2Play said:

So you have a Double NAT your personal router and ATT router correct?

If so have you done port forwarding on both routers?  ie forwarding router to router

I setup the Passthrough to the Synology router. 

[Happy2Play 9781]

And you have all port forwarding done on Synology router also?  Or trying to depend on UPNP port mapping?

 

 

 

[iamjarbear 8]

17 minutes ago, Happy2Play said:

And you have all port forwarding done on Synology router also?  Or trying to depend on UPNP port mapping?

 

 

 

This is what I have setup on the Synology Port Forwarding.

[Happy2Play 9781]

2 minutes ago, iamjarbear said:

This is what I have setup on the Synology Port Forwarding.

Looks like you are set as I can see you Emby login page at least on 8096.

[iamjarbear 8]

45 minutes ago, Happy2Play said:

Looks like you are set as I can see you Emby login page at least on 8096.

Local works no issues, it's just the remote access. When I check on canyouseeme it still says timed out. 

 

 

Edited July 29, 2024 by GrimReaper
WAN IP masked

[Happy2Play 9781]

23 minutes ago, iamjarbear said:

Local works no issues, it's just the remote access. When I check on canyouseeme it still says timed out. 

Sorry but that is not Emby port (8096).  8920 fails do to you don't have it configured on ATT router I will guess.  But at the same time not needed until you have your own SSL configured.

Edited July 29, 2024 by GrimReaper
Quote trimmed

[Happy2Play 9781]

Also will need a mod to edit your image or you delete it as you got one IP but not the other.

Edited July 29, 2024 by Happy2Play

[iamjarbear 8]

12 minutes ago, Happy2Play said:

Sorry but that is not Emby port (8096).  8920 fails do to you don't have it configured on ATT router I will guess.  But at the same time not needed until you have your own SSL configured.

Im not sure what I did or if it just needed a minute to update by after going through and taking all these screengrabs with you, it seems to be working now. I appreicate all the help. The solution appears to be doing the IP Passthrough followed by adjusting the port warding.

[Q-Droid 989]

When you passthrough the BGW you want to disable everything else on that device. No filtering or forwarding or NAT settings. All disabled. Then only your second router is in play and needs the settings. 

Also bounce them both when you make changes like these. 

[Q-Droid 989]

5 hours ago, Happy2Play said:

So you have a Double NAT your personal router and ATT router correct?

If so have you done port forwarding on both routers?  ie forwarding router to router

Unfortunately this is normal when the ATT gateway is in Passthrough mode. It's not a true bridge mode so the internal IP from the gateway shows up in the trace route.

 

[js28194 36]

On 7/29/2024 at 3:31 PM, Q-Droid said:

When you passthrough the BGW you want to disable everything else on that device. No filtering or forwarding or NAT settings. All disabled. Then only your second router is in play and needs the settings. 

Also bounce them both when you make changes like these. 

This is correct.  You only use passthrough, based on the link I provided above.  You input your ROUTER MAC address in the AT&T gateway.  This allows the BGW to pass it's public IP to your router.

Then you create your port forward rules in your router.  I am not if its on purpose or oversight or just your naming convention you use, but UnPnP client seems odd wording but I digress. Also, try only 1 first.  In your Synology Router, create a port forward rule inbound 8096 but TCP/UDP to your internal server.  Get that working without SSL, then think about your next move to enable SSL.

As already stated above, you are testing the incorrect port, you are testing port 80 and EMBY is/should be running on port 8096.  Double check again.

Edited August 2, 2024 by js28194