This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Let me state at the outset that I have had these two computers successfully networked in the last two weeks, but they will not stay networked. This machine is running Windows 7 (64 Bit) and the other machine is running Windows XP Professional Service Pack 3, 32 Bit. Both computers are set up to share everything in their C drives. The XP machine has a D drive that is also set up to share. In the last two weeks I have copied files back and forth between the two machines on all the drives. Both computers still show up under the network folders for each machine. Both computers are set up on the network with a workgroup name of HOME. I have run the Network Troubleshooter on the Windows 7 machine and it does not detect any problems. The Windows 7 Computer is named NEWCOMPUTER. The Windows XP computer is named OLDCOMPUTER. I have also shut down the firewalls and Virus protection programs on both machines. Network discovery is turned on for the Windows 7 machine. File and printer sharing is turned on. File sharing connections are set to 40 or 56 Bit encryption. Password protected sharing is turned OFF. Windows is allowed to manage Homegroup connections. Using the services.msc command, I set the Computer Browser properties startup type to automatic, the Server properties to automatic, the SSDP DEiscovery to automatic, and the TCP/IP NetBIOS Helper to automatic.
When I initially set up the Windows 7 machine, I tried to share the whole C drive with the Windows XP machine, but Windows XP would give an error message that said "Access denied you may not have permission..." So I went into the Windows 7 machine and had to set sharing and permissions to full control for everyone for every folder in the C drive. Then the Windows XP machine was able to open, read, and change every file on the Windows 7 machine other than System files. Now, when I click on the OLDCOMPUTER from the Windows 7 machine I get the error message "Error Code: 0x80070035 Windows cannot access\OLDCOMPUTER. When I click on the NEWCOMPUTER from the Windows XP machine I get the following error:
"An error occurred while reconnecting Y:to\Newcomputer\C: Microsoft Windows Network: The Network path was not found. The connection has not been restored."
A GUEST account is also set up on the XP machine. I am running a Netgear RP614v4****wired 4 port router that is connected via Ethernet cables to a Satellite Broadband modem. There is also a printer connected to this same router. Both computers can print to the printer via this router. Both Computers can access the Internet. They just cannot access each other.
Remember - This is a public forum so never post private information such as email or phone numbers!
Ideas:
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
hi
I do this solution that I meet mentioned error (0x080070035);
it occure between xp & 7 sometimes
so in Start type secpol.msc
go this path -> local policies -> security options -> network security: Lan Manager ...
-> choose second choice -> Send LM & NTLM- use NTLMv2 session security if negotiated
maybe OK
Hi Mike Sutherland 777,
Welcome to Microsoft Windows.
I would suggest you to change the security firewall settings or disable security software on the system and try to access the location.
For more information you may visit the link mentioned below where the customer has come the similar problem.
Hope this information is helpful.
Regards,
Sujan – Microsoft Support
Visit our Microsoft Answers Feedback Forum and let us know what you think.
Yes, Thx. The only thing is to use static IP. How come it was working before with DHCP??????
Thx anyways
Yes, static i/p usually works, but that can be a pain. I suggest you read all pages in this thread and try EVERYTHING. Sometimes it is a combination of changes, but sometimes it is just luck!! The problem I believe is an inherent fault whereby on a workgroup network (no separate Domain Name Server) each PC offers to do the local DNS function. Mostly one fulfills the role, but sometimes (as in this case) NEITHER takes the role, so there is no DNS resolution for the LAN. Use of static i/p means there is no requirement for DNS on the LAN.
By now Microsoft should be very well aware of this problem which has been around for years, but have failed to fix it.
PS. DHCP only allocates i/p addresses, it does not do the name resolution (DNS)
P.S. - Good Luck!
I've been having this problem for two months now in a windows 7 domain network and found that using Explorer and typing \ipaddress\sharename and \machinename\sharename will both work but what won't work is \machinename only. But, \ipaddress only will work.
If I disable network adapter and enable the adapter, \machinename then works again. The command from PeteNetLive, "netsh winsock reset" and "netsh int ip reset c:\temp\resetlog.txt" will also bring back the \machinename in Explorer without a reboot. I can do this as a workaround but after an unknown amount of time the problem re-occurs. From command prompt, I can ping either way and it works so it does seem like this is an Explorer bug but somehow related to DNS?
I have long believed this is a Windows networking DNS fault. Machines in the workgroup vie/offer to provide the DNS function in the absence of a separate (specified) Domain Name Server on the LAN. Sometimes no machine ends up providing the DNS service which gives rise to the problem. Resetting one of the network adapters allows the other to take over the DNS function, so for a while, it works OK, but then the machine providing the function decides to relinquish the function, it is then up for grabs, but if no machine picks up the DNS function, name addressing then fails.
If you have a separate device on the LAN providing a dedicated Domain Name Service, the problem should not occur. eg: a Domain Server setup to provide DNService.
Microsoft need to fix this problem, but as they are struggling to fix the botched releases of Windows 8.x and don't want to admit to the problem, I think it unlikely that we shall see a fix for this occasional problem any time soon.
