Why can't I map C$?
I have three computers, A, B and C, all with the same password and username. A runs Vista Ultinmate 64-bit Sp2, B runs Vista Business 64-bit SP2 and C runs Win7 Professional N SP1. If try to map C$ on A from B or C, this works. But if I try to map C$ on B or C from any of the other, this fails. For B, this could construed to be a feature, since this is a laptop, but I would like to have it to work with C. (Yes, it probably works if I set up official shares, but I'm lazy.) I've been trying to compare settings on the computers, but I just can't make out what the difference is. Firewalls? Both A and B runs Outpost 7.1. C in this very moment has no firewall at all. (I temporarily uninstalled Outpost to investigate another problem.) If I connect to SQL Server on any of other computers with integrated security this works, so username and password are good. Here is an interesting piece of information. If I run this: net use \\B\c$ TheRightPassword I get (after a couple of seconds): System error 5 has occurred. Access is denied. But if I use the wrong password, I get error 86: "The specified network password is not correct" It is possible that I in some time in the dim and distant past changed some setting on A that I have forgotten. I believe I've check the basic settings, Network discovery and that, but I might have overlooked something. Or could the error message indicate that something is locked? Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
August 10th, 2011 12:26am

Hi, According to your description, I suggest to perform these test to troubleshoot the issue on Windows 7: 1 Check credential manager on Windows 7, clear all credentials. 2 Use IP address instead of PC name: Net use \\Ipaddress\C$ Then press Enter first, it will command you to input the user name and password, then put the right user name and password to see the result. 3 Use GUI to map C$: 1) Open “Computer” 2) Click “Tools”---“Map network drive…” 3) Choose a drive letter, and input \\Ipaddress\C$ in the bank and click “Finish” 4) A credential window will pop up to ask the user name and password 5) Input your user name and password Hope that helps. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2011 5:37am

1 Check credential manager on Windows 7, clear all credentials. Had one generic credential on machine C. Things did not change. 2 Use IP address instead of PC name:  Net use\\Ipaddress\C$ <file://ipaddress/C$> No change. Then press Enter first, it will command you to input the user name and password, then put the right user name and password to see the result. Not surprising, I had already tried that. 3 Use GUI to map C$: Not surprising, this is where I began. I get a logon window that keeps coming back. The command line does at least gives the hint Access is Denied. Which may be mean insufficient permissions. But which also may mean that a file or some other resource is locked by other process. I tried to use Process Monitor to catch this, but I was not successful. In the Security Event Log I see Login and Special Login events that may be related to my attempts to map the disk. These say Audit Success. Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
August 10th, 2011 10:27pm

Hi, The reasons of cannot map network driver can be: 1) a misconfigured firewall or overlooked firewall (including a stateful firewall in a VPN. 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall. 3) Not having identical user accounts and passwords on all Workgroup machines. 4) Shares where the operating system does not permit it. I suspect the issue should related with firewall. Please remove antivirus program and disable firewall on both Windows 7 and Windows Vista. And try to enable NetBIOS over TCP/IP, disable UAC on PC. Also logon with Safe Mode with networking to check the result. Furthermore, make sure all PC Network discovery is turned on and the computers are in same home group. This link may helpful to you: Troubleshoot problems with computers not appearing on the network map http://windows.microsoft.com/en-US/windows-vista/Troubleshoot-problems-with-computers-not-appearing-on-the-network-map Hope that helps. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2011 5:37am

I suggest you to temp disable or uninstall Outpost 7.1 and try mapping again and see how it goes. Try mapping it's path with it's name instead of IP, example: \\David-PC Lastly is the above 3 rig belong to the same homegroup or workgroup?
August 11th, 2011 11:00am

