>>Presumably you set the decyrptionKey attribute to a fixed value?
>
>Yes, that is the purpose of dropping it in the Web.config. It boots up performance a little bit but I didn't think I would have had to benefit from that here.
>
>>As I understand it the querystring generated for the webresource.axd url is encrypted. If the encryptionKey on the server changes between the time this is done and the resource actually being requested then the decryption (and thus then request) will fail. Normally this should not be a problem since the time lapse between the two events is minimal (but might happen, for example, when a web crawler hits the site).
>
>Well, that seems to be a problem between local drive VS share located on another computer. Local drive will respond immediately and the key won't have the time to change. But, on a shared located on another computer, if additional milliseconds are to be in effect, that could have been the reason.

> But, if that is the case, that is a serious flaw in that version. In overall, the analysis I have completed is that when we will upscale to Windows Server 2008 OS, this will give us 64 bits, the ability to move up to .NET Framework 4.5 as well as using IIS 7, which all combined, will move us to much more recent technology and I think both issues I had are then resolved.
>
>>One obvious case where this would be essential is on a web farm - all servers would need the same key.
>
>Well, we will not be too far from that. Load balancing will kick in shortly so that might be a proactive step in the right direction.
>
>>That said I don't see how this is related to having files located on a share.....
>
>Me neither, but I built a local Web site, an exact copy of the other one, on drive C:, and it works immediately. Just checking to point to another location changed its reaction completely.
>
>Thanks for the feedback, it is always nice to exchange on those topics with experts on this site.

O don't think the key gets regenerated very often - only on web site updates, application pool recycling etc - so I wouldn't expect a few milliseconds to normally have that effect.

Expert :-} - you should see how much I struggle with ASP.NET sometimes :-}