When connecting to windows 10 computer b Lenovo laptop , it connects automatically when it's visible but it's sometimes shown as "unknown". If I re-boot the windows 10 machine it will show as available and connects automatically. The windows 10 machines are connected to the network via wi-fi; the windows Xp machine is connected via ethernet cable.
When I first set up the network, I could connect from the Xp machine to both 10 machines and vice-versa, but I could only connect from the windows 10 machines in one direction.
I added the user accounts from windows 10 to my windows xp workgroup. The result of this is that I can communicate both ways for machine a to machine b but not reliably but I can't see my workgroup in windows Xp and I can't connect from windows 10 to windows xp.
I simply want to create a home network, consisting of a windows XP machine and 2 windows 10 machines. This seems to be almost impossible. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
I have the same question Report abuse. By BrianWolk , July 31, in Windows. Does anyone know what the difference is between Security vs Sharing permissions as applied to Windows XP and ? In particular, how come I can't get Windows to "see" users on other computers and allow me to set access permissions for them? Does a user have to have an account on both local and remote computers if they wish to access a folder? Also, what is the difference between a "deny" setting as opposed to just un-checking the equivalent "allow" setting?
I am finding Windows file sharing management very confusing. The ability to "see" users on other computers or basically to assign rights to people on your network and not the local machine is dependant on a domain controller. Unless you are a member of a domain you will only be able to set rights for accounts on the local machine.
If you configure the same user account on 2 machines with the same password then the remote machine will be able to use the same security settings when connecting. Best Practice - set the share permissions to Everyone, full control. Choose users or security groups you wish to have access to your share and select them in the Security tab.
The reason for this is that the most restrictive permission applies, so you say everyone can see the share but their permissions in Security will dictate the access level. Sounds confusing but this is a module in a couple of Microsoft courses and is not easy to explain. These are examples of what I have to work with and what others deal with too. Yes, we know Windows XP is bad, but we don't always have a choice.
NathM , your correct. I saw that they pinged the IP, but missed that they tried connecting to it. Sorry for the confusion. Thanks for the replies. NicCrockett- You are correct in saying that the system is a legacy piece of hardware that controls a specialized machinery that isn't easily upgradeable.
I found what the issue was. What I failed to realize at the time was that the server side of SMB was not enabled. Once I enabled SMBv1. Server-side via Windows features, everything worked fine. Funny you mention that. I was just getting ready to post this photo, suggesting you manually check the settings instead of using PowerShell.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Hi All, In some need of expert opinions regarding an issue I'm facing. I have tried accessing the share by both name and IP from the XP machine to no avail. Is it even possible to access a file being shared from a Windows 10 computer to Windows XP? Best Answer. Cuber This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
View this "Best Answer" in the replies below ».
0コメント