The reasons of cannot map network driver can be: Please note that it is a matter of mapping the administrative drive C$. If I make explicit shares that works. 1) a misconfigured firewall or overlooked firewall (including a stateful firewall in a VPN. I have no problem configuring the firewall so that mapping attempts ends with "The network path was not found". (Interesting enough it proved to be more difficult to prevent connections to SQL Server.) 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall. Nope. 3) Not having identical user accounts and passwords on all Workgroup machines. If I hadn't, integrated security in SQL Server wouldn't work. Nor would mapping against explicit shares work. 4) Shares where the operating system does not permit it. C$ has worked in many versions of Windows. Has this changed in Windows 7? I suspect the issue should related with firewall. Please remove antivirus program and disable firewall on both Windows 7 and Windows Vista. And try to enable NetBIOS over TCP/IP, disable UAC on PC. Also logon with Safe Mode with networking to check the result. So I have this virtual machine (Win7) where I have uninstalled Outpost, Windows Firewall is turned off. I've reduced UAC to the lowest level. (But I still have to confirm UAC to access the DATA directory for SQL Server, which has a different owner. Is it possible to turn off UAC entirely in Win7?) And, no, I still cannot map C$ on this VM (which runs under VMware, I should say.) I did not try Safe Mode with Networking, but anyway, it does work on one of my machines. Are you able to map C$ on a Win7 machine in a workgroup? Furthermore,make sure all PC Network discovery is turned on and the computers are in same home group. There isn't home groups on Vista, is there? I tried to set up a homegroup for the host machine and the VM, but it failed. I don't know much about home groups, but from the dialog to set it up, I get the impression that it is mainly for what's under C:\Users. Lastly is the above 3 rig belong to the same homegroup or workgroup? They are all in the group WORKGROUP. And, as I said, integrated authentication in SQL Server works. Mapping to named shares works. Mapping to C$ works on one machine, but not the other two. I can see that mapping to administrative shares is turned off by default, but what switch do I need to flip? Your answers make it seem that it should work out of the box. Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2011 12:49am

"They are all in the group WORKGROUP. And, as I said, integrated authentication in SQL Server works. Mapping to named shares works. Mapping to C$ works on one machine, but not the other two. Both A and B runs Outpost 7.1. C in this very moment has no firewall at all. (I temporarily uninstalled Outpost to investigate another problem.)" Care to share which two workgroup you're not able to map? Is it both A & B which run outpost 7.1?
August 12th, 2011 3:07am

> Care to share which two workgroup you're not able to map? Is it both A & B which run outpost 7.1? Not sure that I understand this which two workgroup. I only have workgroup, or so I believe. (Can you really have more than workgroup?) Anyway, if I am on B or C I can map C$ on A. If I am on A or C, I cannot map C$ on B. If I am on A or B, I cannot map C$ on C. A runs Windows Vista Ultimate x64 SP2 and Outpost 7.1 B runs Windows Vista Business x64 SP2 and Outpost 7.1 C runs Windows 7 Professional N x64 SP1 and Outpost 7.5. (But when I made my post, I had temporaily uninstalled it to investigate another problem. I thought I had no firewall at all that point, but Outpost may have turned on the Windows firewall when it was uninstalled.) In any case, the firewall as such is not likely to be the culprit. If I run "NET USE H: \\C\C$", I can see Audit Success events with Logon in the Event log. Possibly some malware protection strikes in the next step. However, the behaviour is exactly the same when I try to map C$ on a virtual machine that runs Win7 Professional N 32-bit SP1, and which has no firewall at all enabled. But let me ask you a question: can you map C$ on a Windows 7 in a workgroup (assuming that you have something around to test on). Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2011 10:31am

Erland, Just a wild guess ... try this KB on your W7 machine. http://support.microsoft.com/kb/951016 Kind Regards DFT IM me - TWiTTer: @DFTER
August 12th, 2011 12:26pm

Hi, I have tested already that Windows 7 in workgroup can map C$ from Windows Vista. These steps below what I have done: 1 Disable firewall on both Windows 7 and Windows Vista 2 Remove antivirus programs on both Windows 7 and Windows Vista 3 Set Windows 7 network to “work network”, and Windows Vista network to “public network” 4 Turn on Windows 7 network discovery and file sharing, also set it on Windows Vista 5 On windows 7 computer\tools\map network drive, and input \\Ipaddress\c$, it asks me for the credential. After inputting the right username and password, success mapping C$ on Windows Vista. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2011 12:44pm

Just a wild guess ... try this KB on your W7 machine. http://support.microsoft.com/kb/951016 Thanks! That was the setting I was looking for! I checked, and it is set on my old Vista machine (computer A), but not on my laptop (computer B). I don't remember that I ever set it, but that would not be the first time my memory fails me. And of course, I might have set it indirectly through some UI somewhere. Leo, yes, when I lowered the setting for UAC to Windows 7, I was also able to map C$ after a reboot, but the point was that on Vista it could work with both UAC and firewall in place. "daft" nailed it. Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
August 13th, 2011 1:10pm

That’s sound great. And could these three PC map C$ each other? Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2011 4:21am

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
August 18th, 2011 11:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics