Our website may also include cookies from third parties like Google Adsense, Google Analytics, Youtube. By using the website, you consent to the use of cookies.
If you are still running a combination of Windows XP and Windows 7 client machines you may come across an issue when introducing your first Windows R2 Domain Controller server into your environment that your Windows XP clients no longer run login scripts.
The problem is to do with the versions of SMB which is supported between client and server communication which can cause issues with connecting to shares via UNC or executing login scripts on the DC. The following image will give you an idea of the versions of SMB between different clients and server. You can see that SMB1 and 2 driver is allowed.
If the configuration is successful a summary screen similar to the one illustration in the following figure will be displayed:. By default, shared folders are listed when users browse for shared resources.
From time to time, however, it may be necessary to share a folder but having it hidden such that only users who know of its existence can access it by referencing the share name. This concept is known as hidden share access. The most important point to note about hidden shares is that it does nothing to prevent access other than hiding the fact the that share exists.
If, for example, a user learns of the existence of a hidden share perhaps because another user tells them about it , and the share permissions are such that they have access to the folder, the fact that it is hidden will do nothing to keep the user out of that folder. As outlined at the beginning of this chapter, Windows Server provides two levels of permissions for shared files and folders, namely share permissions and file and folder permissions.
Share permissions are apply when access is made via the network. When shared files and folders are accessed locally from the server on which they reside these permissions server no purpose.
File and folder permissions, on the other hand, take effect both when accessing files and folders both locally and over the network. In the case of network access to a shared files and folder, the shared permissions are applied first, followed by any file and folder permissions. The key issue to note is that file and folder permissions provide a far greater level of control over access than the more more general permissions options provided by share permissions.
In this section, share permissions will be covered. For details on file and folder permissions refer to the chapter entitled Understanding Windows Server File and Folder Ownership and Permissions. Share permissions are granted on a per user and per group basis.
In addition to allowing a cap on the number of concurrent users accessing a share to be defined, share permissions also provide three permission options, each of which can be be set to Allow or Deny :. Permissions are cumulative in that a user will inherit the permissions of all the groups of which he or she is a member. If a permission is Denied , however, it overrides any cases where that permission may have been granted. For example, if a user is a member of a group where full control is provided over a folder, and also a member of a second group where full control is specifically denied, the user will be deined full control regardless of the fact that it was granted in the first group.
To configure share permissions, start Computer Management, connect to a remote server if not working on local shares, unfold System Tools and select Shares to list all currently shared folders.
To configure share permissions for a folder, select it from the list, right click and select Properties. In the properties dialog select the Share Permissions tab as illustrated in the following figure:. This screen displays the current share permissions and provides the ability to configure addition permission controls.
To change the settings for a currently configured group or user select the user from the list, modify the permissions accordingly and click on Apply to commit the changes..
To add permissions for a specific user or group click the Add button and enter one or more users or groups into the text box separating multiple entries with a semi-colon and click on Check Names to verify the names are correct. Click on OK to return to the properties dialog where the added users and groups will appear in the list.
Once again, select each name in turn and configure the desired share permissions. Finally, click Apply to commit the new permissions. Office Office Exchange Server. Not an IT pro? When I have ever logged into a server account at work, I used network resources, such as software and folders and access to network drives.
When I log into the server on my Windows XP computer, it goes through a prolonged setting up the desktop. It gives me the Dell default desktop background. My server is not a Dell computer. It tried to set up Outlook Express and got stuck. I had to remove it. Then the thing was able to finish setting up - and gave me the exact same icons that exist on the Windows XP computer. When I looked at network places it showed me the shared drive and folders it has access to on the server.
When the two computers were simply networked, each computer could see itself and the other one in its own version of the view the network computers screen. What am I doing wrong? Or have I misunderstood what is involved, and all office setups that are using Windows XP computers either have the computers directly internetworked, or use Server to network them?
Below is what I did to get the computers to see each other. Online that seems to be most of the battle of being able to join XP computers to a Server domain. Computer browser esrvice present, automatic and started. Check on DNS. Service Pack 3 contains a later version than what is on. Active network is Work. In Windows 7, right-click the folders you'd like to share and choose share with, and choose Homegroup Read and Write or equivalent.
I'm a little confused by your post here, you've provided a lot of information but I'm not sure exactly what it is that you are trying to do so can you start with the very basics of what it is you're trying to do and then we can look at some of the other issues.
So, you've got a windows server and a Windows XP machine and the XP machine isn't on the server domain?
In some cases I have given the computer a different name, to see if the Server was somehow remembering it, and these problems still occurred. An IP Config confirms this. At the moment they are awaiting a shutdown to install Office SP3, IE8 compatibility list and a security update.
Local Profiles have been deleted with no change. The one thing I haven't yet tried is removing the user from the Server entirely, deleting their Exchange account, and then re-creating them from scratch.
I have resisted doing this as I'm worried that I will loss data or E-Mails etc in the process. I know it is simple, just over cautious. Ok more information. These errors started to occur when we changed from a Domain Server to a new server with and changed the Domain level. This all happened before I started to how this was done I don't know. The users which have been effected all this long could be due to corruption during the change, except within the past month, a couple more users who have never had the problem before have also started to experience these issues.
So if we look away from it being User profile corruption, what else should I be looking into? The IT guy at the time doesn't think it is User Profile corruption, although he hasn't said much more then that.
We have had a real good look around DNS, and done a lot of Googleing on it. A few changes have been made, although this hasn't made any difference. Again I will look into DNS further. Its a tough one!
Ben YES! In the research I have done this is something I have come across several times but have so far failed to resolve. With all the different articles I find which could be related to the problems we are having, this is one which has been playing on my mind for a while so I'm glad you have mentioned it.
0コメント