This is possibly caused by logging off on a CNET page that requires you to be logged in to access. Let me know if this still occurs for you.

Thanks!
-Lee