It would appear that a local service does not start in time. Is this an issue on just one machine or several?
My initial thoughts were to point a finger at name resolution. Either the local WINS or DNS client is not ready early enough or the browse list hadn't built in time. If it's just one machine you may just have to scrub and rebuild.
Kent,
I can't see where the group cache would have a bearing on this. By simply delaying the logon, it works.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
