Link to home
Start Free TrialLog in
Avatar of mkramer777
mkramer777Flag for United States of America

asked on

Can't connect to shared folder on windows 10 Pro computer from windows Xp Pro computer

User generated image

 have a software program that is very old and running on windows xp pro.  The xp pro computer is in a workgroup called "LANDFILL"  I have another computer in this remote office (FYI.  These computers are on the same network) and it is windows 10 pro.The windows 10 computer is part of the domain and is not on the workgroup landfill.  I have shared out a folder on this computer but cannot access it with the xp pro computer.  I can ping from xp pro computer to windows 10 computer.  I get the errors when I try and do START -RUN - \\ip address.  


User generated image




I


Avatar of Scott Silva
Scott Silva
Flag of United States of America image

The ONLY way to get XP to connect to a Win 10 PC is very risky as you have to allow some very unsafe protocols on the Win 10 machine. It would be better to virtualize the XP machine if possible, and use the built in file sharing bits of the hypervisor.

Avatar of mkramer777

ASKER

Still need to know how to do this until the win xp pro computer is retired.

1. what is the IP configuration of the Win XP machine? IP address, subnet mask, router IP?
2. could you show the ping results Win 10 from Win XP?
192.0.0.183
255.255.255.0
192.0.0.3

I don't have a ping results page.  What are you looking for?  I saw it when I ran it when I was over at the remote office.
Just showed a reply from (192.0.0.174 - ip of win 10 pro pc) and TTL 
On Windows 10 (logged into an administrator account) Press Windows Key + R and then type appwiz.cpl in the run box.
Then click on turn on or off Windows features.
You'll then be greeted by a smaller window with a list of features that you can turn on/off.
Enable SMB 1.0/CIFS File Sharing Support and then click OK.
This should allow you to access the network share on your XP system
 
It is recommended to turn off SMB 1 after you're finished as it's considered as an old and vulnerable protocol .
For more infomation:
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows-server
https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/

At least this used to work...

Do you have the same user name and password on both computers?

On a separate note, 192.0.0.x is a public address.  That shouldn't be an issue with this sharing (though it would be an issue accessing anything on the internet with the same subnet), but it is unusual on a LAN.
ASKER CERTIFIED SOLUTION
Avatar of Dr. Klahn
Dr. Klahn

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Is there a way to check if computers on the network have SMBv1 installed other than going into windows features and seeing if it there?  Just curious

Are you using a domain?
If so maybe something like this...

$b4={Get-SMBServerConfiguration  |Select-Object EnableSMB1Protocol,EnableSMB2Protocol,pscomputername}

ForEach ($COMPUTER in (Get-ADComputer -Filter '*' | Select -ExpandProperty Name))
{if(!(Test-Connection -Cn $computer -BufferSize 16 -Count 1 -ea 0 -quiet))

{write-host "cannot reach $computer" -f red}



else {


Invoke-Command -ComputerName $computer -ScriptBlock $b4
}
}

Open in new window