Remote Ops Transport Agent Name Servers

Summary

The article provides guidance on configuring Remote Ops (Hi-Track) Transport Agent Name Servers. It emphasizes that customers must use DNS host names (not IP addresses) for all four transfer servers due to planned disaster recovery failovers that will change the IP addresses. The article specifies HTTPS as the required protocol (port 443), confirms that dial-up and FTP are no longer supported, and provides authentication credentials for each server. For employees, it includes current internal and external IP addresses for reference only, with a clear warning that these addresses will change and should not be used for configuration. The overall message emphasizes DNS-based connectivity to ensure uninterrupted service during network changes.

Content

Question

What are the Remote Ops (Hi-Track) Transport Agent Name Servers?
How should I configure Remote Ops connectivity?

Environment

Remote Ops (Hi-Track) Monitor Agent
Remote Ops (Hi-Track) Service Processor (SVP) Agent
Remote Ops Agent

Answer

Remote Ops (Hi-Track) Site Agent - HTTPS Configuration

The Remote Ops (Hi-Track) System at the customer site must be configured to use HTTPS.

Important:

Dial-up is no longer supported

FTP is no longer supported (effective May 5, 2021, per Technical Bulletin A2018120301

HTTPS Configuration Requirements

Port 443 needs to be open to the following host names:

Host Name	Description
ushtinet01.hds.com	Remote Ops (Hi-Track) Transfer Server
ushtinet02.hds.com	Remote Ops (Hi-Track) Transfer Server
usdenhtinet01.hds.com	Remote Ops (Hi-Track) Transfer Server
usdenhtinet02.hds.com	Remote Ops (Hi-Track) Transfer Server

Critical Update: Always use DNS host names rather than IP addresses. Due to planned disaster recovery failovers, the IP addresses of all four transfer servers will change. Any static IP configurations will stop working after these changes.

To allow for redundancy, configure all 4 destinations.

HTTPS Authentication Parameters

Use the following parameters to set up HTTPS information in the Remote Ops (Hi-Track) site agent:

For ushtinet01.hds.com and ushtinet02.hds.com:
- User: ht_http_row
- Password: htpw0425
For usdenhtinet01.hds.com and usdenhtinet02.hds.com:
- User: ht_http_row
- Password: htRp$0925

Best Practice: Always use the DNS host names (e.g., ushtinet01.hds.com) rather than IP addresses for HTTPS connections. This ensures proper certificate validation and allows for seamless transition during IP address changes.

FTP Support Status

Support for FTP has been discontinued effective March 15, 2019, per Technical Bulletin A2018120301

To convert from FTP to HTTPS, please see How to Configure Remote Ops (Hi-Track) to Use HTTPS Instead of FTP

TLS Configuration

As of June 22, 2026, all Remote Ops Agent servers support TLS 1.2 and TLS 1.3, with the following ciphers:

TLS 1.3

TLS_AES_256_GCM_SHA384
TLS_AES_128_GCM_SHA256

TLS 1.2

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

Keywords: https://knowledge.hitachivantara.com/Knowledge/Support_Tools/Remote_Ops/Using_Remote_Ops/Remote_Ops_Transport_Agent_Name_Servers_and_IP's raexternalrequest