Azure AD Workstations and Local network Shares Not working

%3CLINGO-SUB%20id%3D%22lingo-sub-867391%22%20slang%3D%22en-US%22%3EAzure%20AD%20Workstations%20and%20Local%20network%20Shares%20Not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867391%22%20slang%3D%22en-US%22%3E%3CP%3EMost%20of%20our%20environment%20has%20been%20switched%20over%20to%20an%20Azure%20AD%20Joined%2FAutopilot%2FIntune%20managed%20infrastructure.%26nbsp%3B%20Most%20machines%20I%20can%20manually%20map%20a%20drive%20to%20a%20file%20share%20on%20an%20internal%20server%20without%20much%20issue.%26nbsp%3B%20Running%20Windows%2010%20with%20Hello%2C%20I%20have%20to%20switch%20from%20PIN%20to%20username%20but%20otherwise%20the%20solution%20works.%20We%20do%20have%20AD%20Connect%20running%20however%2C%20the%20server%20has%20guest%20login%20enabled%2C%20as%20some%20users%20are%20not%20on-premise%20at%20this%20point.%26nbsp%3B%20Again%20this%20is%20an%20old%20file%20server%20that%20has%20older%20data.%20New%20stuff%20is%20in%20SharePoint%20Online.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20problem%20I%20have%2C%20on%20occasion%2C%20I%20have%20a%20machine%20that%20refuses%20to%20connect.%20%22Windows%20cannot%20access%20%5C%5CSERVERNAME%22%20%22Check%20the%20spelling%20of%20the%20name...%22%26nbsp%3B%20Try%20to%20connect%20via%20Net%20Use%20from%20command%20line%20states%20it%20is%20not%20possible%20as%20the%20user%20is%20already%20connected%20using%20a%20different%20name%3B%20which%20is%20not%20the%20case%2C%20as%20there%20is%20only%20one%20local%20resource%20users%20on%20these%20occasions%20need.%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20times%20a%20restart%20will%20correct%20it.%20Other%20times%2C%20it%20does%20not.%20As%20in%20right%20now.%20I%20have%20a%20user%20that%20it%20will%20simply%20not%20allow%20them%20to%20connect.%20They%20do%20not%20even%20get%20prompted%20to%20login.%20Already%20checked%20and%20removed%20any%20windows%20credentials%20that%20might%20have%20been%20saved%20as%20well.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1074523%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20Workstations%20and%20Local%20network%20Shares%20Not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1074523%22%20slang%3D%22en-US%22%3EI'd%20also%20try%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzure-Active-Directory%2Fct-p%2FAzureActiveDirectory%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FAzure-Active-Directory%2Fct-p%2FAzureActiveDirectory%3C%2FA%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Contributor

Most of our environment has been switched over to an Azure AD Joined/Autopilot/Intune managed infrastructure.  Most machines I can manually map a drive to a file share on an internal server without much issue.  Running Windows 10 with Hello, I have to switch from PIN to username but otherwise the solution works. We do have AD Connect running however, the server has guest login enabled, as some users are not on-premise at this point.  Again this is an old file server that has older data. New stuff is in SharePoint Online. 


The problem I have, on occasion, I have a machine that refuses to connect. "Windows cannot access \\SERVERNAME" "Check the spelling of the name..."  Try to connect via Net Use from command line states it is not possible as the user is already connected using a different name; which is not the case, as there is only one local resource users on these occasions need.    

Some times a restart will correct it. Other times, it does not. As in right now. I have a user that it will simply not allow them to connect. They do not even get prompted to login. Already checked and removed any windows credentials that might have been saved as well. 

 

Thanks. 

1 Reply