Windows 10: connect to remote drives after 1803 update fails Solved


  1. Posts : 12
    Win 10 Enterprise x64
       22 May 2018 #1

    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?
      My ComputerSystem Spec

  2.    24 May 2018 #2

    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--
      My ComputersSystem Spec


  3. Posts : 12
    Win 10 Enterprise x64
    Thread Starter
       24 May 2018 #3

    EdTittel said: View Post
    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.
      My ComputerSystem Spec

  4.    30 May 2018 #4

    Glad you got it sorted. Hope you find the other information cited both useful and interesting.
    Best wishes,
    --Ed--
      My ComputersSystem Spec


  5. Posts : 12
    Win 10 Enterprise x64
    Thread Starter
       30 May 2018 #5

    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.
      My ComputerSystem Spec


 

Related Threads
Hello, Iíve made 5 unsuccessful attempts at upgrading to the latest 1803 version. Each time it fails at the first reboot with an error 0xc1900101-0x30017. Had the exact same issue with the 1709 version too and had to do a clean install then. Iíve...
Hi all, I have SBS 2003 domain controller and there is a problem with new release Win10 1803. When I make clean install (ISO), it cannot join DC with general error message: - cannot contact AD DC for domain XY - make sure the name is correct...
Installing win 10 pro x64 using usb and mounted ISO. Both failed. It failed several times and the installer exits with a very uninformative window saying Windows 10 installation has failed. I was running Controlled Folder Access and the...
Wifi fails to automatically re-connect after Sleep after Windows 10 - Microsoft Community Been looking all over for a solution & there is none. There is no power management tab in the driver properties. Worked fine until the upgrade to 1703....
Can't connect to remote printer in Network and Sharing
I'm using windows 10 and I'm trying to connect to a printer attached to a remote networked Windows 7 Pro computer. When I go to Settings/Devices/Add printer my printer attached to the remote computer shows up. When I click on the printer I get a...

Tags for this Thread

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:18.
Find Us