All submitted content is subject to our Terms Of Use. General discussion. I have an urgent need for this information. Thank you. Share Flag. All Comments. Collapse -. I too am looking for this solution.
Found possible solution. This was my first thought. This may be the only situation where I will ever recommend you make sure SMB1 is on.
I think I've figured it out Did not know this was possible Good job, Microsoft! Bump - still need help, please. However, Win7 and newer clients do not have this issue. I'm out of ideas, please help! To continue this discussion, please ask a new question. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks.
Best Answer. This posting is provided AS IS with no warranties or guarantees , and confers no rights. My Linkedin Profile. My MVP Profile. Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. Check if we can ping domain or domain controller. Check whether all the Windows XP clients can not be added to the same domain. Check whether we use correct domain administrator credentials when we join Windows XP to domain.
Check if we try to create the Windows XP computer name in the domain first, then if we can add it to domain. However, this method is not work either. But surprisingly that, I found the computers membership is been disabled when I join the win p client to the domain. It's strange! Btw, thanks all for your feedback, suggestion and answer, appreciate it.
Anyway, i think i need to find a plan for the win XP client. Scriven Tan. The RC4 encryption support is enabled in policies for DC but it still doesn't work and DC ignores this setting when and r2 and even r2 works correctly.
I think that MS got decision to block RC4 support but no documentation about that was found. I hope that this is a bug and it will fixed whenever because this also affects other RC4 kerberos clients as various old Linux implementations being joined to AD domain.
Personally, I have no problem with nonsupporting of old protocols by default. So, it is definitely OK to not support it by default but still let to admins the option to enable it on their own risk in case they do want to support old clients such as XP or old Linux. But this is not the same case because theoretically Microsoft still has left the option to enable DES and RC4 support in policies in Windows but despite this it isn't working and no glue in MS documentations has been found about this limitation.
So, my conclusion this is a bug or some undocumented design change. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in.
0コメント