In our office, we have a file server running Windows 2008 32 bit basic. Had no problems connecting to it at first using my computer, which has Windows Ultimate 64-bit installed. But soon afterwards, I noticed my computer has lost connection to the file server. I will get the "Windows cannot access \\SERVER\" message, and the "Error Code 0x80070035, The network path was not found". After a few attempts, I'll eventually connect to the file server. During this time where I cannot see the files, I can still ping the file server via cmd so its not like my computer cannot see it. Any ideas what is causing it. From an internet search it appears to be a common problem with Windows 7 users. We have machines running Windows XP and they have no problem whatsoever. Help! Thanks!

Hi, I also experienced this kind of a problem: Server 2008 R2 in form of small business server 2011, windows xp pro clients with no probs and windows 7 64 Bit clients with the problems we are taking about. The phenomena: after a random amount of time, maybe 2 or 5 or 10 minutes, in the windows explorer all network drives are shown with a red "X" and when I try to use network drives in any way, there is the message "path not found". Then I leave the client for a while alone, 2 or 3 or 5 minutes or sometimes only for a few seconds and the connections are active again. I tried: - install the feature WINS to have NetBIOS browsing again. - fixed IP addressing at the clients - turning SMB V2 off (lanmanserver/parameters/smb2=0) - update nic drivers I tried not: - setting autodisconnect to off cause in many discussions people told, that they turned it off with no improvement. I'm supporting many clients with server 2008 (r2) and windows xp clients and there are no problems in any of this kind. Also this problem is not showing with server 2008 (r2) an windows 7 clients in many trainings I gave. This problem now shows for the first time in connection with small business server 2011, so I guess this must be a problem in the Microsoft configuration especially what the stunning Group Policy Objects belong. Has anyone tried to delete this Group Policy crap before connecting the first client? I will try this in a testing environment and reporting back about my experiences. Any other ideas out there? Steven

Please do let us know the outcome...its been a nagging issue for nearly a year and doesn't seem like I could find the solution. On a side note, I'm going to install Windows 7 32-bit to see if it has any problems connecting to Server 2008.

Hi, Sometimes this would be related to the third-party firewall or anti-virus programs, try to test this issue in Safe Mode with Networking to check the result. Alex ZhaoPlease 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.

Thanks Alex, but I don't believe that is the problem. I have already removed my Norton Anti-virus software and still have the same problem. And I'm using the resident firewall in Windows 7, deactivated it, problem still exists.

I don't think its a fix for me, but the connectivity is better. Found this was discussed in the kb2194664 fix, but it was for W7 and Server 2008 R2. Installed the x64 version onto my Windows 7 Ultimate 64-bit laptop and while I do get disconnected, its less frequent than before. According to Microsoft, this was included in the SP1...but when I checked the list of upgrades I couldn't find it. So, I installed it. I would install this onto my server, but its only for 2008 R2 and not 2008 Standard. Any idea if kb2194664 would work on Server 2008 Standard?

I don't think its a fix for me, but the connectivity is better. Found this was discussed in the kb2194664 fix, but it was for W7 and Server 2008 R2. Installed the x64 version onto my Windows 7 Ultimate 64-bit laptop and while I do get disconnected, its less frequent than before. According to Microsoft, this was included in the SP1...but when I checked the list of upgrades I couldn't find it. So, I installed it. I would install this onto my server, but its only for 2008 R2 and not 2008 Standard. Any idea if kb2194664 would work on Server 2008 Standard? EDIT: within 2hr 25 minutes after this post apparently Microsoft removed this Hot Fix. Anyone from Microsoft would care to say why?