How To Create Map Network Drive In Windows 10
I do have exactly this same problem.
In Windows upwardly to 8.i mapping network drives always worked without whatsoever bug (when CMD run as Administrator).
In Windows 10 it does not: meet fastened screen!
ii people found this reply helpful
·
Was this respond helpful?
For what it's worth, I've got a like trouble.
I take a 2012 R2 DC that uses a policy to create some mapped network drives to shares on a 2d 2012 R2 server.
Using Windows 10 the shares are mapped - but they cannot be used, Windows 10 but sits and eventually the File Explorer times out when trying to open any of them. Needless to say, it all works fine under Windows 8.i
1 person found this reply helpful
·
Was this respond helpful?
Only had a blinding flash of inspiration.
My problem was acquired past Windows ten having Jumbo Frames enabled on the NIC. Turned information technology off and it started working.
HTH
2 people found this answer helpful
·
Was this reply helpful?
@sweet
Let me know how you did that, Ill give it a try.
4 people found this respond helpful
·
Was this reply helpful?
Yous can change the holding via the Advanced tab page of the network card's backdrop dialog. Yous'll need to have admin rights to alter information technology; you tin can get to the properties dialog via several ways one of which is:
Correct click on the Showtime Button -> Network Connections -> Right click on your Network Interface -> Properties -> Click Configure... push -> Select Advanced Tab -> Change the Jumbo Frame property in the list to disabled
Was this reply helpful?
Thanks was already disabled on mine, back to foursquare one.
Was this reply helpful?
It looks like I had the same problem and found a solution.
Using Windows 10 Pro on a home network to connect to a Linux server running Samba. I employ to be able to \\server and would become a list of shares. Right click and map a drive. Add together my name, password, drive alphabetic character and I was done.
Outset bug: Sometimes Win10 likes the IP accost and sometimes it Only works with the hostname.
Second Issues: The username and password defaults take changed. Win10 prepends the username with the workgroup or domain proper noun in front of your username, regardless of what information technology's showing y'all.
So, now to map a drive I accept to include the WORKGROUP that the server is a part of in my username.
Instance:
In File Explorer I'll put in the address \\server name
When it lists the shares, I right click and select the checkmark for "Connect using different credentials"
Username: WORKGROUP\Username
Password: as normal.
This has been the ONLY fashion I can go a bulldoze to map, and I take tried IP's, and every pick I can retrieve of. The Jumbo packets doesn't utilise for me since the Wireless card doesn't support it.
Bonus 3rd Bug: I have to do a Network troubleshoot and repair on the network cards afterward installing Win10, before the network become's a default route.
135 people found this respond helpful
·
Was this respond helpful?
What worked for me was to edit the Windows host file.
C:\Windows\System32\drivers\etc\host
Open up it in a text editor.
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP accost should
# be placed in the first cavalcade followed by the corresponding host proper name.
# The IP address and the host name should be separated past at least one
# infinite.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For case:
#
# 102.54.94.97 rhino.elevation.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled inside DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
192.168.0.2 LocalServer1
192.168.0.iii LocalServer2
#####################################################
Here I listed "LocalServer1" and "LocalServer2" that I want to map drives from. I saved the changes but Windows wants me to save it someplace other than the electric current directory. Brand sure to save it equally text file without an extension selected in the Save dialogue box. I just copy the edited file and place dorsum in the C:\Windows\System32\drivers\etc\
It took a few minutes but when I go file explorer and type \\LocalServer1\ all the volumes I could mount are listed. I followed @Larry-2000 advice on how to input credentials and it seemed to work for me.
half dozen people establish this reply helpful
·
Was this respond helpful?
No Dice, I get this msg now, and I used a drive that has never been mapped, and then I know its non because its currently mapped on the computer, this obviously has something to do with the HTPC computer not allowing it.
All computers are on WORKGROUP, Aforementioned WiFi network, and Windows 10; this is condign frustrating.
iv people plant this reply helpful
·
Was this reply helpful?
Same issue here...
2 people plant this reply helpful
·
Was this respond helpful?
Source: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-map-network-drive-not-accepting/8f0bbbf7-3051-4289-a038-0933d2fbcd64
Posted by: ramseythipper82.blogspot.com
0 Response to "How To Create Map Network Drive In Windows 10"
Post a Comment