We are building world's most useful & helpful IM-based Azure community!
https://learn.microsoft.com/en-us/answers/questions/2102498/windows-11-24h2-azure-file-share-broken
Читать полностью…have you tested the authentication ..
Читать полностью…I checked ad connect it syncing
Читать полностью…I did unjoin and rejoin but not help
Читать полностью…There is no issues with the trust relationship. you can verify this - nltest /domain_trusts from the AVD machine.
Читать полностью…I checked all the way chat gpt and other fallowed process but still same
I tried to rejoin previous version azhybrid
I have shared the Azure function code to you in a personal chat
Читать полностью…I will share my code to review if you are fine
Читать полностью…If you can successfully connect to the SFTP server using FileZilla and through Logic Apps but are facing issues with your Azure Function, then i would say the problem may lie in the configuration or code of the Azure Function itself.
Читать полностью…Still getting same error message
Читать полностью…check if the authentication method (password, public key, etc.) used in your Azure Function is compatible with the SFTP server settings.
Читать полностью…Facing issue on Azure function Authentication failure message to establish connection to SFTP server, I have all checked all the options like credentials are correct and able to connect through fileZila correctly
Читать полностью…Are his videos good for az305?
Читать полностью…https://www.youtube.com/watch?v=R74bm8IGu2M&list=PLlVtbbG169nFr8RzQ4GIxUEznpNR53ERq
Читать полностью…As I did further teste today still failing
• Troubleshooting Steps and Results (Detailed):
1. Initial Kerberos Checks (On DC): Initial Kerberos checks performed on a domain controller showed valid tickets. However, this test was invalid as it didn't test the authentication flow from the AVD host.
2. klist on AVD Host (Initial Result): The klist command on the AVD host produced the following error:
Error calling API LsaCallAuthenticationPackage (GetTicket substatus): 0x6fbklist failed with 0xc000018b/-1073741429: The SAM database on the Windows Server does not have a computer account for this workstation trust relationship.
1. This indicated a problem with the secure channel or the AVD host's computer account in AD.
2. Storage Account Rejoin: The Azure Storage account was rejoined to the domain to ensure Kerberos key synchronization. This did not resolve the core issue.
3. Debug-AzStorageAccountADDSAuth Cmdlet: This cmdlet was used to verify various settings. It confirmed:
◦ Correct Kerberos ticket and channel encryption.
◦ Existence and permissions of the user's AD object.
◦ AVD host domain membership.
◦ Port 445 connectivity.
◦ Storage account domain membership.
◦ User RBAC assignments.
◦ Kerberos key synchronization (after the storage account rejoin).
4. klist on AVD Host (After Rejoin): After the storage account rejoin, the klist command on the AVD host continued to produce the same error as in step 2, indicating that the secure channel issue persisted.
5. Secure Channel Verification and Repair (On AVD Host): The following commands were run on the AVD host:
◦ nltest /sc_verify:lyv-srv-01.local
◦ Test-ComputerSecureChannel -Repair (and with explicit credentials)
6. Other Troubleshooting Steps:
◦ Permissions on the file share were verified multiple times.
◦ Time and date settings were confirmed to be accurate.
◦ A new VM was deployed from a snapshot, and repairs (SFC scans, updates) were performed.
◦ Testing from a DC worked, but not from AVD hosts.
◦ Microsoft Entra Kerberos was tested but reverted to AD DS.
◦ DNS resolution was confirmed.
◦ The error "The network path cannot be located" (Smb2DiagReasonDns) was investigated, but DNS resolution was working.
◦ FSLogix logs were reviewed but did not provide conclusive evidence.
◦ A new test user was created, but the issue persisted.
◦ Simplified mapping tests (using FQDN and short name) also failed.
Current Status:
• Kerberos authentication appears to be functioning correctly on the domain controller itself.
• The AVD session hosts are unable to establish a stable and functional secure channel with the domain controllers, preventing them from properly authenticating to the Azure File Share. This is the root cause of the credential prompts and FSLogix profile attachment failures.
Double-check the configuration of Azure Hybrid Identity. Ensure that the Azure AD Connect is properly syncing the on-premises Active Directory with Azure AD.
Читать полностью…if you think trust relationship is indeed broken , you may need to unjoin and rejoin the AVD machine to the domain. this can sometimes resolve issues with authentication.
Читать полностью…Windows version windows 11 24H2 multisession
Читать полностью…Hi ,
Can anyone help?
I have a storage account that connects using Azure Hybrid Module Identity with on-premises.
I have configured all permissions, but on the AVD machine, when that user logs in, it fails to attach.
Further troubleshooting revealed that the same user can access the storage account file share when logging into any server as the user.
However, on the AVD, the same user login prompts for a username and password. After entering them manually, the user is able to map the drive.
When I ran klist
for the storage account, it worked fine.
But on the AVD, klist
returns an error: “Trust relationship failed between domain.”
I checked the server to AVD trust, and it is fine.
I have rejoined another storage account but still have the same issue.
How to check the compatible, while directly connecting using FileZila is working and LogicApp through API connection as well
Читать полностью…Thank you for responding, I have uploaded hostkey in the function as well
Читать полностью…Help on this issue would greatly appreciated
Читать полностью…Hi All, Need help on Azure functions with Python code base, I am trying to SFTP Server copy files from blob storage container to SFTP server using Http trigger through Logic Applications
Читать полностью…This is the only thing you need. In deed a master class.
Читать полностью…YouTube is the best my friend
Читать полностью…