Vista - Cannot Connect to server Error Code 0x80070035

windows 32 bit, netgear switch GS724t, Fileserver chilibox. I have had connectivity for over a year with my main work station. Now after I shut the PC down for the weekend I can no longer connect to my file server and give me an error code 0x80070035 when I try to remap the drive. I can get on the server with other computers on the network but not the original work station. I also cannot get on the other networked pcs but can see them and they can connect to me??? I have tried with no luck disabled all firewalls, reset everything to factory settings still the same result.

I have tried different nic cards. I think I have exhausted everything I can do. It is weired since I can ping the IP. PLEASE HELP!!

I'm having the same problem since a recent Windows Update. Dell says it's an ISP issue one moment then a Netgear issue the next.

-I have Netgear WPN824v.2.
-On PC and laptop both I can see each computer, but on laptop cannot see folders within the PC shared files.
-On laptop, when pulling up Desktop shared files I receive the following message: "Windows cannot access\\DESKTOP" with "Check the spelling..., click Diagnose" and so forth.
-In the deails, it reads, "Error Code: 0x80070035 The network path was not found."
-After clicking Dx., i get the following message: "Cannot communicate with DESKTOP(10.0.0.#). Network diagnostics pinged the remote host but did not receive a response. -> Windows found a problem that cannot be repaired automatically"
Beneath that it reads: "Contact your Internet service provider or network administrator for help or click here for information about things you cantry to help resolve the problem.

I'll let you know what my ISP says when I get to that point. You're not alone, and I hope we can both resolve this similar challenge.

I was able to troubleshoot this problem completely by allowing full access to certain programs on Windows Firewall with Advanced Security which came with my computer. I also had to do some other troubleshooting before I got that far, but now I'm completely connected and don't remember what the troubleshooting process consisted of. If anyone knows, kindly post a reply so that I can write it down somewhere and in the event that I need to share it with someone else. Thanks.

Nolan