Link to home
Start Free TrialLog in
Avatar of Svlss
Svlss

asked on

Unable to access Shared drive from Win 8.1 Pro

I am trying to access a Shared Drive/folder from a Win 8.1 system and for some reason the system is unable to access the Shared drive. I Also tried to map the drive and it dint work either.

The system is on network and i ma able to ping the shared drive server but i am unable to access it. What could be the reason ?
Avatar of McKnife
McKnife
Flag of Germany image

What happens instead?
->error message on access=?
->what error message when trying to map?
->
telnet servername 445

Open in new window

to what result?
Go to Control Panel, Network and Sharing options, Advanced Sharing Options.

Make sure Network Discovery is ON
Make sure File and Print Sharing is ON
Make sure Homegroup is OFF

Then make sure the firewall is not blocking things.
Avatar of Svlss
Svlss

ASKER

When I do telnet servername 445 a blank telnet window opens

And in run when I do \\servername it wont do anything. I am not getting any error message
Open cmd.exe and run:

NET USE Z: \\Servername\folder  

What System Error do you get?
"Telnet blanks" means, the smb port (445) is open and accessible from that client, so it should work. Network discovery is not needed, neither is file and printer sharing, because we don't want to serve, but to access ourselves.

I also asked for the error when trying to map.
Avatar of Svlss

ASKER

When Mapping a network drive I get the below error message

Windows Cannot access \\server

Check the spelling of the name, Otherwise there is a problem with your network. To try to identify resolve network problems. Click diagnose.
Avatar of Svlss

ASKER

when expand details I get Error code )x80070079
The Semaphore timeout period has expired
Try:  NET USE Z: \\IP_address_of_server\folder.

Now what error do you get?  Please let us also know the error number
Does it work from another computer right now?
Are firewalls or security suites with network protection installed at the client or server side? Uninstall those for a test.
Avatar of Svlss

ASKER

It works on all the laptops in the office except this one :-(
What about the network setting suggestions in my first post.

Also try TCP/IP Reset and DNS Flush.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Restart the computer
Remake wireless profiles as needed

Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Avatar of Svlss

ASKER

John,

I tried your commands and it still did not work
Avatar of Svlss

ASKER

John,

When I tried  NET USE Z: \\IP_address_of_server\folder.

I got below error

System error 121 has occurred

The Semaphore timout period has occure
d
Windows 8.1 Pro can access almost anything - I have been using Windows 8 for a couple of years.

If ALL the suggestions above failed to resolve the problem, then try deeper repair methods.

First try System File Checker and then (if no luck) try DISM:

System File Checker:

Open cmd.exe with Run as Administrator and run SFC /SCANNOW.
Allow to complete, restart or, preferably, shut down the computer and then start up again.
Test to see if the problem has been corrected.

DISM:

Open cmd.exe with Run as Administrator.
DISM.exe /Online /Cleanup-Image /Scanhealth (takes 15 - 20 minutes).
DISM.exe /Online /Cleanup-Image /Restorehealth (takes 15 - 20 minutes).
Restart the computer and test.
This symptom is sometimes seen when network security software or anti virus play foul. That's not rare. So please feedback on uninstalling AV + restarting at least at the client.
Avatar of Svlss

ASKER

John,

Tried above commands and no change.


Uninstalled AV and restarted but same result.
ASKER CERTIFIED SOLUTION
Avatar of John
John
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You should at least try and repair it using the inplace upgrade method: http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html describes it. But before, I would update the network card driver. And again make sure there's no 3rd party firewall around.
@Svlss  - Thanks and I was happy to help.