Hayden,
It will make no sense for you to try and read and understand all of the cookie data. As I said, there are going to be maybe up to 10 or 12 of them, not just one. There is encrypted data in all those cookies. You cannot understand it unless you are a C++ and HTML programmer.
It is beyond our expertise (Ibrahim, Muhammad, Hakim). We have forwarded the details of this issue to our database administrator. He is one of the best in this nation. He will look it over. However, as I have said, I am not optimistic that it is a server or forum software issue. Usually these are related somehow to your own background utilities, anti-virus checkers, and related programs.
Did you locate and delete ALL of the TBN cookies, restart the browser and log back in?
You would be astonished at the hundreds of processes that are running all the time, and all the Windows OS modifications that get made via updates, and especially "automatic" updates. Many add-on programs get linked in, especially to browsers, without telling you.
Until we can duplicate it from one of our own three locations or 11 PC's, I am afraid we are just guessing. It may seem logical that we should be able to "see" what it happening on your system, but we cannot. The only action of the server is to query your system ask ask if a cookie is present, then if so, to read it.
Many "security" software programs will add all kinds of restrictions, such as not allowing "referral" to other cookies and so forth. This could be part of the issue. Also, someone else mentioned their same problem was solved by getting fully up to date with Windows updates. Did you do that?
Texasjohn (also claiming this issue) said he is running COMODO SAFE SURF, COMODO FIREWALL, AVAST antivirus -- one or all of which can alter cookie behavior. BTW, dozens and dozens of "utilities" cause problems like this.
Here is a blurb on the first "utility":
Comodo SafeSurf Browser Toolbar
The Comodo SafeSurf Toolbar protects against data theft, computer crashes and system damage by preventing most types of Buffer Overflow attacks. This type of attack occurs when a malicious program or script deliberately sends more data to a target applications memory buffer than the buffer can handle - which can be exploited to create a back door to the system though which a hacker can gain access. Comodo developed the SafeSurf Toolbar explicitly to protect end-users from these kinds of attacks whilst they browse the Internet. After installation, the program will monitor and protect the memory space of all applications that are running on your system and immediately block any buffer overflow attacks.
"Protect memory space" would/could mean dumping out of a script call that it felt was "suspicious". There may be ways to tweak the settings of Comodo, or to list "exceptions" that will not be affected by the "safe surf" protections.
"Comodo Safe Surf Toolbar - not safe"
At least one expert site has issued a warning about various problems with Comodo: "After testing the toolbar ASG has found that the comodo toolbar saves your search history. You must manually clear it every time on your own. There is no automatic feature that deletes it for you... ASG considers this toolbar not to be safe because of this issue. A toolbar that is made for security should not contain a security flaw."
It is surely possible that this is somehow in confilct with TBN cookies.
I believe that Comodo toolbar utility is still in a beta version, and often beta versions install with default parameters that are excessively conservative. In any event, we have no way to know how all of these and other programs may be interacting with TBN.
There are some very high end tools that could be used on your machine to look at the actual execution of code. But we do not have the support staff to walk users through using those kinds of utilities.
It is also possible that your pagefile size, or Internet cache size, could be causing this. When was the last time you cleared your cache?
It is also possible that if you are using a "satillite" service for Internet access, or even one of the cable systems, their "page caching" could cause issues like this.
Usually the next debug step would be for you to log in via safe mode and if the problem goes away, you need to disable or uninstalll of of those system utilities; add them back one by one until the problem "re-appears." Then you'll know the cause.
Unless quite a few more than 3 or 4 (out of 350,000) users have the problem, or until our sysadmin provides further insight, we have expended as much resources of personnel as we can to try and assist with this issue.
I will post here again if I have new info to report.
Hakim