Trouble with network storage after reboot

[TuckNTruck]

I've got my Aux 1 folder set to a network folder on a different PC in my house. I only use this for long term storage of clips I manually save. Nothing happens on this drive automatically.

Recently Windows did a big update or something (the reboot process took 15+ minutes and gave me a big welcome to windows screen after it finally updated/restarted).

Now whenever I restart the PC, BI says NAS location can't be reached. When I try to access the network storage folder from file explorer it asks for my credentials, but won't accept any the username/password for any of my machines.

Once I go to Network Connections and disable/enable the ethernet connection on my BI PC (the one that did the windows update), everything works fine. I can access the network folder without entering credentials and BI sees it without having to do anything there either. Next reboot, I have to disable/enable the ethernet connection again. The internet connection works fine before the disable/enable. It appears to just be a LAN issue?

It's clearly not a BI problem since I can't access the network folder in File Explorer either, so is this is bug with a windows update or am I missing something obvious?

 

[TonyR]

Insure that the Windows Update did not change your NIC's network properties from "Private" to "Public."

Although I don't see how this would cause your particular issue but an update has been changing the network properties and causing other network issues for many people.

 

[TuckNTruck]

Insure that the Windows Update did not change your NIC's network properties from "Private" to "Public."

Although I don't see how this would cause your particular issue but an update has been changing the network properties and causing other network issues for many people.

Yeah, it did change it. First time after update, that entire page was different and didn't even let me select private/public. After disable/enable cycle, those options opened up so I could put it back to private. Works fine until next reboot when another disable/enable cycle is required. There are a few tutorials on youtube about this or similar issues after the update and I've followed them all the way to resetting network adapters and reinstalling drivers etc. No change. I guess I need to look into rolling back to a previous windows version if that's even an option. Very frustrating to have a nice problem-free system running for a long time only to have a windows update mess it up.

 

[TuckNTruck]

Well, fingers crossed but it looks like I got it resolved. I was fumbling around in some windows security/firewall stuff and noticed it was saying I needed to verify login details for my microsoft/windows account. It sent a code to my email, plugged that into the box, it restarted and problem is solved. So I still don't understand why it acted the way it did, because it seems like resetting the ethernet adapter shouldn't bypass a missing account verification, but whatever. I've rebooted several times and it's working as it should again.