Right now the internal web server listens to * - any incoming host communication. Try listening to "localhost" specifically. This might allow us to take advantage of the hotfix outlined here: http://support.microsoft.com/kb/939786/

It looks like the combination of the hotfix and us listening to localhost specifically will fix up the "Access Denied" issue. Try it out, see if the change affects functionality. If not, try to verify the access issue gets fixed. (Regardless, it's probably a good idea to be specific about the place we're listening, so if it works, leave it localhost.)