System error 64 has occurred, connecting XP to Win10

When I got here, I believe the XP Service Pack 3 PC connected fine to their Win10 Pro PC, which they use as their "server" to share files.  Now I have replaced the Win10 PC with a newer one--and now I can't connect their XP PC to it.  I can successfully ping from XP to Win10 PCs, but when I try "Net Use F: \\Whse\F-Drive" like all the other PCs on the LAN use, I get:

"System error 64 has occurred.  The specified network name is no longer available."

I have tried many things that do NOT work--including similar questions on e-e--but I'm hoping someone here will know what WILL work to solve the problem.  TIA
LVL 3
sasllcAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
XP uses and depends on SMBv1. That is gone from Windows 10 now. So with a new Windows 10 machine, XP will never connect again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dr. KlahnPrincipal Software EngineerCommented:
It would appear that the previous IT administrator enabled SMB version 1 on at least some of the systems.  This is a poor decision security-wise because SMB version 1 is insecure.

Three possibilities:

1.  Enable SMB version 1 on the server.  An extremely bad idea.
2.  Go the long way around.  Install the Microsoft XP Virtual Machine on a system.  Attach F: \\Whse\F-Drive to the host's file structure.  Configure file and folder sharing in the XP VM.  Share the necessary segment of the file structure with the VM.  Move the XP application to the VM.
3.  Migrate the XP application to Vista 32, which may be close enough for it to run successfully.
0
JohnBusiness Consultant (Owner)Commented:
No system Windows 7 forward should be using SMBv1 - do not do that as was suggested above.

Even as VM (at least VMware Workstation) XP will not connect. I have a Windows XP machine here.
0
McKnifeCommented:
As will all security related questions, you need to ask "does it even matter?".
If this environment needs no protection, simply enable the smb1 feature on win10. (Be aware: that endangers win10, not xp)

If it does need protection, I would use this simple solution: connect to xp from the win10 machine that xp wants to access the shares of via RDP and use host drive redirection.
1
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.