I understand the forbidden part if the url is changed, but I don't understand why that would be happening. If I type in the full url (including the _layouts part, this still happens.
I have done a bit of AAM editing, extending the web application to an intranet zone with the (logical) urlhttp://abc/ but my access was working successfully. My most recent changes were to play around with a couple of External
Content Types and external lists.
The user account I am working with is a Site Collection Admin.
What could have changed (or what could I have changed) to make something like this happen?
This 403 Forbidden issue usually occurs when a request from an authenticated user without local admin rights results in a failed read of the /BIN directory by the impersonating w3wp.exe (IIS worker process for ASP.NET) process.
This behavior is typically associated with lack of permissions to the temporary folder /BIN where ASP.Net assemblies are Just In Time (JIT) compiled.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.