Troubleshooting tools

These tools can be used to investigate and resolve issues that occur on Access Gateway, Okta, applications, the network, and browsers.


Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

ping <destination>

Sample output:

root@Access Gateway ~]# ping
PING localhost ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=64 time=0.033 ms
. . . 
64 bytes from ( icmp_seq=5 ttl=64 time=0.048 ms
--- Access Gateway ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4479ms
rtt min/avg/max/mdev = 0.033/0.042/0.048/0.006 ms

In cases of no response from the target host, most implementations of ping display nothing, or periodically print notifications about timing out. Possible ping outputs indicating a problem include the following:

  • H, !N, or !P — host, network, or protocol unreachable

  • S — source route failed

  • T — return time in milliseconds or 1/4 meters-second (normally in telephone meters per and in traffic control milli per second)

  • F — fragmentation needed

  • U or !W — destination network/host unknown

  • I — source host is isolated

  • A — communication with destination network administratively prohibited

  • Z — communication with destination host administratively prohibited

  • Q — for this ToS, the destination network is unreachable

  • X — communication administratively prohibited

  • V — host precendence violation

  • C — precendence cutoff in effect

In case of error, the target host or an intermediate router sends back an ICMP error message, such as “host unreachable” or “TTL exceeded in transit.” In addition, these messages include the first eight bytes of the original message (in this case, the header of the ICMP echo request, including the quench value), so the ping utility can match responses to originating queries.

NS Lookup

nslookup is a network administration command-line tool available for many computer operating systems for querying the Domain Name System (DNS) to obtain domain name, IP address mapping, or any other specific DNS record.

nslookup [-option] [name | -] [server]

Please see this page for more details on available options.

Sample output:

[root@localhost ~]# nslookup

Non-authoritative answer:	canonical name =

Error:Here is sample output when nslookup fails to find the DNS record:
[root@localhost ~]# nslookup
** server can't find NXDOMAIN


The telnet command is used for interactive communication with another host using the TELNET protocol. It begins in command mode where it prints a telnet command prompt (telnet>).

telnet <host> <port>

Sample output of Successful Connection:

[root@localhost ~]# telnet 443
Connected to
Escape character is '^]'.
Connection closed by foreign host.`

Sample output of Failed Connection:

[root@localhost ~]# telnet 445
telnet: connect to address Connection refused

In the example above, host is listening on port 443, but not on port 445.

If telnet is not available on Windows, it can be enabled using these steps:

  1. Click Start → Control Panel.

  2. Click Programs and Features.

  3. Click Turn Windows features on or off.

  4. In the Windows Features dialog box, select the Telnet Client option.

  5. Click OK. The system installs the appropriate files. This will take a few seconds to a minute to complete.

The nc (or netcat) utility is used for many tasks involving TCP, UDP, or UNIX-domain sockets. It can open TCP connections, send UDP packets, listen on arbitrary TCP and UDP ports, do port scanning, and deal with both IPv4 and IPv6. Unlike telnet, nc scripts nicely and separates error messages into standard errors instead of sending them to standard output like telnet does.

Usage: nc [options] <host> <port>

Example: Similar to telnet, nc can also be used to validate whether a host is listening on a specified port.


Below are are example output of both successful and failed connections:

Successful connection:

[root@Access Gateway ~]# nc -v -z -w 1 443
Connection to 443 port [tcp/https] succeeded!

Failed Connection:

[root@Access Gateway ~]# nc -v -z -w 1 example.oag.infoo 445
nc: connect to port 445 (tcp) failed: Connection refused

nc is only available on Unix, Linux, and Mac operating systems.

Access Gateway Sample Header Application

The sample header application is bundled with Access Gateway and can be used to validate the state of the environment and identify issues. The tests below can be performed using the sample header application to identify the root cause of some issues.

No. Component to Validate Validation Steps


Connectivity with Okta

  1. Add/Edit an application in Access Gateway.

  2. Access Gateway will fail to create/save application if it fails to connect to Okta.


Okta API token

  1. Add/Edit an application in Access Gateway.

  2. Access Gateway will report an error if Okta API key is not active.


Okta attributes

  1. Add/Edit the sample header app in Access Gateway.

  2. Add the required attribute in the Attributes tab, and pass it to the header.

  3. Open the sample header app and validate the value of the attribute.


Access Gateway

  1. Open the sample header application.

  2. This should redirect you to Okta for authentication (if Okta session does not exist and policy is set to protect the app).

  3. Any discrepancy in application flow points to an issue in the environment.


Application in Okta

This can be tested in 2 different ways.

Application chiclet in Okta:

  1. Log in to Okta.

  2. Click the application chiclet.

  3. This should redirect you to the application. If it does not, there is an issue in the environment.

Application URL in Access Gateway:

  1. Log in to the Access Gateway Admin UI.

  2. Go to the Applications tab.

  3. Right-click the Goto app button.

  4. Click Copy link address if using Chrome or Firefox, Copy Link if using Safari, or Copy shortcut if using Internet Explorer.

  5. Paste the URL in the address bar, and press Enter.

  6. This should take you to Okta for authentication before proceeding to the application. If you are not directed to the application after authentication, there is an issue with the environment.


Application in Access Gateway

  1. Open the public URL configured in Access Gateway Admin UI for the application in a browser window.

  2. This should take you to Okta for authentication before proceeding to the application. If you are not directed to the application after authentication, there is an issue with the environment.