Testing network connectivity

You can use the Absolute Network Diagnostics Tool to test the network connectivity of your account's Windows devices to the Absolute Monitoring Center. Specifically, the tool tests whether Secure Endpoint Agent connections are blocked or otherwise interrupted by your network's proxies and firewalls. It can also detect man-in-the-middle (MITM) attacks.

Using the Network Diagnostics Tool

Run the Network Diagnostics Tool to ensure that a Windows device's Secure Endpoint Agent will have uninterrupted connectivity to the Absolute Monitoring Center.

To run the tool, you will need to enter the hostname of the Absolute Monitoring Center that your devices connect to. Use the following table to find your hostname:

If your Secure Endpoint Console URL is...	Enter hostname...
cc.absolute.com	resources.namequery.com
cc.us.absolute.com	resources.us.namequery.com

To use the tool:

Open a Command Prompt window as a user with administrator permissions.
Navigate to the DDSNdt.exe file that you extracted in the previous section.

To run the Network Diagnostics Tool, enter one of the following commands:
- To run the tool and save the log file to the default location, enter:
  Copy
```
DDSNdt.exe /server=<hostname>
```
  To find your hostname, refer to the table above.
  
  For example, if the URL of the Secure Endpoint Console is cc.absolute.com, enter:
  Copy
```
DDSNdt.exe /server=resources.namequery.com
```
- By default, the log file is saved in the working directory. To run the tool and save the log file to a location of your choosing, enter:
  Copy
```
DDSNdt.exe /server=<hostname> /log=<full path to desired directory>
```
  For example, if you want to save the log file to a folder named NDTLogFile on your C: drive, enter:
  Copy
```
DDSNdt.exe /server=<hostname> /log=c:\NDTLogFile
```
  The folder where you want to save the log file must exist on your device. If you want to use a new folder, you must create the folder first. Do not use special characters or spaces in the folder name.
- To automatically close the tool after it runs, enter:
  Copy
```
DDSNdt.exe /server=<hostname> /autoclose
```
  This option is recommended if you are using a batch file (.bat) to run the tool. If the option is omitted, a user must enter a keystroke to close the Command Prompt window.
- To view a help file showing the different options available for the tool, enter:
  Copy
```
DDSNdt.exe
```
  -or-
  Copy
```
DDSNdt.exe /help
```

When the Network Diagnostics Tool finishes testing your device's connection, it saves the log file either to the default location or to the location you specified.

Viewing the Network Diagnostics log file

To view the log file, navigate to the location on your device where the tool saved the log file and double-click the log file to open it.

HTTP status codes

The log file may contain one or more HTTP status codes. See the following table for more information about the status codes included in the log file.

Network Diagnostics Log File: Status Codes
Status Code	Description
200 OK	The request succeeded.
202 ACCEPTED	The request was accepted for processing, but the processing is not complete.
302 FOUND	The request resides temporarily under a different URL.
307 TEMPORARY REDIRECT	The request resides temporarily under a different URL.
401 UNAUTHORIZED	The request requires user authentication. The client needs to send the request with a suitable authorization header field.
403 FORBIDDEN	The server will not fulfill the request and it should not be repeated.
404 NOT FOUND	The server could not find the URL. The status does not indicate whether it is temporary or permanent.

HTTP error messages

If some requests fail, the log file may contain one or more HTTP error messages. For a complete list of HTTP error messages, refer to https://docs.microsoft.com/en-us/windows/desktop/winhttp/error-messages.

For details about additional error codes that may show in the log file, refer to the following table.

Network Diagnostics Log File: Errors
Error Code	Description
100100	Deep Packet inspection detected The agent call failed due to a certificate host name error.
100101	Deep Packet inspection detected The agent call failed due to a certificate validation error. The pin is missing from the pinset or the pin value is blank.
100103	Deep Packet inspection detected The agent call failed due to a certificate validation error. The public key retrieved from the server doesn't match the pinned version of the public key.
12019	Fallback port connection issue The connection failed. The fallback port may be closed. Check the port connection.
12029	Deep Packet inspection detected The agent call failed to connect to the server due to man-in-the-middle (MITM) detection. -or- Fallback port connection issue The connection failed. The fallback port may be closed. Check the port connection.
12030	Connection Error with the Server The connection with the server has been reset or terminated, or an incompatible SSL protocol was encountered.