Scenario:
I have created a WSS 3.0 website with all the bells and whistels when it comes to workflow, customized pages etc. Now the client requests that some of these lists be accessible to anonymous users so that they are able to submit some items and view others.
So, off I go and enable anonymous access via the central administration and then enable it on the specific site collection where the lists are kept (this all according to official and unofficial documentation).
Tests show that anonymous users are unable to access the main site, exactly what I want.
Problem:
When I access the list with anonymous access enabled, via an anonymous account; none of the styles show correctly, I can see and interact with the list data though.
So what went wrong?
Solution:
Well after much clicking, code checking, cursing and some nicotene I happened on the problem:
If you plan to enable anonymous access for a site collection, ensure that during the setup of the web application that you enable anonymous access first - not after the fact (this only works if you plan to allow anonymous read access to the entire site).
I suspect that when you create site collection in this web application extra code is added to the config files to allow anonymous read access to the '_layouts' and '_themes' folders that stores all stylesheet info.
So the solution is to rebuild the friggin site! Ah well, practice makes perfect I suppose :)