Recently upgraded from 7 to 10 (clean install). When I use the net use command it doesn't quite work the same as it used to.
In Windows 7 when I would run net use and include credentials, I could put the UNC path into the run command and the folder would open right up. Now when I do that I have to login, even though I included credentials in the net use command itself.
If I map a network drive with net use, it doesn't show anywhere in Windows explorer, and if I type in the drive letter of the network drive into the "address bar" it says it can't find it.
What is the exact command you are using and are you using an elevated command prompt or a normal user one? Is the share local and was the share made with the same account?
Elevated command prompt.
Command is "net use \10.1.0.9c$ /user:domainusername "password""
Then in run, I type \10.1.0.9c$ and it should take me straight to that folder.
Instead, it prompts me for my username and password again.
In the case of mapping a network drive i just add the drive letter to the command. "net use Z: \10.1.0.9c$ /user:domainusername "password""
The shares are not local and I'm using the credentials of an account other than what I'm currently logged in with.
Is the password supposed to be in quotes? Also try a * instead of a password to see if it prompts you correctly for one, especially if you have spaces in it. May help narrow it down at least.
I always have used quotes, but it doesn't appear to be necessary.Is the password supposed to be in quotes? Also try a * instead of a password to see if it prompts you correctly for one, especially if you have spaces in it. May help narrow it down at least.
The * does prompt for a password, but the results are the same if I enter it that way.
Are you runing W10-pro or W10-home?
I found that W10-home offers you a more relaxed and automaticly correct sharing of devices and folders in a home network.
W10 ProAre you runing W10-pro or W10-home?
I found that W10-home offers you a more relaxed and automaticly correct sharing of devices and folders in a home network.
If you run it from an Administrator command prompt you'll not see it in explorer as explorer doesn't run elevated.
Run it in a normal command prompt and you should see it OK (but elevated apps will not see it)
See here also Network drive not showing in elevated apps - Windows 10 blog
Experimenting I disabled both Firewalls: home and world. No difference. W10-pro refuses to see the other computers but pinging works fine. The computer with XP-pro (Dell) is not allowed to access the shared folder on W10-pro (Athlon) but can access the shared folder on the W10-home computer without problems.
The W10-home (Toshiba) shows all shares on all computers with active and default Firewall settings.
The problem is W10-pro. W10-home is still working like I was used without troubleshooting in W7-pro and W7-home.
Microsoft Netherland says it has a solution but that would cost me $125,- for one year support!!!!!
Yep, I can confirm this is the answer. Just tested. Probably related to admin approval mode. My least favorite Windows "feature" since Vista.If you run it from an Administrator command prompt you'll not see it in explorer as explorer doesn't run elevated.
Run it in a normal command prompt and you should see it OK (but elevated apps will not see it)
See here also Network drive not showing in elevated apps - Windows 10 blog
