Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, July 30, 2015 8:49 AM | 1 vote
I upgraded to Windows 10 from Windows 8.1 today and it looks very nice.
I have a problem though in that am now unable to browse my local network - there should be at least 2 servers - I can see no other computers (nor their shared drives) but I can see a wifi printer and my router.
My mapped drives (Samba Linux drives) are subsequently unavailable. Theye were visible and accessible in Windows 8.1.
Odd thing is that I am able to PING the Linux servers and I can access their Apache pages via a web browser but cannot see them on the network.
My Windows 7 laptop can see the network and all drives no problem, and as a Windows 8.1 device my (now windows 10) laptop could see and connect.
I have disabled the windows firewall but that did nothing.
I can browse the web no problem so it's something local to my machine which has changed during the upgrade.
Stumped and a little frustrated as I can't do any coding until i get this fixed lol.
:(
Whenever I try to access it via explorer using an ip address I get "0x80004005 Unspecified Error". I can however access the same server via IP address using MySQL WorkBench so it has to be a credentials thing on Windows 10
All replies (7)
Thursday, July 30, 2015 3:44 PM âś…Answered | 1 vote
I know when I installed Win10, I had to first set up the Advanced Sharing Options then go to Settings > Network & Internet > Ethernet > then click the Ethernet Connected icon and turn on the Find devices and content. Then my server on the network will show, when I try to connect to it via shared folders, it will ask for a username and password, then put in your MS Account credentials (Dont have to do that if using Local Account
Thursday, July 30, 2015 3:14 PM | 3 votes
same here.. can ping my NAS device, can reach it via web browser and all other services, as ftp, ssh. can ping it
but trying to access my cifs shares via windows explorer with IP or hostname, neither mapping the network drives are unsuccessful.
"The specified server cannot perform the requested operation"
Sunday, July 16, 2017 7:17 PM
after windows 10 upgrade i could not connect to shares on the two computers i upgraded
i tried several things but finally i found that control panel / windows firewall /allow an app or feature through windows firewall
select 445 TCP IB_BLOCK and 445 UDP IB_BLOCK and select Private for those items
this fixed the drive sharing problems i had on two computers
Tuesday, July 31, 2018 2:46 AM | 2 votes
down vote
Windows 10 does not support SMBv1 since build 1709. This blocks connection to legacy devices using this protocol.
Check: https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
In this page, MS describes some workarounds. If it does not work, you can enable SMBv1 following this approach:
I have an old NAS server. I had to enable SMBv1 to access my old files...
Regards, Da Silva
-- Marcos Silva
Saturday, December 15, 2018 8:14 AM
tanks MASILVIO for this answer. after 10 month i can resolve my issues by windows xp computer in my network that was not appear name in network browser and cant connect to shared folder on it !
Tuesday, March 19, 2019 9:57 PM
How do you set up the Advance Sharing Options to get started? I'm not a techie or a computer geek and I just don't know how.
Wednesday, September 25, 2019 4:45 PM
"Windows 10 does not support SMBv1 since build 1709"
Sorry, this part bugged me a bit. You mean to say it's off by default. This is true for a fresh install via media creator 100% of the time. Other builds I can't say its true. My new laptop I got 3 months ago had SMBv1 enabled by default but in any case, the articles you pointed out clearly shows it's an optional add-on.