Share this question

Welcome to Teachnovice Q&A, where you can ask questions and receive answers from other members of the community.

This is a collaboratively edited question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Windows 7 Unable to connect to a shared network drive in same network

0 like 0 dislike

I am using windows 7, I cannot connect to a shared network drive on another machine on my network.

  1. I can ping the PC's.
  2. I can remote desktop to these PC.
  3. The PC is on the same subnet
  4. I ask my friend to try this at my house he has exact same laptop as me (and on the same network, same workgroup) can connect to the shared folder.
  5. The machine I am trying to connect to and my friends machine can both see shared folders on my machine.
  6. I also I cannot see shared folders on the friends laptop.
  7. When I select diagnose, windows tells me nothing useful.
  8. When I select see details on the error pop up, I see: Error code: 0x80004005 (google doesn't help much)
  9. I can nbtstat -a the machine who has the shared folder.
  10. When I try with my firewall turned off the same happens.
  11. I have ensured my windows 7 has all updates.
  12. I run security essentials to ensure my laptop is clean.
  13. I run ccleaner to clean up my registry. Same error.
  14. I have tried with my laptop on both wireless and ethernet.

As you can imagine, I am banging my head against the wall on this one.

asked Oct 18, 2012 by anonymous  

5 Answers

0 like 0 dislike
Best answer

Right finally this to work. Firstly, I am putting down everything here I tried that didn't work as it might also be of use to someone. If you have the same problem as I described here, you should do everything here.

In Control Panel \ Network and Internet \ Network Connections \ My Connection \ Properies:

  • I ensured Link-Layer Topology Discovery Mapper I/O Driver was enabled
  • I ensured Link-Layer Topology Discovery Responder was enabed Tried with
  • I tried with IPV6 enabled / disabled

In Control Panel \ All Control Panel Items \ Network and Sharing Center \ Advanced sharing settings and I checked relevant settings in "Home or Work profile".

  • I ensured: "Turn on network discovery" is set
  • I tried both security settings in "File sharing connections"

In Control Panel \ All Control Panel Items \ Network and Sharing Center

  • I wnsure my network was marked as a "Work" network. Ensure this is correct for you.

Ok so none of the above yielded any luck.

Then, I did the following:

At, Control Panel \ All Control Panel Items \ System

I selected: "Computer Name" tab.

  • I entered something in the computer description text box. This was blank.
  • I selected the Change... button.This gives you the opportunity to change the Workgroup name Mine was "WORKGROUP". I set it to something else and then set it back to WORKGROUP. The thinking was this might flush something.

I then logged onto the machine that had the folder I wanted to share thru RCP. Then I accessed a share folder on my PC. Now, when this session was alive, I opened up Computer Management and I opened the "shared folders" and sessions and saw the computer I was trying to connected, connecting to me.

Again the thinking was this would flush something out. After, I did all this it worked. I am not sure exactly what step fixed it. I was under too much time pressure to keep checkeding after I changed anything.

Thanks for all who helped out here.

answered Oct 18, 2012 by anonymous  
0 like 0 dislike

0x80004005 = Access Denied.

Double check your login name and password (credentials) to ensure they match on both the computer you are connecting from and the one you are attempting to connect to.

Then ensure the account/credentials are given access to both the share itself and the folder that's shared.

answered Oct 18, 2012 by anonymous  
As stated I don't even get to the credentials stage
So, you're logging in with a username/password that also exists on the target machine, and the account on the target machine has permission to the share and the folder? I'm not sure what 'credentials stage' you are expecting? Perhaps edit your question and include the exact error message you receive
I don't even get to specify my user name and password. I open up a windows explorer and type \\themachine and then I get the error
0 like 0 dislike

The frustrating thing about Windows, even Windows 7, is that it caches your account credentials SOME WHERE for these types of network accesses. If the credentials to access the remote machine changed, it is possible that Windows is still referring to the old credentials.

One thing you might try is changing the remote machine's name and / or IP address (this assumes Windows is storing credentials on a per-machine name or per-IP basis). If credentials are required, it SHOULD ask for a new set of credentials when you try to access the new name or IP.

Another possibility is that you / your user (whatever you are logged in as) does not have share permissions on the remote machine, folder, drive, whatever. Make sure those match too!

Last but not least, does your friend have his laptop sharing properly?

answered Oct 18, 2012 by anonymous  
I don't even get to the stage of being asked for credentials. Another friend can connect to the machine that I can't. He has no permissions that I don't have
Anyone else got ideas for this - really stuck
0 like 0 dislike

You said you have Microsoft Security Essentials installed. I had a very similar problem and wrote a tutorial with a simple fix I found: disable the Network Inspection System which seems to cause conflicts with simple network sharing features.

I hope this fixes your issue.

answered Oct 18, 2012 by anonymous  
Thanks. I tried this but it did not work. Same error. Any other ideas?
0 like 0 dislike

I had a similar but different problem. QNAP TS410 NAS. This is a Linux based network RAID array. Two Win 7 machines, one could access the shared drives on it, the other could not. problem turned out to be DNS related. Two networks with a VPN between them. NAS and two PCs on one network and the Domain Controller on the other. Had to set Domain Controller's IP as the first entry in DNS within the network adapter properties on the problem machine.

answered Oct 18, 2012 by anonymous