Banner Access: Authentication Fails and Local Network Access Permissions

Overview

This article provides temporary browser configuration steps to restore access to Banner Forms when authentication or form loading fails due to local network permission restrictions.

Screenshot of the "Authentication Failed: User denied local network access permission" block in the appnav-prod page.

 

 

 

 

 

 

 

 

Users encountering this issue may see Banner Forms fail to open, stall during launch, or return access-related errors with App Navigator. The workaround involves adjusting a browser security setting that controls how websites interact with local network resources.

The original workaround described below was intended as a temporary solution to restore access. If you previously implemented these steps, please follow the instructions in the next section to revert those changes now that Banner has been patched and the issue has been resolved.

User Instructions:

  • Try using a different browser, such as Mozilla Firefox.
  • Manually disable Local Network Access Checks via browser flags:
    • Google Chrome
      • Open Chrome.
      • Paste the following into the address bar:
        chrome://flags/#local-network-access-check
      • Locate Local Network Access Checks.
      • Change the setting to Disabled (not Default).
      • Restart Chrome.
    • Microsoft Edge:
      • Open Edge.
      • Paste the following into the address bar:
        edge://flags/#local-network-access-check
      • Locate Local Network Access Checks.
      • Change the setting to Disabled (not Default).
      • Restart Edge.

 

To restore Local Network Access Checks to default state:

  • Google Chrome:
    • Open Chrome.
    • Paste the following into the address bar:
      chrome://flags/#local-network-access-check
    • Locate Local Network Access Checks.
    • Change the setting to Default (not Disabled).
    • Restart Chrome.

Screenshot of the Chrome browser flags page, with Local Network Access Checks highlighted in yellow, and "Default" circled in red.

 

 

 

 

 

 

 

  • Microsoft Edge
    • Open Edge.
    • Paste the following into the address bar:
      edge://flags/#local-network-access-check
    • Locate Local Network Access Checks.
    • Change the setting to Default.
    • Restart Edge.

 

Banner Access Prompt (Expected Behavior)

The next time you log into Banner Production and open a Banner Form, your browser may prompt you to allow local network access. Click Allow. Your browser should remember this permission for future Banner sessions.

A screenshot of the Banner Access prompt, with text reading: appnav-prod.ec.umt.edu wants to - Look for and connect to any device on your local network" and the options to choose "Allow" or "Block."

 

 

 

 

 

 

 

 

If Banner Forms Still Do Not Open

While on the Banner App Navigator page:

Google Chrome

  1. Click the Site Settings (sliders) icon to the left of the URL.
  2. Locate Local network access.
  3. Toggle to the on position.
  4. If you do not get the expected result after reverting to the default settings, clear your browser cache and then retry.

Screenshot of Application Navigator page in Chrome browser, with Local network access feature toggled to "on"

 

 

 

 

 

 

 

 

 

 

 

Microsoft Edge

  1. Click the Lock icon to the left of the URL.
  2. Locate Local network access.
  3. Set to Allowed.
  4. If you do not get the expected result after reverting to the default settings, clear your browser cache and then retry.

 

Screenshot of Application Navigator page in Microsoft Edge browser, with "Local netowrk access" highlighted and a popup showing the option to check "Allowed"

 

 

 

 

 

 

 

 

 

 

 

Background

Chrome version 142 enabled a new default security control called Local Network Access Checks. This feature restricts browser access to internal/local network resources unless explicitly approved. Because Banner Forms and certain search components rely on local network calls, the feature blocked Banner Forms (App Navigator).

This issue was first observed in November 2025 and resurfaced following Chrome’s automatic updates. A permanent fix was implemented through Ellucian Banner updates delivered as part of the Q4 Banner releases and patches installed in Production at the end of January 2026.

 

Was this helpful?
0 reviews
Print Article