Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I've got a rather interesting problem cropping up on a few machines right now. I've got a bunch of Windows 7 machines networked with a workgroup at home. I used to be able to simply open the "Run" box and type in "\\computername\sharename" to browse the contents of other machines, but recently this has stopped working. In fact, it doesn't even work when attempting to browse to shares on this very computer. Observe:

Run Dialog

Network Browse Failed

(Reliant is, of course, the machine used to take these screenshots)

The effect is the same with both UNC names and IP addresses. The error message (in this case 0x80070002) actually seems to vary from one attempt to the next, sometimes reading "Network path not found". Ive done a bit of googling on each of the various error messages that come up, but I have found nothing.

The odd thing about this situation is that I can still access all shares by mapping them as network drives, as illustrated here:

Mapping network drive

Works!

At the moment I can work around the problem by simply mapping each drive as needed, but it's a tedious and annoying process. Any suggestions/questions are welcome.

share|improve this question
    
Weird, the same thing is happening on my machine. This has been driving me nuts. –  Chris Aug 16 '11 at 18:05
    
Is this on every machine or just one? –  William Hilsum Aug 22 '11 at 17:58
    
It was on most machines, but not all of them. Chris's solution seems to have fixed it. –  Fopedush Aug 22 '11 at 18:01

6 Answers 6

up vote 3 down vote accepted
+200

OK, I figured it out. No idea if this is your problem, but here's my fix. I removed the "Network" icon using some registry tweak a "friend" gave me. It removed the following keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\Desktop\NameSpace\{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}

However this alleged friend failed to tell me that this also screws with your ability to use direct path names (or even browse the network in any sane fashion). Here's the fix:

Windows Registry Editor Version 5.00

; Restore the damned network icon in explorer 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}]
@="Computers and Devices"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\Desktop\NameSpace\{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}]
@="Computers and Devices"

Just import this reg file, reboot (3 times -- no more, and no less) while chanting the lyrics to a song by Radiohead (any song will do). For me, all is well. I'm going to go murder my friend now.

share|improve this answer
    
Nailed it. Give that guy a good thrashing for me. –  Fopedush Aug 22 '11 at 17:56

Very strange...

I would first suggest you suspect some cached permission set via "remember my credentials" being stored for the browsing getting in the way - i.e. they are wrong u/pw combination.

Have a look at the control panel section

Control Panel\User Accounts\Credential Manager

See if something in there stands out as wrong, or clear anything related to the remove machines and try again.

share|improve this answer
    
The credential manager, I'm afraid, is completely empty. No luck there. –  Fopedush Aug 16 '11 at 5:52

I was facing the same issue when I tried to see how it goes for me,

all what I did, is :

[ net share ] on the remote machine to see if c$ is shared

then on my machine, typed :

[ net use /user:Administrator ]

That was exactly everything, then when I used \\remote\c$ it prompted me for the user name and password.

I really don't like solving things this way, but tell how it goes for you.

share|improve this answer
    
I'm not quite sure what you're getting at here. "net use /user:administrator" isn't valid syntax for the net command. Do you mean that I should be mounting the location as a network drive as administrator? If so, that's basically the same as the workaround I've already got. However, mounting the location as a network drive does not allow me to then browse to it using the \\UNC-Name syntax. –  Fopedush Aug 19 '11 at 20:53

Add the line into hosts file and try again. It might be DNS magic.

12.34.0.12 reliant

If you don't know the reliant's IP just command:

ping reliant

If you use the same share regularly you can create a batch file like this, here I do same on a laptop which one is not the member of the domain and forgets user/password seldomly:

net use \\reliant\c$  password /user:you /savecred
share|improve this answer
    
Or try \\12.34.0.12\c$ instead... –  Nime Cloud Aug 19 '11 at 21:06
    
Same effect, still no love. –  Fopedush Aug 19 '11 at 21:12

I've run into the problem you're describing many times before and sometimes I've found that running the Network Setup Wizard on each computer to reconfigure your settings will fix the issue.

Remember to restart your computer after running the wizards.

share|improve this answer
    
Sorry, no luck here either. –  Fopedush Aug 22 '11 at 3:21

I resolved this way:

  1. cmd -> net use -> this gives you all the active connections.
  2. For each of the non-working connection: net use "<connection name>" /DELETE
  3. Start -> Credentials -> remove all of them
  4. TaskManager -> Kill all EXPLORER.EXE processes, and start a new EXPLORER.EXE
  5. Now you can re-map the network share as a drive.
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.