Similarly, we create folders called Girlstuff and Kidstuff. Click Permissions. Notice how, by default, the Everyone group has Full Control. This means that all users can read, write, and even delete files. Power User Tip : Ctrl-Click allows you to make multiple selections!
By default, the newly-added users have read-only access. You need to do this for each user! Select each user in the list in turn, and specify Change permission. To prevent Guest access to this share, we must remove the Everyone group! Select it, and click Remove.
Then click OK to close the share properties. Now, only the specified users can access the shared folder! Right-click the Girlstuff folder, then repeat the procedure above to give Iona and Catriona Change permission for the share. Remember to remove the Everyone group! Finally, right-click the Kidstuff folder, and repeat the procedure to give all the kids Change permission for the share.
Again, remember to remove the Everyone group. To keep files private from other local users, Windows XP provides a different mechanism. You can assign permissions to individual files and folders at file system level. Individual users may step up the security a notch to remove Administrators from the list.
Then, only that individual user can access his or her own files. When a user with an Administrator account sets a password on the account, Windows XP automatically prompts the user to step up the security on My Documents.
In order access shared data, a user connecting from the network needs to get past both gatekeepers:. If the shared folder is contained within Documents and Settings e. It depends on whether the user accounts are Limited or Administrators , and it also depends on whether the shared folder has been previously marked as Private. If you created a folder structure elsewhere, then you most likely do not need to do anything more.
Right-click the folder and select Sharing and Security. Go to the Security tab and look at the list. Note that the permissions are additive. Apart from yourself and Administrators , how can the users Alasdair and Fraser access the data in this share? It looks like they are not included on the NTFS permissions! They seem to have Read-only access.
Yet, if you try it, they have Write access, too! How can this be? What, pray tell, is Special Permission? Click Advanced to see. When a user on another computer on the network attempts to access a shared disk or folder, Windows XP Professional checks to see whether that user has permission to access it.
The client computer sends the user name and password of the user who is currently logged in, and the XP Professional computer checks them. If the ACL permits access by that user, access is granted; if not, access is denied. The user must be logged in with a user name and password that XP Professional recognizes. The following shows how to connect to a shared disk or folder from a computer running Windows 95, 98, or Me, and also shows some of the more common error conditions which can occur.
In this example, the client computer is running Windows 98 Second Edition. The most important thing is to understand that everything is keyed to the user name. When you boot up the client machine, you need to get logged in with the correct user name. If this is the case, click the Start button, and look at the Log Off menu option. It will show you what user name is currently logged on. If the XP Professional account was set up with a password, then you must enter that password at the Windows logon prompt.
Now, you ought to be able to browse the network by double-clicking Network Neighborhood or My Network Places. See the Troubleshooting section for how to proceed.
Basically it doesn't see the share and fails to connect. I'm able to access the Windows 10 share from other computers running Windows 10 and 7 without an issue. SMB1 is enabled on the Windows 10 computer. The XP machine can access a different file share that's being shared from a Windows 7 machine without any issues. I share between Windows 10 and Windows XP all the time. That's going both ways. Thanks all for the replies.
Unfotunately these are all suggestions Iv'e already checked. The folder is being shared out to everyone. It isn't a permission thing. Its setup to use a password and shared from the public folder. I verified SMB1 is enabled via Powershell. Some of us have to run legacy applications or have equipment that is specifically run by a Windows XP PC.
In these cases, a major capitol expenditure isn't an acceptable solution when the equipment still works perfectly fine. If you can prove me wrong, hand me 4 million dollars to replace two presses. Otherwise, only offer a helpful option, not what gets shoved down our throats daily already. Unless I'm mistaken, this isn't a software compatibility issue on the Windows 10 PC, it's a matter accessing a shared folder. Please, correct me if I'm wrong.
I'm referrencing when you said "Some of us have to run legacy applications or have equipment that is specifically run by a Windows XP PC. So the real problem is that you have legacy software that prevents you form upgrading to windows It would be worth trying to see if this software would run in compatibility mode on a windows 10 machine in a test environment.
Sorry, I thought you were referencing the OP's original post. String allocatecdroms to value 0 [it was previously at value 1]. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. Thanks for the reply and the links to all of your documentation.
However, I'm still a no go for accessing XP shares from my Windows 7 laptop. The firewalls are allowing all traffic on the Contact your network administrator to request access. I appreciate that you will have already tried turning off the Symantec Firewalls as an experiment so I will not suggest that. I do recall seeing warnings about accidentally running the XP sharing wizard more than once. Might that have been done? I did not turn off Simple file sharing on the XP Pro [I did not envisage needing to for its limited intended purpose].
0コメント