|11 Mar 2011||#1|
| || |
Error Code 0x80070035
My father and brother each has a separate Windows 7 desktop, and neither one has any problems with connectivity. There is also a Windows XP machine on the same network, and it has no problems with connectivity. The XP is attached to a shared printer that can be successfully accessed from any desktop machine on the network.
Now comes the interesting bit: I have a laptop PC which I upgraded to Windows 7 from Windows Vista x64 Home Premium. I am able to see the two Windows 7 computers in the Network list, but when I double-click on them, I get the message:
Windows cannot access \\MACHINE-NAME
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
Error code: 0x80070035
The network path was not found.
All the machines on my network have a static IP address. When I try to access any of the other Windows 7 computers on my network, I get the same message as above but with the following two lines replacing the last two lines above:
Error code: 0x80004005
The troubleshooter found this problem:
Windows can't communicate with the device or resource (IP address) - Detected
I am unable to see the XP machine on the network list, and until recently, I have been able to view its files via IP address only. I have tried every solution I found so far, including:
Any help would be welcome.
|My System Specs|
|11 Mar 2011||#2|
| || |
Also, when I try to ping my own IP address, I get the result "Reply from <IP address>: Destination host unreachable." on each of the four trials. When I ping any other IP address on my home network, the request times out on all four trials.
I also can't join the existing homegroup; Windows says that "there is currently no homegroup on the network" despite the fact that every other computer running Windows 7 is able to enjoy the full benefits of the Homegroup.
|My System Specs|
|12 Mar 2011||#3|
| || |
I just want to clarify that the host machine for the homegroup is broadcasting its name, and my laptop can see it on the network (though, once again, I cannot connect to it by double-clicking or by using Remote Desktop Connection (message reads "Remote Desktop Connection can't find the computer "MACHINE-NAME". This might mean that "MACHINE-NAME" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
(I just discovered that I am able to see this computer's shared files and folders using its IP address as the network address, but that is the only computer I can see. I can't see my own computer using its IP address. When I try, Network Diagnostics says "Your computer appears to be correctly configured, but the device or resource (IP address) is not responding.")
My user account is password-protected, and User Account Control is enabled on all Windows 7 machines.
EDIT: Diagnostic report
Diagnostics Information (Network Adapter) Details about network adapter diagnosis: Network adapter Wireless Network Connection driver information: Description . . . . . . . . . . : Broadcom 4322AG 802.11a/b/g/draft-n Wi-Fi Adapter Manufacturer . . . . . . . . . : Broadcom Provider . . . . . . . . . . . : Microsoft Version . . . . . . . . . . . : 184.108.40.206 Inf File Name . . . . . . . . . : C:\Windows\INF\netbc664.inf Inf File Date . . . . . . . . . : Monday, July 13, 2009 8:37:27 PM Section Name . . . . . . . . . : BCM43XNM_NT61 Hardware ID . . . . . . . . . . : pci\ven_14e4&dev_432b Instance Status Flags . . . . . : 0x180200a Device Manager Status Code . . : 0 IfType . . . . . . . . . . . . : 71 Physical Media Type . . . . . . : 9 Diagnostics Information (Wireless Connectivity) Details about wireless connectivity diagnosis: Information for connection being diagnosed Interface GUID: d0d1af98-1e0e-4e4e-af23-16b30e54fbf4 Interface name: Broadcom 4322AG 802.11a/b/g/draft-n Wi-Fi Adapter Interface type: Native WiFi Connection incident diagnosed Auto Configuration ID: 1 Connection ID: 1 Connection status summary Connection started at: 2011-03-12 10:34:46-340 Profile match: Success Pre-Association: Success Association: Success Security and Authentication: Success List of visible access point(s): 4 item(s) total, 4 item(s) displayed BSSID BSS Type PHY Signal(dB) Chnl/freq SSID ------------------------------------------------------------------------- 00-0F-66-9D-EF-4F Infra g -58 6 linksys 00-12-17-D0-5D-3E Infra g -82 6 StephenM 00-24-8C-0E-CC-0A Infra g -88 11 lakehouse3 00-21-7C-09-2C-19 Infra g -48 1 2WIRE398 Connection History Information for Auto Configuration ID 1 List of visible networks: 4 item(s) total, 4 item(s) displayed BSS Type PHY Security Signal(RSSI) Compatible SSID ------------------------------------------------------------------------------ Infra g No 80 Yes linksys Infra g No 16 Yes StephenM Infra g Yes 4 Yes lakehouse3 Infra g Yes 87 Yes 2WIRE398 List of preferred networks: 3 item(s) Profile: UCONN-SECURE SSID: UCONN-SECURE SSID length: 12 Connection mode: Infra Security: Yes Set by group policy: No Connect even if network is not broadcasting: No Connectable: No Reason: 0x00028001 Profile: UCONN-PUBLIC SSID: UCONN-PUBLIC SSID length: 12 Connection mode: Infra Security: No Set by group policy: No Connect even if network is not broadcasting: No Connectable: No Reason: 0x00028001 Profile: linksys SSID: linksys SSID length: 7 Connection mode: Infra Security: No Set by group policy: No Connect even if network is not broadcasting: No Connectable: Yes Information for Connection ID 1 Connection started at: 2011-03-12 10:34:46-340 Auto Configuration ID: 1 Profile: linksys SSID: linksys SSID length: 7 Connection mode: Infra Security: No Pre-Association and Association Connectivity settings provided by hardware manufacturer (IHV): Yes Security settings provided by hardware manufacturer (IHV): No Profile matches network requirements: Success Pre-association status: Success Association status: Success Last AP: 00-0f-66-9d-ef-4f Security and Authentication Configured security type: Open Configured encryption type: None 802.1X protocol: No Key exchange initiated: Yes Unicast key received: No Multicast key received: No Number of security packets received: 0 Number of security packets sent: 0 Security attempt status: Success Connectivity Packet statistics Ndis Rx: 69553 Ndis Tx: 51287 Unicast decrypt success: 0 Multicast decrypt success: 0 Unicast decrypt failure: 0 Multicast decrypt failure: 0 Rx success: 3844 Rx failure: 10612 Tx success: 848 Tx failure: 0 Tx retry: 12 Tx multiple retry: 4 Tx max lifetime exceeded: 0 Tx ACK failure: 16 Roaming history: 1 item(s) Times: 2011-03-12 11:24:36-386 Roamed from BSSID: 00-0f-66-9d-ef-4f Reason: 0x00000000 Diagnostics Information (Wireless Connectivity) Details about wireless connectivity diagnosis: For complete information about this session see the wireless connectivity information event. Helper Class: Auto Configuration Initialize status: Success Information for connection being diagnosed Interface GUID: d0d1af98-1e0e-4e4e-af23-16b30e54fbf4 Interface name: Broadcom 4322AG 802.11a/b/g/draft-n Wi-Fi Adapter Interface type: Native WiFi Result of diagnosis: There may be problem Diagnostics Information (Wireless Network Adapter) Details about wireless network adapter diagnosis: For complete information about this session see the wireless connectivity information event. Helper Class: Native WiFi MSM Initialize status: Success Information for connection being diagnosed Interface GUID: d0d1af98-1e0e-4e4e-af23-16b30e54fbf4 Interface name: Broadcom 4322AG 802.11a/b/g/draft-n Wi-Fi Adapter Interface type: Native WiFi Profile: linksys SSID: linksys SSID length: 7 Connection mode: Infra Security: No Connect even if network is not broadcasting: No Result of diagnosis: There may be problem Network Diagnostics Log File Name: CBADE0AA-BA3B-4311-8700-FA2B2F116DD8.Diagnose.0.etl Other Networking Configuration and Logs File Name: NetworkConfiguration.cab Collection information Computer Name: SCOTT-UCONN Windows Version: 6.1 Architecture: amd64 Time: Saturday, March 12, 2011 11:42:52 AM
|My System Specs|
|30 Mar 2011||#4|
| || |
Here is the solution to "error code 0x80070035 network path was not found" on Windows Vista and Windows 7 Computers. Click on the "START" button, select "CONTROL PANEL", and go into "DEVICE MANAGER". Click on "NETWORK ADAPTERS", then click on "VIEW", and select "SHOW HIDDEN DEVICES". In the expanded view you will see a long list of numbered "MICROSOFT 6to4 ADAPTER". My Windows 7 Professional desktop had 200 of them. Right click and select "DELETE" on all but 1 of them. You can only do 1 at a time so it does take a while. When you have only 1 left, restart computer and enjoy being able to see your other network computers, including HOMEGROUP files.
|My System Specs|
|30 Mar 2011||#6|
| || |
error code 0x80070035
Creating a restore point will assure that you can get back to where you were before any deletes. I only deleted the Microsoft 6to4 adapter's. That was all that it took to repair the error code. The extra adapters were added to your system by Microsoft during automatic updates.
|My System Specs|
|Similar help and support threads for2: Error Code 0x80070035|
|Error 'code: 0x80070035 The network path was not found||Network & Sharing|
|Error code 0x80070035 redux, and I am getting battier by the minute||Network & Sharing|
|Error Code: 0x80070035 Unable to acces computer via network||Network & Sharing|
|Windows cannot access ... Error code: 0x80070035||Network & Sharing|
|It's not the printer, it's the network (Error code 0x80070035)||Network & Sharing|
|network error message: "Error code: 0x80070035". No file shareing help||Network & Sharing|
|Error Code 0x80070035 "Windows can not access"||Network & Sharing|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 02:43 PM.