logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
robhambly  
#1 Posted : Sunday, December 16, 2018 2:56:19 PM(UTC)
robhambly


Rank: Guest

Joined: 12/16/2018(UTC)
Posts: 3
Location: canada

Has anyone successfully configured this to work through Google Wifi hubs?

I switched to Google Wifi after my Apple Airport died after power outage..

You can't open ports directly on the Google Wifi hub - You can only open by machine. My Screenconnect runs locally on my main Mac, and if I open the ports 8040/41 for that machine via the google software, I can not connect via external connection.

I am able to connect ok locally.
SoCo_Systems  
#2 Posted : Sunday, December 16, 2018 3:58:52 PM(UTC)
SoCo_Systems


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 1/29/2014(UTC)
Posts: 118
Man
United States
Location: Indianapolis, IN

Thanks: 1 times
Was thanked: 19 time(s) in 19 post(s)
It has been a long time since I've touched a Google router, but I seem to remember I had to enter the port forwards, click save/apply, and then restart the router before the forwards would work correctly. It does work though. My primary, self-hosted ScreenConnect server is sitting behind a Google Fiber router.
robhambly  
#3 Posted : Sunday, December 16, 2018 4:31:40 PM(UTC)
robhambly


Rank: Guest

Joined: 12/16/2018(UTC)
Posts: 3
Location: canada

Thanks for the reply SoCo. It looks like Google Fibre you open ports directly ast the router level? (What I'm used to with all routers until now)

WIth the Wifi hubs you can only open ports at the machine level, which I haven't experienced before - and I'm guessing this is why I'm having the issue getting connected externally.

Originally Posted by: SoCo_Systems Go to Quoted Post
It has been a long time since I've touched a Google router, but I seem to remember I had to enter the port forwards, click save/apply, and then restart the router before the forwards would work correctly. It does work though. My primary, self-hosted ScreenConnect server is sitting behind a Google Fiber router.


SoCo_Systems  
#4 Posted : Sunday, December 16, 2018 6:11:13 PM(UTC)
SoCo_Systems


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 1/29/2014(UTC)
Posts: 118
Man
United States
Location: Indianapolis, IN

Thanks: 1 times
Was thanked: 19 time(s) in 19 post(s)
No, what you are seeing is just Google's attempt at dumbing down the process. Rather than manually entering an IP address to forward traffic to, like you would on most routers, Google has you pick from the known device list. Same thing, just a different way of going about it. When you create a port forward to a device, you are also opening that port on the router's firewall.
Try creating individual forwards, one for each port, rather than the range.
robhambly  
#5 Posted : Sunday, December 16, 2018 6:28:01 PM(UTC)
robhambly


Rank: Guest

Joined: 12/16/2018(UTC)
Posts: 3
Location: canada

Interesting - Thanks, I'll give it a shot.


Originally Posted by: SoCo_Systems Go to Quoted Post
No, what you are seeing is just Google's attempt at dumbing down the process. Rather than manually entering an IP address to forward traffic to, like you would on most routers, Google has you pick from the known device list. Same thing, just a different way of going about it. When you create a port forward to a device, you are also opening that port on the router's firewall.
Try creating individual forwards, one for each port, rather than the range.


Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.