Thank you for helping out. How exactly I can maintain this connection?
what i meant was to connect to it via a unc path. \192.168.32.62\config
enter that in file explorer or in a cmd window do:
net use * \192.168.32.62\config
that creates a connection to your homeassistant for filesys access. would be interesting to see if that connection is reliable or if it times out as well.
Thank you. When I enter net use * \192.168.32.62\config into CMD on my client pc i get that System Error 67 occurred. The network name cannot be found.
Thank you. Now it took like 30 seconds to actually show some message, but still I received same error:
System Error 67 occurred. The network name cannot be found.
The reason I wanted to see all of the IP addresses in one post was to verify that all the pieces are on the same subnet. I do not use VMs or containers but I have seen cases where the VM IP address is different from the Home Assistant IP.
Boyudag - Are you using a separate PC to ping Home Assistant? Also, why can’t you connect Home Assistant by Ethernet? That would seem to be a preferred fix to the issue.
up above a bit he says he’s pinging it from his separate pc and is able to do so.
that’s what he’s trying to figure out. he’s trying to connect it via hardwire ethernet from his client pc to the vm running on the host pc but that’s failing. however when he pulls the ethernet and runs over wifi from that 2nd client pc, it works.
so far, i’m a baffled, so trying to eliminate different elements to narrow down to the problem component.
I would like the same. I suspect that his device is configured to use Ipv6 binding first on the ethernet segment (default for win10+) while ipv4 on wifi (depends on how dhcp is set on the two segments.) if ipv6 is misconfigured it would do exactly what op says. Works on wifi and doesn’t work on ethernet. But it’s actually an ipv6 DNS issue v. Ipv4 DNS.
Application installed. I receive same error System error 67. Strangely I do see that some kind of Linux appeared in the tab:
To sum up, correct here’s my current build:
Host PC on Windows 11 connected to the internet via Wi-Fi running Virtual Box with Home Assistant running on Linux 64.
In a different room there are 2 PC that are connected via Ethernet cable to the internet. Both PCs CAN ping the IP address of the home assistant, but can’t open up the http://homeassistant.local:8123/ address - Request takes too long.
If I unplug the ethernet cable and enable Wi-Fi on my client PC, I’m able to open up the address.
As mentioned previously, it was running perfectly fine for a 3-4 days before that. I turned off the Client PC, went to sleep, woke up, started pc and no longer able to access it.
Yes, rebooted everything - router, client pcs and host pc. IP reservations? How to check that? I’m not using any static ip and haven’t made any network changes at all during my initial internet set up.
. super useful.
