Transfer files between on premiss AD joined and Azure AD joined device. \\computername\C$ doesnt work

Joe Tech 1 Reputation point
2021-11-12T08:40:49.683+00:00

Normally to simply and fast transfer files over the internal network i use \computername\C$ so i can copy it. The envirement is hybrid with on premiss AD and Azure AD connected.

Now i have the problem this doesnt work with devices in Azure AD, is there another method how i can simply transfer files between AzureAD devices? Or need something to be configured?

The plan is to install all devices in our network with Intune and let them Join Azure AD. But simple things like this need to work before we go further.

Azure AD is new for me Thanks in advance!

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,107 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Chris Phillips 11 Reputation points
    2021-11-19T17:24:49.467+00:00

    A couple things to look at with your scenario as we're also going through the transition from all our computers being joined to an on premise AD to strictly AAD joined or some that are hybrid joined.

    First, if you were disabling the Windows firewall on your on premise joined computers via AD group policy, specifically when they were on the domain's network, this isn't the case with AAD joined computers. Even though the AAD joined computers are sitting on the same network as your on premise domain, they are not pulling those same AD group policies, at least not without some further configuration. So access to the admin share on that PC is probably being blocked by the Windows firewall.

    Second, if you get past that network error, the next error you'll probably run into is authenticating to the AAD computer if you're trying to access it from a hybrid joined or other non-AAD joined device. Typically when you try and access one AD joined computer's admin sharer (c$) from another AD joined computer, Windows authentication takes place behind the scenes seamlessly. But in this case, the AAD computer won't be able to authenticate due to it not recognizing the username format "username@keyman .com" like a typical AD joined computer would. So instead you'll need to authenticate using the format "azuread\username@keyman .com" (assuming you have everything setup to sync between your on premise AD and AAD via the Azure AD connect client.)

    Hope this help you out. (I found this post as we are trying to copy files to AAD joined computers when they're not on our network, rather sitting on the internet at home or at a coffee shop. We need to replace a config. file and are trying find a way to push that out to all our AAD computers when they don't have access to a local file share within our datacenter. Your situation is a bit easier since they reside on your network.)

    2 people found this answer helpful.

  2. MotoX80 31,391 Reputation points
    2021-11-15T15:23:44.96+00:00

    Now i have the problem this doesnt work with devices in Azure AD,

    It's really hard to help you based on a description of "doesnt work". What error do you get? Access denied? Network path not found? What account are you logged in with? Is the on-premise server able to authenticate that account? Have you tried using a non-admin share?

    Log on to the Azure server and use Powershell to test connectivity and to see if some firewall is blocking the TCP port.

    Test-NetConnection -ComputerName YourServerName -CommonTCPPort SMB   
    

    When we simply want to transfer some files from 1 pc to another pc. Without the need of a fileserver.

    In mstsc.exe, have it connect the local drives. and copy the files that way.

    149398-capture.jpg

    1 person found this answer helpful.

  3. Jason Sandys 31,146 Reputation points Microsoft Employee
    2021-11-12T15:47:23.827+00:00

    What's the scenario where this is needed?


  4. Georg Matviak 171 Reputation points
    2021-11-12T16:35:45.117+00:00

    Hello JoeTech-7816,

    Thank you for your question and reaching out. My name is Jainth and I’d be more than happy to help you with your query.

    For security reasons, connections to Azure file shares are blocked if the communication channel isn't encrypted and if the connection attempt isn't made from the same datacenter where the Azure file shares reside.

    Unencrypted connections within the same datacenter can also be blocked if the Secure transfer required setting is enabled on the storage account.

    An encrypted communication channel is provided only if the user's client OS supports SMB encryption.

    Do check out the below link which discuss on how to Troubleshoot Azure Files problems in Windows (SMB)

    https://learn.microsoft.com/en-us/azure/storage/files/storage-troubleshoot-windows-file-connection-problems

    Hope this answers all your queries, if not please do repost back.

    ---------

    --If an Answer is helpful, please click "Accept Answer" and upvote it--


  5. Georg Matviak 171 Reputation points
    2021-11-12T16:37:49.083+00:00

    Hello JoeTech-7816,

    Thank you for your question and reaching out.

    Below Microsoft article shows the basic steps for creating and using an Azure Files share. In this quickstart, the emphasis is on quickly setting up an Azure Files share so you can experience how the service works. If you need more detailed instructions for creating and using Azure file shares in your own environment,

    https://learn.microsoft.com/en-us/azure/storage/files/storage-files-quick-create-use-windows

    -------

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments