I am using windows 7, I cannot connect to a shared network drive on another machine.
As you can imagine, I am banging my head against the wall on this one.
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:
In Control Panel \ All Control Panel Items \ Network and Sharing Center \ Advanced sharing settings and I checked relevant settings in "Home or Work profile".
In Control Panel \ All Control Panel Items \ Network and Sharing Center
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 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.
Maybe it's a little too late to answer this, but I solved this issue in this way:
Go to start, run, type services.msc and press enter.
When you are on the services applet make sure the service "Workstation" is running and is set to start atomatically.
Hope this helps more people looking for a solution.
I had to reinstall my OS and immediately i could have full access to my network share
As I installed programs I kept checking accessibility to my share.
It turns out that Brother installed a printer monitor for the HL-2270DW that when turned off allowed access to my NAS.
Too bad I had to do a reinstall to locate the problem.
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.
I encountered the same problem and got 0x80004005 when I was connecting to server. I spent hours and hours struggling with it. At last I found the solution.
Here are my steps:
Network and Sharing Center->Change adapter settings ->Right click on you connection->Properties.
Client for Microsoft Networks have been installed. If not, use the
Install button to install it.
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?
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.
Here is how I was able to fix it in Windows 7 Enterprise in a 2008 R2 domain:
I noticed Offline Files were enabled, and the status bar in Windows Explorer (bottom) was saying that I was working offline.
I went into Control Panel, disabled offline files, rebooted the computer, and voilá --> I could access the shared folders again!
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.
Dont know if its too late for this, but I found a solution in my case. I ended up enabling all the sharing options under "Change advanced sharing settings" I then right clicked on my computer then hit the manage button.
This brought me into Computer management, i then expanded the shared folder, then clicked on the shares section. This did alot of things for me, it allowed me to redefine an absolute list of sharing folder (i had a lot of sharing folders stuck in limbo, which I could now unsure). I right clicked on the drive i was having issues with, in my case E: drive. This opened up drive properties. I clicked on the Security tab, then clicked on the Edit button.
this brought me to a permissions section. I the add button, then added a user called "guests" press ok, then goe down to the permissions section and click allow on everything.
*warning, dont do this if your computer is on a shared network, IE other random people that join consistantly as this opens it up to anyone"
Also, if you just wanted one computer to connect, IE your laptop to your desktop (you desktop being the computer that is sharing the drive) then add the name of your laptop to this list.
push ok, ok, ok, ok ok ok ok then ok one more time for measure, and you should have full control of that particular drive.
I had the same issue, and while on the client machine (the one trying to access the network files) I had to remove/re-add the credentials using the credential manager. Note that both the host and client machines use the same OS (Win7 Ultimate, how 64, client 32) witht he same username and password (full usernames are different as the machine names are different and there is no AD/Server environment).
Once I removed and re-added the credentials, it all worked.
Also, I had the same issue after changed the login password.
I am a little late to the scene here, but here is my solution:
After several hours of fooling around with this issue, it seemed to be a full version install of AVG antivirus (due to an accidental installation of the evaluation version).
Nuked it, and up and running perfectly. (I am confident that there was a security setting in AVG that I could have simply disabled, but I do not care to reinstall it to find out.)
Hope this helps someone.
For me all up stated did not work and i found some different solution that work form me.
Problem is in the "6to4 adapter" to view it goto Device Manager, click View and select Show hidden devices – expend Network Adapters – check the status of 6TO4 adapter.(hope fully you will find number of them as I found )
You can turn off this through netsh via the command prompt.
netsh int teredo set state disabled netsh int 6to4 set state disabled netsh int isatap set state disabled
Re-enable the tunnel adapters
netsh int teredo set state default netsh int 6to4 set state default netsh int isatap set state default
you can remove them manually which is tedious to do for me due to huge number. alternate using a bach file (included in attached file)
Also need to install this patch from microsoft. https://support.microsoft.com/en-us/kb/980486
Include Patch from Microsoft, 6to4 Adopter remover and batchfile. http://www.4shared.com/zip/Sln40vGTce/6to4remover_2.html
Found yet another way to try to resolve this - When trying to change the WorkGroup name to see if resetting it would help - I got a pop up message that stated the exact same computer name was used elsewhere on the network. I changed the computer name and everything began working properly.
Hope this helps someone.
Changed network from AT&T U-verse DSL to AT&T Home Base wireless. Shares from my Win7 Pro 64-bit computer became inaccessible from my Vista Home 64-bit computer that worked just fine with the earlier network. Network only, nothing else changed. Vista could display the Win7 machine name and shares under File Explorer's ">NETWORK" item. Ultimately added NETWORK user with "Full Access" permission to the share's user list on the Win7 machine and now Vista can map that share and use its contents, read, write, save, delete, etc.
Not sure just why this approach worked or what vulnerabilities have been opened up to hackers though.
User contributions licensed under CC BY-SA 3.0