WAC + Storage Migration Service: Source fails validation - SMB connection, access denied

Hi all,

I'm brand new to WAC and Storage Migration Services.  I'm trying to set it up so that I can copy data from SourceA server to TargetB server.   SourceA is being migrated to TargetB machine, surprise surprise.

I am running into a problem getting the Job set up for this process.  After I have added the two machines and click on 'Validate' the status for the SourceA machine says that it failed:  "SMB Connection works -> Fail: Access is denied".

Strange part is that I am able to administer this SourceA machine from the rest of the WAC console; selecting it from Devices shows the full data from the remote machine.

SourceA:

  - Validation result = FAIL

  - Windows Server 2016  (AWS instance)

  - I believe that I have all the ports open in the Windows Firewall.

  - I do have access to the AWS console:   As an AWS instance, I also have to open up the Security profile for this machine; this is also done.  (I think ... I was skeptical about the recommended port range for the RPC/DCOM ephemeral ports - it's almost opening the entire port range?!  Why not just disable the firewall?  Just to be sure:  I did open the AWS Security firewall up to everything from the TargetB machine - all ports, all the time.  SMS Validation still fails; I AM still able to admin the SourceA machine, though.)

TargetB:  Windows Server 2019 (AWS instance)

  - Validation result = PASS

  - I have installed WAC on this machine, so my Orchestrator and my destination are the same machine

  - I have installed SMS here (via WAC console)

  - I do NOT have access to the AWS console for this machine - I can't directly modify the Security/firewall of AWS.  (I can modify the OS firewall.)

When setting up the Job, I entered credentials for the SourceA machine; this same account is not on the TargetB machine.  (Seems like you should be able to specify different credentials for each machine involved...)  But it is the SourceA machine that is complaining, that SMB says Access Denied.

[ A bit later:  I went back and set up a user account on both machines that was in the Administrator group; this user has the same PW on both machines.  I created a new Job, using this new Account.  It didn't help.  The validation for the local machine passes, but the SourceA machine still fails.

Hmmm... I also just noticed that the test for 'The credentials have administrative privileges' has the result 'Warning: Action isn't available remotely'.  Could that be the real root issue?  I was distracted by the following big-red error icon and hadn't really paid attention to the first entry. 🙂 ]