Home network problem: error code 0x80070035

Topic

New Reply

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.

Reply | Quote

Replies

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.

Reply | Quote

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?

Reply | Quote

Tony,

Do your settings look like this?
33621-W8NetworkSettings
:cheers:

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Not quite – Under ‘HomeGroup connections‘ on each of my PCs the ‘Allow Windows to manage …’ option has been selected.

Reply | Quote

Tony,

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.
33622-Sharing-Tab
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.
33623-Permissions
In the Permissions box check the permissions you wish to allow others to have.
Click Apply
Click OK.
Done.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Works a treat – Thanks very much for your help

Reply | Quote

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.
33670-Mapping-with-IP-numbers

Reply | Quote

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.

-- rc primak

Reply | Quote

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?

Reply | Quote

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.

-- rc primak

Reply | Quote

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?

Reply | Quote

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.

-- rc primak

Reply | Quote

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).

Reply | Quote

I think we’re forgetting that XP Pro can join a domain.

Reply | Quote

I think we’re forgetting that XP Pro can join a domain.

No one is saying it can’t. A Homegroup and a domain are different things.

Reply | Quote

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).

I think you may be correct, in that what I have is not a real network. This may be demonstrated in the lack of any IP addresses, the possibility that all that is being used is a Network Share strategy, and that an ad-hoc connection is used without a router. I also don’t get into the contents of the Windows 8 computer by logging in with the Homegroup’s Network Password, as I posted before.

All things considered, I think what I really have in this setup may well be an ad hoc connection without a true network. Nothing prevents this, and a Homegroup is not necessarily involved at all.

What the Windows 8 computer is using, it displays as a Home Network, and all Shares are through what the Windows 8 machine displays as its Homegroup. This is what has me wondering just what is actually going on here.

Maybe sometime when I have the time, I’ll connect the computers through my router’s Ethernet Ports and try to establish this same connection in a wired network with a router. If this works, it would tend to support my claim that Windows XP really is joining a Homegroup under Windows 8. I suspect, however, that the effort will fail, and only a Windows XP Workgroup will succeed with the router between the two computers.

I’ll try this sometime and report back in a new thread in the Lounge under Networking. It may be awhile before I get the free time to do this, but I am definitely interested in exploring this situation further.

I hope no one has become as confused as I now feel about all of this. And until I can test my theory further, I’ll stop posting that Windows XP can join a Windows 8 Homegroup. This may not be the case after all.

-- rc primak

Reply | Quote

I investigated Samba users to see how they are affected, and found the following solution:

For Win7:

Use regedit and edit the following:

HKEY_LOCAL_MACHINESYSTEMControlSet001ControlLsa
and
HKEY_LOCAL_MACHINESYSTEMControlSet002ControlLsa

under those 2 keys, add the following Value (or modify it if it already exists)

Type : 32-bit DWORD Value
Name : LmCompatibilityLevel
Value: 1

The following web page is explanatory: http://technet.microsoft.com/en-us/library/cc960646.aspx

The solution suggests to me that the actual differences in the incompatible formats are quite minimal.

Reply | Quote

It would be interesting to see what would happen with the router scenario, indeed :).

Reply | Quote

Just to confuse things a little, a Windows 7 or Windows 8 computer will support both a HomeGroup and a Workgroup at the same time. Obviusly, the Workgroup names have to be identical on all computers and it helps if the same user IDs and passwords are also used on all PCs.

Jerry

Reply | Quote

For those who wish to clear up some of the mystique surrounding Windows networking, the following site may be helpful:
http://networking.nitecruzr.net/2006/07/advanced-windows-networking-using.html.

Reply | Quote

For those who wish to clear up some of the mystique surrounding Windows networking, the following site may be helpful:
http://networking.nitecruzr.net/2006/07/advanced-windows-networking-using.html.

In this post at that site, the term Homegroup is never mentioned. This actually muddies the waters even worse for the current situation.

What I have is Ethernet Crossover. It is also ad hoc (device to device with no router or switch or hub).

What is at issue is that Windows XP in its Network Places does not clearly mark a Homegroup differently from a Workgroup. I have both showing up by Network Name (of each Computer) on both computers. And all logins use the Network Path followed by the local user name, and then the user’s local password. But whether or not either computer is part of (has joined) a Homegroup, a Workgroup, is involved in other types of Network Shares, or none of the above, neither the Explorer Tree, nor the Windows Explorer/File Explorer Network Places, nor the Windows 8 Network and Sharing Center seems to make clear.

So, the best way to prove that the Windows XP computer does not see a Homegroup in a real network (with a router, a switch or a hub) seems to be to actually try to set up both computers in such a (wired) full network, and see then what shows up, and where and how the Homegroup and the Workgroup are represented graphically in the Windows GUI (Network Places, both computers) and the Windows 8 Network and Sharing Center.

I’d bet the Windows XP computer would then only see one Workgroup, and never an additional Homegroup under its Network Places, and that the Windows 8 computer could log into the Windows XP computer, but this time a Workgroup Network Password (not local user credentials) would be requested. Same when the Windows XP computer would want to connect with the Windows 8 computer under the Workgroup, except that Windows XP would already be logged in to its own Workgroup, and would not even see the Windows 8 Homegroup.

That’s what I would expect to see. The proof is in the doing. When I have time, I’ll test this scenario. Im the meantime, I will refrain from declaring that I have connected Windows XP to a Windows 8 Homegroup.

-- rc primak

Reply | Quote

Your reservation about Home Groups missing from the site is well taken.

I have since learned that Home Groups use Peer Name Resolution Protocol (PNRP), Peer Networking Identity Manager (p2pimsvc), and Peer Networking Grouping (p2psvc). In short, this is an entirely different methodology with different services and protocols from those used in Work Groups.

Reply | Quote

Your reservation about Home Groups missing from the site is well taken.

I have since learned that Home Groups use Peer Name Resolution Protocol (PNRP), Peer Networking Identity Manager (p2pimsvc), and Peer Networking Grouping (p2psvc). In short, this is an entirely different methodology with different services and protocols from those used in Work Groups.

This is something I haven’t investigated. I should do so. I suspect neither of my “networks” is doing the Homegroup protocols. Next time I get a chance, I should look into these characteristics and post back.

-- rc primak

Reply | Quote