Home network problem: error code 0x80070035

Iíve just purchased a new Samsung Laptop running Windows 8 (aghh!!) to joint my network of two PCs running Windows 7 (SP1) and two running Windows XP (SP2). The problem Iím now experiencing is that although my four existing PCs and the new laptop can see each other and share files, the new laptop can only see and read any files on the PCs running XP while none of the four existing PCs can read any files on the new laptop (all can see and write to any C:/Users/Public area). From the view-point of sharing, Iíve set up the new laptop to be exactly the same as my Windows 7 PCs in respect to partition and file sharing and all the network parameters. When I get Windows to investigate the problem it comes up with error code 0x80070035, which isnít very helpful. It should be noted that Iím running F-Secure on all but one of my four existing PCs; the fourth just relying on Windows 7 Firewall.
Can anyone suggest what I can do to enable all my PCs to be able to share all of their files.

The error code means "the network path isn't found". Well, "setup to be the same" isn't correct. Each computer has to have its own name, and they all have to belong to the same network group (name). You may have that correct. Careful that the home network for the laptop is not marked as "public". Post back if you need more help.

Thanks for your response. I think my problem lies in the fact that when I go to 'Network and Sharing Center' on my new laptop I'm not seeing a network map above 'View your active networks' which I'm seeing on my other PCs; and also below it says 'Private network' in black whereas my other PCs say 'Home network' in blue denoting a clickable area. I can't see any way of changing 'Private Network' to 'Home Network'. Any ideas?

Homegroups will not work with XP. My recommendation is that you exit the homegroup and use standard sharing methods that work across all versions of windows. The easiest way I know is to create IDENTICAL accounts {User Name and Password} on every machine.
Then set your shares to Authenticated Users and things will work just fine.

On the Sharing Tab of the Drive/Folder properties of the object you want to share click the Advanced Sharing... tab.Sharing Tab.JPG
On the Advanced Sharing dialog click the Permissions button.
On the Permissions dialog click the Add button .
On the Select Users or Groups dialog click the Advanced button.
On the next screen click the Find Now button.
From the list displayed in the Search results box Click on Authenticated Users.
Click the OK button.
Click the OK button again.
Click on Authenticated Users in the Group or user names: box.Permissions.JPG
In the Permissions box check the permissions you wish to allow others to have.
Click Apply
Click OK.
Done.

File sharing using IP numbers

I have found that that using IP numbers instead of computer names sometimes gets around situations where one cannot otherwise share files. I have no idea why this works and welcome an explanation for this.

In order to use IP numbers, you have to assign static IP's to each machine and then type the share name into the dialogue box instead of browsing for the share when mapping a drive.Mapping with IP numbers.gif

Homegroup DOES work on Windows XP Pro SP3 with Windows 8 Pro on my network with my laptops. As long as I don't use a Picture Gesture login in Windows 8, the Windows XP machine can log in as any user of the Windows 8 laptop and join either the Homegroup or the Windows XP Workgroup. Login credentials are whatever the Windows 8 account uses. The Windows XP machine does not have access to Administrator files or folders on the Windows 8 laptop, even if they are Shared. The desired shared contents have to be copied to the Public User, and then Windows XP can do as it pleases with them.

Windows 7 is able to do either Homegroup or Workgroup, and here the issue lies. Windows 7 cannot allow Windows XP to join its Homegroup. So if there are Windows 7, Windows XP and Windows 8 computers on the network, Workgroup is the way to go.

With just Windows 8 and Windows XP (both Pro and XP with SP3) either Homegroup or Workgroup will work in my experiments. This is in a wired (ethernet) network.

Homegroup DOES work on Windows XP Pro SP3 with Windows 8 Pro on my network with my laptops. As long as I don't use a Picture Gesture login in Windows 8, the Windows XP machine can log in as any user of the Windows 8 laptop and join either the Homegroup or the Windows XP Workgroup. Login credentials are whatever the Windows 8 account uses. The Windows XP machine does not have access to Administrator files or folders on the Windows 8 laptop, even if they are Shared. The desired shared contents have to be copied to the Public User, and then Windows XP can do as it pleases with them.

