F5F Stay Refreshed Power Users Networks Unable to connect to your local machine.

Unable to connect to your local machine.

Unable to connect to your local machine.

D
DU5KF1RE
Junior Member
9
11-01-2016, 04:37 AM
#1
I operate a mesh network at home with devices connected directly to the router. I can reach the internet from 192.168.50.168 without issues, but I can't send or receive packets out of it. I'm unsure what caused this behavior. I tested pinging the gateway on both devices and it worked properly. It seems I only get a "timed out" message when trying to ping, not actual connectivity.
D
DU5KF1RE
11-01-2016, 04:37 AM #1

I operate a mesh network at home with devices connected directly to the router. I can reach the internet from 192.168.50.168 without issues, but I can't send or receive packets out of it. I'm unsure what caused this behavior. I tested pinging the gateway on both devices and it worked properly. It seems I only get a "timed out" message when trying to ping, not actual connectivity.

P
PopPunkKid
Member
100
11-01-2016, 10:24 AM
#2
Did you turn on the port in isolation mode? That will trigger this kind of result.
P
PopPunkKid
11-01-2016, 10:24 AM #2

Did you turn on the port in isolation mode? That will trigger this kind of result.

R
rebelzeina
Member
110
11-02-2016, 01:49 PM
#3
The isolation mode or firewall might be preventing access, or another device's firewall could be blocking it.
R
rebelzeina
11-02-2016, 01:49 PM #3

The isolation mode or firewall might be preventing access, or another device's firewall could be blocking it.

M
MCDark_Reaper
Member
146
11-02-2016, 02:15 PM
#4
The AP Isolation option in Asus appears to be disabled, and there doesn’t seem to be a specific setting for Windows Firewall. The search results might not be helping, or you have the right information.
M
MCDark_Reaper
11-02-2016, 02:15 PM #4

The AP Isolation option in Asus appears to be disabled, and there doesn’t seem to be a specific setting for Windows Firewall. The search results might not be helping, or you have the right information.

C
Cutie_Kitcat
Senior Member
644
11-02-2016, 03:40 PM
#5
Both devices are configured to enable Network Discovery.
C
Cutie_Kitcat
11-02-2016, 03:40 PM #5

Both devices are configured to enable Network Discovery.

R
ricby
Senior Member
681
11-03-2016, 12:39 AM
#6
They appear similar to what I see with my current network setup. Likely, the issue stems from the network discovery being disabled in the public settings. Private Public
R
ricby
11-03-2016, 12:39 AM #6

They appear similar to what I see with my current network setup. Likely, the issue stems from the network discovery being disabled in the public settings. Private Public

I
icas111
Member
79
11-03-2016, 11:41 AM
#7
On Windows, navigate to the Settings app (avoid Control Panel), then go to Network & Internet, tap on your network connection’s properties, and verify it’s labeled as Private. This ensures discovery tools work and your PC stays responsive to pings.
I
icas111
11-03-2016, 11:41 AM #7

On Windows, navigate to the Settings app (avoid Control Panel), then go to Network & Internet, tap on your network connection’s properties, and verify it’s labeled as Private. This ensures discovery tools work and your PC stays responsive to pings.