Connecting Through Google WiFi

[MrSerendipity 0]

I'm not sure I even know how to explain my problem but I'll try my best.

 

I recently moved to a new state, where I'm staying with family until I buy a place of my own. While I'm here, I've connected my Google WiFi system to their modem in another room. I have another Google WiFi in my room that I have my PC (which hosts my Emby Server) connected to via Ethernet. When I went to Port Forward on my Google WiFi system, it only allows me to Port Forward devices. Thus I did two port forwards for my PC, one for 8096 and another for 8920, because that was all I knew to do. It doesn't give you much to fill in. Am I going to have to also Port Forward the family member's modem? If so, I don't think it's possible as it greys out all but the last entry of the IPV4 and the entries before it don't match my PC's IP. 

 

I know, this was probably terribly explained but I'm so confused at this point that I can't make sense of basic math.

[Carlo 4561]

Your Emby server should still work correctly for any devices connected on your Google WIFI system but not from the Internet or even possibly from the house WIFI.

 

You have a double NAT situation.  If you need access from outside the house you will need to assign a static or reserved address for your router from the main house router, then setup the house router port forwarding to pass through to your router.

 

So basically you need to setup Emby then also manually setup the two layers of routers.

 

Make sense?

[MrSerendipity 0]

Sure, I can take a look into all of that. With that said, Emby is only working on my PC. (Possibly because its connected via Ethernet?) None of the devices that I also have connected to the Google WiFi via Wireless can connect. That includes iPhones, Apple TVs and Roku TVs.

[Carlo 4561]

Are you connecting to the same WIFI "subnet" that your server is on?  Same IP range?

[MrSerendipity 0]

I believe so, Emby is running on a PC that is connected via Ethernet to one of the Google WiFi ports. All of the devices that I'm attempting to view my server on, are connected to one of the three Google WiFi ports. Sadly, I think this is where a lot of my tech savvy-ness comes to a head. I've created a static IP for the Google WiFi. I created a Port Forward on the Main Router for the IP of the Google Wifi and I had it start with 8096 and end with 8920. I think that should be right?

 

Now, I'm in a position in which I need to do something with the Google WiFi. I can do port forwarding in the Google WiFi app but you have to do it by device. I'm assuming that I should do the PC, as that is what my Emby server is on. So I go to create a rule for the PC but the PC has an IPV4 address that is far different (in terms of final two numbers) than my Google WiFi port that I created the previous Port Forward for. I've created the rule that will Port Forward 8096 through 8920. 

 

After doing all of that, it still doesn't work. It won't even work in the home, on devices also connected to the Google WiFi. I genuinely have no idea what to and I apologize for the confusion. I had Emby working flawlessly for the last year in my previous home and Plex working for several years before that. This is the first time I've run into a connection issue but then at the same time, this is also the first time that I haven't been connected directly to the Router.

[MrSerendipity 0]

UPDATE: I have it working inside of the home now. Somehow I had managed to switch my PC over to Public as opposed to Private when I was troubleshooting things. Switching it back to Private made it work within the home. Its still not working outside of the home however.

 

 

Additionally, I've been able to confirm that my IVP4 on my PC is "outside of subnet range" when compared to the IP of the Main Modem. I don't know how to rectify that as it seems the IVP4 Address isn't something I can control on my PC.

Edited March 13, 2019 by MrSerendipity

[Luke 42085]

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 !

[MrSerendipity 0]

I'm at a loss, I've been looking at this all day and very simply don't know what to do at this point. I might just not be able to use Emby externally until I'm in a new home and can directly connect. I've set up a Port Forward on the main modem, it's connected to the IP for my Google Wifi system. For the Start Port I put 8096 and for the End Port I put 8920. When I go on my Google Wifi, I'm getting an IP 192.168.86.XX (hid the last numbers) for my PC that hosts the Emby server. When I select that, I can enter an external port and internal port for TCP. I've tried entering 8096 and 8920 each different way in those options for the rule. Nothing opens up for me. I feel as if the issue is the Google WiFi system does Port Forwarding for Devices, as opposed to just IPs in general.

[Luke 42085]

What were the results of each test in our connection troubleshooter?

[Carlo 4561]

You're doing a few things wrong.

First remove the port forwarding you have setup on the home router.  You've open up hundreds of ports that should not be open.

 

 

Next we need to know if you have setup SSL on your server or not.

We need to know what the values show for this box on your dashboard:

 

Let's start with that as far as Emby is concerned.

 

Now we need to know a couple of things about your LANs

1) What is the home router IP address for the inside network?

2) What is the IP address of the Google WIFI router on it's outside/public side.  This is the side connected to the home network in step 1.

3) Is this a fixed IP or Reserved IP address?  If not we need to make it so.  We can't have this IP changing or it's going to break your forwarding.

4) What IP address space do you have setup for the Google WIFI router space?