Win 10 networking to an XP computer has changed

GerryPeters said:

For many years I've had a successful wired network between 2 Win 10 computers and a XP computer. Everything was working just fine. 2.5 years ago I had a lightening strike take out the XP's network card and I happened to have a Netgear wireless USB that I used instead in my XP computer.


It kept on losing the wireless network connection. I finally gave up trying to get it to work and found an exact replacement for my very old XP network card. I installed it and everything immediately worked fine, except for one thing.


From my XP computer it can't access the Workgroup, so it can't see folders or mapped drives on either Win 10 computer. Yet I can use remote desktop on any of the 3 computers to see the other computers and I can see my XP computer and all it's files from both Win 10 computers.


The only thing I can't do is access Win 10 files from my XP computer. Using Windows Explorer if I go to Network places / Workgroup. I get this error message - ":Workgroup is not accessible, might not have permission"


Since I save lots of image files, I returned my XP to it's Nov 2016 state and one of my Win 10 computers to it's Nov 2016 state. Everything works fine whit both computers using those old images. I've left my XP computer using that old image, since I haven't done much to the OS and programs since then. But my Win 10 computer needs to be current.


I looked at the Network settings of my Win 10 computer when using the Nov 2016 image and wrote down what I found, including some tweaks to SERVICES I did so I could see all my network computers in the Network folder. - I turned these services on:
Function Discovery Services
SSDP DiscoveryUPnP Device Host

also this: Control Panel\All Control Panel Items\Programs and Features>>Turn Windows Features On or Off
Find SMB 1.0 CIFS File Sharing Support /check only SMB 1.0 CIFS client


i wouldn't think any of these have caused my current problem. My guess is something has changed in Win 10, because my Win 10 computer has all the current Win Updates and some of the network settings look different than they did in Nov 2016.


So I'm hoping someone has some ideas on how to fix this

Hi there
@GerryPeters

@Bree

you don't need to disable IPV6 access provided Ipv4 can run concurrently -- usually on a home Lan addresses are in xxxx.xxxx.xxxx.xxxx (ipv4) format anyway.

On later builds of Windows 10 you need this as well : (Has to be done on the XP machine of course).

On the XP machine you need to enable SSP / NTLM (and of course on the windows 10 machines SMB1 must be enabled).

Here's an old thread showing what to do --don't worry that it's a VM (physical machine same rules) or NAS - this shows connectivity to / from XP to Windows 10 and NAS type systems.

XP and NAS (Samba) access

Cheers
jimbo

jimbo45 said:

you don't need to disable IPV6 access provided Ipv4 can run concurrently -- usually on a home Lan addresses are in xxxx.xxxx.xxxx.xxxx (ipv4) format anyway.

But I did have IPv6 and IPv4 running concurrently and it didn't allow XP to see the master browser for those machines on IPv6. And on my home network the router's DHCP server allocated each machine an IPv6 address as well as an IPv4 one.

XP can't see the IPv6 master browser. All the IPv6-capable machines use that in preference to IPv4, leaving the XP machine isolated, becoming the sole master browser on IPv4.

Not all of us have a Linux server on the network as you do, which is what you linked fix seems to be for.

Bree said:

But I did have IPv6 and IPv4 running concurrently and it didn't allow XP to see the master browser for those machines on IPv6. XP can't see the IPv6 master browser. All the IPv6-capable machines use that in preference to IPv4, leaving the XP machine isolated as the sole master browser on IPv4.

Not all of us have a Linux server on the network as you do, which is what you linked fix seems to be for.

Hi there
@Bree

No you STILL NEED the fix (NTLM etc) which will work giving XP and W10 access both ways on the latest W10 builds.

I'll fire up an XP VM machine later running on a Windows 10 host (latest 1909 18363.418) and post some screenshots once I've copied / "cloned" the XP VM from the Linux server.

Give me a couple of hours though -- going to local "hostelry" for a nice "liquid lunch" -- avoiding shopping which "SHE" of course wants to do when I've got a few days off !! .

I LOATHE shopping in physical stores at any time unless it's looking at and test driving nice fast sports cars (icelandic roads would kill a ferrari stone dead in about 3 mins flat outside town) or testing a nice new Cessna plane --- "if only ..." (I do have a PPL --Private Pilots License --with instruments for night flying etc BTW !!).


so had to say "Taking Dog for a walk !!" Best reason for having a Dog in these situations !!!!!!

Cheers
jimbo

Fafhrd said:

Whether these would help the OP or Bree in their respective cases would require them to try these out and report back...
Still what's the rush, regarding IPv6 changeover?

Thank you for your welcome contribution.

For my part it is not a pressing issue as my ISP (BT) supports IPv6 on all their broadband, albeit with only their BTHub 6 router (which is the one I now have) capable of using it.

It has been interesting to note the part that IPv6 vs IPv4 plays in the case of the master browser, and that it's possible to have two master browsers active at the same time, one on IPv6 and the other (the XP machine) on IPv4.

I have re-enabled IPv6 on my router now, as that's seem to be what all my machines (bar XP) prefer to use. I'll live with XP not seeing anything but itself on the network, as I can connect directly to a share from XP using the \\servername (and everything else can see the XP machine on the network anyway). I mainly keep the XP VM handy for support questions like this thread, not for any serious use. (the same could increasingly be said for the W7 and W8 VM's).


BTW, you can test your IPv6 connectivity by visiting this website: IPv6 Test and Dual-Stack Test For Network Connectivity