See the domain it has is the win10 box computer name -- which sure in the hell is not the domain or name of my i5-w7 box. Close the Registry and Reboot Windows I'm having a very similar problem, where the permissions exist, but the path is not accessible to the user. On windows 10 in the username box instead of entering just the username enter the computer name plus the username. I have made sure that all relevant computers have discovery turned on but that didn't change anything either. Let us see how to fix this issue. I do not even get as far as a challenge for credentials. Many resources are stored on network file shares for collaboration, security, and data protection reasons.
Both are connected to the router via Ethernet and I myself am connected to the router via Ethernet as well. But am unable to connect with Finder. I've run out of solutions. A Windows Security box will ask for login information for the network file share. Also, the following steps almost always fix the problem but again it only lasts for a day or two or sometimes a few hours. Good afternoon my win10 surface pro had mapped drives.
I'm on build 10240, seems that some people who upgrade to this build unable to use net drive, and I did upgrade from 8. On the server side, the folders are all intact. Try mapping my by both name and ip address, sometimes one will work when the other doesn't. You will see the client box is unticked. Below is a link to the fix. First, select the letter you want to assign to the drive you are about to map. Also restarting the computer which hosts the shared drives also doesn't seen to solve the problem for more than a few hours.
These are both Win 7 Pro machines. Click on it and the wizard starts. Thanks very much for any help. Would you like to answer one of these instead? And you can access this drive while you are connected to the Local Area Network. He started with Windows 95 and is good at software usability testing. When my clients logged on, they couldn't see their network drives. I can ping the bejezus outta it.
I am just not able to access the external hard drive that I can on the local network. Have not been able to restore yet, very irritating. If it does contain data. There are lots of other fixes to try, too -- a distressingly large number, in fact! I also have a second Network Storage device, a TeraStation Live. To do it, take the following steps: Step 1.
If the network drive is made using name instead of ip address. Is it in a workgroup or a domain member? But perhaps in your answer you should have provided an example of your explanation. That worked and it turned all my drives back on. The issue appears to be effecting only this one client computer. Normally when you connect to a network drive it prompts you for your username and your password. Restoring Network Connections: An error occurred while reconnecting Z: to Network folder i. This isn't the only weird thing about my home network that is happening under Windows 10 and I should probably mention the rest as it may bear on this problem.
Zoot85 wrote: Are you using offline files? Then latter after I get prompted and actually send the correct password for the budman account on that machine i5-w7 I get accepted and then get share listing, etc. Could see and access the laptop share from the other pcs but couldn't access them through the share on the laptop. Once I made the modification to the Host file on each client step 6. Does it have any firewall settings? It uses either domain authentication or standard user authentication. Are you using offline files? I first I watched a couple of videos on youtub:. Select a Drive letter and a Folder path. At least this is the only thing we have used this wizard for.
Then I turn it on Monday morning and it can't connect to the drives. You will have to configure the laptop network drive access to automatically reattach upon making a network connection though check reconnect at login box. This will also be covered in this lesson. If you truly want to make them accessible, you should pin them to the Start screen in Windows 8, the Desktop, or the taskbar. Windows tries to map the network drives too early in the logon process and that is the reason they fail. We have offline files disabled through group policy, but it sometimes tries to look at the offline cache still.
Since it has nothing to do with the authing process. Solution 4: Reset your router According to many users reported, reset their routers help them fix the error. This can be beneficial to other community members reading the thread. Also, you will understand when to use one or the other. And the fact that it works from windows 7 is prob just pure dumb luck edit. The network location is now removed.