Accessing network shares stopped working
I have a problem with my network. Everything was working fine. I believe that problem started after my computer got frozen a few times one day. The problem is that I cannot connect to my network shares. There is one NAS server, one XP laptop, one Vista laptop and two Windows7 laptops (including mine) in my network. The only computer I could see in network places is the other one with Windows7. However, when I execute '\\NAS\Public' I got an error: "Network location not reachable" (It could sound a little different, I have Polish system). Error code: 0x800704cf. The same situation when I try to connect to shares on XP computer. The paths are typed correctly, because it all started when my mapped discs stopped working (could not reconnect after boot). Other facts: - Internet connection is working fine - I can connect NAS server via FTP - I can connect to NAS via webbrowser and login to admin panel It is just windows explorer what cannot reach network shares.
January 24th, 2010 1:12pm

Just a litte review for you about that error codehttp://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/77a9fbf8-e889-414c-a9f9-f3fa72e3b593.mspx?mfr=trueThe exception number 0x800704CF means "Automatic certificate enrollment for local system failed to contact the active directory". Are these machines in a domain? You didn't mention anything regarding a domain.I have found this support article that shows how to disable automatic certificate enrollment that you might want to look into:http://support.microsoft.com/kb/310461 but that doesn't explain why its looking for AD unless one or more machines where on a domain before or are now.MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2010 2:47am

I didn't mention the domain, because there is none. I've tried to disable automatic certificate enrollment, but it didn't work. What I should also mention is that the other computers are able to access network shares (including the other one with win7). The Nas server is QNAP TS-100 if this could be relevant. Thanks for your answer. Do you have any other ideas?
January 28th, 2010 4:13pm

What is also weird is that the error code is different when I try to WINDOWS + R and type in "\\NAS\Public" (then it's 0x800704cf) and when I try to type "\\NAS\Public" into windows explorer address bar (then it's 0x80004005)
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2010 4:27pm

I am experiencing the same issues with windows 64bit computers (windows 7, and windows xp) connecting to a Netapp FAS3140 .. the weird thing here is, i can map a drive to \\nas\share no problem, but when i map to a Virtual interface on the same NAS, for example \\nas-e0a\share$... i receive the following message: "The network name is no longer available"the only change i applied to the network is, the addition of windows 2008 R2 Domain controller recently...Rob Davis
January 28th, 2010 5:23pm

No idea what the cause might be?
Free Windows Admin Tool Kit Click here and download it now
January 30th, 2010 6:37pm

net view \\192.168.1.10 gives error 53. Net use P: \\192.168.1.10\Public gives error 1231. What else could I post to help you find a solution?
January 30th, 2010 10:43pm

I found what caused the problem... The version of ONTAP 2.7.3 has a bug causing drive mappings to disconnect randomly.. their is a workaround from NetApps website, or i will just upgrade to the latest Version which is 3.something.. Rob Davisdisregard the version that may not be correct).. .all i know is, i didnt have the latest version of ONTAP, and updrading to the lastest will fix it...
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2010 5:33am

Rob, I am having the same issues. Fount a couple of kb @ now.netapp, but they didn't help. Wich article did you found to work around this problem? Tomas
March 25th, 2010 11:03am

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

Other recent topics Other recent topics