Unable to Access OpenShift Intranet Routes from Windows Machine

Solution Verified - Updated -

Issue

Access to OpenShift routes is unavailable from a Windows machine, even though the console is reachable via curl from the bastion host.

Symptoms:

  • OpenShift console is accessible from the bastion host but not from a Windows machine.
  • Browser fails to load OpenShift routes.
  • Missing or incorrect DNS resolution for OpenShift routes on the Windows machine.

Possible Causes:

  • The Windows machine does not have proper DNS resolution for OpenShift routes.
  • Required hostnames are not mapped to their corresponding IP addresses.
  • Network policies or firewall rules are restricting access.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
  • 4
  • 3
  • Windows operating system
  • Bastion host with network access to the OpenShift cluster

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content