Logon failure: No network provider accepted the given network path(1203) (code: PE029)

Modified on 2025-06-10 11:52:28 +0200

Wir überwachen eine SMB-Freigabe auf einem RedHat Server mit einem PRTG "Folder" Sensor. Ab und zu meldet der Sensor für mehrere Minuten folgenden Fehler: Logon failure: No network provider accepted the given network path(1203) (code: PE029)

Der PRTG-Server und der RedHat Server stehen im selben LAN. Auf dem PRTG-Server sind 215 Sensoren angelegt. Das Scan-Interval beträgt jeweils für ca. die Hälfte der Sensoren 1 min bzw. 5 min.

Was könnte diese Fehlermeldung verursachen? Wie können wir sie vermeiden?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hallo,

leider gibt es für den Fehler keine eindeutige einzelne Lösung. Es gibt aber verschiedene Dinge auf die man achten sollte:

Mit freundlichen Grüßen

May, 2011 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

Logon failure: No network provider accepted the given network path(1203) (code: PE029)

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.