I removed him from local admin and it borked again. So i added him again as local admin and it's still borked. Why does MS only keep the Windows.
Really trying not to re-image this end user's computer. If the domain user account is just a member of the local users group, you won't be able to browse to the server by it's short-name, but FQDN works fine. Make the domain user account a member of the local admin group and everything works as expected.
I ended up disconnecting the previous drive mapping via a script and remapping the drive with the FQDN in a login script. This then allowed me to access the share, and if the drive is mapped using the FQDN, you are then able to browse to the share via the short-name. Yes, no problems. The other server shares are on Server R2 and servers. I just confirmed that my method works on a fresh Win10 VM I installed. Back to the permissions thing though, what the heck would be causing to not work right with a domain user who is a member of just "Users" group.
This points to some sort of permission issue? If I put that user as a local admin, works fine. According to what I've seen, a patch for this was released for the x versions - and obviously it did not cause the shares to fail.
But the "flaw" is "fixed" a. I've been trying to track down what that solution is in FU and what it does, but???????? You may be able to track down the issue via trace but be aware that some of the argument syntax is incorrect missing dashes, unnecessary slashes and asterisks. We have to roll back the update on quite a few machines. Just in case anyone is still dealing with this there does appear to be a functioning work around. It'll at least get us by until we can finally and fully deprecate our SMB1 shares.
It fixes the perpetual "reconnecting" status of the SMBv1 drive at logon and everything has been functioning normally and quickly for users we've added that registry key. Only needs to be added to the drive letters under Network that correspond to SMBv1 shares.
Credit goes to user LeeB in this thread. For those still experiencing, looks like MS released an update in October and supposedly fixed the SMB1 issue from version I am running the update now on a system to see if this is true..
Email Address:. Sign me up! Karachi, Karachi City, Sindh, Pakistan. Share this: Twitter Facebook. Like this: Like Loading Comments 1. Thank you so much i were facing this issue now i will try this Step Once Again Thank you. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public.
Name required. Archived Forums. File Services and Storage. Sign in to vote. We have a Domain with a DC running server r2 and 2 file servers also running server r2. The shared folders on one of the file servers cannot be accessed I can ping both ways with ip and name. I have removed the server from the domain and added it back. Even the DC cannot access the file server. I have read forums and have tried various fix with not luck. I have enabled the guest account, added both computer name and user name to the shared folder still no luck, any thoughts would be appreciated.
Wednesday, November 10, PM. Yes I verified that it was. At this point I am looking at everything twice. Thanks for the input. Hi, Please try to share a folder to Everyone and see whether you will still get the same error related to permission.
If so, please type the error exactly in reply. Shaon Shan TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb microsoft. Monday, November 15, AM. Hello I created a folder called test and set permissions for everyone.
Thank you for any thoughts you might have Ed Whidden.
0コメント