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.
That's different.
PeterM_42 replied on December 22, 2016 implied it was a DNS Failing in Windows 7 and Microsoft needs to fix it.
It MIGHT be a name resolution problem in NETBIOS, sure, but it's not a DNS failing, if there isn't a DNS server on the network - and DNS can't really run on a network without integration into the DHCP server, etc.
Do we know NETBIOS was turned on? It isn't always.
I've noticed some home wireless hubs now have pass through DNS installed; maybe that resolves it.
I don't disagree about a bug in Windows, but just a general rant about Microsoft isn't going to fix anything, especially when the person clearly didn't understand how DNS works.
So, what is specifically failing? Did you try ping/nslookup, a network sniffer to see if the packets are going out, NETBIOS or any other resolution turned on, etc?
If there is a fundamental failing, it's with the IETF to understand home networking needs too!
Oh, yes (BTW) I CAN connect to other machines on the network as \192.168.n.nnn, but it is annoying to have to know their ip addresses (let alone any suggestions of adding a lookup into the HOSTS file). Yes, NETBIOS is enabled when this problem occurs.
As more and more people have it, "Home" networking needs things to work properly!
It's a bug because it occurs randomly, usually four times out of ten. That is, with NON CHANGE in terms of parameters, network, settings, and machines, sometimes a system is able to resolve the name of the other system, sometimes it does not. Since resolution is base don broadcasting, there is some problem in the network browsing mechanism.
That's different.
PeterM_42 replied on December 22, 2016 implied it was a DNS Failing in Windows 7 and Microsoft needs to fix it.
It MIGHT be a name resolution problem in NETBIOS, sure, but it's not a DNS failing, if there isn't a DNS server on the network - and DNS can't really run on a network without integration into the DHCP server, etc.
Do we know NETBIOS was turned on? It isn't always.
I've noticed some home wireless hubs now have pass through DNS installed; maybe that resolves it.
I don't disagree about a bug in Windows, but just a general rant about Microsoft isn't going to fix anything, especially when the person clearly didn't understand how DNS works.
So, what is specifically failing? Did you try ping/nslookup, a network sniffer to see if the packets are going out, NETBIOS or any other resolution turned on, etc?
If there is a fundamental failing, it's with the IETF to understand home networking needs too!
