I know this thread is way stale, but by posting my experience here I hope to bring it back current and add my call for help.
I have been having the *exact* same problem since setting up my MOSS farm in early April. I've been running a WSS 3.0 single-server setup for right at a year now and have never had an issue like this, but then it doesn't use (or need) Kerberos. It has been my observation as well that the underlying reason might be a timeout issue. Just as nash says, once it occurs you can close the browser and immediately reopen it and everything is fine. I've had the problem correct itself before, though, just by leaving the browser alone then trying again later.
Interestingly, this problem also occurs with frustrating regularity when using SharePoint Designer 2007, and the fix is the same - close and reopen the application. SPD's error is "You do not have permission to do this operation", which apparently is the same message thrown by the Frontpage server extensions, because googling that message got a lot of results, none of which obviously were helpful. Once when I tried to just close and reopen the site without closing SPD, I got a slew of permission errors (with logon prompts) that I just ESCaped through, and the site opened in folder view where I could browse around and look into the subfolders, lists and libraries. I was still denied making any changes, though.
I normally use Firefox for all my browsing, and would like to report I haven't seen the issue in that browser, but MOSS doesn't render well outside of IE (tends to leave out all XmlHTTPRequest/AJAXy stuff) so I can't really use it for the day to day work I need to do. Also, I've tried sniffing the HTTP conversation with Fiddler but this breaks the communication completely (due to the proxy?) and connections always fail due to permissions. I use Vista and wanted to blame the problem on that, but I've seen it occur on XPSP2 so no luck there either.
It doesn't seem the problem is with MOSS per se, but with IIS and/or Kerboros and/or the browser. MOSS exposes a lot through web services, is there something hiding there to cause these errors? This is a maddening problem on so many levels, but primarily for me is because I feel the answer is just *right* there if someone with more experience in IIS permission intricacies would just heed the call and help out we poor souls.