Windows 10: Sharing files on Windows 10 to Windows XP

Well, I've just about configured everything I need for Windows 10. Last is file sharing. It's the same old story with Microsoft sharing. See from one, can't see from another. I'm not using homegroup. The problem or error I receive is that on the XP laptop, the message says I don't have permissions. As anyone had any success with file sharing with the old Windows platforms and Win10? Can you provide me some steps?

:)

 

Printer sharing Windows 10 and Windows XP

I have the same problem. I know how to share a file, folder or printer since Win3.1

File sharing is working fine among Windows XP, Windows 7 and Windows 10. Printer sharing is working fine between Windows 7 and Windows 10, but it does not wokr with Windows XP, it must be a Windows 10 issue, please advice on workaround solution.

 

Networking a Windows 10 PC and a Windows XP PC

Do you have File Sharing turned on in Windows XP. You may have to specifically allow the login name used on the Windows 10 device to access the Windows XP device.

 

Hmmm, I was hoping to get some takers on my question. But I guess not too many people are using XP anymore. I still the XP PC because I'm just cheap. I have, through hours of trial and error, found the solution. Hope it helps others who want to share between Windows 10 and Windows XP.

These registry keys were defined on both platforms:
KEY: HKLM\System\CurrentControlSet\Control\Lsa
DATA: everyoneincludesanonymous = 1
KEY: HKLM\System\CurrentControlSet\Control\Lsa
DATA: NoLmHash = 0
KEY: HKLM\System\CurrentControlSet\Control\Lsa
DATA: LmCompatibilityLevel = 1
KEY: HKLM\System\CurrentControlSet\Services\LanManServer\Parameters
DATA: restrictnullsessaccess = 0

On Windows 10:
Change Advanced Sharing Settings:
All Networks section -> Turn of public folders, 128 bit encryption, turn off password protection
Private section-> Turn on network discovery, Turn on file/print sharing, Allow Windows to manage homegroup

I created a test share C:\Temp (L: \\PCNAME\Temp)
Open the properties to the share and do the following:
I defined the Share Tab permissions to accounts: Everyone and Administrators. Each account should have full control over the share.
I defined the Security Tab permissions to accounts: Everyone, Administrators, Users, and my logon username (example: tester). Give full control to each account.

In the Security tab section, all of those names should be present. The one I had to add was Users.

After making all the changes to the network settings, the Windows XP PC can access the shares on the Windows 10 PC

 

Hi there


Thanks for the solution - not only for XP but also for Mobile phone connection and Linux.

Had trouble connecting Linux shares as well - Had all firewalls switched off etc but didn't work until I saw the post. Windows Networking Ugh!!!!!!!

Cheers
jimbo

 

That's good everything worked out. I thought I had the solution but was tripped up the next day. I narrowed my problem down to NetBIOS over TCP/IP from the XP Pro SP3 laptop. Something to do with how it uses port 139 and or 445 when making the connection to the Windows 10 shares. My thing is that I want to use "My Network Places" (the thing is garbage) from XP. XP was also acting as the LAN browse master. I could see both PCs listed in My Network Places but received that dumb butt message described in original post. Well, using "netstat -an -p tcp" I found that XP was trying to connect first with Win10 on port 139. It would fail and then try port 445. In doing this, it might take a minute or two to time out. So I disabled NetBIOS over TCP/IP from each network properties. Added the IP and PC names to each hosts file. Now when I type L: \\pcname\temp from My Network Places the connection is made on port 445. And it is fast. never fails. I'm sure this is a well documented issue with XP Pro and I wish I could find more information about this. But like you said, Windows Networking Ugh!!!

Configure SMB use of Netbios | Network | Smallvoid.com

 

I just can't let it go. And this is yet another reason for me to dump XP. I put all the network parameters back in their original states. Then on the Windows 10 PC, I specifically disabled port 139 but leaving all other firewall settings alone. Now when the XP PC attempts to connect through port 139 on Win10. Win10 drops the request instantly and goes over to port 445 for the connection. Now those ugly connection delays through My Network Places are really gone.

 

Whoops. Disabling the port kind of worked. It was better to set the rules to block port 139 requests. Both inbound and outbound. It's very apparent now that MS changed something in the way file/printer sharing works. Because on my Windows 7 Pro PC I've never had to manipulate the firewall rules to work with XP Pro SP3.

 

A Knowledge Base article was given to me that specifically states what is happening on my home network. An old bug that somehow was reintroduce into Windows 10, maybe? And since I have no DNS running and no other method to execute name resolution. I have to address my shared computers and folders by the IP addresses. I hope a patch is produce. Though this release in Win10 is a preview, it would be nice to prove all important aspects of the OS works before officially being release to general public.

http://support.microsoft.com/kb/940684

 

thanks a lot finally connected my computers since i upgraded to windows 10 and i am still using my older computers and this works straightaway

 

Do you mean THAT's what they were before you DID anything? Or THAT's what you CHANGED them to? On the XP, the Win 10, or BOTH?

And in this second section......where you say, "Turn of public folders".....did you mean Turn ON....or turn OFF?
Thanks,
Michael

 

I'm starting to get a little concerned now because I began making your suggested registry edits and found that the key HKLM\System\CurrentControlSet\Control\Lsa
DATA: LmCompatibilityLevel = 1...........no longer exists. (At least not in my Windows 10 registry.)

Should this be a big cause of concern for me.....or should I just plunge ahead??

BTW, I'm running ver 1607, OS build 14393.576

Thanks, anyone, for any help/suggestions.