Skip to content

Commit 34d0c1b

Browse files
committed
Reviewing, feedback
1 parent f9f1573 commit 34d0c1b

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

articles/defender-for-iot/organizations/how-to-troubleshoot-sensor.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,7 @@ The **Cloud connectivity troubleshooting** pane covers the following types of is
4848
|**Proxy authentication issues** | Occurs when a proxy demands authentication, but no credentials, or incorrect credentials, are provided. <br><br>In such cases, make sure that you've configured the proxy credentials correctly. For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration). |
4949
|**Name resolution failures** | Occurs when the sensor can't perform name resolution for a specific endpoint. <br><br>In such cases, if your DNS server is reachable, make sure that the DNS server is configured on your sensor correctly. If the configuration is correct, we recommend reaching out to your DNS administrator. <br><br>For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration). |
5050
|**Unreachable proxy server errors** | Occurs when the sensor can't establish a connection with the proxy server. In such cases, confirm the reachability of your proxy server with your network team. <br><br>For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration). |
51-
|**Time drift detected** |Occurs when the UTC time of the sensor is not synchronized with Defender for IoT on the Azure portal.<br><br>
52-
In this case, configure a Network Time Protocol (NTP) server to synchronize the sensor in UTC time. This can be done through the sensor settings. |
51+
|**Time drift detected** |Occurs when the UTC time of the sensor is not synchronized with Defender for IoT on the Azure portal.<br><br>In this case, configure a Network Time Protocol (NTP) server to synchronize the sensor in UTC time.<br><br>For more information, see [Configure OT sensor settings from the Azure portal](configure-sensor-settings-portal.md#ntp). |
5352

5453
## Check system health
5554

articles/defender-for-iot/organizations/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Features released earlier than nine months ago are described in the [What's new
2626

2727
This version introduces a new troubleshooting test in the connectivity tool feature, specifically designed to identify time drift issues.
2828

29-
One common challenge when connecting sensors to Defender for IoT in the Azure portal arises from discrepancies in the sensor’s UTC time, which can lead to connectivity problems. To address this issue, we recommend that you configure a Network Time Protocol (NTP) server in the sensor settings.
29+
One common challenge when connecting sensors to Defender for IoT in the Azure portal arises from discrepancies in the sensor’s UTC time, which can lead to connectivity problems. To address this issue, we recommend that you configure a Network Time Protocol (NTP) server [in the sensor settings](configure-sensor-settings-portal.md#ntp).
3030

3131
## February 2024
3232

0 commit comments

Comments
 (0)