>Ok, I was able to find why Fiddler was not able to show the content. This is because, by default, it doesn't show anything under https. So, I activated that support. Now, I see that the request to the .axd page is 404. This works ok on the production environment where this is a local drive where there is no domain controller. So, at this time, to prepare the upcoming environment, I need to find what has to be configured so .axd page will be returned at 200 and work ok under a Web site that is configured as "A share located on another computer" under a domain controller.

I'd be surprised if the share was the problem. Bear in mind that WebResource.axd is not a physical file but created by an HTTP handler.

This might help : http://blogs.msdn.com/b/carloc/archive/2008/12/04/webresource-axd-or-scriptresource-axd-not-working.aspx

Also some have reported a problem caused by time differences on the production server:
http://stackoverflow.com/questions/1098548/axd-files-generate-a-404-error
http://stackoverflow.com/questions/4797435/scriptresource-axd-404-error-in-asp-net-4-application-webresource-works-fine-t