Windows 7 is able to do either Homegroup or Workgroup, and here the issue lies. Windows 7 cannot allow Windows XP to join its Homegroup. So if there are Windows 7, Windows XP and Windows 8 computers on the network, Workgroup is the way to go.

With just Windows 8 and Windows XP (both Pro and XP with SP3) either Homegroup or Workgroup will work in my experiments. This is in a wired (ethernet) network.

I don't think I understand very well your statement, Bob. Windows XP does not recognize a Homegroup, so how does it join a Homegroup? Can you explain exactly how you make a Windows XP computer join a Windows 8 Homegroup?

I don't think I understand very well your statement, Bob. Windows XP does not recognize a Homegroup, so how does it join a Homegroup? Can you explain exactly how you make a Windows XP computer join a Windows 8 Homegroup?

I too thought the statements made by folks who haven't tried it were gospel. But I HAVE tried it since Windows 8 DP (through the current Windows 8 Pro, System Builder, PUL install) and every time, the Windows XP machine DID find the Windows 8 Homegroup as a Network Place, very distinct and with a separate login from the Windows XP Workgroup. Nothing special needed to set this up -- it just happened. This discovery struck me as strange and possibly undocumented, but I assure you, no chance in the world I've got any Windows 8 or Server component installed on a single-core Pentium P4m Winbook laptop from 2002 vintage running 32-bit Windows XP Pro SP3.

I even turned off the Windows Workgroup in Windows 8 (made it forget the Windows XP Workgroup completely) and Windows XP still found the Windows 8 Homegroup and joined it.

My Windows 7 Homegroup is NOT found by Windows XP in my setup.

Sometimes we need to ignore the warnings that something cannot be done, and just go ahead and DO it. that's how I found out that Windows 8 (in my network with my two laptops) did indeed let Windows XP Pro (any account) join its Homegroup (without Administrator privileges) and log in using any user's Windows 8 credentials, as long as the login type is supported in Windows XP Pro).

My Winbook has had a fresh install and complete rebuild since the last time anyone put any Server or Remote Access software on it, so this is not a sleight of hand trick. I only patch from official sources, so all I have are genuine Microsoft Windows XP patches. And third-party software updates, but no Remote Desktop or anything like that which could add networking clients or protocols. None that I know of, anyway. Not since the last rebuild.

Sorry if this is unbelievable, but TRY it -- it may work on your hardware and network. If anyone in The Lounge does try it and it works, perhaps you (anyone) can post.

Further details -- this is a wired connection between two computers without a router or switch between them. (Crossover Ethernet.) But it is a network. And the Homegroup is a Homegroup, distinct from the Workgroup.

If anyone has a better alternative explanation of what I really am using (Homegroup, Workgroup or Network Sharing) please post and explain.

So you inserted your homegroup password on the XP computer? Or what you actually mean is that you were able to connect to the Windows 8 machine with it configured just with the Homegroup?

I was and am able to log on to the Windows 8 Homegroup with the Windows XP computer when the Windows 8 computer doesn't know of the Windows XP Workgroup. To do this, Windows XP must find the Network Path of any user on the Windows 8 computer, then log in as that user with that user's credentials. The Windows 8 machine was configured with only a Homegroup and no Workgroup at the time.

Is it possible that Windows 8 sees the connection as Ad Hoc, and not a true network? Does this make any difference in how Homegroup is treated in terms of protocols and clients? No IP Address is ever recognized by either PC when connected in this configuration. Windows 8 does not list this connection as Ad Hoc, and Windows XP doesn't seem to distinguish visibly between ad hoc and true network connections.

I think, Bob, that the terminology is leading to some confusion. What I think you mean is that you can connect from XP to Windows 8, without the need for an active workgroup on Windows 8. This doesn't mean that you are using the Homegroup, as an Homegroup requires you to join the Homegroup with the password your set for that specific Homegroup when you created it and I don't think you are doing this, but please correct me if i am wrong.

The fact that you are using a crossover cable may be the cause for that, indeed. To establish your initial assertion beyond doubt, a traditional network configuration would need to be used (that is, having the computers connected through a router / hub / switch).