Skip to content

Commit dc2fe77

Browse files
authored
Merge pull request #100378 from jeffpatt24/patch-4
Update storage-sync-files-troubleshoot.md
2 parents d1552ae + f142c8d commit dc2fe77

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

articles/storage/files/storage-sync-files-firewall-and-proxy.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,6 +140,15 @@ For business continuity and disaster recovery (BCDR) reasons you may have specif
140140
> - https:\//kailani1.one.microsoft.com (paired fail-over region: East US)
141141
> - https:\//tm-kailani.one.microsoft.com (discovery URL of the primary region)
142142
143+
## Test network connectivity to service endpoints
144+
Once a server is registered with the Azure File Sync service, the Test-StorageSyncNetworkConnectivity cmdlet and ServerRegistration.exe can be used to test communications with all endpoints (URLs) specific to this server. This cmdlet can help troubleshoot when incomplete communication prevents the server from fully working with Azure File Sync and it can be used to fine tune proxy and firewall configurations.
145+
146+
To run the network connectivity test, install Azure File Sync agent version 9.1 or later and run the following PowerShell commands:
147+
```powershell
148+
Import-Module "C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"
149+
Test-StorageSyncNetworkConnectivity
150+
```
151+
143152
## Summary and risk limitation
144153
The lists earlier in this document contain the URLs Azure File Sync currently communicates with. Firewalls must be able to allow traffic outbound to these domains. Microsoft strives to keep this list updated.
145154

articles/storage/files/storage-sync-files-troubleshoot.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -117,6 +117,9 @@ This error occurs if the server endpoint path is on the system volume and cloud
117117
<a id="-2147024894"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2147024894 or 0x80070002)**
118118
This error occurs if the server endpoint path specified is not valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync does not support mapped drives as a server endpoint path.
119119

120+
<a id="-2134375640"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2134375640 or 0x80c80328)**
121+
This error occurs if the server endpoint path specified is not an NTFS volume. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync does not support mapped drives as a server endpoint path.
122+
120123
<a id="-2134347507"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2134347507 or 0x80c8710d)**
121124
This error occurs because Azure File Sync does not support server endpoints on volumes which have a compressed System Volume Information folder. To resolve this issue, decompress the System Volume Information folder. If the System Volume Information folder is the only folder compressed on the volume, perform the following steps:
122125

0 commit comments

Comments
 (0)