As far as I am aware, MVC 5 comes with the new OWIN/ASP.NET Identity authentication bits. In the web.config on a new MVC 5 project, I actually note that the FormsAuthenticationModule is disabled
<system.webServer>
<modules>
<remove name="FormsAuthenticationModule" />
</modules>
In addition, there is a new file that is created in the App_Start folder called Startup.Auth.cs. Inside of this file is the definition for the CookieAuthenticationOptions (the new FormsAuthentication name) with a default login path of "/Account/Login"
public void ConfigureAuth(IAppBuilder app)
{
// Enable the application to use a cookie to store information for the signed in user
app.UseCookieAuthentication(new CookieAuthenticationOptions
{
AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie,
LoginPath = new PathString("/Account/Login")
});
Try changing that path to the correct path for your application. Or, you could not use the new ASP.NET identity bits and remove the lines in the web.config that remove the FormsAuthenticationModule.
If you are not using or wanting to use the new authentication options, remove the call to the ConfigureAuth() in the Startup.cs file at the root of your application and delete the above lines in the web.config which removes the FormsAuthenticationModule. This should reinstate the expected behavior (again, without knowing how much customization you have done to the default code).