Merge pull request #8071 from MicrosoftDocs/main

Auto push to live 2025-01-20 02:00:03

Author: Deland-Han

support/breadcrumb/toc.yml

@@ -19,6 +19,9 @@ items:
       - name: Windows Client
         tocHref: /troubleshoot/windows-client/
         topicHref: /troubleshoot/windows-client/welcome-windows-client
+      - name: Windows 365
+        tocHref: /troubleshoot/windows-365/
+        topicHref: /troubleshoot/windows-365/welcome-windows-365
       - name: Application Developer
         tocHref: /troubleshoot/windows/win32
         topicHref: /troubleshoot/windows/win32/welcome-windowsdeveloper

support/docfx.json

@@ -82,7 +82,8 @@
         "windows/win32/*.*": "MSDocsHeader-WinDevCenter",
         "windows-client/**.*": "MSDocsHeader-Windows",
         "windows-hardware/**.*": "MSDocsHeader-WinHW",
-        "windows-server/**.*": "MSDocsHeader-WindowsServer"
+        "windows-server/**.*": "MSDocsHeader-WindowsServer",
+        "windows-365/**.*": "MSDocsHeader-Windows365"
       },
       "feedback_product_url": {
         "dynamics/gp/*.md": "https://experience.dynamics.com/ideas/categories/?forum=771cc5ac-c117-e811-8105-3863bb2e0320&forumName=Dynamics%20GP",
@@ -103,6 +104,7 @@
         "power-platform/dataverse/**/*.md": "https://powerusers.microsoft.com/t5/Microsoft-Dataverse/bd-p/CDS_Apps",
         "windows-server/**/*.md": "https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/bd-p/WindowsServer",
         "windows-client/**/*.md": "https://support.microsoft.com/windows/f59187f8-8739-22d6-ba93-f66612949332",
+        "windows-365/**/*.md": "https://feedbackportal.microsoft.com/feedback/forum/6ab53114-95ab-ec11-9840-000d3a1c7d74",
         "windows-hardware/**/*.md": "https://support.microsoft.com/windows/f59187f8-8739-22d6-ba93-f66612949332",
         "developer/dotnet/**/*.md": "https://developercommunity.visualstudio.com/dotnet/report",
         "developer/visualstudio/**/*.md": "https://developercommunity.visualstudio.com/VisualStudio",
@@ -146,6 +148,7 @@
         "windows-hardware/drivers/**/*.md": "HaiyingYu",
         "windows-client/**/*.md": "Deland-Han",
         "windows-server/**/*.md": "Deland-Han",
+        "windows-365/**/*.md": "Deland-Han",
         "mem/**/*.md": "helenclu",
         "system-center/**/*.md": "helenclu",
         "dynamics-365/customer-insights/**/*.md": "m-hartmann",
@@ -178,6 +181,7 @@
         "windows-hardware/drivers/**/*.md": "haiyingyu",
         "windows-client/**/*.md": "delhan",
         "windows-server/**/*.md": "delhan",
+        "windows-365/**/*.md": "delhan",
         "mem/**/*.md": "luche",
         "system-center/**/*.md": "luche",
         "dynamics-365/customer-insights/**/*.md": "mhart",
@@ -242,7 +246,8 @@
         "windows/win32/**/*.md": "windows-dev-apps",
         "windows-hardware/drivers/**/*.md": "windows-hardware-driver-quality",
         "windows-client/**/**.*": "windows-client",
-        "windows-server/**/**.*": "windows-server"
+        "windows-server/**/**.*": "windows-server",
+        "windows-365/**/**.*": "windows-365"
       },
       "titleSuffix": {
         "developer/dotnet/**/*.md": ".NET",
@@ -263,6 +268,7 @@
         "windows-hardware/drivers/**/*.md": "Hardware Developer",
         "windows-server/**/*.md": "Windows Server",
         "windows-client/**/*.md": "Windows Client",
+        "windows-365/**/*.md": "Windows 365",
         "mem/intune/**/*.md": "Intune",
         "mem/configmgr/**/*.md": "Configuration Manager",
         "system-center/dpm/**/*.md": "Data Protection Manager",

support/sql/database-engine/connect/resolve-connectivity-errors-overview.md

@@ -1,10 +1,11 @@
 ---
 title: Troubleshoot connectivity issues in SQL Server
 description: Provides an overview of common connectivity issues in SQL Server and describes the tools to troubleshoot the issues.
-ms.date: 06/16/2022
+ms.date: 01/20/2025
 ms.custom: sap:Database Connectivity and Authentication
 author: HaiyingYu
 ms.author: haiyingyu
+ms.reviewer: jopilov
 ---
 # Troubleshoot connectivity issues in SQL Server
 
@@ -14,7 +15,7 @@ _Original KB number:_   4009936
 There are various causes for connectivity issues in SQL Server. This article series helps you troubleshoot the most common SQL Server connectivity issues and describes the tools and methods you can use for troubleshooting.
 
 > [!NOTE]
-> If multiple SQL Server instances in your environment are impacted, or the issue is intermittent, it usually indicates Windows policy or networking issues. Although this series of articles provides guidance, it may not effectively troubleshoot some specific scenarios.
+> If multiple SQL Server instances in your environment are impacted, or the issue is intermittent, it usually indicates Windows policy or networking issues. 
 
 ## Preparation
 
@@ -26,16 +27,15 @@ Use the following list to navigate to the appropriate article page for detailed
 
 - [A network-related or instance-specific error occurred while establishing a connection to SQL Server](../connect/network-related-or-instance-specific-error-occurred-while-establishing-connection.md)
 
-- [Cannot generate SSPI context](cannot-generate-sspi-context-error.md)
+- [Can't generate SSPI context](cannot-generate-sspi-context-error.md)
 
-- [Login failed for user](/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error?context=/troubleshoot/sql/context/context)
+- [Login failed for user](/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error?context=/troubleshoot/sql/context/context) which covers the following login errors:
 
-  Covers the following Login errors:
-  - "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
-  - "Login failed for user '(null)'"
-  - "Login failed for user (empty)"
-  - "Login failed for user '\<username\>'"
-  - "Login failed for user '\<domain>\\\<username>'"
+  - > "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
+  - > "Login failed for user '(null)'"
+  - > "Login failed for user (empty)"
+  - > "Login failed for user '\<username\>'"
+  - > "Login failed for user '\<domain>\\\<username>'"
 
 - [Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding](../connect/timeout-expired-error.md)
 
@@ -45,29 +45,41 @@ Use the following list to navigate to the appropriate article page for detailed
 
 - [The certificate chain was issued by an authority that is not trusted](../connect/error-message-when-you-connect.md)
 
-## Tools and methods that help you troubleshoot connectivity issues
+## Tools and methods to troubleshoot connectivity issues
 
-The following articles provide details for various tools and procedures to troubleshoot different connectivity errors:
+The following sections provide details for various tools and procedures to troubleshoot different connectivity errors:
 
-- [Configure firewalls to work with SQL Server](/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?context=/troubleshoot/sql/context/context)
+### Configure Windows Firewall to work with SQL Server
 
-  Describes how to configure Windows firewall for successful connections to instances.
+[Configure firewalls to work with SQL Server](/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?context=/troubleshoot/sql/context/context) describes how to configure Windows Firewall for successful connections to instances.
 
-- [Test connections to SQL Server by using Universal Data Link (UDL) files](../connect/test-oledb-connectivity-use-udl-file.md)
-  
-  Describes how to test connections between SQL Server and clients using UDL files.
+### Test an OLEDB or ODBC connection to SQL Server
 
-- [Use PortQryUI tool with SQL Server](../connect/network-related-or-instance-specific-error-occurred-while-establishing-connection.md#named-instance-of-sql-server)
+- If you want to quickly test a connection from a client machine to a SQL Server instance, you can configure a UDL file. For more information, see [Test connections to SQL Server by using a Universal Data Link (UDL) file](../connect/test-oledb-connectivity-use-udl-file.md).
 
-  Describes how to use the PortQryUI tool (a graphical user interface (GUI) port scanner) to help troubleshoot connectivity issues.
+- You can also use the ODBC Data Sources (64-bit) or ODBC Data Sources (32-bit) Administrator to configure and test an ODBC connection to SQL Server. For more information, see [ODBC Data Source Administrator DSN options](/sql/connect/odbc/windows/odbc-administrator-dsn-creation#create-a-new-data-source-to-sql-server---screen-1).
 
-- [Check whether SQL Server is listening on dynamic or static ports](../connect/static-or-dynamic-port-config.md)
+### Discover if a port is blocked with PortQryUI
 
-  Provides steps to check whether SQL Server is listening on dynamic or static ports.
+You can use the PortQryUI tool (a graphical user interface (GUI) port scanner) to help troubleshoot connectivity issues. For more information, see [Use PortQryUI tool with SQL Server](using-portqrytool-sqlserver.md).
 
-- [Use Kerberos Configuration Manager to fix SPN issues](../connect/cannot-generate-sspi-context-error.md#fix-the-error-with-kerberos-configuration-manager-recommended)
+### Find which ports SQL Server listening on
+
+This article [Check whether SQL Server is listening on dynamic or static ports](../connect/static-or-dynamic-port-config.md) provides steps to identify which ports SQL Server is listening on.
+
+### Get a detailed diagnostic report with SQLCheck
+
+Microsoft product support engineers frequently use [SQLCheck](https://github.com/microsoft/CSS_SQL_Networking_Tools/wiki/SQLCHECK), which is a tool they built to diagnose causes of connection failures. You can follow the [instructions](https://github.com/microsoft/CSS_SQL_Networking_Tools/wiki/SQLCHECK) to download and collect the SQLCheck report for in-depth analysis. 
+
+### Use Kerberos Configuration Manager
+
+To identify and resolve Service Principal Name (SPN) issues, you can use the Kerberos Configuration Manager. For more information, see 
+[Use Kerberos Configuration Manager to fix SPN issues](../connect/cannot-generate-sspi-context-error.md#fix-the-error-with-kerberos-configuration-manager-recommended).
+
+### Collect and analyze a network trace with SQLTrace and SQLNAUI
+
+In many cases, a network trace might be the most effective tool to investigate network failures. You can follow the steps in [Collect network traces on the client and server](intermittent-periodic-network-issue.md#collect-network-traces-on-the-client-and-server) to investigate failures. Then, you can analyze the network trace using the [SQL Network Analyzer UI SQLNAUI](https://github.com/microsoft/CSS_SQL_Networking_Tools/wiki/SQLNAUI).
 
-  Describes how to use Kerberos Configuration Manager to fix Service Principal Name (SPN) issues.
 
 ## See also
 

support/windows-365/breadcrumb/toc.yml

@@ -1,7 +1,16 @@
-- name: Troubleshoot
-  tocHref: /troubleshoot/
-  topicHref: /troubleshoot/index
+items:
+- name: Docs
+  tocHref: /
+  topicHref: /
   items:
-  - name: Windows 365
-    tocHref: /troubleshoot/windows-365/
-    topicHref: /troubleshoot/windows-365/welcome-windows-365
+  - name: Troubleshoot
+    tocHref: /troubleshoot/
+    topicHref: /troubleshoot/index
+    items:
+    - name: Windows
+      tocHref: /troubleshoot/windows/
+      topicHref: /troubleshoot/windows/index
+      items:
+      - name: Windows 365
+        tocHref: /troubleshoot/windows-365/
+        topicHref: /troubleshoot/windows-365/welcome-windows-365