Maybe an update messed it up. Thanks Adam, but there's no pending updates, static wired IP properly configured etc etc. Internet access is OK as is everything bar file shares and network discovery in the file browser. Oddest thing is that a W10 VM running on the same workstation has no problem reading everything as expected.
Mattheiu - Already been there, and I also disabled windows firewall and there's no AV in the way either. Alright let's go back to the basics then. You can ping the machines containing the shares Can you post the error you are getting when you are trying to access the shares? Remove all the network drive attached, go in registry and make sure the entries containing cached credentials have been removed :. Update - switched back to original static IP, all still good - whatever it was that flipped me out I have no idea!
I have been using windows since Windows1. I updated laptop beginning of December, had problems connecting through a share to another pc, kept getting share name not spelt right, missing protocols on this computer. Today decided to sort it out spent several checking, I could ping from and to laptop from other pc's.
Could see and access the laptop share from the other pcs but couldn't access them through the share on the laptop. Tried searching the web tried various things, came across this post and remembered that I had to do something like this years back on an old Microsoft version.
Many thanks for this. Recently upgraded all PCs to Windows 10 Pro. All other PCs can access shared drives on 2 of the PCs with no problem. Randomly, the shared PCs in question did not appear in the Network in Explorer, but have since come back. I have pfsense set-up at home and a site to site connected Ipsec connection to an ipcop at H. I had the same problem: w10pro unable to access remote shared folder.
Ping worked fine. Previous posted solutions did not work for me. Just change "allow windows to manage homegroup connections Greetings to all from Romania. I created an account just to post it, hope it helps someone else too. Good afternoon my win10 surface pro had mapped drives. Then I turn it on Monday morning and it can't connect to the drives.
I got the error above "windows can not access". What worked for me was mapping a new drive and checking the box "connect using different credentials.
That worked and it turned all my drives back on. Mine is a credentials issue. I have this workaround but I'm not sure it is a solution. Its a solution! Just check the box to remind your system on your user and passw. Bell Techlogix is an IT service provider. To continue this discussion, please ask a new question. Cloud Help Desk: Delays for ticket imports:. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Does anyone have the faintest idea what went wrong while I was away? Best Answer. This can happen if someone registered your IP on a different computer while you were away. View this "Best Answer" in the replies below ». Popular Topics in Windows Which of the following retains the information it's storing when the system power is turned off? Submit ». It is a storage device on a local access network within a business or home, allowing the content can be shared with other devices on the same LAN and even remotely over the Internet.
So, in order to create a shared folder or allow other devices on the same LAN to access the content, you need to map the network drive. You can fix the mapped network drives problems by creating and running two scripts either using the Startup folder or running a task when the user signs into their account.
Then click File , click Save as , and save the text file as MapDrives. You can run the scripts using the Startup folder. Open File Explorer.
