You're going to hate my answer but double and triple check the handlers entry.  If you've copied down to an IIS6 entry you'll need to look in the <httpHandlers> section instead of <handlers>  The reason I say this was someone else I know (who shall remain nameless but works for DNN corp) fell into that hole very recently.  An ASP.NET 404 handler for the linkclick url almost by definition has to mean that it can't find and run the handler.

Alright, finally swung back around to this issue.  I have made a discovery.

I went ahead and installed a clean install of DNN 5.6.1.  I tried to do exactly as I did before and got the same 404 error.   I messed around some more and instead of linking to a file I linked to a url and turned on the tracking.  This time LinkClick.aspx works just fine, I am able to track the link and go to the new page.

Therefore the error seems tied to linking to a file.

What I am doing exactly is;

•  going to the file manager creating a secure folder (non-db)
• setting the permissions so that "registered users" have download rights.
• putting a text module on a page.
• Typing some text, clicking either link or the document management icon in the RadTextEditor. 
• Selecting to link to a file.
• At this point I notice that the folder doesn't appear secure.
• If I just select the file and don't turn on tracking the link creates a url such as http://loclahost/portals/0/securetest/testpdf.pdf, which is obviously incorrect as secure files shouldn't be accessed directly via url.  If you click on this link you get a 404.
• If I turn tracking on, then I get a linkclick.aspx url with a fileticket. Clicking on this link results in a 404

Can anyone tell me how to get around this or confirm to me that this is going on and I am not crazy?
Thanks,
Stuart

---

Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com From Module Development to DNN Upgrades, your one stop DNN Shop