connect to remote drives after 1803 update fails

Been looking for a fix for this for a little while, haven't found anything so far, if I missed a post here in my quick searching forgive me :)

I updated to Win 10 1803 last week. Now whenever I try to access a remote server or computer drive Windows is too stupid to find it.

For example, if i try and access \\server1\f$\inetpub\wwwroot in explorer windows fails to find the server.

However i can ping it, I can RDP to the server and access those folders without issue. I just can't figure out what changed so i can't remote to the F drive anymore. I was doing this probably daily previous to the update.

Ideas?

EdTittel said:

If you check this TF thread Cannot access Admin shares Solved - Windows 10 Forums, you'll see this kind of thing happens when the network gets reset from "Private" to "Public." Bet that's what happened to one or both of your PCs. It's not an uncommon side effect of a feature upgrade. Here's a tutorial on making that switch: Set Network Location to Private or Public in Windows 10.
HTH,
--Ed--

good info there, I've bookmarked that thread for reference.

However my connection is set as "Work". These servers are in a domain. I think i found my issue though.

The day i wrote the OP, i was working on a specific group (our development) of servers. All of those servers were failing to allow windows to connect with the c$. Didn't dawn on me then that i was also connected to our production and test servers the same way. I do this so often i have shortcuts setup for the production and test servers. I don't use the Dev servers much. Habits form and you forget the basics.

Anyway, thanks for your time. The network admins are restoring the DNS entries to these servers so we can connect to them with name\c$. After i figured out my brain lapse, the IP address\c$ connection worked fine.

One thing the network team found that may be helpful to others -

2 of the servers i was trying to connect to were 2003 server, and it doesn't support SMB 2, or SMB Direct as it's listed in Windows features. I had to enable "SMB 1.0/CIFS File Sharing Support" to connect to the 2003 servers again. Evidently the update to 1803 disabled that for me. Gotta love when that happens.