Troubleshooting Windows Clients

Please test these steps in order. If a step is completed successfully, please move to the next test.

Verify the client can resolve the API endpoint via DNS

  1. Open a windows command prompt
  2. Type nslookup click Enter
  3. Type the API endpoint apigwx-aws.qualcomm.com click Enter
  4. You should see a response with a list or Ips similar to below. nslookupWindows
  5. If no IP’s are returned: Reach out to your company DNS team to troubleshoot why apigwx-aws.qualcomm.com is not resolvable from your client. There is any issue with your clients DNS.

Verify the client can reach the API endpoint via PING

  1. Open a windows command prompt
  2. Type ping apigwx-aws.qualcomm.com
  3. You should see a response below with Packets Lost=0 pingWindows
  4. If you are seeing packets lost or packets not received. Reach out to your companies networking team to troubleshoot why apigwx-aws.qualcomm.com is not working via Ping.

Verify the client can reach the API endpoint via Tracert

  1. Open a windows command prompt
  2. Type tracert apigwx-aws.qualcomm.com
  3. When you run this command, you should see an initial message Tracing Route to *.cloudfront.net [IP Address]
  4. The trace route will show the internet route taken to reach the endpoint from #3. The example below is the expected response.
    • NOTE: It is normal to see some time outs. tracertWindows
  5. If there are any connection issues where the final hop does not reach the endpoint from #3 you have an issue with your client’s route to the apigwx-aws.qualcomm.com endpoint. Please contact your local IT with the above example showing your client is not routable to Qualcomm's endpoint apigwx-aws.qualcomm.com.