Windows VM suddenly can't see unraid shares?

[TyantA]

• Win 10
• Latest Unraid
• Can access internet

 

This VM has been fine for ages. I had to log in, so I presume it rebooted due to updates. Windows did give the slide-out notification of a "Network 2" connection, oddly. I told it I was on a private network. 

 

It's been a while since I've had to troubleshoot an error like this but I spent an hour and a half on it and got nowhere. (Enabled sharing devices on local network, set to private network, found & uninstalled the most recent Windows updates...) 

 

Any one run into the same thing & fix it? 

 

TIA> 

[JorgeB]

Make sure the VM is still using br0, bot vibr0.

[TyantA]

Thanks for the reply & idea. 

Just checked - Network Source: br0 is what it's set to. 

 

Edit: the only change I made - and this was AFTER the issue arose - was Fix Common Problems had warned me to change the docker network type to 
ipvlan, so that seems completely unrelated. 

Edited June 21 by TyantA

[JorgeB]

34 minutes ago, TyantA said:

so that seems completely unrelated. 

Should be, I assume you can still access the shares with other devices? If yes it would point to a Windows problem in the VM.

[TyantA]

Yes, I can. 

 

I assumed the same, so I just spent the last hour spinning up another VM and it too cannot access Unraid's shares...

[TyantA]

Update: 
Took a bit more time and tested: 

From within both VMs, I could NOT ping my router or the unraid web UI. That led me down the path to realizing both VMs were assigned an IP (DHCP) on the wrong subnet. I just haven't figured out why... and why that happened out of the blue, seemingly after Windows updates. 

 

I'm trying to determine if that's an

• unraid core setting issue - don't think so Network Settings shows the correct subnet for its IPv4 address, gateway and DNS server. 
• In Windows itself - why would it, when set to use DHCP, not pick up the correct subnet? 
• A VM config issue. It's just set to use br0 which, under network settings shows the correct subnet under "route".

So... it must be the 2nd then. I guess I'll manually assign an IP and see what happens... 

 

Edit: Manually assigning an IP on the correct subnet (obviously) worked on the new VM I spun up. 
I still have no idea why it changed (guessing windows updates) moreover why it's not automatically picking up an IP from the correct subnet. 

Edited June 22 by TyantA

[JorgeB]

If the VMs are using br0 they will get an IP assigned from your DHCP server, usually your router, if they were being assigned an IP from a different subnet, you likely have more than one DHCP server on your network.