asked on
Net Use on Win10 doesn't work
Hello,
The " net use " with Win 10 is not working and I spent a lot of time on the internet and found no answer.
Here is the context :
I shared directories on both servers. Server A is on our local network 192.168.x.x and server B is located in one of our providers 149.202.x.x.
With Win 7 which is on our local network , the command "net use" works with the server A & B
With Win 10 that is on our local network , the command "net use" works with Server A but does not work with server B. I get error 53 .
I disabled the firewall on Win 10 but does not change anything .
I need help or suggestions
Thanks,
The " net use " with Win 10 is not working and I spent a lot of time on the internet and found no answer.
Here is the context :
I shared directories on both servers. Server A is on our local network 192.168.x.x and server B is located in one of our providers 149.202.x.x.
With Win 7 which is on our local network , the command "net use" works with the server A & B
With Win 10 that is on our local network , the command "net use" works with Server A but does not work with server B. I get error 53 .
I disabled the firewall on Win 10 but does not change anything .
I need help or suggestions
Thanks,
Windows NetworkingWindows OS
Last Comment
dsm dsm
System Error 53 is generally Network Path not found and that could be DNS as suggested above.
https://support.microsoft.com/en-us/kb/137565
Try mapping the folder using IP address instead of names.
Run TCP/IP Reset, DNS Flush (DNS Flush also suggested above)
Open cmd.exe with Run as Administrator
Then netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer
Check the TCP/IP settings in the Network Card properties to ensure the settings are complete.
https://support.microsoft.com/en-us/kb/137565
Try mapping the folder using IP address instead of names.
Run TCP/IP Reset, DNS Flush (DNS Flush also suggested above)
Open cmd.exe with Run as Administrator
Then netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer
Check the TCP/IP settings in the Network Card properties to ensure the settings are complete.
ASKER
Hi,
Thanks you for response, unfortunatly the problem is not solved.
I tested "net use \\149.202.x.x\Data" give the same error 53.
I have the same problem with the "net view" command
When i try to use the same command with local server "net use \\192.168.x.x\Data" i have no error.
My opinion is the configuration in Win 10 is not the same as Win 7. I think there's a parameter to change in Win 10 in order to work like Win 7.
I think also the problem is not a DNS problem.
If it's a DNS problem, I should have the same problem in Win 7 and Win 10.
Thanks you for response, unfortunatly the problem is not solved.
I tested "net use \\149.202.x.x\Data" give the same error 53.
I have the same problem with the "net view" command
When i try to use the same command with local server "net use \\192.168.x.x\Data" i have no error.
My opinion is the configuration in Win 10 is not the same as Win 7. I think there's a parameter to change in Win 10 in order to work like Win 7.
I think also the problem is not a DNS problem.
If it's a DNS problem, I should have the same problem in Win 7 and Win 10.
Network mapping is the same in Windows 10 as Windows 7 (and Windows 8). You may have a configuration error on your machine.
Please review my article on Folder Sharing
https://www.experts-exchange.com/articles/16639/Folder-sharing-on-modern-machines.html
and check all the Network Discovery settings discussed. You may be using a public network profile which will cause the problem above.
Please review my article on Folder Sharing
https://www.experts-exchange.com/articles/16639/Folder-sharing-on-modern-machines.html
and check all the Network Discovery settings discussed. You may be using a public network profile which will cause the problem above.
ASKER
Thanks,
but i think the problem came from win 10 which have some restriction to use shared folder from remote server located in our provider.
but i think the problem came from win 10 which have some restriction to use shared folder from remote server located in our provider.
Windows 10 uses the same sharing methods as prior operating systems so please look through my article and check all your settings.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Have you tried pinging server B and clearing the DNS cache on your local machine (ipconfig /flushdns from command line).