Resolve ASP.NET SignalR Access

I’m running an ASP.NET-based chatbox that relies on SignalR. The JavaScript file that SignalR generates is physically present in the /Scripts folder on the server, yet browsers receive an “access denied” (401) response whenever they request it. Windows Authentication is enabled, and the site is intended to work both inside our network and for remote users who log in through the same mechanism.

I need someone to trace the root cause—whether it’s IIS permissions, web.config rules, SignalR endpoint mapping, or something else—and apply a clean, permanent fix. Once it’s resolved the script should load without errors and the chatbox must connect successfully for any authenticated user, regardless of where they are.

Please document the change you make so I can replicate it in staging and future deployments.
https://aptchat.coepdindia.com/signalr/negotiate?clientProtocol=2.1&connectionData=%5B%7B%22name%22%3A%22aptchatcontroller%22%7D%5D&_=1772088147884

Domain:https://aptchat.coepdindia.com/