2.4.0 Login

I've got the C7 and updated with 2.4.0.139 and cannot login into the hub on my PC with Windows 10. I can find the hub but get "cant't reach this page" message. I can get into it via my Ipad and Macbook but not the PC. This has been an issue since 2.4.0.128

Update to the current version first.

Are you sure you are browsing to the correct IP on your PC?
Try using My Hubitat to get in.

3 Likes

Yes I have The same on the MacBook and PC but only the MacBook works. I clicked on the link you sent and it finds the hub, but will not connect via the pc

That’s some sort of routing issue on your Lan then. Try command line arp -a on the windows
Machine. Look for the IP and if it’s there verify the MAC shown matches your hub.

Another person did this exercise and found they had two devices on the lan fighting over the same IP

1 Like

When I use that command, the IP address is not on the list.
I have confirmed this IP address by looking at the hub details on my MacBook. and have looked at my router and see the same ip address and mac ID

Did you try to reboot the hub?

It’s a networking issue. Is that machine possibly connected to an isolated network like a guest wifi or something?

What is the IP of the windows machine and what is the IP of the hub?

1 Like

@Lakecrest

Is there a VPN client running on your Windows machine?

No VPN
Same network
MacBook on Wi-Fi
PC wired to same network as hub
Windows PC wired - ....5.18
MacBook - ...4.50
Hub - ...4.63

Pulled cord to get PC Wi-Fi (...4.45) and now can connect to hub
Reattached cord and cannot get to hub again

Does anyone have a clue why the PC can only attach to the C7 hub via Wi-Fi?

What’s the subnet mask set to on the hub?

Because your hub is on the .4.x subnet and your PC was on .5.x when on ethernet.
Unless you have a subnet mask that spans more than 255 IPs?

Not sure why you sure hiding the full IP, if its a private LAN those numbers do not mean anything outside of your local network.

2 Likes

All at 192.168.x.x I'm not sure why the PC is at .5 I noticed the only other items on the network that are at .5 are the DirectTV boxes

What you may not realize is that your PC will have a different address on both the Ethernet and the Wi-Fi connections.

In this image you can see that my Ethernet IP is 192.168.100.184 and my Wireless IP is 192.168.200.101

The address of my hub is 192.168.100.161, so by default, I can only connect to it over Ethernet. (in reality I have setup firewall rules to allow a Wi-Fi connection to the hub, but that isn't relevant in your situation).

The address of your MacBook on Wi-Fi is 192.168.4.50

Since the address of your PC (wired) is 192.168.5.18, it looks like your Wi-Fi network is not on the same LAN as your wired devices. That probably means your Wi-Fi is setup as an isolated "guest" network.

You didn't say if your hub was connected by Wi-Fi or ethernet. but since it has an address that belongs to your Wi-Fi network, it must be connected by Wi-Fi.

So in the current configuration, only devices connected to Wi-Fi can connect to your Wi-Fi connected hub.

There are methods to resolve this limitation depending on your network hardware, and your security needs.

I'm looking into how to resolve... May need to reserve IP for wired PC. My hub (.4.63) is wired, so I'm not sure why EERO chose .5.18 for the wired PC

Still Confused... I set Wired PC to .4.150, rebooted PC and Hub, and still no luck connecting on wired PC.

Same network or same exact device?
What is the hub plugged into and what is the Laptop plugged into? Both the same eero node? I assume you have a mesh setup with multiple access points? Do you have any other network hardware that other the eero and some sort of modem?

Run ipconfig /all from command line and post a screenshot similar to what @user5298 showed above. It would be good to see it both from the wired connection and the Wifi to see if there is any differences. You may wish to mask the IPV6 addresses as I think technically those are exposed to the internet, could also hide the MAC if you want. Everything else should be private LAN info and there is no harm in posting.

IIRC Eeros default to an odd choice of subnet mask, /22 I think?

So your Eero gateway might be assigning addresses in both the x.y.4.1 and x.y.5.1 ranges.

If that’s the case, the network in the eero app can be reconfigured to a /24 subnet, e.g. x.y.4.1 or x.y.5.1 (but not both).

They said the hub did not even show up in the arp list. I know HE does have issues with subnets that are not /24, maybe that has something to do with it. Seems like the laptop should still be able to see it though, the HE issues I think were just in the UI at this point.

I would definitely start with setting the subnet mask to 255.255.255.0 (or /24) and see if that makes a difference at all. May need to restart a bunch of devices so they pull new DHCP info.

The PC, HE hub and eero are wired to an unmanaged ethernet switch.
I set the mask to 255.255.255.0 in the eero, but still do not have connection with the wired PC even though the wired IP address has changed.

For some reason the wired PC is still not seeing the HE

Do you have anything else that can connect via ethernet? Plug into the same port as the laptop was using, I suspect the results will be the same. Its some sort of networking issue, I have no idea what it would be though.

You can also try running this IP scanner to see if it find anything different from arp
https://angryip.org/